From: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
To: Daniel James Laird <daniel.j.laird@nxp.com>, linux-mips@linux-mips.org
Subject: Re: [pnx833x_port]: device name prefix - ttyS or ttySA?
Date: Tue, 13 Jan 2009 20:13:10 +0200 [thread overview]
Message-ID: <fce2a370901131013r240abe16l576ef6269aba945f@mail.gmail.com> (raw)
In-Reply-To: <C13DBBE85AD6974B85C118C35890CA5F1A85149CC6@EU1RDCRDC1WX029.exi.nxp.com>
On Tue, Jan 13, 2009 at 7:09 PM, Daniel James Laird
<daniel.j.laird@nxp.com> wrote:
> I cant find the file you are talking about however
Sorry, I misspelled the file name. It's 'drivers/serial/pnx8xxx_uart.c' instead.
> I think that the major number should infact be 4 with a minor number of 64,65,66 etc. This seems to be what other devices do. This would mean you can still be ttyS... but not clash with SA1100 if that's what you mean.
You're wrong. There are lots of board specific serial drivers that
define special major-minor numbers. For example look at sc26xx,
mpc52xx_uart, bfin_5xx drivers. The problem with pnx8xxx_uart driver
is that it uses special major:minor numbers for generic ttyS* devices.
I think we need one of these changes:
1) make a special CONFIG_PNX8XXX_UART_TTYS option for switching
between ttyS*+4:64 and ttySA*+204:5 variants (see f.e. atmel_serial
driver). Of course this CONFIG_PNX8XXX_UART_TTYS option will be
disabled if CONFIG_SERIAL_8250 enabled.
2) Just stick with ttySA*+204:5 (not with ttyS*+204:5 as it's now).
Please tell me what you prefer and I'll send you a patch.
>
> With regards,
> Daniel Laird
>
> Daniel Laird, Software Engineer
> NXP Semiconductors, BU Home, BL STB
>
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Ihar Hrachyshka
> Sent: 2009 Jan 13 15:08
> To: linux-mips@linux-mips.org
> Subject: [pnx833x_port]: device name prefix - ttyS or ttySA?
>
> In 'drivers/serial/pnx833x_port.c' we define the prefix for UART serial
> device as "ttyS". Anyway, we use major:minor numbers for SA1100 serial
> driver (that are 204:5). Why don't we use "ttySA" prefix then? That's
> what different embedded build systems expect for populating /dev (f.e.
> buildroot).
>
>
>
prev parent reply other threads:[~2009-01-13 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 15:07 [pnx833x_port]: device name prefix - ttyS or ttySA? Ihar Hrachyshka
2009-01-13 17:30 ` Florian Fainelli
2009-01-13 18:15 ` Ihar Hrachyshka
2009-01-13 17:39 ` Sergei Shtylyov
[not found] ` <C13DBBE85AD6974B85C118C35890CA5F1A85149CC6@EU1RDCRDC1WX029.exi.nxp.com>
2009-01-13 18:13 ` Ihar Hrachyshka [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=fce2a370901131013r240abe16l576ef6269aba945f@mail.gmail.com \
--to=ihar.hrachyshka@gmail.com \
--cc=daniel.j.laird@nxp.com \
--cc=linux-mips@linux-mips.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