qschulz has quit [Remote host closed the connection]
jclsn9 has quit [Ping timeout: 256 seconds]
qschulz has joined #u-boot
jclsn9 has joined #u-boot
vagrantc has quit [Quit: leaving]
jclsn9 has quit [Ping timeout: 268 seconds]
jclsn9 has joined #u-boot
<marex>
sjg1: is there some way to say that a driver must be also probed, not just bound ?
<marex>
e.g. for a misc driver which does poke a few registers during HW init and that's it
<marex>
Tartarus: ^
jclsn9 has quit [Quit: Ping timeout (120 seconds)]
jclsn9 has joined #u-boot
jclsn9 has quit [Ping timeout: 248 seconds]
jclsn9 has joined #u-boot
thopiekar_ has joined #u-boot
thopiekar has quit [Killed (lithium.libera.chat (Nickname regained by services))]
thopiekar_ is now known as thopiekar
jclsn9 has quit [Ping timeout: 256 seconds]
jclsn9 has joined #u-boot
jclsn9 has quit [Ping timeout: 248 seconds]
jclsn9 has joined #u-boot
<Forty-Bot>
marex: board_init ;)
jclsn9 has quit [Ping timeout: 248 seconds]
jclsn9 has joined #u-boot
mripard_ has quit [Ping timeout: 246 seconds]
mripard_ has joined #u-boot
jclsn9 has quit [Ping timeout: 248 seconds]
jclsn9 has joined #u-boot
<marex>
Forty-Bot: I dont want to hack it in code
<Forty-Bot>
well, you can probe the driver there
<marex>
Forty-Bot: I dont want to hack it in code
<Forty-Bot>
then figure out a way to make it required by a "real" driver
<marex>
... is what my original question was about
<Forty-Bot>
well, the right way to do that depends on what "poking a few registers" is actually doing
<marex>
Forty-Bot: run the .probe() callback, that's what it means
<Forty-Bot>
right, but why do those registers need to be poked
<marex>
Forty-Bot: you can literally substitute "run the .probe() callback" for "poke a few registers"
<Forty-Bot>
if all you want to do is probe the driver
<Forty-Bot>
I don't see why you're opposed to board_init
<marex>
Forty-Bot: I dont want to hack it in code
<Forty-Bot>
do a dummy read with the misc command and put that in preload
<marex>
again, workaround, no
<Forty-Bot>
make it a clock driver and use assigned-clocks in the device tree
<marex>
this line of discussion is terminated
<Forty-Bot>
:P
jclsn9 has quit [Ping timeout: 268 seconds]
jclsn9 has joined #u-boot
jclsn9 has quit [Ping timeout: 256 seconds]
mmu_man has quit [Ping timeout: 272 seconds]
jclsn9 has joined #u-boot
jclsn9 has quit [Ping timeout: 268 seconds]
jclsn9 has joined #u-boot
jclsn9 has quit [Ping timeout: 256 seconds]
jclsn9 has joined #u-boot
sobkas has quit [Quit: sobkas]
swiftgeek has quit [Ping timeout: 268 seconds]
swiftgeek has joined #u-boot
<sjg1>
marex: no but there should be. Perhaps a driver flag. We could use it for x86 PCI too
crb has joined #u-boot
akaWolf has quit [Ping timeout: 268 seconds]
akaWolf has joined #u-boot
sobkas has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 260 seconds]
GNUtoo has quit [Ping timeout: 240 seconds]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
GNUtoo has joined #u-boot
___nick___ has joined #u-boot
Net147 has quit [Quit: Quit]
Net147 has joined #u-boot
Net147 has joined #u-boot
Net147 has quit [Changing host]
baltazar has quit [Remote host closed the connection]
mmu_man has joined #u-boot
Mike23 has joined #u-boot
Mike23 has quit [Quit: Client closed]
mmu_man has quit [Ping timeout: 256 seconds]
vagrantc has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
<flyback>
well trying to test a new u-boot binary before flashing it by loadb it into ram then executing it
<flyback>
but I was getting illegal instruction error and reboot
<flyback>
turns out it does that even if you don't load anything into ram
<flyback>
so I guess I am doing it wrong
<flyback>
could it be you don't start at address 0 the start of the binary?
<flyback>
this wouldn't be a problem if qemu worked but appentely it got broken a long time ago
<flyback>
might try teh old version that is in my ubuntu 10.04 vm I made to build u-boot since newer stuff either has broken cross compilers or the eldk toolkit won't load
* flyback
needs to setup a vpn to work, trying to rdp thru 4 machines is a pain in the ass
<flyback>
this is so rediculous
<flyback>
nevermind folks
<flyback>
I took the board down
<flyback>
done fighting with it
<flyback>
at least till after the move sometime end of year
___nick___ has quit [Ping timeout: 268 seconds]
sobkas has quit [Quit: sobkas]
sbach has quit [Read error: Connection reset by peer]