19:06 <xdarklight> chewitt: congrats on sending your first kernel patches :)

19:10 <chewitt> thanks

19:11 <chewitt> i'll have a play with the dts for the Hub box, as it's already using serdev to load the wifi side (no hciattach)

19:14 <chewitt> however it's working at the moment .. it works nicely :)

19:23 <chewitt> xdarklight: chip details https://marc.info/?l=linux-bluetooth&m=153608351032693&w=2

20:47 <xdarklight> chewitt: as far as I know the wifi side is using a "standard" sdio driver, no serdev (serial - as in UART - device) is involved

20:47 <xdarklight> SDIO cards can be auto-detected by the operating system as they have a vendor ID and card ID (just like USB and PCI vendor / product IDs)

20:49 <xdarklight> the Bluetooth controller is different: you explicitly have to instruct the kernel that there's a Bluetooth controller attached to "that" UART controller, because there's no standardized way for a UART device to identify itself

20:49 <xdarklight> (you even have to give the kernel a hint about the correct Bluetooth controller, because different vendors use different UART "protocols"...)

20:52 <xdarklight> this is exactly why I like embedded hardware development: I get to learn so much about how all the puzzle pieces fit together :)