GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
thopiekar has quit [Ping timeout: 260 seconds]
mmu_man has quit [Ping timeout: 258 seconds]
thopiekar has joined #u-boot
apritzel has joined #u-boot
milkylainen has quit [Quit: Ping timeout (120 seconds)]
haritz has joined #u-boot
haritz has joined #u-boot
thopiekar has quit [Ping timeout: 276 seconds]
thopiekar has joined #u-boot
thopiekar has quit [Ping timeout: 276 seconds]
thopiekar has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
sszy has quit [Ping timeout: 260 seconds]
milkylainen has joined #u-boot
prabhakarlad has joined #u-boot
GuestNew has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 276 seconds]
alan_o has joined #u-boot
mmu_man has joined #u-boot
GuestNew has quit [Quit: Client closed]
GuestNew has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
prabhakarlad has quit [Quit: Client closed]
mmu_man has joined #u-boot
camus has quit [Quit: camus]
<hanetzer>
around what time did FIT support land in u-boot? (arm, if that matters)
torez has quit [Quit: torez]
prabhakarlad has joined #u-boot
Wouter0100 has quit [Read error: Connection reset by peer]
Wouter0100 has joined #u-boot
tre has quit [Remote host closed the connection]
littlebobeep has joined #u-boot
<Tartarus>
Interesting question hanetzer and I suppose the answer isn't quite 2008 since there wasn't likely anyone using it then for ARM, even if technically it worked.
<hanetzer>
Tartarus: working against a vendorified 2010.06 :)
<Tartarus>
FIT images are fairly generic, the maybe harder question is does one that old have everything for device tree booting on arm
<Tartarus>
A quick skim of the git log for that tag says that might be iffy, so you'd be relying on whatever the vendor did
<Tartarus>
if their kernel is device tree not atags
littlebobeep has quit [Ping timeout: 240 seconds]
<hanetzer>
unfortunately no devicetree :)
<hanetzer>
working on mainline linux for it, so i guess I'm stuck with uImage(zImage+dtb) for now :)
torez has joined #u-boot
thopiekar has quit [Ping timeout: 248 seconds]
mmu_man has quit [Ping timeout: 240 seconds]
monstr has quit [Remote host closed the connection]
GuestNew has quit [Quit: Client closed]
thopiekar has joined #u-boot
qschulz has quit [Ping timeout: 240 seconds]
zandar has quit [Quit: Leaving.]
mmu_man has joined #u-boot
frieder has quit [Remote host closed the connection]
zibolo has quit [Ping timeout: 248 seconds]
matthias_bgg has quit [Read error: Connection reset by peer]
prabhakarlad has quit [Quit: Client closed]
guillaume_g has quit [Quit: Konversation terminated!]
<marex>
hanetzer: did you consider updating to newer version of u-boot ?
<hanetzer>
marex: I have, but that doesn't happen overnight :P
prabhakarlad has joined #u-boot
apritzel has quit [Ping timeout: 246 seconds]
sobkas has joined #u-boot
littlebobeep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebo1eep has joined #u-boot
sobkas has quit [Quit: sobkas]
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
sobkas has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
JoaoSchim has quit [Remote host closed the connection]
joaoSchim_ has quit [Remote host closed the connection]
JoaoSchim has joined #u-boot
joaoSchim_ has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
littlebobeep has joined #u-boot
sobkas has quit [Quit: sobkas]
sobkas has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
qschulz has joined #u-boot
sobkas has quit [Quit: sobkas]
sobkas has joined #u-boot
NonaSuomy has joined #u-boot
sobkas has quit [Remote host closed the connection]
sobkas has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
littlebobeep has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
thopiekar has quit [Ping timeout: 260 seconds]
littlebobeep has quit [Remote host closed the connection]
sobkas has quit [Quit: sobkas]
littlebobeep has joined #u-boot
sobkas has joined #u-boot
thopiekar has joined #u-boot
apritzel has joined #u-boot
___nick___ has quit [Ping timeout: 255 seconds]
sobkas has quit [Remote host closed the connection]
jsmolic has quit [Ping timeout: 248 seconds]
sobkas has joined #u-boot
sobkas has quit [Client Quit]
jsmolic has joined #u-boot
sobkas has joined #u-boot
thopiekar has quit [Ping timeout: 258 seconds]
thopiekar has joined #u-boot
<broonie>
Are there any gotchas with enabling the ethernet on sunxi? I've got a libretch-h5-cc board which reports an essentially immediate timeout trying to reset the ethernet MAC with current git.
<Tartarus>
It ought to be fine, but sunxi is such a huge family
<Tartarus>
I forget which sunxi pine variant I have in my lab, and that works
<Tartarus>
(and I test networking)
<broonie>
There's boards in kernelci with the same SoC working (though not with tip of tree u-boot).
<broonie>
More likely to be something silly missed with driver/device setup than anything major.
sobkas has quit [Quit: sobkas]
<Tartarus>
apritzel: any ideas? ^^
macromorgan has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
sobkas has joined #u-boot
vagrantc has joined #u-boot
<apritzel>
broonie: Tartarus: I will have a look. I don't have that board, but will try with an H5 one
<broonie>
apritzel: FWIW it's reporting a timeout in sun8i_emac_eth_start() when it tries to soft reset the MAC.
sobkas has quit [Quit: sobkas]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
<lvrp16>
broonie: libretech-h5-cc is not available in retail
sobkas has joined #u-boot
<lvrp16>
broonie: i think you meant libretech-h3-cc
<broonie>
lvrp16: No, the h5 is available - the libre.computer website is confusing since it lists it together with the -h3 as a 2G variant.
<lvrp16>
broonie: yes, that's the all-h3-cc-h5, all-h3-cc is a completely different board with gigabit ethernet
<broonie>
apritzel: Whatever armbian are shipping (reports as 2021.10-armbian) appears to work.
<lvrp16>
broonie: for libre computer products, "{platform}-{soc-family}-{form-factor}-{soc}"
<lvrp16>
all-h3-cc is an unreleased product
<lvrp16>
h5*
<broonie>
Ah, that's very conrusing
<lvrp16>
all-h5-cc is an unreleased product with gigabit ethernet and no cvbs
<lvrp16>
yes sorry for the confusion
<apritzel>
broonie: so do you have the H5 (Cortex-A53) or the H3 (Cortex-A7)
<lvrp16>
apritzel: he has the h5 with 2gb ddr3
<lvrp16>
ALL-H3-CC-H5
<broonie>
apritzel: It's a H5, I'm running with arm64 for everything (and upstream TF-A).
<apritzel>
sun50i-h5-libretech-all-h5-cc.dts?
<lvrp16>
apritzel: no sun50i-h5-libretech-all-h3-cc.dts
<broonie>
That's what I was using but lvrp16 is telling me it might be the wrong DT.
<lvrp16>
my apologies, i designed the naming convention
<lvrp16>
so it gets a little confusing
<apritzel>
and is it Gigabit Ethernet? Should have a Realtek 8211 PHY then, as opposed to no extra PHY (H3/H5 have on-SoC 100Mbit PHYs)
<broonie>
lvrp16: I suspect it'd be fine if there were a separate DTS upstream for the h5 variant.
<lvrp16>
ALL-H3-CC PCBs does not have gigabit, ALL-H5-CC PCBs does have gigabit, h3 and h5 can be put on either PCB so the suffix after the platform distinguishes
<apritzel>
so this board is using the integrated PHY then?
<lvrp16>
apritzel: yes, that's the only one available for retail
* apritzel
reaches for the Neutis N5 ...
<broonie>
Ah, I see the labelling in u-boot is clearer.
<apritzel>
OrangePi PC2 (H5 with Gigabit works fine)
<broonie>
apritzel: lvrp16: It's working fine if I build for the right board, sorry for the nose :(
<broonie>
and thanks for your help.
littlebobeep has joined #u-boot
torez has quit [Quit: torez]
<lvrp16>
broonie: sorry about the confusion, happy to clear it up.
<broonie>
lvrp16: FWIW these and the le potatos are fantastic boards for my test lab (upstream kernel stuff, both subsystems I maintain and making them available to kernelci).
<broonie>
cheap, mostly open, easy to deploy and generally relaible (apart from the one of the potatos which seems to eat serial cables somehow :/).
<lvrp16>
broonie: thanks, that's awesome. glad to see people use them for upstream testing
<lvrp16>
broonie: if you have any issues, you can ping me directly and I'm happy to address.
<lvrp16>
with the hardware
<broonie>
lvrp16: thanks.
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
<apritzel>
broonie: where do you load the firmware from? SD card?
<broonie>
apritzel: yes, SD
thopiekar has quit [Ping timeout: 258 seconds]
sobkas has quit [Quit: sobkas]
thopiekar has joined #u-boot
littlebo1eep has joined #u-boot
sobkas has joined #u-boot
<kettenis>
apritzel: did you send a v2 of that VHE diff that I missed?
littlebobeep has quit [Ping timeout: 240 seconds]
<apritzel>
kettenis: oops, not really, I think. I made the fix, though.
<apritzel>
give me a few minutes ...
littlebobeep has joined #u-boot
littlebo1eep has quit [Ping timeout: 240 seconds]
<kettenis>
it's ok to get some sleep first ;)
littlebo1eep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
sobkas has quit [Quit: sobkas]
sobkas has joined #u-boot
thopiekar has quit [Ping timeout: 258 seconds]
thopiekar has joined #u-boot
sobkas has quit [Quit: sobkas]
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
sobkas has joined #u-boot
eternalforms has quit [Ping timeout: 248 seconds]
rfried has quit [Ping timeout: 248 seconds]
sobkas has quit [Remote host closed the connection]