On Wed, Apr 15, 2015 at 09:17:13PM +0200, Paul Kocialkowski wrote: > Le mercredi 15 avril 2015 à 10:29 +0200, Maxime Ripard a écrit : > > On Tue, Apr 14, 2015 at 07:15:24PM +0200, Paul Kocialkowski wrote: > > > Le mardi 14 avril 2015 à 16:47 +0200, Maxime Ripard a écrit : > > > > On Tue, Apr 14, 2015 at 04:29:08PM +0200, Paul Kocialkowski wrote: > > > > > Le mardi 14 avril 2015 à 16:22 +0200, Maxime Ripard a écrit : > > > > > > On Tue, Apr 14, 2015 at 04:14:24PM +0200, Paul Kocialkowski wrote: > > > > > > > > > I understand the point though, that it can be > > > > > > > > > seen as an ABI (don't break the ABI), but it would be a shame > > > > > > > > > for us to > > > > > > > > > this as a pretext to not correct our mistake. > > > > > > > > > > > > > > > > > > Don't get me wrong, I don't like breaking ABIs more than the > > > > > > > > > next guy > > > > > > > > > (even though I fear Hans is starting to think this is > > > > > > > > > becoming kind of > > > > > > > > > habit for me), but this is really borderline. > > > > > > > > > > > > > > > > Nothing borderline about it, take a standard Fedora or Debian > > > > > > > > image, > > > > > > > > both of which rely on the dtb name embedded in the u-boot > > > > > > > > binary, > > > > > > > > change the dtb name in the kernel, upgrade the kernel, try to > > > > > > > > boot, > > > > > > > > and voila the board will not boot (and no the old dtb file will > > > > > > > > not > > > > > > > > help, as each kernel build has its own dir with dtb files). > > > > > > > > > > > > > > > > Really this is as hard an ABI as one can get, please do not > > > > > > > > break it. > > > > > > > > > > > > > > Okay that makes sense, let's forget about the device-tree side > > > > > > > then. > > > > > > > > > > > > If you have some suggestions for future DT names, I'm definitely > > > > > > open > > > > > > to it though. > > > > > > > > > > Well, I think the best thing to do is to agree on a global naming > > > > > scheme > > > > > that allows spaces, dashes upper-case and lower-case and just apply > > > > > rules to convert that name to each particular project. > > > > > > > > > > The rules for device-tree names would look something like: > > > > > * replace spaces with dashes > > > > > * replace upper-case by lower-case > > > > > > > > How is that different from what we're doing right now? > > > > > > Not very different of course. The difference only lies in that > > > global naming scheme. > > > > What is this naming scheme then? > > Well, the discussion has started on the other part of the thread. I > think we've agreed so far that it should be: [Vendor]_[Device], except > in a few cases where [Vendor]_ should be omitted: > > * When the vendor (or design maker) cannot be identified precisely > * When the device can clearly be identified without mentioning the > vendor, due to a certain renown in the community: I'm thinking of > Cubieboard, Cubietruck and the Olimex devices. This clearly doesn't > apply to devices like the AW1 produced by Ainol. > > Also, boards should have a name that matches the officiel product name, > especially with regard to the use of caps, dashes a spaces. > > I'll try to come up with a list of what changes this implies precisely > (for each device).
I'm interested, because it really looks like it's what we're already using. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
