#
…

2021-12-01

00:48yuyichao has joined #asahi
01:03chamomile has joined #asahi
01:29leah has quit [Quit: WeeChat 3.3]
01:36leah has joined #asahi
02:00DragoonAethis has quit [Quit: hej-hej!]
02:00DragoonAethis has joined #asahi
02:46darkapex4 has joined #asahi
02:51darkapex3 has quit [Ping timeout: 480 seconds]
03:06phiologe has joined #asahi
03:10PhilippvK has quit [Ping timeout: 480 seconds]
04:04kov has quit [Quit: Coyote finally caught me]
04:13bgb_ has quit [Ping timeout: 480 seconds]
04:15marvin24_ has joined #asahi
04:19marvin24 has quit [Ping timeout: 480 seconds]
04:39bgb_ has joined #asahi
04:42chamomile has quit [Ping timeout: 480 seconds]
04:48bgb_ has quit [Ping timeout: 480 seconds]
04:54Graypup_ has quit [Quit: meow]
04:56Graypup_ has joined #asahi
04:59Graypup_ has quit []
04:59Graypup_ has joined #asahi
05:16bgb_ has joined #asahi
05:20user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:21user982492 has joined #asahi
05:23chamomile has joined #asahi
05:24user982492 has quit []
05:26bgb_ has quit [Ping timeout: 480 seconds]
05:29palmer_ has joined #asahi
05:29palmer_ has quit [Remote host closed the connection]
05:42leah has quit [Quit: WeeChat 3.3]
05:50leah has joined #asahi
05:52bgb_ has joined #asahi
05:53user982492 has joined #asahi
05:59user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:00bgb_ has quit [Ping timeout: 480 seconds]
06:04chamomile has quit [Ping timeout: 480 seconds]
06:04kov has joined #asahi
06:26user982492 has joined #asahi
06:33sailorek1234 has joined #asahi
06:49d0p1__ has joined #asahi
06:53Dcow has joined #asahi
06:56Dcow_ has quit [Ping timeout: 480 seconds]
07:21d0p1__ has quit [Ping timeout: 480 seconds]
07:27bgb_ has joined #asahi
07:29VinDuv has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
07:29VinDuv has joined #asahi
07:31cth451_desktop has quit [Quit: Quitting]
07:33cth451_desktop has joined #asahi
07:34bgb has joined #asahi
07:39bgb_ has quit [Ping timeout: 480 seconds]
07:45nepeat has quit [Remote host closed the connection]
07:46nepeat has joined #asahi
08:06bingoChecker has joined #asahi
08:09Dcow_ has joined #asahi
08:11Dcow has quit [Ping timeout: 480 seconds]
08:30hendry2 has joined #asahi
08:31loki_val has joined #asahi
08:35crabbedhaloablut has quit [Ping timeout: 480 seconds]
08:37hendry1 has quit [Ping timeout: 480 seconds]
08:46aleasto has joined #asahi
09:02the_lanetly_052 has joined #asahi
09:03the_lanetly_052 has quit [Remote host closed the connection]
09:04the_lanetly_052 has joined #asahi
09:09the_lanetly_052 has quit [Quit: Leaving]
09:36the_lanetly_052 has joined #asahi
09:43user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:02kenzie has quit [Quit: The Lounge - https://thelounge.chat]
10:03kenzie has joined #asahi
11:23chamomile has joined #asahi
11:31chamomile has quit [Ping timeout: 480 seconds]
12:07bingoChecker has quit [Ping timeout: 480 seconds]
12:42darkapex has joined #asahi
12:46darkapex4 has quit [Ping timeout: 480 seconds]
12:48Gaspare has joined #asahi
12:51yuyichao has quit [Ping timeout: 480 seconds]
12:53bingoChecker has joined #asahi
13:18yuyichao has joined #asahi
13:21chamomile has joined #asahi
13:29chamomile has quit [Ping timeout: 480 seconds]
14:04dsrt^ has quit [Remote host closed the connection]
14:21sailorek1234 has quit []
14:25mpstesting u-boot apple-m1-m1n1-nvme branch, usb keyboard works, detects usb storage and tries to boot but then it hangs and after some minutes reset machine and repeat
14:25mpsdoesn't show it detected nvme device
14:26mpstesting boot with efi formated and set usb device
14:27sailorek1234 has joined #asahi
14:57kettenisare you using firmware from macos 12.0?
15:00mpskettenis: firmware? which and where it is needed for u-boot? first time hear about this
15:03mpsI upgraded machine to macos 12.0.x (x is 1 iirc)
15:06Darksecond4 has joined #asahi
15:07kettenisthat may explain why nvme isn't working for you
15:10mpsdoes that means I should downgrade to 11.0
15:11sailorek1234 has quit []
15:12Darksecond has quit [Ping timeout: 480 seconds]
15:12Darksecond4 is now known as Darksecond
15:19Gaspare has quit [Quit: Gaspare]
15:20kettenisno, it means I should fix the code
15:26aleasto has quit [Ping timeout: 480 seconds]
15:35aleasto has joined #asahi
15:36hspak has quit [Ping timeout: 480 seconds]
15:43NightRaven[m] has joined #asahi
15:43NightRaven[m]I have a question does anyone know when arch will be done for m1 ?
16:07opticroncommon question and depends on your personal definition of "done"
16:08opticronalyssa has been running an unaccelerated desktop env for a while now (GPU support is not yet done)
16:11garyodernichts[m] has joined #asahi
16:27wouter has joined #asahi
16:51chamomile has joined #asahi
17:03woutershould the m1n1 thing allow dual-booting my M1 mini, or is that something I shouldn't be playing with just yet?
17:04chamomile has quit [Ping timeout: 480 seconds]
17:05j_eywouter: dual booting macOS and linux? you'll just do that through 1TR
17:05j_eypower on, and then hold the power button
17:05wouterj_ey: yeah, that
17:05wouteroh, right, I can do that I guess
17:05wouter(I just repartitioned the internal storage that way)
17:05sventhat’ll very likely be the only way dual booting will be possible
17:06wouterfair enough
17:06wouter(this m1 mini isn't mine, it's work's, but I thought I'd give "start porting debian-installer to m1 mac" a go...)
17:06wouterand yes, I know it's way too early for release :)
17:07svenas long youre
17:07sven*as long as you’re comfortable building downstream kernels with patches you can already somewhat use Linux :)
17:07kettenisthere really shouldn't be a need to "port" debian-installer
17:08svenI think jannau has a nice collection for arch
17:08mazthe debian installer works out of the box.
17:08mazall it needs is a kernel that knows about the M1.
17:09wouterwell, it'd need a module for the boot loader
17:09wouterand perhaps some other things that are different on the m1 (if any)
17:09wouterI guess "porting" isn't the right word
17:10wouterbut I have done d-i work in the past, for m68k and nbd-related things, so I have a fairly good idea how it works ;-)
17:10mazwouter: Debian knows about EFI, and u-boot provides just enough EFI for debian to be happy.
17:11woutermaz: oh, asahi uses u-boot? yeah that does make things easier then
17:11wouterI thought it used m1n1 as a custom boot loader or something
17:12j_eywouter: m1n1 boots u-boot
17:12wouteroh, okay, right
17:12j_ey(as an option)
17:12wouterwell, really, then all that needs is another flavour for m1 I guess
17:16bingoChecker has quit [Quit: Leaving]
17:18Gaspare has joined #asahi
17:24dottedmagwouter: Also some firmware files will need to be copied: https://twitter.com/marcan42/status/1456189751510257667
17:26the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:34nickiminjaj has joined #asahi
17:38d0p1__ has joined #asahi
17:44fgfhmnrtry4r4t[m] has joined #asahi
18:04jakou[m] has joined #asahi
18:26chamomile has joined #asahi
18:50nickiminjaj has quit [Quit: leaving]
18:52marcanwouter: I don't really expect distro installers to need any porting beyond adding some bits once we have them (e.g. some kind of bundled touchbard for the M1 13" MBP, or else you get no function keys...)
18:53marcanmostly just the firmware thing
18:53marcanthe bootloader should be GRUB or whatever, u-boot provides EFI services
18:53marcanso just like any other GRUB machine from a distro's point of view
18:53marcan(or whatever EFI bootloader the distro wants to use)
18:55marcanwe provide m1n1+u-boot which will be required to boot the distro installers in the first place (which users will install using a script from macOS/1TR); I don't expect distros to attempt to roll their own from scratch replacement for that (trust me, you don't want to)
18:55marcanonce that's installed it'll just be an EFI boot which should work with USB disks for distro installers and such
18:55marcanor you could preinstall a netinstall image or what have you
18:56marcanI also want to offer distro images pre-configured in our installer so people can just dump those in in one shot; I need to get around to writing a spec for those...
18:59marcanfor the firmware, I also need to write a spec for that, but my current thinking is something like <EFI PART>/asahi/firmware.tar.gz; distros would be expected to untar that into /lib/firmware, and keep track of the mtime so they can do it again if it changes (e.g. the user ran a bootloader/firmware upgrade)
19:00marcanthere are some subtleties to work out around multi-boot; my current thinking is we should recommend that users do multi-distro-boot by using completely separate OS containers from the machine's point of view, which lets you use the native boot picker, and means each distro gets its own EFI partition (which is important because we don't have a good way to do efivars, so no configurable EFI boot menu, ...
19:00marcan... just the default boot)
19:00marcanbarring changes to distros, maybe we can have u-boot mark only the currently booted EFI part with the real GUID, so distros don't get confused by multiple EFI parts
19:02marcanand then it might be nice if we could get some feedback on the currently installed kernel version, e.g. dumping a file in <EFI PART>/asahi/kernel.ver or something. that could be used by our bootloader installer/updater to filter the firmware versions we offer, so users don't accidentally install firmware that's too new for their kernel
19:06kettenismarcan: for u-boot we need to annotate a few nodes in the device tree with a "u-boot,dm-pre-reloc" proprty
19:06marcandm-pre-reloc?
19:07j_eymarcan: kernel.ver being macos version or linux version?
19:07marcanlinux version
19:07kettenisthis is needed to make sure the power domains needed for the serial console can be found in the early "pre-relocation" phase of u-boot
19:07marcan(openbsd can pick whatever version it claims to support the same stuff as :p)
19:08j_eymarcan: was about to mention openbsd :p
19:08marcanI assume openbsd will at least try to follow the same "blessed" firmware versions we pick for linux, otherwise things will get really confusing :-)
19:09ketteniswill be fine
19:09kettenisif we store the firmware on the ESP our firmware update tool should be able to grab it from there
19:10marcanthe tag *could* be macos version, but it's possible they release updates that don't change the ABI (they already have, dcp.py works across a few releases at least) so I feel it makes more sense to have the flexibility to decide what works and what doesn't at the installer
19:10marcanand just track linux kernel release support
19:10marcanand it's not just firmware; it's also potentially a devicetree thing (though we will try not to screw up compat there)
19:12marcankettenis: re power domains, sure
19:12marcanI was actually thinking about how to maintain our out of tree devicetrees
19:13marcanideally I want to automate syncing with linux somehow, while still being able to have patches on top
19:13kettenisu-boot solves this by having *-u-boot.dtsi files that get included automatically
19:13marcanah, sure, but I mean not just that, also just extracting the DTs out
19:13marcanthough there was already a tree for that IIRC
19:14kettenisalternatively, for these u-boot,dm-pre-reloc properties we could write code that add them
19:15kettenisbut that is probably a bigger mainenance burden
19:15marcanfwiw the serial console should be powered on boot, m1n1 certainly uses it and won't be shutting it down
19:15marcan(that would break earlycon too)
19:17marcanso given that DT tree tracks all official kernel releases, I'm thinking I can have some minor scripting to transfer changes from one or more of our asahi branches on top of that, and then we can have some includes/overlays if we need something extra
19:18kettenisyup, the problem is that u-boot sees the power-domain property, tries to find a driver, fails and then ends up without a serial console
19:18marcanah, I see
19:20marcanand yeah, I think we can just have some makefile voodoo to overlay those properties on top
19:21marcancould even do it in code in m1n1 though, it wouldn't be too hard to pick out the serial0 alias and walk the power domain reference adding that
19:21marcanthat should work for all machines, right?
19:21nabaiste^ has joined #asahi
19:21marcanwe already do a bunch of walking for things like disabling devices/DARTs on certain platforms, so...
19:22kettenisalso need the syscon node that sits on top of the power domains
19:22marcanyeah, but that'd just walking up the tree
19:22kettenisbut yes, that's what I was thinking of
19:22marcanremind me if I don't get to it, shouldn't be a big deal to add
19:22marcangoing to get some sleep now :)
19:23marcanand hopefully catch up on reviews and send arnd_ some pulls tomorrow
19:23marcanI've had... a few days full of external IRQs
20:14aleasto has quit [Remote host closed the connection]
20:23bgb_ has joined #asahi
20:27bgb has quit [Ping timeout: 480 seconds]
21:56kettenisthe changes I just pushed to my apple-m1-m1n1-nvme u-boot branch may fix nvme with the macos 12 firmware
22:03mpskettenis: thanks, I will test it tomorrow, too late is here and I'm tired now and going to bed
22:30Gaspare has quit [Quit: Gaspare]
22:54pg12_ has quit [Ping timeout: 480 seconds]
23:34pg12_ has joined #asahi
…