All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abdoulaye Walsimou GAYE <awg@embtoolkit.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Charles Manning <manningc2@actrix.gen.nz>, linux-omap@vger.kernel.org
Subject: Re: Is changing serial from /dev/ttySx to /dev/ttyOx a good idea?
Date: Mon, 20 Dec 2010 08:20:51 +0100	[thread overview]
Message-ID: <4D0F03D3.7040506@embtoolkit.org> (raw)
In-Reply-To: <AANLkTi=P58XerK8jdyvfT9JS6tU3U11tYP=KH4_B-cn=@mail.gmail.com>

On 12/20/2010 04:04 AM, Ming Lei wrote:
> Hi,
>
> 2010/12/20 Charles Manning<manningc2@actrix.gen.nz>:
>> Hi All
>>
>> With the change to the new omap-serial stuff, the device names have changed
>> from /dev/ttySn to /dev/ttyOn.
>>
>> Using the "fit/form/function" argument, this would seem to be a bad idea.
>>
>> The kernel does not exist in a vacuum. It is surrounded by u-boot scripts,
>> command line options, init scripts etc etc. Flipping back and forth between
>> 2.6.36 and 2.6.37 kernels for testing purposes needs these to be changed.
>> Annoying and anti-productive.
>>
>> Isn't it just better to just replace the ttyOn name with ttyS. That would make
>> a far smoother transition.
>>
>> Thoughts?
> In fact, the transition is not friendly indeed for a user. I don't know why
> the transition is introduced, for what purpose? Who can give a explanation?
>
> thanks,

Hello,
And another question, why there is no entry in Documentation/devices.txt?
Regards,
AWG

      parent reply	other threads:[~2010-12-20  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20  2:46 Is changing serial from /dev/ttySx to /dev/ttyOx a good idea? Charles Manning
2010-12-20  3:04 ` Ming Lei
2010-12-20  4:28   ` Abraham Arce
2010-12-20  7:34     ` Ming Lei
2010-12-20 11:21       ` Koen Kooi
2010-12-20  7:20   ` Abdoulaye Walsimou GAYE [this message]

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=4D0F03D3.7040506@embtoolkit.org \
    --to=awg@embtoolkit.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=tom.leiming@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.