ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
nsklaus_ has joined #asahi-dev
nsklaus has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
phire has quit [Remote host closed the connection]
phire has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
derzahl has joined #asahi-dev
chengsun has joined #asahi-dev
chengsun_ has quit [Ping timeout: 480 seconds]
AProgrammer has joined #asahi-dev
<AProgrammer> Was able to install Asahi although its not immediately obvious to me how to build the kernel as I see no .config in the /boot directory?
<AProgrammer> That is - build the kernel targeting AARCH_APPLE or whatever the correct platform name for M1 is - I'm not quite sure
<tpw_rules> /proc/config.gz is in it
ditlood has joined #asahi-dev
AProgrammer has quit [Remote host closed the connection]
chengsun_ has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
chengsun has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
chengsun_ has quit [Ping timeout: 480 seconds]
chengsun_ has joined #asahi-dev
nuh^ has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
chengsun has joined #asahi-dev
chengsun_ has quit [Ping timeout: 480 seconds]
chengsun has quit [Read error: Network is unreachable]
chengsun has joined #asahi-dev
chengsun has quit [Quit: Quit]
chengsun has joined #asahi-dev
nuh^ has quit [Remote host closed the connection]
chengsun_ has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
saina has joined #asahi-dev
saina has quit []
dsrt^ has joined #asahi-dev
phiologe has joined #asahi-dev
PhilippvK has quit [Ping timeout: 480 seconds]
chengsun_ has quit [Ping timeout: 480 seconds]
chengsun has joined #asahi-dev
nicolas17 has quit [Quit: Konversation terminated!]
millenialhacker has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
chengsun has joined #asahi-dev
dsrt^ has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
chengsun_ has joined #asahi-dev
dsrt^ has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
chengsun_ has quit [Read error: Connection reset by peer]
chengsun has joined #asahi-dev
chengsun_ has joined #asahi-dev
chengsun has quit [Ping timeout: 480 seconds]
dsrt^ has quit [Ping timeout: 480 seconds]
mps has quit [Quit: leaving]
mps has joined #asahi-dev
millenialhacker has joined #asahi-dev
doggkruse has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
<chadmed> hmph neofetch is going to *suck* to make work properly with big.LITTLE systems
<chadmed> its just an enormous shell script so it will require some pretty annoying changes to how it enumerates the cpus
<tpw_rules> i thought as long as the picture shows up that's all that matters :)
<chadmed> heh true but "(10) @ 2.064 GHz" looks stupid and is wrong to boot
<chadmed> but its going to be too painful to fix so im not gonna bother
<chadmed> kf5solid and lscpu were easy
<chadmed> the style rules for neofetch make it almost impossible to efficiently support proper identification of aarch64 parts anyway
<chadmed> youre not allowed to pipe anything and youre meant to avoid external utilities altogether...
<chadmed> so it would be an absolute mess of case/esac and evil awk regex matching
millenialhacker has joined #asahi-dev
<JTL> If neofetch is the largest thing you need to worry about I'd consider that a small problem :P
<chadmed> well yeah i dont really care at this point, if the patches i sent to util-linux and kde get merged then thats good enough for me
<chadmed> i kind of want to hack minimal DT support into kinfocenter's main view but i feel like it would be messy and not well received
<chadmed> currently it only supports getting information from DMI
millenialhacker has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi-dev
gladiac is now known as Guest4717
Guest4717 has quit [Read error: Connection reset by peer]
gladiac has joined #asahi-dev
gladiac has quit [Read error: No route to host]
gladiac has joined #asahi-dev
mps has quit [Remote host closed the connection]
mps has joined #asahi-dev
millenialhacker has joined #asahi-dev
mps_ has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
mps has quit [Ping timeout: 480 seconds]
bisko has joined #asahi-dev
the_lanetly_052 has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi-dev
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
the_lanetly_052 has quit [Remote host closed the connection]
the_lanetly_052 has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
<marcan> asahi branch pushed, now based on 5.19-rc5 and with preliminary t8112 support
<marcan> seems to work on my t6000, hopefully there are no regressions. the reboot notifier stuff got merged with significant changes, so that series is now dropped and macsmc is ported over.
<marcan> povik: minor fixup to macaudio too
<marcan> err... USB broke?
<marcan> so much for no regressions
<j`ey> $ git rev-list 88084a3df167..asahi/asahi | wc -l
<j`ey> 170
<j`ey> how does USB break?
<marcan> just plays dead
<j`ey> :(
<marcan> I probably broke old DART
bisko has joined #asahi-dev
<marcan> wait now I'm confused, it worked
<marcan> it works now... I'm lost
<jannau> it works with the usb device plugged already before boot
<jannau> ?
<marcan> it's always been plugged in
<povik> marcan: did you pick up upstream admac?
<povik> not sure if it's in 5.19-rc5
* povik is checking
<marcan> don't think so
<povik> ah not yet there
<povik> that's good actually
<povik> the binding changed
<jannau> usb-reset was one thing which could have explained working/broken usb in some situations
<povik> (it's overdue that we update the binding, but as i understand it marcan you have a flight to catch :p)
<marcan> it was erroring out on controller init, but it seems just that one time?
<marcan> yeah er, I'm going to try to get a -dev everything release out today and if nothing is broken promote to prod after the flight
<marcan> well, if nothing regresses anyway
<sven> i've seen that when messing with the usb3 mess but I hope you haven't merged that yet :D
<marcan> nope :p
<marcan> bluetooth neither, but I can add that if you want
<sven> ideally someone would test bluetooth on a m1 max/pro/ultra first
<sven> but other than that it should be fine
<marcan> I'll do that, I always test on m1pro by default (it's my build machine)
<jannau> I thought it was known broken with the newer wifi/bt modules
<sven> _older_ actually :D
<sven> it crashes the T2 wifi/bt module after exchanging a few HCI commands
<sven> M1 pro/max/ultra should work since that's what R did their reverse engineering with
<marcan> okay, let's go for it. where's the branch?
<marcan> (just pushed -asahi1 packages to asahi-dev if anyone wants to play along with the testing, but let's add BT and call it -asahi2)
<marcan> also I need to clean up the t8112 devtrees a bit... and add the air speculatively :)
<sven> https://github.com/AsahiLinux/linux/tree/bluetooth-wip, you'll need to add the board-type for the t6xxx ones though since I based it on the latest RC
<sven> and you probably also want my latest m1n1 PR which byte-swaps the BD address because of course it has to be the other byte order than mac addresses
<marcan> right
<sven> anything else would be too easy, can't have that *sigh*
<marcan> I remember that from the wiimote days...
wuhoipok[m] has joined #asahi-dev
<jannau> marcan: m2 u-boot patches are here: https://lore.kernel.org/u-boot/20220630220617.23530-1-j@jannau.net/
<marcan> thanks!
<marcan> punting on the keyboard for now, we need to investigate that
<jannau> 5.19.0-rc5-asahi-1-1-ARCH boots on the mac studio and usb works
<marcan> (hint: if anyone wants to throw the MTP firmware into ghidra and see if there's any sane way to shut it down such that it spits out the HID descriptors again on the next startup, that would be most helpful)
<marcan> yay!
<sven> oh, right, the wiimotes were Bluetooth as well
<marcan> jannau: what keyboard layout do you have, btw?
<marcan> on M2
<jannau> german, was the only option for release day delivery
kov has joined #asahi-dev
<marcan> jannau: can you pull m1n1 and run experiments/mtp.py and paste the output? (you need to chainload)
<marcan> just want to see if there is something that looks like keyboard countrycode with a different mapping
<marcan> (bbiab, quick dinner)
<marcan> hmmm
<marcan> [MTP][stm] 00000000 14 01
<marcan> [MTP][stm] 00000000 14 02
<marcan> ... who wants to bet 00 = ANSI, 01 = ISO, 02 = JIS
<marcan> I suspected something like that
<marcan> I might just go with that, hope I guessed right. saves me from having a nasty translation table in m1n1...
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<kettenis> I should put the m2 patches on the u-boot asahi branch now that I reviewed them ;)
bisko has joined #asahi-dev
joske has joined #asahi-dev
<joske> marcan: I'm getting: drivers/iommu/apple-dart.c:1268:79: error: macro "DART_TCR" requires 2 arguments, but only 1 given
<marcan> oh, I think that's with PM_SLEEP
<marcan> I forgot I missed that
dsrt^ has joined #asahi-dev
<kettenis> marcan: pushed the m2 patches onto the u-boot asahi branch in case that helps
<marcan> it does! thanks!
<kettenis> the branch is up-to-date with u-boot master, which means it is pretty much u-boot 2022.07 which is supposed to be released today
<kettenis> not on that branch are:
<kettenis> 1. the nvme shutdown patch (you really need to send that one upstream)
<kettenis> 2. jannau's patch to pick the paired ESP
<j`ey> marcan: will we need APPLE_RTKIT_HELPER for m1 machines?
bisko has quit [Ping timeout: 480 seconds]
<_jannau_> j`ey: maybe, not for the currently supported HW
<j`ey> ok thanks
<marcan> don't think so
bisko has joined #asahi-dev
MajorBiscuit has quit [Quit: WeeChat 3.5]
<kettenis> that reminds me; I did look at the mtp/dockchannel diff over the weekend
<kettenis> so APPLE_RTKIT_HELPER is just a driver that brings up RTKit and processes log messages on the "standard" endpoints?
MajorBiscuit has joined #asahi-dev
dsrt^ has quit [Ping timeout: 480 seconds]
bisko has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi-dev
bisko has joined #asahi-dev
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<marcan> yes
<marcan> I suspect I will need some MTP<->RTKit cooperation at some point for suspend/resume
<marcan> but for now this works
<marcan> the problem is handoff to linux
<marcan> for keyboard only dockchannel is trivial, you can pretty much hardcode an init message and start getting HID reports
<marcan> though ideally you'd process the init messages and look for the right interface
nsklaus has joined #asahi-dev
nsklaus__ has joined #asahi-dev
nsklaus_ has quit [Read error: Connection reset by peer]
dsrt^ has joined #asahi-dev
<kettenis> since the boot picker uses the keyboard/touchpad, there must be a way to reinitialize
<_jannau_> the bootpicker reboots
<chadmed> how does that work for booting into paired recovery tough
<chadmed> it doesnt reboot if you do that
Gaspare has joined #asahi-dev
<chadmed> or is the boot picker an app inside the paired recovery
nsklaus has quit [Read error: Connection reset by peer]
<_jannau_> yes, the boot picker is the initial app of the paired recovery
<kettenis> ah, ok
joske has quit [Remote host closed the connection]
joske has joined #asahi-dev
millenialhacker has joined #asahi-dev
Gaspare has quit [Quit: Gaspare]
joske has quit [Remote host closed the connection]
joske has joined #asahi-dev
Gaspare has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
Gaspare has quit [Quit: Gaspare]
<marcan> kettenis: do not underestimate just how shitty apple firmware designs can be :p
<marcan> this isn't new
<j`ey> reseting seems to have been a problem since day 1
Gaspare has joined #asahi-dev
<kettenis> u-boot 2022.07 was released so I rebased the u-boot asahi branch once more to pick up the Makefile changes that drops -rc6
joske has quit [Remote host closed the connection]
Gaspare has quit [Quit: Gaspare]
dsrt^ has quit [Ping timeout: 480 seconds]
dsrt^ has joined #asahi-dev
Gaspare has joined #asahi-dev
Catyre has joined #asahi-dev
millenialhacker has joined #asahi-dev
balrog has joined #asahi-dev
Gaspare has quit [Quit: Gaspare]
dsrt^ has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
dsrt^ has joined #asahi-dev
dsrt^ has quit [Remote host closed the connection]
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Catyre has quit [Remote host closed the connection]
balrog has quit [Ping timeout: 480 seconds]
Gaspare has joined #asahi-dev
Catyre has joined #asahi-dev
balrog has joined #asahi-dev
millenialhacker has joined #asahi-dev
mps_ is now known as mps
saina has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
saina has quit []
doggkruse has joined #asahi-dev
Gaspare has quit [Quit: Gaspare]
c10l has quit [Quit: Bye o/]
mps_ has joined #asahi-dev
mps has quit [Ping timeout: 480 seconds]
<marcan> sven: I see the newer BT firmwares end in 'es2'
<marcan> FILE brcm/brcmbt4387c2-apple,madagascares2-u.bin SHA256 d18a3cf25d8a24638d81ff81e60b5ae48c79ec1f5602ee3fab7764d8756b5c1e
<marcan> FILE brcm/brcmbt4387c2-apple,madagascares2-u.ptb SHA256 754c5e3d73c9c9e07a5e54bb8386f01269c2c1016cf5237ed1ebe66a697c9971
<marcan> FILE brcm/brcmbt4387c2-apple,maldiveses2-u.bin SHA256 a6bc9668240087301f55b52377f906f296e0fcfff841dd3d4bc08121e6ad7ea6
<marcan> FILE brcm/brcmbt4387c2-apple,maldiveses2-u.ptb SHA256 992bb635f267c385a4ead8d217a34256a4e59dc2d6c7586f627b3c99b373333b
<marcan> FILE brcm/brcmbt4387c2-apple,okinawaes2-u.bin SHA256 1dccd2749e374f791aa73457b6d9458a60bf9c3eeb3d1f322bd9d5fe9c51a54a
<marcan> FILE brcm/brcmbt4387c2-apple,okinawaes2-u.ptb SHA256 77853c87c0bab51be2039694b850526644a3e450eee2d64cdf69989e9adc375d
<marcan> should we put that into the board name for bluetooth, or drop it in the firmware extractor?
<sven> huh, I assume the WiFi board type is without that es2 then?
<marcan> yup
<sven> macos itself just has a static list of filenames for bt fwiw
<marcan> lovely...
<marcan> I say drop it, I think it's BS and not part of the real platform name
Erik52 has joined #asahi-dev
<sven> I think I’d drop it…
Erik52 has quit []
<sven> yeah, that
<marcan> besides, we don't control the ACPI name and it wouldn't have it
<marcan> ok
<sven> dunno if you saw, but the Bluetooth function has no acpi companion on the T2 macs
<sven> so it’s either hardcode “formosa” since there’s only a single FW anyway or do some hacks to get to the WiFi acpi name
<marcan> ah, we can just hardcode it then, heh
<sven> yeah, I don’t expect them to release another t2 Mac ;)
jole has quit [Remote host closed the connection]
jole has joined #asahi-dev
Catyre has quit [Remote host closed the connection]
MajorBiscuit has quit [Ping timeout: 480 seconds]
<marcan> sven: pacman upgrade on asahi-dev for some magic :)
<marcan> (building kernel with bluetooth right now, that's not there yet)
Gaspare has joined #asahi-dev
nicolas17 has joined #asahi-dev
<marcan> sven:
<marcan> [ 7.237106] hci_bcm43xx 0000:01:00.1: enabling device (0000 -> 0002)
<marcan> [ 7.237734] hci_bcm43xx 0000:01:00.1: Reading OTP failed with -2
<marcan> [ 7.237735] hci_bcm43xx: probe of 0000:01:00.1 failed with error -2
<sven> huh
<sven> can you enable the dev_dbg prints?
<sven> I guess the otp might’ve moved on the max/pro then
<marcan> the wlan one did
<sven> or maybe just dump the entire BAR0 from the HV, that's how I found it in the first place :D
<j`ey> marcan: did you intentionally remove rtkit-helper in asahi-5.19-rc5-2?
<marcan> nope
<marcan> did -1 have it?
<j`ey> yes
<marcan> huh
<marcan> I didn't touch the config
<marcan> weird
<j`ey> no, I mean the file disappeared
Catyre has joined #asahi-dev
<marcan> the module?
<marcan> oh like in the merge?
<j`ey> fatal: Path 'drivers/soc/apple/rtkit-helper.c' exists on disk, but not in 'asahi-5.19-rc5-2'.
<marcan> ohh wait I know what that is
<marcan> I dropped the dockchannel branch because that stuff ended up in the hidspi one anyway
<marcan> forgot rtkit helper was only there
<marcan> I'll put it back
<marcan> thanks :)
<j`ey> np, I always 'git diff asahi-5.19-rc5-1 asahi-5.19-rc5-2' when i see a new branch ;)
<marcan> :D
dingodoppelt has quit [Quit: ZNC 1.9.x-git-170-9be0cae1 - https://znc.in]
dingodoppelt has joined #asahi-dev
<marcan> 00000005c14140e0 84cc0000 00000038 00000000 00000000 00000000 00000000 00000000 00000000
<marcan> 00000005c1414100 00000000 00000000 00000000 00000000 00000000 00000000 00000000 80004433
<marcan> 00000005c1414120 00000002 18001ff9 00000000 80005f71 00000002 19328ff5 00000000 00081d15
<marcan> 00000005c1414140 3d730000 4d003243 4850543d 3d6d204e 20372e34 3d562020 80ff0075 060c8309
<marcan> 00000005c1414160 70955119 0000ae00 00000000 00000000 00000000 00000000 00000000 00000000
<marcan> 00000005c1414180 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<marcan> that's regmon swapped, but you get the idea
<marcan> 413c maybe?
Catyre has quit [Ping timeout: 480 seconds]
bisko has joined #asahi-dev
<sven> yeah, could be
<sven> (Not at a computer here, staring at those numbers on my phone :D)
<marcan> [bluetooth]# list
<marcan> Controller F8:4D:89:61:CE:97 macherie [default]
<marcan> :
<marcan> :D
<sven> \o/
<sven> guess that just leaves those weird T2 chips
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
<anoake[m]> This will help jail break the T2 chips
<marcan> that's of no use here
<marcan> we're not trying to jailbreak anything
<marcan> T2 Macs are already open machines as far as the AP is concerned
<marcan> we're talking about the bluetooth chipset
<sven> pushed the OTP offset thingy
<sven> (plus some minor cleanup)
millenialhacker has quit [Ping timeout: 480 seconds]
<marcan> sven: I already did that lol
<sven> :D
<marcan> -3 is already pushed
<sven> that also works
<sven> that driver needs a bit more work before I'll submit it anyway
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sven> i'd mainly like to figure out suspend and how to reset this thing
<marcan> yeah well wifi is kind of broken there too..
<marcan> from what I saw, it's Yet Another Bespoke Thing for wifi
<marcan> some other command mechanism or something, instead of the little mailbox thing brcm normally uses
<sven> i only briefly looked at BT but it didn't seem to bad
<marcan> wifi is probably just bad because that driver is a hairball to begin with
<marcan> at least with bt it's your driver :>
<sven> fair :D
<sven> I think suspend is mostly just tear down the communication rings + write 0 to a register that R called "sleep control"
doggkruse has joined #asahi-dev
<j`ey> weird, 'git fetch --all' doesn't give me asahi-5.19-rc5-3
<sven> i'm probably also missing some kind of "ack this irq" poke because if you switch to legacy interrupts it'll trigger an irq storm
<marcan> j`ey: it's totally there...
<j`ey> marcan: I know, I see it in the github UI!
<marcan> sven: okay, I tried pairing my phone and it exploded :p
<marcan> I see a lot of [ 96.167889] Bluetooth: hci0: Unknown advertising packet type: 0x2713
<sven> huh, how?
<marcan> and a
<marcan> [ 56.933345] Bluetooth: hci0: sending frame failed (-22)
<marcan> pairing failed
<marcan> and now the list is empty
<sven> ugh
<sven> ive seen the first thing as well, that should be harmless
<marcan> connecting fails
<sven> there’s a decent chance it died
<marcan> it does let me try again if I remove the device
doggkruse has quit []
<marcan> and goes through the pin dance so it's not dead
<marcan> but pairing fails
<sven> huh, that's new
<sven> usually when you do something wrong it just dies
<sven> -22 is EINVAL, let's see
<marcan> sec, this *could* be my fault
<marcan> Jul 12 03:40:51 macherie bluedevil-wizard[986]: kf.bluezqt: PendingCall Error: "br-connection-profile-unavailable"
<marcan> maybe this is just bluetooth stupidity
<sven> let me add some more warnings around return -EINVAL anyway
<marcan> I do get that error when pairing fails though
<marcan> so it seems related
<marcan> failed with my speakers too
<sven> let me try to re-pair something
<marcan> could be a 4387 thing
<sven> looks like it, pairing with my phone still works here
<marcan> [ 43.841986] too big 1032 0 1028
<marcan> sorry, had my own crap debug :D
<marcan> but yes
<marcan> it's the length
<sven> huh, which ring is that?
<sven> maybe I messed up the payload size somewhere
<marcan> let me use your patch
<sven> looks like ACL
<sven> I guess just bump it by another 4 bytes and call it a day, lol? :D
<marcan> I don't get how it can be that big but ok lol?
<sven> me neither :D
<sven> just s/HCI_MAX_FRAME_SIZE/HCI_MAX_FRAME_SIZE + 4/ and i guess it'll work
<marcan> just for completeness
<marcan> [ 185.661718] hci_bcm43xx 0000:01:00.1: payload len 1032 is too large for ring 5 (max is 0 or 1028)
<sven> yeah, that’s acl host to device
<sven> guess this is the time where I finally have to take a look at the Bluetooth spec
AProgrammer has joined #asahi-dev
<AProgrammer> How can I install the linux kernel headers in asahi?
<marcan> sven: still fails
<marcan> might be unrelated to the tx failure tbh
<marcan> this could just be userspace fail
<sven> hrm, this is pairing with an Android phone?
<marcan> yes, but also happened with some speakers, let me try them again
Catyre has joined #asahi-dev
<sven> pairing so far has as always worked here fwiw, usually the userspace fail happened afterwards
<marcan> yeah I think it's just the UI being stupid
<marcan> it does actually pair possibly
<marcan> oh yeah, it works
<sven> :)
<marcan> just pulseaudio was down so it refused to connect lol
<sven> ah yes, that sounds like userspace fail I ran into as well :D
<marcan> yeah, obex works and stuff
<sven> nice! I could never get obex to work because apparently macOS doesn’t really support that out of the box
<nicolas17> I once actually thought Linux didn't support my laptop's bluetooth chipset when in fact I hadn't installed pulseaudio-module-bluetooth x_x
<marcan> ah wait, probably just because I startx'ed instead of starting a real session
<marcan> (this is my weirdo test machine)
<marcan> ok, let me push another kernel with the +4 anyway, and see if it magically works on my cleaner machines
<sven> I did play a sine wave from macOS and sent that to the m1 though via that audio ACL thing :D
<sven> still couldn’t really recognize it in btmon though :(
<nicolas17> sven: I think "Applications/Utilities/Bluetooth File Exchange.app" does OBEX
<sven> oh, I didn’t find that one
<nicolas17> it's kinda hidden nowadays, "cool kids use AirDrop"
<sven> just some 10+ year old Python based thing that wouldn’t run anymore and some crappy App Store apps that didnt do what they claimed to do
<nicolas17> yeahhh I don't think iOS ever gave third-party apps access to Bluetooth at the level needed to implement OBEX
doggkruse has joined #asahi-dev
<nicolas17> there's many apps like that which actually only work with another instance of itself on the other phone
<nicolas17> ... oh you mean mac app store? that's more plausible
<sven> yeah
<marcan> sven: did you see my firmware shenaigans btw? :>
<marcan> just pacman -Syu should make it work
<marcan> *shenanigans
<sven> I, uh, don’t actually have the asahi distro installed and kinda still boot from sown random rootfs :D
<sven> mostly because I’ve been too lazy to hook up screen/keyboard/mouse and do the while 1TR dance again
<sven> got a link though? I wanna see what you did :>
AProgrammer has quit [Remote host closed the connection]
<sven> ah, found it
<povik> share
<sven> asahi-installer
<marcan> (and the PKGBUILDs to go with it)
<sven> it contains a asahi_firmware Python package now and I…
<sven> yeah… and I assume there’s a marching PKGBUILD ;)
<marcan> asahi-fwextract
<sven> *matching
<marcan> which has a postinstall that runs it
<sven> very nice
<marcan> and all of which is now a dep of asahi-base
<marcan> *asahi-meta
<marcan> ... and the bluetooth stuff a dep of asahi-desktop-meta
<marcan> including a postupgrade that enables bluetooth.service
<marcan> I want the bluetooth icon to just pop up for people :D
<sven> nice, so everything just magically works :>
<j`ey> sven: almost makes you want to install the asahi distro :P
<povik> it does :p
<sven> :D
<marcan> :D
<sven> I’ll switch my main machine over once thunderbolt works
<marcan> also the installer should do M2 now (requires expert mode, the 12.4 for that stub is one of the magic special M2 versions, will not meet prereqs on "normal" 12.4 machines)
<marcan> but I haven't pushed/tested it yet
Catyre has quit [Remote host closed the connection]
<sven> that’s a hard dependency in my setup and the only reason I even decided to get entangled with that mesa
<sven> *mess
<j`ey> and studio too
<marcan> yup
Catyre has joined #asahi-dev
<j`ey> sven: looking forward to testing BT, will be nice to get rid of the headphone cable :D
<sven> :D
<sven> it was fun to write a nice self contained driver again. pretty much the opposite of the thunderbolt mess :)
<j`ey> marcan: I presume youre not going to push a new installer until you're back?
<marcan> you presume wrong
<marcan> I want to get the dev one pushed today
<blazra[m]> it does just work! just updated and rebooted and it works (14" m1pro with BT headphones), thanks!
<j`ey> there was someone asking about m1 ultra a few days ago
<marcan> and if people say it works I can promote to prod during the trip no problem
<j`ey> marcan: cool
<j`ey> blazra[m]: fast feedback!
<marcan> didn't even give *me* time to test it on a proper install :D
<sven> hah
<marcan> also the kernel is still missing the +4
<marcan> asahi4 should be up now
<jannau> marcan: uboot/m1n1 (and kernel) from asahi-dev work on the m2 (not a proper install but asahi on an usb stick). kernel not fully tested since I can't convince mkinitcpio to include all necessary modules
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan> yes, I expected that
<marcan> was just going to look now
<marcan> oh btw, for the installer, not sure if you all saw ./test.sh
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
<marcan> assuming you have a proper dev env on macos (notably, you need the rust stuff for m1n1 to build, but you could cheat by copying over a built tree), you can just test the installer in-place
<jannau> haven't looked yet at the installer
<sven> Bluetooth on M2 would be interesting as well. If it has a new chip revision the driver maybe needs a chance for sending the calibration data
<jannau> lol, in my cursed usb install we're not using it
<marcan> I think it's the same rev?
<marcan> jannau: using what?
<sven> oh, maybe j was confused. I thought M2 was 4387 c3 while the pro/max are 4387 c2
<sven> and possibly c3 also needs the beam forming calibration. that thing again is a hard coded list somewhere in macOS :/
<marcan> ah, wait, M2 *pro* is 4378 r3
<marcan> M2 *air* I think is just the same 4387
<sven> yeah, than maybe it needs an additional check in that send_calibration as well. Or maybe not
<jannau> marcan: the asahi initcpio hook but nervermind, seems to be just my cursed setup
<marcan> jannau: pushed an asahi-scripts bump for that
doggkruse has joined #asahi-dev
<marcan> trying to make new OS images now, let's see if they work on M2
<jannau> it should, packages from asahi-dev work on m2
<marcan> yup, bluetooth Just Worked on my (no nonsense end user install) iMac
<marcan> OS images built, going to take a shower while they upload
<sven> nice!
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
saina has joined #asahi-dev
saina has quit [Read error: Connection reset by peer]
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
<marcan> installing on the M2...
<jannau> marcan: mkinitcpio hooks needs "map add_firmware apple/tpmtfw-j413.bin apple/tpmtfw-j493.bin"
<marcan> no it doesn't
<marcan> dockchannel-hid.c needs MODULE_FIRMWARE ;)
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
leitao has joined #asahi-dev
<marcan> but really this is a problem for redistribution
<marcan> so I need to find a solution for that
mps has joined #asahi-dev
<marcan> I think the driver should probably have some kind of retry logic, so that it picks up the firmware once booted
<marcan> since the keyboard will work perfectly fine without it
mps_ has quit [Ping timeout: 480 seconds]
leitao has quit [Remote host closed the connection]
<marcan> whoops, u-boot failed to boot RTKit NVMe. that's annoying.
<marcan> "apple_rtkit_boot returned -110"
<marcan> isn't that a timeout?
<marcan> didn't we increase those?
<jannau> yes, I did increase the timeouts
<marcan> oh well, I tried
<marcan> I need sleep
<marcan> feel free to try to debug it if you have time...
<marcan> I may need to punt on this for a few days, I'm not sure I'll have time before the trip
<jannau> sleep well, m2 nvme works for me in u-boot (chainloading m1n1+u-boot over usb)
<marcan> release u-boot does not
<marcan> configs/etc are in the PKGBUILDs repo
<marcan> is it supposed to go 1...0... boot, or is it supposed to boot immediately at 0?
<marcan> I see 1 second from 0 to the error, either that's the 1 second timeout, or it isn't actually waiting 1 second
<jannau> I'm chainloading the boot.bin from the system
<jannau> but m1n1 doesn't touch the nvme in that setup
<marcan> try actually chainloading
<marcan> make -C .. CHAINLOADING=1 && python tools/chainload.py -r ../build/m1n1.bin && cat ../build/m1n1.bin <(echo -ne 'chosen.asahi,efi-system-partition=a17b7e46-e950-bb4f-bc82-8ab1047a058e\nchainload=a17b7e46-e950-bb4f-bc82-8ab1047a058e;m1n1/boot.bin\n') >| /tmp/m1n1-chainload.bin && python tools/chainload.py -r /tmp/m1n1-chainload.bin
<marcan> (replace with your ID)
<marcan> anyway, good night :)
<marcan> it's possible I broke it with the m1n1 rtkit power stuff in stage1, and it's broken for new installs on m1 too
<marcan> but I've been chainloading like that and it worked for me, I think?
<marcan> so I'm not sure
<jannau> with m1n1 chinloading from the nvme it's broken as well
<jannau> it's not broken on m1 ultra
Catyre has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
<jannau> fixed by resetting nvme via pmgr on probe
Catyre has joined #asahi-dev
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
joske has joined #asahi-dev
<joske> povik: marcan: new asahi branch, no audio, I got this in dmesg: firmware designs can be :p
<joske> <marcan> this isn't new
<joske> <j`ey> reseting seems to have been a problem since day 1
<joske> <kettenis> u-boot 2022.07 was released so I rebased the u-boot asahi branch once more to pick up the Makefile changes that drops -rc6
<joske> oops
<jannau> doesn't cause problems on the m1 ultra
<joske> that was some palm x-select, I meant: [ 18.077498] apple-mca 238400000.mca: ASoC: error at snd_soc_dai_set_sysclk on mca-i2s-2: -16
joske has quit [Remote host closed the connection]
Catyre has quit [Ping timeout: 480 seconds]
joske has joined #asahi-dev
<joske> hmm if I boot previous kernel same problem, even when reverting boot.bin, so please disregard for now
joske has quit [Remote host closed the connection]
Gaspare has quit [Quit: Gaspare]
Catyre has joined #asahi-dev
c10l has joined #asahi-dev
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
Catyre has joined #asahi-dev
psykose has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]