#
…

2022-07-12

00:06Catyre has joined #asahi-dev
00:14Catyre has quit [Ping timeout: 480 seconds]
00:15Catyre has joined #asahi-dev
00:30Catyre has quit [Remote host closed the connection]
00:33Catyre has joined #asahi-dev
00:58millenialhacker has joined #asahi-dev
01:05Catyre has quit [Remote host closed the connection]
01:06Catyre has joined #asahi-dev
01:06millenialhacker has quit [Ping timeout: 480 seconds]
01:14Catyre has quit [Ping timeout: 480 seconds]
01:16bard[m] has joined #asahi-dev
01:20Catyre has joined #asahi-dev
01:39Catyre has quit [Remote host closed the connection]
01:39Catyre has joined #asahi-dev
01:43chadmedmarcan: does asahi-fwextract do anything different to the extant update-vendorfw script that would necessitate an ebuild?
01:45chadmedor would i be better off just writing a little openrc service that runs update-vendorfw on boot
01:48Catyre has quit [Ping timeout: 480 seconds]
02:04Catyre has joined #asahi-dev
02:41derzahl has quit [Remote host closed the connection]
02:42WindowPain has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
02:53Catyre has quit [Remote host closed the connection]
02:54millenialhacker has joined #asahi-dev
02:56Catyre has joined #asahi-dev
03:00PhilippvK has joined #asahi-dev
03:00WindowPain has joined #asahi-dev
03:01skipwich_ has quit []
03:02skipwich has joined #asahi-dev
03:02millenialhacker has quit [Ping timeout: 480 seconds]
03:03phiologe has quit [Ping timeout: 480 seconds]
03:30kov has quit [Quit: Coyote finally caught me]
03:31marcanthey are different things
03:32marcanasahi-fwextract isn't really intended to keep existing in the long term
03:32marcanonce we extract all firmwares it will not longer be needed
03:32marcan*no longer
03:33marcanjannau: m1n1 should already reset NVMe on shutdown, why would we need to do it twice?
03:33marcanmaybe udelay(1) is not enough?
03:34marcanoh wait, I bet I know
03:34marcanit's called ANS now, not ANS2.
03:35marcanso the m1n1 reset does not work
03:35marcansince it was by name
03:36marcanchadmed: update-vendorfw *already* runs on boot
03:36marcanthat one just copies firmwares
03:36marcanasahi-fwextract *recreates* the source file for that copy, it has actual logic
03:37marcanupdate-vendorfw puts the firmwares in the right place after an external entity (installer) updates them, e.g. due to a stub upgrade
03:38marcanasahi-fwextract just does what the installer does to extract them in the first place, because the installer isn't complete yet and I didn't want to have to tell people to go back to the installer just for this
03:47millenialhacker has joined #asahi-dev
03:55millenialhacker has quit [Ping timeout: 480 seconds]
04:07marcanok, boots now and the trackpad works but... the first time setup stuff failed? got me stuck in an empty login screen, heh
04:14marcanohh calamares needs a rebuild
04:19marcanruh roh, different issue now
04:19marcanu-boot explodes with USB devices connected
04:19marcanscanning bus usb@502280000 for devices... Device NOT ready
04:19marcan Request Sense returned 02 3A 00
04:19marcan"Synchronous Abort" handler, esr 0x96000005
04:19marcanelr: 000000000001d5d0 lr : 0000000000028440 (reloc)
04:20marcanah wait, this is because it's a storage device that's not ready? bug then I guess (I have a multithing connected that includes card readers)
04:20marcankettenis: might want to look at this ^
04:20marcanprobably a null deref or something when USB storage devices are connected and not ready
04:24chadmedmarcan: yea ik it runs on boot on asahi but i havent gotten around to setting up an openrc service to do so on gentoo just yet so i probably should for when these fw upgrades roll out
04:25nicolas17earlier I saw a merge request in KDE and recognized chadmed's username... before even reading the description which clearly mentioned asahi ^^
04:26chadmedheh yeah ive got a few weeks off at the moment so i thought id start paying off the enormous tech debt i owe
04:27chadmedi hacked basic DT support into kinfocenter last night but its pretty ugly so idk if itll fly upstream
04:27chadmedits no uglier than the dmidecode stuff i guess but...
04:27nicolas17hm slighly concerning that we don't even compile that file in GitLab CI
04:28nicolas17oh, I guess we do as part of android
04:28chadmedit works on x86 machines, kinfocenter shows my macbook pro's dmi information
04:28nicolas17sorry I meant solid's cpuinfo_arm.cpp
04:29chadmedoh right
04:30chadmedwell it complained about a syntax error i made but maybe that was the android pass
04:35nicolas17hm did it?
04:36chadmedyeah i had a . instead of a , in the array somehow despite the fact that i built the branch to test it, and it told me that i ruined the code quality
04:37nicolas17ah looks like cppcheck caught it (because it tests all ifdef combinations)
04:37chadmedah righto
04:37nicolas17we do need to add a proper ARM build then...
04:48Catyre has quit [Remote host closed the connection]
04:48Catyre has joined #asahi-dev
04:55marcanmaking another kernel...
04:56marcanI *think* with the m1n1 changes and other things this will finally work on M2 (with proper keyboard detection even)
04:57Catyre has quit [Ping timeout: 480 seconds]
05:01marcansven: bluetooth works on the funky revision in the M2pro :)
05:01Catyre has joined #asahi-dev
05:02nicolas17soon apple will release the larger chip and make all this confusing again (M2 Pro chip or M2 MacBook Pro?)
05:04marcanjannau: I think the trackpad in practice works because the init is slow enough that by the time it requests the firmware the root FS is mounted
05:04sveni wonder if you’d notice if we sent the wrong calibration data though
05:04marcan(because it takes ~1 second for the trackpad to init)
05:04marcansven: *shrug*
05:05svenfair enough :D
05:05marcanthis release is for the news cycle, "we have M2 support oh yeah and bluetooth", it's gated behind expert mode for a reason :p
05:05svenGuess that really just leaves T2
05:06nicolas17do ARM MacBook Pro/Air still have the 'fake' trackpad click that they simulate with haptic feedback?
05:07marcan(that's handled by default in firmware, but can be taken over by the OS)
05:10marcanbuilding new asahi images, hopefully this works because I really don't have time to spend on this the rest of the day...
05:16Catyre has quit [Remote host closed the connection]
05:17nicolas17 has quit [Quit: Konversation terminated!]
05:21marcanimages uploading, alx.sh/dev should work in a few minutes
05:21marcangoing to grab lunch...
05:25Catyre has joined #asahi-dev
05:31doggkruse has quit [Ping timeout: 480 seconds]
05:31doggkruse has joined #asahi-dev
05:36jannaumarcan: trackpad was consistently broken with the rootfs on usb and modules but no firmware inside the initramfs
05:37jannaubluetooth was very unstable on my m2 and detected only 1/2 of the devices
05:52jannauinstaller worked on the m2 macbook pro but touchpad is not working on first boot
05:54doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:58jannautouchpad worked 3 out of 5 boots including the first boot
06:01jannauinstall finished on the mac studio as well
06:05Catyre has quit [Remote host closed the connection]
06:08svenunstable Bluetooth sounds a bit like wrong calibration data
06:11jannauI see lots of "unknow advertising packet type:" and devices missing from the scan which show on my x86 notebook
06:13jannauminor annoyance with the dev installer: it uses "asahi" as package repo. this prevents us from providing updates but I guess it necessary if we want to promote dev to stable at some point
06:14sventhe unknown packet type thing should be harmelsa
06:14jannaumarcan: both the desktop and minimal os images work
06:14sven*harmless
06:14sveni also see that when scanning
06:14sventhe missing devices is strange though
06:17millenialhacker has joined #asahi-dev
06:22minecrell9 has joined #asahi-dev
06:24mrkajetanp has joined #asahi-dev
06:25skrzyp has quit [Remote host closed the connection]
06:25dabaum|2er0 has joined #asahi-dev
06:25skrzyp has joined #asahi-dev
06:25millenialhacker has quit [Ping timeout: 480 seconds]
06:25the_lanetly_052__ has joined #asahi-dev
06:37mps has quit [Ping timeout: 480 seconds]
06:53marcanjannau: the package repo thing is intentional
06:53marcanfor that reason
06:53marcanand yeah, trackpad does not work on first/some boots
06:53marcan"good enough for experimental"
06:54marcanit works, it proves M2 works, bugs happen, whatever
06:54marcanok, then, please test on M1 and friends :)
06:55marcansven: soundflora* tested her AirPods and said they had periodic glitches, but that could be any number of things
06:55marcanI did test some speakers myself and they sounded fine but I wasn't playing super close attention
06:55marcananyway, all this is acceptable for an experimental-gated platform
06:55svenI’ve tested with my Bose headphones and they were fine on M1 fwiw
06:55svenmaybe I should test with my AirPods as well
06:56marcan(note: this was on M2)
06:56svenwouldnt surprise me if apple made Broadcom add some, uh, surprise features for AirPods
06:56marcanoh they definitely do weird magic for airpods, but I don't think the controller would care about that unless the software tells it to
06:57marcan(e.g. the magic pairing etc)
06:57marcanpretty sure apple writes this firmware btw, or part of it
06:57marcan(based on whatever broadcom provides)
06:57marcanit's got tons of AWDL/etc stuff in it
06:57marcan(the AirDrop stuff)
06:57svenmaybe that explains why the ipc interface is so cursed
06:58sventhey had to start with Broadcom’s mess and instead if cleaning it up just added more hacks on top
06:58marcanyeah, see, I think Apple wrote 100% of the macOS driver these days, for wifi
06:58marcanand I guarantee the reason for that was that broadcom's reference code is a massive cursed mess
06:58marcan(you've seen the android thing, right?)
06:58marcanbut they're not quite at the point of writing their own firmware yet
06:59sventhat out-of-tree android broadcom driver?
06:59svenyeah, it's, uh, great
06:59marcanI think at least ever since Skywalk Apple just have a fully bespoke, IOKit/C++ macOS brcmfmac driver
06:59marcanpretty sure they used broadcom reference code before, but no longer
07:00sveninteresting
07:06svenhm, had some trouble to get the airpods to connect here (but that's common without apple magic) but sounds seems to be fine
07:23MajorBiscuit has joined #asahi-dev
07:49the_lanetly_052___ has joined #asahi-dev
07:55the_lanetly_052__ has quit [Ping timeout: 480 seconds]
08:04millenialhacker has joined #asahi-dev
08:11the_lanetly_052 has joined #asahi-dev
08:12millenialhacker has quit [Ping timeout: 480 seconds]
08:14firefox317 has joined #asahi-dev
08:16firefox317marcan: i tested a system update (pacman -Syu) with asahi-dev packages on a m1 air, and got the following crash in dmesg: https://pastebin.com/b5gX0Wre
08:17the_lanetly_052___ has quit [Ping timeout: 480 seconds]
08:17svenbluetooth firmware is missing and that's "only" a WARN_ON so the system shouldn't die after that
08:17svenbut let me see what causes that WARN
08:19firefox317sven: oh yeah i see, I thought doing a pacman -Syu with asahi-dev would cause the firmware to install somehow, but I guess that is incorrect
08:21firefox317sven: The system is not crashing tho, its just the bluetooth driver, the rest still works okay
08:21sveni think i just forgot to add a call pci_free_irq_vectors which causes that warn_on
08:22sventhe bluetooth driver also doesn't crash
08:22svenit just doesn't load
08:22kettenismarcan: the USB code in u-boot isn't great
08:23kettenisbut I'm not sure I'm the one to improve it...
08:23firefox317Ah interesting that a WARN_ON causes such a stracktrace to be printed, but yeah I see whats happening
08:23marcanthe firmware does get installed with a pacman upgrade
08:24firefox317hmm, maybe just a reboot from the terminal caused it to not properly shutdown or something
08:24marcanpaste a ls -al /boot/efi/asahi /boot/efi/vendorfw
08:27marcanlooks like the update didn't work, do you have the `asahi-meta` package installed?
08:29firefox317aha, that one was not installed, not sure why I did not have that package. I think I did a regular install when the first beta came out
08:29marcanyou probably uninstalled a dependency at some point and accidentally uninstalled the meta in the process
08:30firefox317could be yeah, lets try a reboot and see if it works :)
08:30firefox317 has quit [Quit: Page closed]
08:31firefox317 has joined #asahi-dev
08:32marcan(either that or you installed *before* the public announcement, since those meta packages were a very last minute addition)
08:33firefox317yeah I was playing with asahi before the public release, so might have been that. It found the firmware now :)
08:35marcanif you have the desktop install, also do asahi-desktop-meta
08:35marcanthat will pull in all the other randomness to make it just work
08:36firefox317Ah thanks, I was just about to ask that indeed, because I saw that the bluetooth.service was not enabled, which I guess that package does xd
08:36marcanyup, and also pulls in the KDE support stuff
08:36marcanthe minimal install as usual is "roll it yourself" for everything not specific to asahi
08:38firefox317 has quit [Quit: Page closed]
08:39firefox317 has joined #asahi-dev
08:43firefox317fwiw installing that package did not actually enable the bluetooth service, but that might have been something on my side again.. I will just manually enable it :)
08:43firefox317_ has joined #asahi-dev
08:43firefox317 has quit []
08:45marcanah, installing it wouldn't
08:45marcanupgrading it would
08:45marcanthat was intentional
08:45marcanit is upgraded separately when building images
08:46marcan*enabled separately
08:46marcanso I only made it enable it specifically on upgrade from v1 to v2, for existing users
08:47firefox317_okay, that makes sense :) sound from the bluetooth JBL speaker sounds good!
08:50mps has joined #asahi-dev
08:54chadmedok there we go bt is working now on gentoo
08:54chadmedupdated m1n1 and got the bluetooth firmware out of macos
09:05derzahl has joined #asahi-dev
09:06chadmedmy crappy little taotronics buds sound surprisingly good all things considered
09:06chadmednowhere near as good as the built in speakers do but yknow, good enough
09:13kettenismarcan, jannau: should we still reset ANS/ANS2 from U-Boot as well even if m1n1 is now fixed?
09:18marcanI don't think so, because if ANS2 has been put into quiesced mode instead, that would probably break it instead
09:38marcanwhen we get the handoff from iBoot it's in hibernate mode with the reset already applied (or some dance that puts it into an equivalent state), so I think we should keep the reset the responsibility of the shutting down party, since we know it's not something that works every time indiscriminately
09:38marcanand then that keeps the same ABI
09:39marcanhowever we should still do the message+CPU wakeup (which u-boot already does), since that seems to be a reliable way of bringing ASCs up regardless of whether they are in hib or quiesce mode, and that's good (macOS can't handle that, it has to be told in the ADT what the current state is)
09:44the_lanetly_052__ has joined #asahi-dev
09:50the_lanetly_052 has quit [Ping timeout: 480 seconds]
09:59mps_ has joined #asahi-dev
10:01mps has quit [Ping timeout: 480 seconds]
10:04millenialhacker has joined #asahi-dev
10:08dottedmagmarcan: is pointing out typos useful at this stage of draft, or you're going to go through it anyway and correct these?
10:08marcanI'm too tired to find typos, so yeah, please make a list
10:09marcanneed to pack for a flight...
10:10mps_ has quit [Remote host closed the connection]
10:10mps has joined #asahi-dev
10:12millenialhacker has quit [Ping timeout: 480 seconds]
10:12chadmedwhats the go upstream with exposing stuff like serial numbers and the like in the devicetree? there used to be docs on it but all of it seems to have vanished
10:12chadmeddid it become unacceptable to do that?
10:13firefox317_ has quit [Remote host closed the connection]
10:13chadmedi know the rasperry pi firmware inserts /serial-number into the fdt and it seems to have been the canonical way of doing that in 2015 or so
10:18mps has quit [Ping timeout: 480 seconds]
10:20dottedmagmarcan: Checked the whole text, only one typo spotted: "We’ve decide to take the plunge"
10:20marcanfixed, thanks!
10:21marcanchadmed: I don't see how it's any different from DMI, which also exposes serial numbers. was it ever bad?
10:21marcanMAC addresses also count as unique IDs and those certainly go in the DT
10:21dottedmagmarcan: wouldn't it be useful to have a link to a page with current hardware support status?
10:21marcanwe don't have a canonical one, I'd make one but I'm out of time, I just need to get this out...
10:22chadmedyeah ive added it to m1n1 in my local branch already and its working nicely, but i want it to play nice with upstream software so i wanna know where in the DT to put that sorta thing
10:23marcanoh, I guess someone made it then :)
10:23marcanneeds to be updated though
10:24kettenischadmed: looks like that got list somehow with the move of some stuff into the device tree specification and dt-schema
10:24_jannau_marcan: USB-A ports on all mac studio models have the same firmware problem as the m1 max front ports
10:24kettenisu-boot will still set the property if a serial# environment variable exists
10:25marcan_jannau_: ah, right, forgot about those
10:25marcan_jannau_: fixed
10:25chadmedkettenis: ive got m1n1 grabbing it from the ADT and putting it at /serial-number currently, kinfocenter happily picks it up with my DT support changes
10:25chadmedwould it make more sense to somehow pass it to u-boot another way and let u-boot do it?
10:27kettenisno, I think letting m1n1 do this is fine
10:28the_lanetly_052__ has quit [Remote host closed the connection]
10:28Catyre has joined #asahi-dev
10:30_jannau_marcan: "never break backwards with older firmware" misses compatibility
10:31marcanfixed, thanks
10:33j`eymarcan: cool post!
10:35_jannau_marcan: you could mention in the second last DCP paragraph the this changes allows to turn the display off and on
10:36marcanah, yes!
10:38marcan_jannau_: done
10:44marcanoddly enough, this trip is going to be the first time *I* will be using Asahi as a daily driver, since I'm only bringing Macs
10:44marcanwe'll see how that goes
10:45marcancurrently installing the proper release on my M1Pro (what I've been using as a build environment grew out of a manual install and isn't very kosher)
10:47chadmedfor how far along we are its honestly surprisingly useable
10:48chadmedif we had gamma correction for blue light filtering at night id never feel the need to boot back into macos again
10:48chadmedand of course as i say that the alsa preallocation thing comes back :/
10:50marcanif I have free time (big, big if) I might start messing around with your audio stuff
10:50marcanduring the trip, I mean
10:50marcanotherwise, after that
10:51j`eybig.IF
10:51dottedmagchadmed: Don't Wayland compositors have it? Or do they punt to DRI gamma calls (that are obviously not available yet)?
10:51dottedmag*some Wayland
10:51marcanI think most night shift stuff expects to be able to tweak gamma tables directly
10:51chadmedkwin (the only one worth using ;)) relies on gamma LUTs from CRTCs
10:52chadmedthis seems to be the case even in xorg nowadays too unfortunately
10:52dottedmagMessing with gammas is probably not going to work well once CMS protocol lands in Wayland and compositors will start to take care about it.
10:53marcanthe only Asahi machine I've been using with regularity is oddly enough the iMac, and that one has been pretty janky but it's the worst case (big screen, small CPU, and I mostly use it to preview youtube streams so the software rendering really shows there)
10:53dottedmagBut that's in future anyway.
10:53marcan(using in the desktop sense)
10:53marcanthough I see the Mac Studio becoming my storage server in the near future
10:54marcanconsidering buying 2 10Gb Mac Minis and turning it into a proper cluster... but I might wait for the M2 Mac Mini to see how that goes
10:54marcanwell, storage and build server of course
10:54chadmedive been trying to look for a "dumb" thunderbolt drive cage that only exposes a bunch of disks so i can eventually just use dmraid but theyre all like $3000 and have crap implementations of hardware raid in them
10:54mazmarcan: I'm halfway there too. need to move the backups over to the Studio.
10:55marcanchadmed: I want USB3 ones for flexibility (don't really care about perf for spinning rust), and there are a few, but they all seem to have pretty bad performance even by USB3 standards
10:55marcanand questionable behavior on hotplug of the bays
10:56mazBTW, if anyone has recommendations for a good USB-SATA enclosure that would take 4 3.5 HDs, I'm all ears.
10:56marcanokay... I see we're all in the same boat here.
10:56marcanfor what it's worth, I'm starting to lean towards "bunch of single-drive cases" and hubs... I think that's the only thing that's guaranteed not to screw over other drives when one dies, and not to bottleneck as long as the hub is kosher...
10:56marcanit won't be pretty but...
10:57chadmedthe usb ones all look so dodgy which is why ive been avoiding them, im already sus enough about mechanical disks without having to worry about the interface i connect them to as well
10:57dottedmagmarcan: nothing a duct tape or 3d-printed cage to keep them apart for better ventilation can't fix
10:57marcanif I decide to go thunderbolt, that would have to be DIY
10:57marcansome of those cheap reference TB3 bridge boards (I have one, it works), known good SATA controller
10:57marcandottedmag: exactly, and I *do* have a 3D printer
10:57chadmedegpu enclosure -> pcie sata controller -> 4U disk shelf
10:58chadmedmodern problems require modern solutions
10:58marcanalso, I could just buy a bare SATA cage with SFF connectors and DIY the USB backend behind it, it would be prettier and give the same result
10:58marcanand then it would be upgradable to thunderbolt
10:58marcando I actully put making this into a DIY board on my endless project list?
10:58jluthra has quit [Ping timeout: 480 seconds]
10:58marcan(i.e. SFF connector, pile of USB3 SATA bridges, hub, all on one board)
10:58marcan... screw it, it goes on.
10:58marcanwhether it'll ever get popped off, who knows
10:59chadmedi actually did think about attempting that, but fabricobbling together a tb4 to pcie interface doesnt sound like the easiest thing heh
10:59marcanI'm thinking USB
10:59marcanfor TB4-pcie you want those intel things
11:00marcannote: does not provide 12V, you need to jury rig that on if you need it (it's meant for like NVMe drives and such that don't)
11:00marcan$150 is not that bad for the TB3 world
11:00chadmedoh wow thats exactly what i imagined in my head
11:01marcanI have one, it totally works
11:01marcanit's some intel reference board
11:01chadmedonly 50 bucks for me too
11:01chadmedgotta love living so close to the supply chains
11:01marcanwait 50?
11:02marcanyou sure that's not one of the accessories only?
11:02chadmedoh nvm yeah i hadnt selected the board in the options
11:03chadmed225 is still good compared to the $3000 or so that lacie et al ask for here
11:03marcanyup, exactly
11:03marcanand then you plug in your favorite HBA
11:03chadmedyep and i can just stuff it all into a custom unit
11:04marcanTBH since I want 3 of them, if I'm going this route (hi sven, thunderbolt when? :D) I might just go for cheap known-good multi-SATA boards. it's either that or LSI SAS2008, everything else is suspect.
11:05chadmedyeah im just gonna grab whatever 6+ port sata controller i can get and use software raid since you cant really get "real" hw raid cards for reasonable money anymore
11:05chadmed(ones with big juicy caps)
11:05marcanSAS2008 is widely available, but I always use them in HBA mode anyway
11:05marcanthey are still nice and perform well (plug: https://github.com/marcan/lsirec)
11:05marcanbut possibly overkill
11:06marcanI think these days random SATA controllers are good enough, as long as you check for benchmarks
11:06marcanin particular... I've had bad experiences with older JMicron
11:07chadmedthat lsi card is cheaper than a generic asmedia sata card from a local computer hardware retailer
11:07chadmedand id prefer the sff connectors anyway so i can use a real disk shelf or something
11:07marcanlook for IBM M1015
11:08marcanand yeah, the nice thing is these can all do the fancy SAS stuff, enclosures, etc
11:08marcanjust make sure you crossflash a known good IT firmware on
11:08marcanMegaRAID firmware is terrible
11:09sventhunderbolt :<
11:09svenonce I have that I can finally daily drive asahi :D
11:09chadmedis there finally an interface sven hates more than usb?
11:09marcanI wonder if by then the new iMac Pro will be out... that *could* become my main machine
11:10marcanchadmed: I mean he's dealing with bluetooth right now
11:10marcanwhich I've always maintained is USB, but worse
11:10marcanthough that was before USB3/Type C
11:10marcanI think they're sort of tied again now
11:10svenBluetooth was reasonable-ish because I could ignore all the low level crap
11:12svenand thunderbolt is so annoying because it’s part of the entire usb mess
11:13svenI have a rough idea how it works but I can’t really bring it up from Python/m1n1
11:13the_lanetly_052 has joined #asahi-dev
11:15svenso I’ll have to untangle ATC and how the linux thunderbolt and typec subsystem work at the same time and make sure I don’t break dwc3 at the same time
11:15Catyre has quit [Remote host closed the connection]
11:16marcan_jannau_: can you make sure that github comment I keep linking has the latest kernel/u-boot package links? I think what we have in the repo now is what will ship
11:16svenBluetooth was fun compared to that: just implement that cursed ipc and hook into hci_recv and _send_frame :D
11:16marcan(unless something terrible happens)
11:22Catyre has joined #asahi-dev
11:25kettenissomeone should do a cheap NVMe-oF enclosure ;)
11:26kettenismarcan: is there time to get some U-Boot/OpenBSD stuff in that report?
11:27marcanif you write it up and I can just paste it in :)
11:29marcanyeah, I don't think you need to touch that
11:30jannauwould it make sense to copy the files to a separate place so the post doesn't break when we do updates
11:37minecrell9 has quit []
11:38minecrell has joined #asahi-dev
12:13kov has joined #asahi-dev
12:18millenialhacker has joined #asahi-dev
12:20the_lanetly_052 has quit [Ping timeout: 480 seconds]
12:26millenialhacker has quit [Ping timeout: 480 seconds]
12:28mps has joined #asahi-dev
12:34jluthra has joined #asahi-dev
12:35marcankettenis: merged (and slightly edited)
12:51kettenislooks good; thanks
13:50Catyre_ has joined #asahi-dev
13:56Catyre has quit [Ping timeout: 480 seconds]
14:12commandoline has joined #asahi-dev
14:17nicolas17 has joined #asahi-dev
14:49Gaspare has joined #asahi-dev
14:49doggkruse has joined #asahi-dev
14:56zzywysmthere's an 8-bay version too
15:03marcanlooks like that has 2x ASM1062 in it
15:04zzywysmis that bad? i use one for my home server
15:04marcanit's... suboptimal
15:04marcanprobably won't matter for HDDs, but still
15:05marcan(~400MB/s ceiling, vs ~550 for an LSI, with an SSD)
15:08svenhuh, is m2 support not included in the normal Mac is release or did my MacBook not update all the way?
15:08sven*macos release
15:08sven(ofc it enabled autocorrect with that update again *sigh*)
15:10marcansven: it is not
15:11zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:11marcanare you asking because the installer won't let you pick 12.4 on a non-m2 mac?
15:11marcan(even in expert mode)
15:11marcanbecause yes, it won't, for this reason
15:11doggkruse_ has joined #asahi-dev
15:11marcanm2 12.4 is a super funky special version
15:11svenim asking because I need a BlueTool with m2 support to see which calibration data it wants :D
15:11doggkruse has quit [Ping timeout: 480 seconds]
15:12svenI guess I can just grab it from the ipsw
15:12marcanis it in the ramdisk?
15:12marcanI guess it would be
15:12sventhat's what I hope
15:12marcanor just give me a sec :p
15:12svensure :D
15:12zzywysm has joined #asahi-dev
15:16Catyre has joined #asahi-dev
15:22Catyre_ has quit [Ping timeout: 480 seconds]
15:23svenwhat's the m2 chip again? 4387 c2? c3?
15:25svenah, no 43*78* b3 for the pro
15:26alyssa has joined #asahi-dev
15:26alyssare "Night Light" with DCP,
15:26svenlooks like it also wants the beamforming calibration data
15:26alyssathere are 3 colour transforms in KMS. pre-gamma, colour transform matrix, and post-gamma.
15:27alyssaThe middle one -- applying a linear (or affine? I forget) transformation to every pixel -- is easy with DCP
15:28alyssaI have a patch hardcoding such a matrix into my kernel for personal a11y reasons... would be easy to pipe into userspace properly if we had a consumer.
15:29alyssaIt's less obvious how to set gamma curves, and at least GNOME's Night Light is based on gamma (not a linear transform)
15:31alyssachadmed: ^^
15:31nicolas17sven: it's weird, there were 3 builds of 12.4, the original was M1-only, then they released one with M1 and M2, two days later they released another that is M2-only
15:32mps has quit [Quit: Lost terminal]
15:33svenyup, b3 also needs that beamforming blob. that probably explains why bluetooth was unstable on the M2
15:35nicolas17also remember BuildManifest.plist can be downloaded from the same directory as the .ipsw, which is handy to quickly know contents and supported macs :)
15:44mps has joined #asahi-dev
15:46millenialhacker has joined #asahi-dev
15:54millenialhacker has quit [Ping timeout: 480 seconds]
15:54Catyre has quit [Remote host closed the connection]
15:55Catyre has joined #asahi-dev
16:00Gaspare has quit [Quit: Gaspare]
16:04Catyre has quit [Ping timeout: 480 seconds]
16:35Catyre has joined #asahi-dev
16:41MajorBiscuit has quit [Ping timeout: 480 seconds]
16:53Catyre has quit [Remote host closed the connection]
16:54Catyre has joined #asahi-dev
16:59mps has quit [Remote host closed the connection]
17:05millenialhacker has joined #asahi-dev
17:08Gaspare has joined #asahi-dev
17:13millenialhacker has quit [Ping timeout: 480 seconds]
17:27svenall these "Unknown advertising packet type:" seem to more or less line up with "Handoff All Your Privacy – A Review of Apple’s Bluetooth Low Energy Continuity Protocol" https://petsymposium.org/2019/files/papers/issue4/popets-2019-0057.pdf
17:29mps has joined #asahi-dev
17:30doggkruse_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:36nicolas17sven: if company ID is Apple (004C) yep
17:37sveni mean.. I looked at the bt trace and matched up the format to that paper
17:37svenit's more than just the company id
17:39nicolas17well there's more sub-types on every version and they won't be documented there yet, but they're still all vaguely related
17:47derzahl has quit [Remote host closed the connection]
17:53derzahl has joined #asahi-dev
18:25Catyre_ has joined #asahi-dev
18:31Catyre has quit [Ping timeout: 480 seconds]
18:33Catyre_ has quit [Remote host closed the connection]
18:34Catyre has joined #asahi-dev
18:37doggkruse has joined #asahi-dev
18:37trouter has quit [Quit: ZNC 1.8.2 - https://znc.in]
18:40trouter has joined #asahi-dev
18:42Catyre has quit [Ping timeout: 480 seconds]
18:49Catyre has joined #asahi-dev
19:37Catyre has quit [Remote host closed the connection]
19:38Catyre has joined #asahi-dev
19:40derzahl has quit [Ping timeout: 480 seconds]
19:42doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:46Catyre has quit [Ping timeout: 480 seconds]
19:47Catyre has joined #asahi-dev
20:03Catyre has quit [Remote host closed the connection]
20:04Catyre has joined #asahi-dev
20:12Catyre has quit [Ping timeout: 480 seconds]
20:18roxfan has quit [Remote host closed the connection]
20:21roxfan has joined #asahi-dev
20:27Catyre has joined #asahi-dev
20:34derzahl has joined #asahi-dev
20:42Catyre has quit [Remote host closed the connection]
20:51doggkruse has joined #asahi-dev
20:52jluthra has quit [Remote host closed the connection]
20:52jluthra has joined #asahi-dev
20:54millenialhacker has joined #asahi-dev
21:02millenialhacker has quit [Ping timeout: 480 seconds]
21:11whistlingoat[m] has joined #asahi-dev
21:30Catyre has joined #asahi-dev
21:39Catyre has quit [Ping timeout: 480 seconds]
21:57Catyre has joined #asahi-dev
22:12boardwalk has quit [Quit: Ping timeout (120 seconds)]
22:12Catyre has quit [Remote host closed the connection]
22:13boardwalk has joined #asahi-dev
22:38nicolas17oh, in case you missed it macOS 12.5 release candidate is out (public release in 1 week probably)
22:45Gaspare has quit [Quit: Gaspare]
22:47millenialhacker has joined #asahi-dev
22:53Catyre has joined #asahi-dev
22:54derzahlah has joined #asahi-dev
22:55millenialhacker has quit [Ping timeout: 480 seconds]
23:02Catyre has quit [Ping timeout: 480 seconds]
23:10derzahlah has quit [Remote host closed the connection]
23:13Catyre has joined #asahi-dev
23:14Gaspare has joined #asahi-dev
23:53nicolas17 has quit [Ping timeout: 480 seconds]
…