2021-11-04
00:29yuyichao_ has quit [Ping timeout: 480 seconds]
01:24kode54"works for me" seems to be the general point, and that it works for T2 Macs, and that they've never even tested M1
02:03X-Scale` has joined #asahi-dev
02:09X-Scale has quit [Ping timeout: 480 seconds]
03:36kov has quit [Quit: Coyote finally caught me]
03:59PhilippvK has joined #asahi-dev
04:02phiologe has quit [Ping timeout: 480 seconds]
04:09kode54I know that public contributions to pretty much any respectable project require that they work properly, not just for the submitter
04:10kode54when I saw that the patch included a function for getting mapping registers, I didn't realize it was a large switch block inside of a function that was also included in the patch
04:11kode54at least now if that person wishes to volunteer their hardware, you know you have someone who can test if T2 works
04:12kode54unfortunately, it doesn't look like any of that patch automates getting the board info from the ACPI tables, either
04:12kode54guess that's another thing someone will have to implement, if a T2 owner is willing to donate a dump of their ACPI tables
04:32PthariensFlame[m]I have a T2 model and would be willing to contribute, although I might have to be walked through some things.
05:46method_ has quit [Ping timeout: 480 seconds]
06:41Method has joined #asahi-dev
07:07bps2 has quit [Ping timeout: 480 seconds]
07:37useableporthole has quit [Remote host closed the connection]
08:13chadmedyeah, though idk how much slack is acceptable here given that its not really unique to linux that "works for me mate" isnt an acceptable QA test
08:14mazyou can always explain what is expected from a submission. they are of course free to ignore your suggestions, but you are also free to ignore them altogether in athat case.
08:19marcanchadmed: the thing is the corellium patch was meant for M1 but doesn't do any of the DT things it should be doing, so it's actually doing neither of the M1/DT nor the ACPI stuff it should be
08:19marcana proper patch ideally needs to implement both DT and ACPI support so it works on both platforms
08:23marcanbtw, does anyone know of a functional userspace ext4 implementation? It would be really convenient if the installer could poke around the linux rootfs, e.g. to deal with the firmware story
08:23marcanthe alternative is to have a firstboot thing or some firmware copy script that copies it from e.g. the ESP, but that's a bit more annoying since it needs distro integration to a greater extent
08:30marcanlooking at my normal rootfs (which should've been mkfs'ed last year) all the features are compatible with lwext4 as far as I can tell
08:44marcanand diskutil can create partitions without formatting and arbitrary GPT type GUIDs, so no issue there
09:21jacoxon has joined #asahi-dev
09:56kettenisi.e. it would see no free space, offer the user to use the existing Linux partition and wipe it?
09:56chadmedi assume it would just see an empty partition marked as a "Linux rootfs" with the correct GUID
09:57chadmedAnaconda can detect these and offer to automatically configure the rest of the filesystem automatically for you
09:58ketteniswell marcan is thinking about putting a filesystem there an pre-populate it with the wifi firmware
10:01chadmedwell that being said im not actually aware of any distros that offer arm64 installers like they do on the PC, usually you just extract a tarball of a rootfs and its up to the user (or in this case the asahi installer) to configure the rest of the system to boot and point a kernel to it
10:02chadmedso if we had the wifi firmware already dumped into the partition, youd just be adding whatever is in the tarball to /lib/firmware
10:04kettenisespecially the armbian model where you have different rootfs images for each board that is supported
10:04chadmeduntil someone has the bright idea of releasing a new standard that standardises all the standards :P
10:05chadmedyeah thats because those servers are usually equipped with ACPI and UEFI, so the existing amd64/PC installers work with very little modification
10:08chadmedtrue, but for the linux install experience to be "good" theyd have to boot from a live medium through the UEFI provided by u-boot and install... provided the distros release bootable arm live images that work without ACPI
10:10kettenisthere seems to be a little bit of an Arch bias here though, which I think uses the "untar rootfs" approach even on x86 isn't it?
10:10chadmedi think the benefit of supporting m1n1+uboot+edk2 is that once the rootfs is decompressed and configured (which we can make automatic via the asahi installer anyway), future updates and booting looks exactly like a PC to the end user
10:11jixkettenis: not sure if it supports untar rootfs on x86 but it's not the default way to install it
10:11jixkettenis: usually you boot from USB and then use pacstrap, then chroot into that and setup more stuff
10:12chadmednah the arch install is somewhat similar to gentoo with less manual intervention. theres one command to build the rootfs once youve configured your disk
10:13kettenisOn OpenBSD we use the same installer on all our architectures with jost some small quirks for each hardware platform
10:14chadmedthats the best way to do it imo, but im not sure you could convince the distros to rejig their arm tooling to support that on linux... yet...
10:14chadmednow that we have real arm workstations within reach of consumers that dont suck and arent $10,000 (looking at you ampere) they might be more willing to invest time in the process
10:17chadmedcan edk2 boot external media after its been chainloaded from u-boot? would we have to have an EFI executable that presents this as an option to the user?
10:18kettenisthat just works as long as they don't deliberately cripple their kernel config like RHEL does
10:19kettenisand yes, both edk2 and u-boot automatically boot the removable media path thingy from external media
10:19dottedmagCreating a small ext4 fs and stuffing all firmware into it would probably work, distro will only need to mount and symlink it.
10:23kettenishave a generic UEFI install option for Debian/Ubuntu/SuSE/OpenBSD and another option for the ALARM-based distro that marcan has proposed
10:42chadmedyeah i broadly agree. my one concern would be how we make this look sufficiently PC-like that even the most basic users will understand the paradigm
10:42chadmeddo we make a fake efi shim that tells them to mash F12 to boot from USB as a skeuomorph? do we let u-boot sort it out?
10:46marcan"proper installers" are great when distros have had a chance to do all the proper hardware enablement
10:47marcanproper installers won't work until everything is upstream and back downstream; I don't expect most people want to go that path for linux for at least a couple years
10:48kettenisI just commit stuff and within 24 hours Theo has built a new snapshot with it enabled ;)
10:48marcanand yeah, I think I'll dump the firmware into the ESP unconditionally so people can always rely on that being there
10:49phireI personally dislike "proper installers", I always try to install from a previous linux distro
10:51chadmedi havent used a gui installer in like 10 years, but the kinds of people we need to entice over are people who use gui installers...
10:52chadmeddespite not wanting to use it at all, i do think its a worthwhile thing to support. that said, its mostly out of our hands as marcan said. itll be a thing the distros have to sort out themselves.
10:52phireThat was an adventure, I had to install grub from windows, then get the arch iso booting as a loopback
10:53yuyichao_ has joined #asahi-dev
11:04kettenismarcan: so we need to transplant the "module-instance" property from the ADT into the device tree
11:06ketteniswe already add a "local-mac-address" property to the wifi pcie device node, so this isn't too difficult
11:06kettenisthe hard bit is to come up with a sensible property name and where to define the binding for it ;)
11:48maz has left #asahi-dev [Leaving]
11:49maz has joined #asahi-dev
12:33gabuscus has joined #asahi-dev
13:41jbowen has joined #asahi-dev
13:53X-Scale has joined #asahi-dev
13:57X-Scale` has quit [Ping timeout: 480 seconds]
14:00aleasto has joined #asahi-dev
14:08yuyichao_ has quit [Quit: Konversation terminated!]
14:27yuyichao has joined #asahi-dev
14:48minecrell has quit [Quit: Ping timeout (120 seconds)]
14:48minecrell has joined #asahi-dev
15:06yuyichao_ has joined #asahi-dev
15:10yuyichao has quit [Ping timeout: 480 seconds]
15:23yuyichao has joined #asahi-dev
15:27yuyichao_ has quit [Ping timeout: 480 seconds]
16:37___nick___ has joined #asahi-dev
16:41___nick___ has quit []
16:43___nick___ has joined #asahi-dev
16:43___nick___ has quit []
16:45___nick___ has joined #asahi-dev
17:11jbowen has quit [Ping timeout: 480 seconds]
18:52kov has joined #asahi-dev
18:58jbowen has joined #asahi-dev
19:38mnurz has joined #asahi-dev
19:39mnurz has left #asahi-dev [#asahi-dev]
19:52jbowen has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:08jacoxon has quit []
21:14jacoxon has joined #asahi-dev
21:26psykose has quit [Remote host closed the connection]
21:26psykose has joined #asahi-dev
21:37j_eyI think it's this https://github.com/torvalds/linux/blob/master/drivers/input/keyboard/applespi.c#L1455 would have to re-run to double check
21:38jacoxon has quit []
22:42j_eymarcan: getting some (minor) warnings in new m1n1 code https://paste.gg/p/anonymous/f26f9dd2d2214b7eae4a6e0f8622f3ed
22:51aleasto has quit [Quit: Konversation terminated!]
23:55richbridger has joined #asahi-dev