board/device file names, and machine names

[tytso@google.com (Theodore Tso)]

On Tue, Mar 2, 2010 at 5:56 PM, Brian Swetland <swetland@google.com> wrote:

>
>
> We would, of course, prefer to keep the board named mahimahi for all
> the reasons that have been mentioned in various previous discussions
> around trout, etc:
> 1. This was the name used during development for the platform.
> 2. This is the name the bootloader uses and the production bootloader
> passes module parameters, etc under this name
>

This to me is the biggest thing to get right --- if there is deployed
userspace which is using this name (mahimahi) in the bootloader to boot the
machine, then changing this means that it adds a barrier to users who want
to use the standard device userland, but who want to try testing their own
kernel built from mainline.   Assuming that we eventually solve the rest of
the issues, it would be a darned shame that just because the upstream
community wanted to be "helpful" in renaming the device, someone wanting to
build from upstream sources has a to apply a patch reversing the rename so
that it will actually *work* on a standard Nexus One....

-- Ted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100303/eab4760b/attachment.htm>