linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tytso@google.com (Theodore Tso)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Wed, 3 Mar 2010 14:22:37 -0500	[thread overview]
Message-ID: <5fca72811003031122r21402133n4ec36193926f51d1@mail.gmail.com> (raw)
In-Reply-To: <5fca72811003031108n6d4799cbmf9254ab5d9df69d8@mail.gmail.com>

Trying again in plain text to avoid the
HTML-means-mail-is-automatically-SPAM filter.

-- Ted

On Wed, Mar 3, 2010 at 2:08 PM, Theodore Tso <tytso@google.com> wrote:
> 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
>
>
>

  reply	other threads:[~2010-03-03 19:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 21:29 board/device file names, and machine names Daniel Walker
2010-03-02 22:56 ` Brian Swetland
2010-03-02 23:29   ` Daniel Walker
2010-03-02 23:38     ` Brian Swetland
2010-03-03  3:42     ` Bill Gatliff
2010-03-03  3:36   ` Bill Gatliff
2010-03-03  8:00     ` Brian Swetland
2010-03-03 19:08   ` Theodore Tso
2010-03-03 19:22     ` Theodore Tso [this message]
2010-03-03 19:24     ` Russell King - ARM Linux
2010-03-02 23:51 ` Russell King - ARM Linux
2010-03-03  0:39   ` Daniel Walker
2010-03-03  0:47     ` Tim Bird
2010-03-03  0:52       ` Daniel Walker
2010-03-03  1:01         ` Brian Swetland
2010-03-03  3:52     ` Bill Gatliff
2010-03-03  8:42     ` Russell King - ARM Linux
2010-03-03  9:17       ` Pavel Machek
2010-03-03  9:47         ` Russell King - ARM Linux
2010-03-03 10:00           ` Pavel Machek
2010-03-03 10:08             ` Russell King - ARM Linux
2010-03-03 10:18               ` Pavel Machek
2010-03-03 10:19                 ` Russell King - ARM Linux
2010-03-03 14:24                   ` Pavel Machek
2010-03-03 14:38       ` Daniel Walker
2010-03-03 22:08   ` Nicolas Pitre
2010-03-03 22:27     ` Brian Swetland
2010-03-03  3:25 ` Bill Gatliff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fca72811003031122r21402133n4ec36193926f51d1@mail.gmail.com \
    --to=tytso@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).