qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
camus has joined #u-boot
camus1 has joined #u-boot
camus has quit [Ping timeout: 244 seconds]
camus1 is now known as camus
thopiekar has quit [Ping timeout: 240 seconds]
mmu_man has quit [Ping timeout: 255 seconds]
thopiekar has joined #u-boot
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #u-boot
LeSpocky has quit [Ping timeout: 276 seconds]
sbach has quit [Remote host closed the connection]
LeSpocky has joined #u-boot
sbach has joined #u-boot
akaWolf has quit [Ping timeout: 264 seconds]
akaWolf has joined #u-boot
macromorgan has quit [Ping timeout: 244 seconds]
macromorgan has joined #u-boot
Wouter01001 has quit [Remote host closed the connection]
Wouter01001 has joined #u-boot
macromorgan has quit [Remote host closed the connection]
apritzel has joined #u-boot
guillaume_g has joined #u-boot
marc1 has quit [Ping timeout: 264 seconds]
marc1 has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
apritzel has quit [Ping timeout: 276 seconds]
stefanro has quit [Ping timeout: 255 seconds]
frieder has joined #u-boot
stefanro has joined #u-boot
mckoan|away is now known as mckoan
mmu_man has joined #u-boot
Wouter01001 has quit [Ping timeout: 240 seconds]
matthias_bgg has joined #u-boot
sszy has joined #u-boot
mmu_man has quit [Ping timeout: 276 seconds]
Wouter01001 has joined #u-boot
mmu_man has joined #u-boot
___nick___ has joined #u-boot
matthias_bgg has quit [Ping timeout: 240 seconds]
Xeroine has joined #u-boot
apritzel has joined #u-boot
<la_mettrie>
if hardware platform's register data is placed in u-boot and passed to OS's kernel, how/where is this register data from u-boot seen on the kernel code?
matthias_bgg has joined #u-boot
Xeroine has quit [Ping timeout: 252 seconds]
Xeroine has joined #u-boot
Xeroine has quit [Quit: Client closed]
Xeroine has joined #u-boot
Xeroine has quit [Quit: Client closed]
Xeroine has joined #u-boot
<hramrach>
what 'hardware platform's register data'?
<hramrach>
if it is, say, customary on a platfrom for the boot rom to place some hardware information in a CPU register u-boot can save that register and re-load it before executing Linux
<hramrach>
but this is very platform-specific
<la_mettrie>
i have assumed that u-boot's custom code may contain register data - memory addresses of device registers that kernel's generic device drivers may need - that it somehow passes to kernel
<la_mettrie>
i'm not 100 % sure though that i've understood the scheme
<j`ey>
la_mettrie: usually via the device tree
Wouter01001 has quit [Read error: Connection reset by peer]
Wouter01001 has joined #u-boot
mmu_man has quit [Ping timeout: 276 seconds]
<Tartarus>
Yes, you bodge up something to put it in, and pass it along via, the device tree
GNUtoo has quit [Read error: Connection reset by peer]
persmule has quit [Read error: Connection reset by peer]
GNUtoo has joined #u-boot
persmule has joined #u-boot
apritzel_ has joined #u-boot
torez has joined #u-boot
camus has quit [Quit: camus]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 272 seconds]
tsraoien has joined #u-boot
tsraoien has quit [Ping timeout: 276 seconds]
mmu_man has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
zibolo has quit [Ping timeout: 276 seconds]
frieder has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 276 seconds]
mmu_man has joined #u-boot
vagrantc has joined #u-boot
mckoan is now known as mckoan|away
guillaume_g has quit [Quit: Konversation terminated!]