From: Yuli Barcohen <yuli@arabellasw.com>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8xx: Using SCM/SCC and standard 16C550 Uarts together...
Date: Wed, 12 Jan 2005 14:18:10 +0200 [thread overview]
Message-ID: <16869.5506.381522.29009@astp0002.localdomain> (raw)
In-Reply-To: <200501121255.56374.david.jander@protonic.nl>
>>>>> David Jander writes:
David> On Wednesday 12 January 2005 10:59, Demke Torsten-atd012
David> wrote:
Demke> I dont know exactly the state of the DENX kernel, but in the
Demke> standard kernel the 8xx UART driver and the 16550 driver are
Demke> using the same device numbers (TTY_MAJOR) and device names
Demke> (/dev/ttySx). You have to change one of them.
David> You are right! What now? I cannot go around and change
David> TTY_MAJOR! Is it true then, that you normally cannot have a
David> mix of non-16550 uarts and 16550 uarts on the same system,
David> without doing nonstandard things with major numbers?
We've got such a mix but we use completely different MPC8xx support
infrastructure. Our SCC/SMC UART driver takes care of possible external
UARTs (it uses the same major number but configurable minor).
David> Should maybe arch/ppc/8xx_io/uart.c use another major number?
Then you'll have to change all applications using standard device names
(ttySx).
--
========================================================================
Yuli Barcohen | Phone +972-9-765-1788 | Software Project Leader
yuli@arabellasw.com | Fax +972-9-765-7494 | Arabella Software, Israel
========================================================================
next prev parent reply other threads:[~2005-01-12 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 9:59 MPC8xx: Using SCM/SCC and standard 16C550 Uarts together Demke Torsten-atd012
2005-01-12 11:55 ` David Jander
2005-01-12 12:18 ` Yuli Barcohen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 14:46 Demke Torsten-atd012
2005-01-12 9:51 David Jander
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=16869.5506.381522.29009@astp0002.localdomain \
--to=yuli@arabellasw.com \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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