ChanServ changed the topic of #asahi-re to: Asahi Linux: porting Linux to Apple Silicon macs | Hardware / boot process / firmware interface reverse engineering | WARNING: this channel (only) may contain binary reverse engineering discussion | RE policy: https://alx.sh/re (MANDATORY READ) | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-re
yuyichao has quit [Ping timeout: 480 seconds]
phiologe has joined #asahi-re
PhilippvK has quit [Ping timeout: 480 seconds]
yuyichao has joined #asahi-re
nicolas17 has quit [Ping timeout: 480 seconds]
akemin_dayo has quit [Quit: ┐(´д｀🍍)┌ ]
akemin_dayo has joined #asahi-re
emptynine has quit [Remote host closed the connection]
emptynine has joined #asahi-re
alexsv has joined #asahi-re
<rqou_>
has anyone taken any kind of look at bluetooth?
<rqou_>
i assume it's been made way more complicated than just HCI over PCIe?
the_lanetly_052___ has joined #asahi-re
<jannau>
I'm not aware of anyone looking into bluetooth
<chadmed>
its like HCI over USB over PCIe or something silly like that
<chadmed>
but i dont think anyone figured anything out beyond that information
<Jamie[m]1>
is it in the same broadcom chip as the wifi?
<chadmed>
i would imagine so but dont quote me on that
<rqou_>
yes, function 1 vs function 0
<rqou_>
i have no idea how to trace PCIe though
<rqou_>
and i definitely never figured out what driver is even involved in macos, since the macos stack seems really overcomplicated
<rqou_>
there's a pcie driver, but all it seems to do is issue function level resets
<rqou_>
chadmed: are you sure?
<rqou_>
i didn't see any references to USB
<rqou_>
HCI over USB over PCIe also seems pretty reasonable tbh
<Jamie[m]1>
isn't usb over pcie also called HCI? :P
<rqou_>
oh right lol
<rqou_>
i usually see that explicitly specified as {x|E|U|O}HCI though
<jannau>
chadmed: macos ioreg doesn't look like there's usb involved for bt
<jannau>
HCI is just host controller interface. it's just a name from the standards. sata as ahci, nvme has nvmhci, firewire has one too
<sven>
bluetooth will essentially just be a MMIO region inside the pcie one
<rqou_>
interestingly, bluetooth has a compatible of "bluetooth,n88" in the m1 adt, but there exists idevice DTs that have "bluetooth,n88" attached to a UART
<rqou_>
afaict d221ap/iphoneX/A11 has bluetooth on a uart while d331ap/iphoneXS/A12 has it on pcie
<sven>
maybe that bluetooth function just exposes a simple UART over pcie :D
<rqou_>
so what do i have to put into the HV to trace it?
<rqou_>
i'm still not super familiar with all of the trace tooling
<rqou_>
i'm guessing wifi was made working without involving much tracing?
<rqou_>
fwiw bluetooth has 2 BARs so it's not "simple"
<sven>
you should be able to use trace_range to get started
<Jamie[m]1>
one for uart tx, one for uart rx :P
<sven>
just gotta figure out where the BAR is mapped
<rqou_>
lmao no they're different sizes
itsn0k[m] has joined #asahi-re
MajorBiscuit has joined #asahi-re
f14h has joined #asahi-re
bisko has quit [Read error: Connection reset by peer]
the_lanetly_052__ has joined #asahi-re
the_lanetly_052___ has quit [Ping timeout: 480 seconds]
yuyichao has quit [Ping timeout: 480 seconds]
yuyichao has joined #asahi-re
MajorBiscuit has quit [Ping timeout: 480 seconds]
amarioguy has joined #asahi-re
MajorBiscuit has joined #asahi-re
doggkruse has joined #asahi-re
cyrozap has quit [Ping timeout: 480 seconds]
cyrozap has joined #asahi-re
amarioguy has quit [Ping timeout: 480 seconds]
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi-re
MajorBiscuit has quit [Ping timeout: 480 seconds]
amarioguy has joined #asahi-re
nicolas17 has joined #asahi-re
doggkruse has joined #asahi-re
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]