schroes has quit [Read error: Connection reset by peer]
schroes has joined #u-boot
monstr has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
mmu_man has joined #u-boot
<pivi>
Is anybody of you working with qualcomm/u-boot on very recent SoCs? I have not played with it yet, however from the information I have their boot firmware stack is excusively UEFI. Am I wrong?
linfax has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
sszy has joined #u-boot
enok has joined #u-boot
enok has quit [Quit: enok]
enok71 has joined #u-boot
enok71 is now known as enok
enok has quit [Ping timeout: 240 seconds]
abws has quit [Quit: abws]
abws has joined #u-boot
zsoltiv_ has quit [Quit: Left]
zsoltiv_ has joined #u-boot
enok has joined #u-boot
ungeskriptet3 has joined #u-boot
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet3 is now known as ungeskriptet
alperak has joined #u-boot
<marex>
calebccff: I think MX8MP at least has working superspeed, zynqmp probably too
<mps>
calebccff: just fyi, symlinking libncursesw.so.8 to libtinfo.so fixes build kwboot on alpine
<mps>
thanks for help
<mps>
this one line patch fix it on alpine and I guess it would also on Arch https://tpaste.us/vN4O
enok has quit [Ping timeout: 252 seconds]
f_ has joined #u-boot
enok has joined #u-boot
naoki has quit [Quit: naoki]
egavin has joined #u-boot
KREYREN has joined #u-boot
alpernebbi has quit [Ping timeout: 256 seconds]
Clamor has quit [Read error: Connection reset by peer]
<pivi>
I am going thought some housekeeping of multiple board config files (same kind of changes). Single series / separated patches for each u-boot custodian, single series / separated patch for each board? Different series for each custodian? Any preference? Tartarus ?
<pivi>
Personally I would prefer a single series.
jfsimon1981_b has joined #u-boot
<marex>
pivi: separate patches because separate trees ?
<marex>
pivi: git send-email -1 is your friend
<pivi>
marex: yes, separate custodian trees
<pivi>
ok, so separated patches with no series, each patch updating multiple board within the same custodian.
redbrain has quit [Read error: Connection reset by peer]
stefanro has quit [Quit: Leaving.]
<qschulz>
sjg1: yes I did receive your mail... I hadn't had the time to sit down and look at VBE yet sadly... I need to send some patches next week (upstream U-Boot to bringup on another board) but I should finally be able to carve some time for this
<qschulz>
sjg1: ping me again middle of next week if I haven't started asking questions by then (let's say Thursday morning :) )
redbrain has joined #u-boot
jclsn has quit [Quit: WeeChat 4.2.1]
Stat_headcrabed has joined #u-boot
Stat_headcrabed has quit [Client Quit]
mmu_man has joined #u-boot
<sjg1>
qschulz: Thanks
<Tartarus>
pivi: re qcom, talk with calebccff
Stat_headcrabed has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #u-boot
alperak has quit [Quit: Connection closed for inactivity]
<mps>
calebccff: here is musl author (Rich Felker) comment about 'c_[io]speed' in tools/kwboot.c https://tpaste.us/og4B
mmu_man has quit [Ping timeout: 272 seconds]
yann-kaelig has joined #u-boot
<yann-kaelig>
Hello
enok has joined #u-boot
<yann-kaelig>
I have connected a subboard ( HDD-RAID 2xSATA ) to my Cubietruck3, right now I can not boot from this subboard, and I'm trying to find if I missed something or if it's not possible at all.
<yann-kaelig>
I can not find , if possible, how to list from u-boot command line, the list of available connected devices on the board
Stat_headcrabed has quit [Quit: Stat_headcrabed]
<yann-kaelig>
ok, so I found the command line, seems that my subboard is not detected by uboot scsi scan do not find anything
<yann-kaelig>
So now Iwonder that maybe there is an option to build to detect my subboard . Any idea ?
mmu_man has joined #u-boot
monstr has quit [Remote host closed the connection]
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #u-boot
<marex>
yann-kaelig: is that SATA PMP ?
<marex>
try sata init or scsi reset / scsi scan
<marex>
does the board even support sata in U-Boot in the first place ?
<yann-kaelig>
marex: hi the subboard is connected to the board with a SATA cable
<yann-kaelig>
yes, the board support SATA boot
<marex>
yann-kaelig: well what happens if you plug in just one drive with plain SATA cable ?
<marex>
yann-kaelig: also, uboot version ?
sakman_ has joined #u-boot
<pivi>
calebccff: hello! let me know if you have some insight on u-boot support on recent qualcomm soc (I am thinking at "IOT" stuff)
sakman_ has quit [Client Quit]
sakman has quit [Ping timeout: 252 seconds]
<yann-kaelig>
marex: well. uboot version 2017. What do you mean by plain SATA cable ?
sakman has joined #u-boot
flyback has quit [Quit: Leaving]
flyback has joined #u-boot
enok has quit [Ping timeout: 255 seconds]
Clamor has quit [Ping timeout: 252 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
Clamor has joined #u-boot
ikarso has joined #u-boot
KREYREN has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
<calebccff>
pivi: o/ what kind of insights would you like to know about? for which SoCs?
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
KREYREN has quit [Ping timeout: 260 seconds]
<yann-kaelig>
I don't know how to get or which command will provide the value of interface and dev:part from the load command line
<yann-kaelig>
mmcinfo do not provide anyhting useful
<yann-kaelig>
and there is no mmc output than can help to get them. There are a lot of info but none of them give me an interface name and dev:part info
<yann-kaelig>
or maybe the the variable name are diferent ?
<yann-kaelig>
so, how can I can for the load command line the interface and dev:part value
<yann-kaelig>
can/get
<yann-kaelig>
ok I found it with the help of ext4ls
<yann-kaelig>
It's working. Well I can not boot from the subboard so I was thining about another idea, to manually provide the root value /dev/sda1 and the device where the kernel and dtb files are available which is the sdcard on mmc interface
KREYREN has joined #u-boot
KREYREN has quit [Ping timeout: 260 seconds]
slobodan_ has quit [Ping timeout: 252 seconds]
manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
manawyrm has joined #u-boot
<yann-kaelig>
So, from what I understand, I suppose that booting with extlinux.conf is the easiest way for my use case
<yann-kaelig>
I could also use boot.cmd but I'm little worried about overidding some important default values
<yann-kaelig>
I don't know in this second case how to do it in the cleanest way.
<yann-kaelig>
Is there maybe a software for that, which could retry all the defaults variable and value and only override some of them as requested
<yann-kaelig>
I leave u-boot as is and only apply the changes at a higher level with an extlinux.conf file.
sally has joined #u-boot
KREYREN has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
KREYREN has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
KREYREN has joined #u-boot
KREYREN has quit [Client Quit]
KREYREN has joined #u-boot
<sally>
Does 2024.04 support RPi5?
<marex>
yann-kaelig: oh ... please update to something newer then, it is likely the bug was fixed in the last 7 years
<marex>
yann-kaelig: 2024.04 would be preferrable
<marex>
sally: I recall there should be some basic support
<sally>
marex: Okay, thank you.
<yann-kaelig>
marex: ok, that would be a great news. I will try then this afternoon. Thx
naoki has joined #u-boot
yann-kaelig has quit []
KREYREN has quit [Remote host closed the connection]