<Tartarus>
I've been reading along, yes, I want to see how this goes? I know how Siemens uses TI SoCs has been considered in this approach, and I think this works for phytec as well, but maybe not for your case yet? Or maybe it's just not clear enough how to do what you want, I'm not sure
monstr has quit [Ping timeout: 252 seconds]
ikarso has joined #u-boot
<mwalle>
Tartarus: as I said, I don't think it makes sense to just combine board specifics (even if they are the same for all boards at the moment) into one common dtsi. at least if it should be shared among the boards. I don't have any problem with creating my own copy of the binman.dtsi stuff. what i want to avoid is doing all the cleanup myself then and being told to integrate my board into the existing
<mwalle>
approach
<mwalle>
I mean there is a reason why there is MULTI_DTB_FIT
goliath has joined #u-boot
KREYREN_ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
naoki has quit [Quit: naoki]
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
ladis has joined #u-boot
enok has joined #u-boot
zsoltiv_ has quit [Ping timeout: 246 seconds]
zsoltiv_ has joined #u-boot
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
zsoltiv_ has quit [Ping timeout: 252 seconds]
zsoltiv_ has joined #u-boot
rfs613 has quit [Ping timeout: 260 seconds]
rfs613 has joined #u-boot
<xypron>
Is there a good way to display the MMC card detect value in U-Boot.
<calebccff>
xypron: how do you mean?
<xypron>
I want to know if SD-card removal is really detected or the GPIO is as a constant value.
<calebccff>
you want to figure out if the MMC detect GPIO on your board is working?
<calebccff>
"gpio status" with sdcard inserted/removed and comparing the two should show you that
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
sjhill_ has quit [Quit: leaving]
sjhill has joined #u-boot
slobodan__ has quit [Read error: Connection reset by peer]
slobodan__ has joined #u-boot
Stat_headcrabed has joined #u-boot
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
enok has quit [Ping timeout: 268 seconds]
enok has joined #u-boot
enok has quit [Ping timeout: 260 seconds]
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
slobodan__ has quit [Ping timeout: 268 seconds]
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
KREYREN__ has quit [Remote host closed the connection]
enok has joined #u-boot
<LeSpocky>
depends on who handles the gpio, right? some controllers do that native, for some the driver uses a gpio configured in dt
<LeSpocky>
iirc
mmu_man has quit [Ping timeout: 255 seconds]
GNUtoo has quit [Ping timeout: 260 seconds]
enok has quit [Ping timeout: 255 seconds]
mmu_man has joined #u-boot
tgamblin_ is now known as tgamblin
tgamblin has quit [Quit: Leaving]
slobodan has joined #u-boot
monstr has joined #u-boot
Stat_headcrabed has quit [Quit: Stat_headcrabed]
vagrantc has joined #u-boot
mckoan is now known as mckoan|away
ladis has quit [Quit: Leaving]
slobodan has quit [Read error: Connection reset by peer]
prabhakarlad has joined #u-boot
monstr has quit [Remote host closed the connection]
vagrantc has quit [Ping timeout: 256 seconds]
rvalue has quit [Ping timeout: 264 seconds]
slobodan has joined #u-boot
vagrantc has joined #u-boot
rvalue has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
mwalle has quit [Ping timeout: 256 seconds]
___nick___ has joined #u-boot
mmu_man has joined #u-boot
zsoltiv__ has joined #u-boot
zsoltiv_ has quit [Read error: Connection reset by peer]