|| ||Daniel Walker <dwalker-AT-codeaurora.org> |
|| ||Russell King - ARM Linux <linux-AT-arm.linux.org.uk> |
|| ||board/device file names, and machine names |
|| ||Tue, 02 Mar 2010 13:29:58 -0800|
|| ||linux-arm-msm-AT-vger.kernel.org, Pavel Machek <pavel-AT-ucw.cz>,
|| ||Article, Thread
I was wondering if you (or the list) had any suggestions for proper
names to use in these two cases. Under mach-msm we have tons of devices
that could be added, and it can sometimes be hard to isolate a sane
I'll use the Nexus One device as an example .. HTC originally called
this device the HTC Passion prior to release.. Google named the same
device "mahimahi" prior to release .. Then finally it was released as
Nexus One .
So one device has at least three names (more I'm sure),
Google has most of the code support under board files with the name
To me it makes a lot more sense to use a mass marketed name like "Nexus
One" .. Few people know what an HTC Passion is, and extremely few know
what "mahimahi" is.
Here is a link to mach-msm from Google's tree so you can see the naming
Another example of this is,
which in mainline we renamed to,
Dream is actually a released name, so it seems to make more sense.
However, there are many other names we could have used.
machine_is_xx names have a similar kind of problem .. However, it's lot
easier to mainline a machine_is_xxx name ..
Any comments welcome, since this stuff is disputed and up in the air.
I'm sure many other projects have faced similar problems also.
to post comments)