<apritzel>
yes, as the devicetree file is conceptually a hardware description, so should not be different between the software using it
<LordKalma>
yeah, I find that example of a source tree for a BR2 external quite weird
<apritzel>
we try to sync them from the kernel (where they get the best review) into U-Boot
<LordKalma>
anyway, thanks again, I have to get some sleep :)
<LordKalma>
thanks again for all the help, we'll talk more in the future, I'm sure :)
rajkosto has joined #linux-sunxi
jernej has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
moteen has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
moteen has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
rajkosto has quit [Read error: Connection reset by peer]
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
<jernej>
LordKalma: another way to speed up kernel bisecting is to leave your image on SD card as-is and only update U-Boot script to load kernel over network (tftp in my case)
<jernej>
naturally, U-Boot needs to support network, but that's usually the case most of the time
<jernej>
you also have to disable kernel modules support and all drivers must be built-in, but that's acceptable for bisecting
moteen has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
bauen1_ has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
szemzoa has quit [Remote host closed the connection]
<LordKalma>
I copy pasted values from some other A33 defconfig from u-boot's repo
<LordKalma>
that's all (probably?) wrong
<LordKalma>
any suggestions on how I would be able to understand/discover the right configuration?
machinehum has quit [Ping timeout: 480 seconds]
aggi has quit [Quit: connection closed.]
aggi has joined #linux-sunxi
<apritzel>
LordKalma: well, there is not too much in here (that is what I was after the whole time: upstreaming U-Boot support would be rather simple ...)
<apritzel>
so I think I commented on some values earlier, like the DRAM frequency, you should copy what the existing port sets there currently
<apritzel>
IIRC the frequency was shockingly low?
moteen has joined #linux-sunxi
<apritzel>
LordKalma: how does does that config get you? That's probably enough for booting from SD, I guess?
<apritzel>
you should add CONFIG_MMC_SUNXI_SLOT_EXTRA=2 to enable the eMMC (booting), and CONFIG_USB_EHCI_HCD=y and CONFIG_USB_OHCI_HCD=y to enable USB, should you need that in U-Boot
<LordKalma>
apritzel, for context, nobody has built u-boot for it yet, so nobody has a _defconfig
<LordKalma>
"existing" ports extract u-boot with dd from the stock firmware and re-paste it into the sdcard
<LordKalma>
I want to do away with that
<apritzel>
yeah, but if you look at the other defconfigs, there are pretty simple, it's mainly some common A33 boilerplate, plus some features (USB, Ethernet, ...) you need
<apritzel>
LordKalma: so all you need for building mainline U-Boot (on an already supported SoC!) is that DT and some version of defconfig that works
<apritzel>
if you send that to the U-Boot mailing list, people can have a look and advice you on what's missing
<apritzel>
getting display support in U-Boot would require more work, but is probably not really needed?
<apritzel>
does the existing U-Boot enable the display?
moteen has quit [Remote host closed the connection]
<LordKalma>
not sure, I don't where u-boot starts and ends
<LordKalma>
*don't know, sorry
<LordKalma>
I'll have to confirm turning it on connected to the serial port
<LordKalma>
but I don't have it next to me
<LordKalma>
the stock image does have a nice splash screen, dunno at what stage that is
szemzoa has quit [Remote host closed the connection]
<apritzel>
*typically* a splash screen is done from U-Boot, but I don't know if that's the case here
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
<LordKalma>
how did you find out the ram speed btw?
moteen has quit [Remote host closed the connection]
aggi has quit [Quit: connection closed.]
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
szemzoa has quit []
<apritzel>
I looked at their SPL disassembly
aggi has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
<LordKalma>
okay, so CONFIG_DRAM_CLK=384
<LordKalma>
what about CONFIG_DRAM_ZQ
<LordKalma>
what is it?
<LordKalma>
(also, how did you disassembled the SPL? I'm interested :D)
apritzel_ has joined #linux-sunxi
<LordKalma>
apritzel_, saw you reconnecting, I don't know if you saw, but I'm wondering how you disassembled the SPL, I would like to take a look as well
<LordKalma>
for example, the guy that did the Armbian build created a "bypass" system so you can boot to the radio without removing the SD card
<LordKalma>
he turns on the lights manually with that boot script
<apritzel>
so it's PE15? I guess that should warrant an LED node in the DT then
<apritzel>
are the buttons always lit, with the original kernel?
<LordKalma>
they lit up somewhere during the boot process
<LordKalma>
and some of them represent state
<LordKalma>
it's more than just backlight
<LordKalma>
I'm building the LCD panel driver as an external module, and it went to `/lib/modules/5.15.50/extra/panel-sitronix-st7701s.ko` and modprobe says nothing is loaded. That's also interesting
<apritzel>
LordKalma: did you run depmod after copying the module?
<LordKalma>
should be part of the buildroot's process
<apritzel>
did you try to manually modprobe it? anything in dmesg?
<apritzel>
for the key LEDs, I'd suggest to have a gpio-led node, with: function = LED_FUNCTION_KBD_BACKLIGHT; default-state = "on"; gpios = <&pio 4 15 GPIO_ACTIVE_HIGH>;
<apritzel>
that should turn it on automatically, but still allows to turn it off
<LordKalma>
I had to make linux-rebuild (buildroot thing) to get the DTB renewed, and I think it didn't rebuild the kernel module, maybe something to do with that
<LordKalma>
I'll check tomorrow, I'm tired for today