On Fri, Aug 14, 2015 at 7:45 PM, Ian Lepore <ian@xxxxxxxxxxx> wrote: > On Fri, 2015-08-14 at 09:27 -0500, Rob Herring wrote: >> Ian: >> > So if I want to write a FreeBSD i2c eeprom driver that uses DT data, >> > what are my choices? I have exactly one: make my driver essentially a >> > clone of the Linux driver, with all the same data hard-coded in source. >> >> Don't you already have these drivers w/o using DT? If you did, you >> would have this information already in the drivers. It wouldn't be a >> question of the binding being Linux specific, but rather can we move >> more of the data out of drivers and into DT. That is fundamentally a >> different issue than is a binding Linux specific. > > This last paragraph most eloquently illustrates the point I was trying > to make: From the point of view of someone who only knows about the > existing linux driver and how it is written, the current DT data is > perfect. It's exactly what that existing driver needs to know, and from > that position you can argue that it is thus the ONLY thing any driver > written by anyone would need to know. That assumes that everyone wants > to just clone the linux drivers (or in our case, because of licensing, > rewrite the drivers in a completely linux-compatible way that somehow > isn't simply copying them in violation of the GPL). For some reason I just get the feeling that the relationship between *BSD and Linux is lacking in communication. Or that the timing is wrong. The OS:es don't hate each other but they don't really understand each other either. So whenever some shared asset needs management there is a statement like "if you really love me, you should involve me more", from either side. And yes, it is the common human mistake of simply assuming everyone else in the world works exactly like me (and in worst case we assume others are plain stupid or a lesser imperfect version of ourselves if they don't). But as always, they are usually just thinking differently, smart in another way. So I think these communities need some relationship therapy. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
