mmu_man has quit [Remote host closed the connection]
mmu_man has joined #u-boot
wenwuZhang has joined #u-boot
wenwuZhang has quit [Remote host closed the connection]
<Forty-Bot>
shoul u-boot and Linux dtbs be compatible, or just the dts?
Xavier7 has joined #u-boot
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 256 seconds]
sdfgsdfg has joined #u-boot
wenwuZhang has joined #u-boot
wenwuZhang has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 252 seconds]
wenwuZhang has joined #u-boot
wenwuZhang has quit [Remote host closed the connection]
behanw has quit [Quit: Connection closed for inactivity]
camus has joined #u-boot
LeSpocky has quit [Ping timeout: 256 seconds]
LeSpocky has joined #u-boot
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 252 seconds]
Xavier7 has quit [Quit: IRcap 8.72 ]
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 256 seconds]
camus has quit [Quit: camus]
wenwuZhang has joined #u-boot
wenwuZhang has quit [Remote host closed the connection]
Lokis has joined #u-boot
ad__ is now known as kernelspace
camus has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
camus1 has joined #u-boot
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
pgreco has quit [Ping timeout: 252 seconds]
Lokis has quit [Read error: Connection reset by peer]
Lokis has joined #u-boot
pgreco has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
camus1 has joined #u-boot
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
v0|d has joined #u-boot
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
redbrain has joined #u-boot
mmu_man has joined #u-boot
camus has quit [Quit: camus]
sdfgsdfg has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
wenwuZhang has joined #u-boot
wenwuZhang has quit [Ping timeout: 256 seconds]
wenwuZhang has joined #u-boot
wenwuZhang has quit [Ping timeout: 252 seconds]
camus has joined #u-boot
elvishjerricco has quit [Ping timeout: 265 seconds]
elvishjerricco has joined #u-boot
mmu_man has joined #u-boot
<sjg1>
milkylainen: I have the EFI thing building and working I think. How can I get your sign-off on the patches? Can you perhaps reply with it on the mailing list?
<milkylainen_>
sjg1: 64-bit?
<milkylainen_>
sjg1: Sure.
<sjg1>
milkylainen_: Yes
<sjg1>
milkylainen_: OK
<milkylainen_>
sjg1: will you be sending a new series?
<sjg1>
milkylainen_: Yes will send in half an hour
<milkylainen_>
Ack.
<milkylainen_>
Does u-boot use tested-by?
<sjg1>
milkylainen_: Yes
sdfgsdfg has quit [Quit: ZzzZ]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
vagrantc has joined #u-boot
jybz has quit [Ping timeout: 260 seconds]
Lokis has quit [Ping timeout: 252 seconds]
jybz has joined #u-boot
mmu_man has quit [Quit: Lost terminal]
mmu_man has joined #u-boot
mmu_man has quit [Client Quit]
mmu_man has joined #u-boot
Guest30 has joined #u-boot
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 256 seconds]
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 245 seconds]
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 252 seconds]
<Forty-Bot>
should device-tree bindings for u-boot drivers be binary compatible with Linux?
<Forty-Bot>
e.g. should using the same dtb for U-Boot and Linux work
<apalos>
Forty-Bot: you shouldnt really be asking questions like this :D
<Forty-Bot>
or do we just try to have source-level compatibility
<apalos>
Joking, there's just a huge ongoing discussion in the ML for that
<apalos>
Forty-Bot: some DTs work, some dont
<Forty-Bot>
well, I'm reviewing a driver and where Linux has "#define FOO_BAR 5", the submitted driver has "#define FUBAR 6"
<apalos>
ideally whatever is on the kernel DT source should work reasonably well with u-boot
<apalos>
however there's cases were that isnt happening (hopefully yet)
<Forty-Bot>
I wonder if we have this written down somewhere...
<Forty-Bot>
I would really like to be able to say "here is our policy; please write your driver so we can use the same dtbs"
<apalos>
you can,
<apalos>
well let's back up a bit
<apalos>
DT is a *spec*. The .dts files are maintained in the linux kernel partially for historical reasons and partially for convenience
<apalos>
Since a lot of people read that list
<apalos>
However we should try to adhere to the DT spec as much as we can
<apalos>
and that's what linux is mostly trying to do
<apalos>
So unless that diff is a u-boot specific binding (u-boot has some non yet upstreamed bindings for it;s own usage)
<apalos>
It's reasonable to go back and ask that
<Forty-Bot>
ok, so I guess the real question is "is include/dt-bindings" a part of the device tree spec for a given device?
<Forty-Bot>
or is it just the numeric identifiers there?