| c0rnelius | I made some adjustments as I don't believe some of that is relative to the H5. | 00:30 |
|---|---|---|
| c0rnelius | We shall see | 00:30 |
| c0rnelius | Plus it looked like some of it is already in my base patch that board. cpu related junks and what nots | 00:47 |
| c0rnelius | tuxd3v: whats in ur cmdline? | 01:00 |
| tuxd3v | sorry It took a longer nap than expected -.- | 02:11 |
| tuxd3v | I have this: | 02:12 |
| tuxd3v | setenv bootargs "earlyprintk earlycon=uart8250,mmio32,0x1c28000 net.ifnames=0 biosdevname=0 debug=on console=ttyS0,115200 console=tty1 cma=64M root=PARTUUID=${rootfsuuid} rw fsck.repair=yes rootwait usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u elevator=noop" | 02:12 |
| tuxd3v | now I doesn't even need the partuuid, because I have aliases in the DT for all mmc cards :) | 02:14 |
| tuxd3v | earlycon=uart8250,mmio32,0x1c28000 you need to see what address is ttyS0 | 02:19 |
| tuxd3v | in your board.. | 02:19 |
| c0rnelius | I'll check the earlycon but thats not needed on my other boards | 02:34 |
| tuxd3v | yeah its not really neded its only for debug purposes, to give you the logs from beguining.. | 02:35 |
| tuxd3v | its not really needed.. | 02:35 |
| tuxd3v | now that I have it completly working I will got that out too :) | 02:35 |
| c0rnelius | and... no. | 02:42 |
| tuxd3v | humm | 02:42 |
| tuxd3v | what no? | 02:42 |
| tuxd3v | bluetooth? | 02:42 |
| c0rnelius | Yeah doesn't come up | 02:43 |
| tuxd3v | does you have the binary in /lib/firmware/brcm ? | 02:43 |
| c0rnelius | My other patch it will come up, but that isn't editing the dts but actually making changes to the bluetooth business inside the kernel its self | 02:43 |
| c0rnelius | Of course I do | 02:43 |
| tuxd3v | humm | 02:43 |
| tuxd3v | what is your device? | 02:43 |
| tuxd3v | ampak 6212? | 02:44 |
| tuxd3v | yeah its a 6212 like mine :) | 02:44 |
| c0rnelius | Yeah I believe so? Either way the firmware on the device is sufficient. | 02:44 |
| tuxd3v | you need a patch like this:/lib/firmware/brcm/BCM43430A1.hcd | 02:45 |
| tuxd3v | this patch is required | 02:45 |
| tuxd3v | to work flawlessly | 02:45 |
| c0rnelius | Its a lost cause :) Somewhere in between believing in Jesus and caring in general. | 02:46 |
| tuxd3v | no its not believe me! :) | 02:46 |
| c0rnelius | I'm pretty sure I already added that last time we were on the subject. | 02:46 |
| tuxd3v | its for 26 Mhz? | 02:48 |
| c0rnelius | Thats the one you mentioned. So I looked into it. | 02:48 |
| tuxd3v | I will give you a small dmesg of mine: | 02:48 |
| c0rnelius | It should be in there. | 02:48 |
| c0rnelius | In my research I believe its like the a64... It needs a push. | 02:49 |
| tuxd3v | you need binutils or you can use another tool | 02:49 |
| tuxd3v | to a strings on the package | 02:49 |
| tuxd3v | on the firmware :D | 02:49 |
| c0rnelius | On the vendor kernels they just edit the bluetooth bits, on mainline you need a helper. | 02:49 |
| tuxd3v | it should say: 0BCM43438A1 26MHz AP6212A1_CL1 BT4.0 OTP-BD-0034 | 02:50 |
| tuxd3v | almost on the beguining.. | 02:50 |
| c0rnelius | Yes I read the strings | 02:50 |
| c0rnelius | I added it to my firmware | 02:50 |
| tuxd3v | what is the output of this: 'dmesg|grep -E "Bluetooth|cfg80211|brcmfmac|mmc" --color' | 02:51 |
| c0rnelius | The problem is the kernel doesn't know bluetooth is even there... Its not a problem with firmware or else I would see an error. | 02:51 |
| tuxd3v | ho wait.. | 02:51 |
| tuxd3v | so you need this in the kernel def_config: https://paste.debian.net/hidden/92c92aef/ | 02:52 |
| tuxd3v | is really pays off | 02:52 |
| c0rnelius | Yes all of that is there already. | 02:53 |
| tuxd3v | if you have the uart3 configured and bluetooth inside | 02:53 |
| tuxd3v | so it needs to work on boot | 02:53 |
| tuxd3v | dmesg|grep -E "Bluetooth|cfg80211|brcmfmac|mmc" | 02:53 |
| tuxd3v | do this, and see whats going on ^^ | 02:53 |
| c0rnelius | Nothing related to bluetooth is there | 02:54 |
| c0rnelius | zero | 02:54 |
| c0rnelius | I checked | 02:54 |
| tuxd3v | does you have the bluetooth stack installed? | 02:54 |
| c0rnelius | Of course | 02:55 |
| tuxd3v | I use this: apt-get install bluetooth bluez-obexd pulseaudio-module-bluetooth bluez-tools | 02:55 |
| tuxd3v | ho you need dbus too | 02:55 |
| Tenkawa | tuxd3v: those have nothing to do with the dmesg/kernel seeing bluetooth | 02:56 |
| tuxd3v | kernel will see the device because c0rnelius configured in the DT the bluetooth layer | 02:56 |
| tuxd3v | kernel will nring up bluetooth alone, without external intervenction :) | 02:56 |
| Tenkawa | if bluetooth drivers and the kernel loads... those packages dont mean anything | 02:57 |
| Tenkawa | you dont have to have any of them installed | 02:57 |
| tuxd3v | those packages are for userspace only | 02:57 |
| Tenkawa | "thats my point" | 02:57 |
| Tenkawa | your dmesg| grep wasnt helpful | 02:57 |
| tuxd3v | yes it is, because it shows you whats going up in the boot process :) | 02:58 |
| Tenkawa | no it doesmt | 02:59 |
| Tenkawa | er doesnt | 02:59 |
| tuxd3v | for example this: https://paste.debian.net/hidden/cc1c1992/ | 02:59 |
| tuxd3v | yes it is | 02:59 |
| tuxd3v | :D | 02:59 |
| Tenkawa | thats not the boot process | 03:00 |
| Tenkawa | thats the kernel drivers loading | 03:00 |
| Tenkawa | and initial mount | 03:00 |
| Tenkawa | thats all | 03:00 |
| tuxd3v | c0rnelius, take frok here the firmware patch: https://gitea.devuan.org/tuxd3v/extras/src/branch/master/lib/firmware/brcm/BCM43430A1.npi-neo-air.hcd | 03:00 |
| Tenkawa | the boot process is in /var/log | 03:00 |
| tuxd3v | rename it to '/lib/firmware/brcm/BCM43430A1.hcd' | 03:01 |
| tuxd3v | its the same firmware for mine and your device :) | 03:02 |
| tuxd3v | and also the device is using the same 26 mhz crystal | 03:02 |
| tuxd3v | so its exactly the same :) | 03:02 |
| tuxd3v | I have this in my kernel def_config: https://paste.debian.net/hidden/fa086ac1/ | 03:04 |
| tuxd3v | its what you need in your kernel | 03:04 |
| tuxd3v | the rest via device tree it will bring the drivers, and download the firmware automatically to the device :) | 03:04 |
| tuxd3v | Tenkawa, I don't need full boot logs only the interesting parts ;) | 03:05 |
| c0rnelius | tuxd3v: I wills tries again tomorrow. The dts already has the edits, so if its firmware related it should in theory just work? | 03:08 |
| tuxd3v | yes, if you have the Bluetooth drivers selected in the kernel, and the firmware in /lib/firmware, it should work | 03:09 |
| tuxd3v | we had tested a lot of devices today in linux-sunxi | 03:10 |
| tuxd3v | this problems with bluetooth are afacting a great number of devices, until today :) | 03:10 |
| tuxd3v | the puzzle was solved :) | 03:11 |
| tuxd3v | and its like that, out-of-de-box | 03:11 |
| c0rnelius | Well not on mine apparently :) Whats the list of devices? | 03:12 |
| tuxd3v | I believe you shouldn't have '/dev/ttyS3' | 03:12 |
| c0rnelius | I adjusted that. | 03:12 |
| tuxd3v | since tablets, bananapi m64, my neo Air, I don't remember now what wens and megi had, but they also had sbcs with alllwinner devices on them | 03:13 |
| c0rnelius | Mine by default is set to S2. But I did remove it, change it and try diff numbers. | 03:13 |
| c0rnelius | I even added ur early... Nothing was noticed. | 03:13 |
| tuxd3v | some of the bluetooth devices are ampak 6212, 6210, also ando others | 03:13 |
| tuxd3v | but all broadcom related, or cypress related.. | 03:14 |
| tuxd3v | when it boots up it claims ttyS3, it will be unavaillable, because its claimed for Bluetooth | 03:14 |
| tuxd3v | you should see something like: | 03:15 |
| tuxd3v | ls /dev/ttyS* | 03:15 |
| c0rnelius | When mine boots its not claimed by anything because the kernel doesn't know its there. | 03:15 |
| tuxd3v | /dev/ttyS0 /dev/ttyS2/dev/ttyS5 /dev/ttyS7 /dev/ttyS1 /dev/ttyS4/dev/ttyS6 | 03:16 |
| c0rnelius | My old patch it at least saw it | 03:16 |
| tuxd3v | the ttyS3 like you see is not here because its used by bluetooth | 03:16 |
| tuxd3v | on boot it claims it :) | 03:16 |
| tuxd3v | but that is fine | 03:16 |
| tuxd3v | its a good thing | 03:16 |
| tuxd3v | does you have aliases for serials? | 03:17 |
| tuxd3v | both? | 03:17 |
| tuxd3v | I am on 5.10.37 kernel | 03:18 |
| tuxd3v | I have this in aliases: | 03:20 |
| tuxd3v | serial0 = &uart0; | 03:20 |
| tuxd3v | serial3 = &uart3; | 03:20 |
| tuxd3v | mmc0 = &mmc0; | 03:20 |
| tuxd3v | mmc1 = &mmc1; | 03:20 |
| tuxd3v | mmc2 = &mmc2; | 03:20 |
| tuxd3v | I have their the disk devices too WIFI is mmc1 | 03:21 |
| tuxd3v | mmc0 is sdcard,mmc2 is emmc | 03:21 |
| tuxd3v | your serial is in ttyS2? | 03:24 |
| tuxd3v | mine is in ttyS0 | 03:25 |
| tuxd3v | but you can choose if you have seveeral and you have :) | 03:25 |
| tuxd3v | this subject is not board related but device tree related, because its the device tree that will parse the dtb file, and as soon as it sees there: | 03:29 |
| tuxd3v | compatible = "brcm,bcm43438-bt"; | 03:29 |
| tuxd3v | it will load the bluetooth driver | 03:30 |
| tuxd3v | and in the process that triggers a firmware load from rootfs | 03:30 |
| tuxd3v | what is the dts you have now? | 03:31 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!