ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-amlogic
yann has joined #linux-amlogic
nsaenz has joined #linux-amlogic
nsaenz has quit [Read error: Connection reset by peer]
nsaenz has joined #linux-amlogic
mripard has joined #linux-amlogic
paulk-leonov has joined #linux-amlogic
<paulk-leonov>
so this is the new #linux-meson :)
nsaenz has quit [Ping timeout: 245 seconds]
<paulk-leonov>
so while I'm here, is there any known amlogic board where the bootrom doesn't enforce signature verifications on the first bootloader, and where said bootloader is available as free software?
<paulk-leonov>
(just checking in case things have evolved since my last check)
<repk>
paulk-leonov: Depends on what do you mean by bootloader I guess
<repk>
there is a current effort to mainstream s905x's bl31
nsaenz has joined #linux-amlogic
nsaenz has quit [Remote host closed the connection]
Darkmatter66 has quit [Read error: Connection reset by peer]
<paulk-leonov>
repk: I mean whatever runs after the hardwired logic configuration (bootrom) executed by the CPU
<narmstrong>
paulk-leonov: nop sorry, nobody did the RE, yet
<paulk-leonov>
narmstrong: but are there boards where it's even possible to run unsigned binaries?
<narmstrong>
the bootrom doesn't seem to check signature of BL2 by default
<narmstrong>
I haven't checked personnally
<narmstrong>
since we insert DDR setup data in the BL2 binary, I don't think it checks the signature
<narmstrong>
so any Libre Computer, Khadas, Odroid or Nanopi board would be usable
Darkmatter66 has joined #linux-amlogic
nsaenz has joined #linux-amlogic
<paulk-leonov>
narmstrong: oh cool :)
<paulk-leonov>
so it could just be a matter of lack of code
nsaenz has quit [Read error: Connection reset by peer]
nsaenz has joined #linux-amlogic
nsaenz has quit [Ping timeout: 258 seconds]
nsaenz has joined #linux-amlogic
ndufresne has quit [Ping timeout: 252 seconds]
nsaenz has quit [Remote host closed the connection]
sputnik_ has quit [Ping timeout: 246 seconds]
Barada has quit [Quit: Barada]
warpme_ has joined #linux-amlogic
<warpme_>
narmstrong: may you hint me who/where will be to best report issues with beelink gt1 s912 t820 panfrost 5.2-rc5 kernel module?
<narmstrong>
Dri-devel !
<warpme_>
thx!. will try to report this on dri-devel. (only issue i’am affraid is replay like „it is beelink gt1 or amlogic s912 speciffic issue. go to amlogic or beelink…”)
<warpme_>
narmstrong: dri-devel replay „tomeu: I think narmstrong would know”
<warpme_>
:-)
Darkmatter66 has quit [Ping timeout: 272 seconds]
nsaenz has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 246 seconds]
yann has quit [Ping timeout: 245 seconds]
nsaenz has quit [Read error: Connection reset by peer]
nsaenz has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
vagrantc has joined #linux-amlogic
nsaenz has quit [Quit: Leaving]
nsaenz has joined #linux-amlogic
nsaenz has quit [Max SendQ exceeded]
default__ has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 258 seconds]
ldevulder_ has joined #linux-amlogic
default__ has quit [Ping timeout: 244 seconds]
yann has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
dlaube has joined #linux-amlogic
<dlaube>
Hi, already posted on the mailing list about the S905Y2. I got the dts file from my board from the android system via uart but the board is not booting from it :(
default__ has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 248 seconds]
<xdarklight>
dlaube: Hi :)
<xdarklight>
dlaube: (I'm a bit short on time right now, so sorry if I don't reply later on)
<xdarklight>
dlaube: are you trying to use the original .dts from the device with the mainline kernel? that doesn't work (the original .dts doesn't follow the rules which the mainline .dts follows)
<xdarklight>
yes, assuming the devicetree bindings (the allowed properties with their allowed values) are following the rules
<xdarklight>
(mainline u-boot and mainline Linux are using the same .dts for example, so it's possible :) )
<dlaube>
but i can use values from the original dts to construct a valid mainline dts right?
<xdarklight>
yes (assuming the values is defined in the .dts file, I'm not sure about the latest SoCs but with earlier SoCs sometimes values like GPIOs are hardcoded in some driver in the vendor kernel...)
<xdarklight>
debugfs is typically also helpful (for example /sys/kernel/debug/gpio ;))
<dlaube>
i think most of the values are defined there, i've not come a long way reading them because i am very unfamilliar with the format of dts files
<dlaube>
kind of hard to "read" :D
<xdarklight>
one more hint for Amlogic boards: they mostly follow the reference design. so you can always look at another board with a similar SoC and it's likely that both boards use the same values
<dlaube>
yeah most of the stuff works, no wifi thought but it looks like it is attached to some other bus internally because there is no entry in the dts so it gets detected on the fly
<xdarklight>
it's typically attached to one of the MMC controllers
<xdarklight>
sd_emmc_{a,b,c}
<dlaube>
but i guess it would be helpful if there was a specific dts file for that board even if it is the same as the reference board/another board. Then nobody needs to guess
<dlaube>
narmstrong told me that these systems only work in the upcoming 5.3 kernel?
<xdarklight>
that's exactly why we want specific .dts files for each board :)
<dlaube>
but there is definitly a reaction of some sort.... spamming dmesg 20 times a second :D
<xdarklight>
yes, S905Y2 is part of the "G12A" SoC family. you can check the status and the "changelog" for v5.3 here: http://linux-meson.com/doku.php (the changelog is not up to date, but it'll give you an idea how much work went into v5.3 ;))
<dlaube>
but shouldn't there be no response if these things are not in my kernel right now?
Darkmatter66 has quit [Ping timeout: 246 seconds]
<dlaube>
not familliar with the inner workings of the kernel (thats why i wan't to participate :) )
<xdarklight>
can you be more specific (post a kernel log!) with what exactly is spamming? ;)
<xdarklight>
(with post I mean use pastebin and drop the link here)
<dlaube>
i will plug this thing in in a few minutes so i can paste :) kind of diffucult to get things from the device without ethernet/wifi :)
<dlaube>
(and only one usb socket)
<xdarklight>
maybe you're lucky and it's the USB port that can be forced into device mode (meaning you could setup Ethernet via USB)
<dlaube>
i have an ethernet/usb adapter at hand that works :)
Darkmatter66 has joined #linux-amlogic
dlaube has quit [Remote host closed the connection]
dlaube has joined #linux-amlogic
dlaube has quit [Remote host closed the connection]
Darkmatter66 has quit [Ping timeout: 245 seconds]
dlaube has joined #linux-amlogic
<dlaube>
i forgot the ethernet/usb dongle at work :/
<dlaube>
but i can type the spamming message: "RTL8723BS: ERROR sd_recv_rxfifo: alloc recvbuf FAIL!"
Darkmatter66 has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
buzzmarshall has joined #linux-amlogic
warpme_ has joined #linux-amlogic
dlaube has quit [Remote host closed the connection]
warpme_ has quit [Quit: warpme_]
dlaube has joined #linux-amlogic
dlaube has quit [Client Quit]
dlaube has joined #linux-amlogic
<dlaube>
don't know if this is caused by missing periphal support in that kernel (definitly not 5.3) seems more like an memory allocation failure
<xdarklight>
so it may be a RTL8723BS (wifi chip) driver bug or "feature"
<dlaube>
kind of, https://lkml.org/lkml/2017/6/12/504 states that this happens when an sdio error happens (sdio is not working on this chip right?)
<dlaube>
so a missing sdio driver for our soc results in memory allocation failures in other drivers :D
<dlaube>
they also say that this happen only after a few failed reads (because then there is no memory left to allocate for the driver or sth like that), because i can't copy dmesg right now i can't validate that
<xdarklight>
SDIO should be working, I believe (can't remember 100% though) I tested it with linux-next on my X96 Max (S905X2 SoC)
<dlaube>
error message was on an armbian kernel, so it might not work on this device :D