mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pazzo Da Legare <pazzodalegare@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NEWBIE: how to change serial device<->port association
Date: Thu, 29 Jan 2009 15:16:39 +0100	[thread overview]
Message-ID: <1a26b4920901290616r40c1edd0tec62d0e6bf24dc9@mail.gmail.com> (raw)
In-Reply-To: <20090129134537.12121834@lxorguk.ukuu.org.uk>

Dear Alan,

Thank you very much for your help.
I'm going to have a look at the table you mentioned. Yes, I know that
usually one should make the selection from application, in my case I'm
trying to uniform two different hardware maintaining  the
configuration for applications (running on both).

The hws have a different combination of kind serials and I would like
to present the same ttyS* to applications. I need to have different
kernel configuration so I thought I could uniform things there....I'm
going to evaluate the hardness


p

2009/1/29 Alan Cox <alan@lxorguk.ukuu.org.uk>:
> On Thu, 29 Jan 2009 12:02:49 +0100
> Pazzo Da Legare <pazzodalegare@gmail.com> wrote:
>
>> Dear ML,
>>
>> how can I instruct the kernel (if possible) to map a certain serial
>> port to a specific device ttySx?
>
> The kernel mapping defaults are from a table so you could recompile
> the kernel. However applications should always let you select a serial
> port.
>
> Alan
>

  reply	other threads:[~2009-01-29 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 11:02 Pazzo Da Legare
2009-01-29 12:43 ` Jan Engelhardt
2009-01-29 12:54   ` Oliver Neukum
2009-01-29 15:04     ` Pazzo Da Legare
2009-01-29 13:45 ` NEWBIE: " Alan Cox
2009-01-29 14:16   ` Pazzo Da Legare [this message]
2009-01-29 16:06     ` Alan Cox
2009-01-29 16:22       ` Jiri Kosina
2009-01-29 16:34         ` Alan Cox
2009-01-29 16:38           ` Pazzo Da Legare

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=1a26b4920901290616r40c1edd0tec62d0e6bf24dc9@mail.gmail.com \
    --to=pazzodalegare@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®