linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Remco Treffkorn <remco@rvt.com>
Cc: Dan Malek <dan@embeddededge.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Tom Rini <trini@kernel.crashing.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC)
Date: Mon, 29 Jul 2002 21:18:29 +0100	[thread overview]
Message-ID: <20020729211829.F25451@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200207291246.43134.remco@rvt.com>; from remco@rvt.com on Mon, Jul 29, 2002 at 12:46:42PM -0700


On Mon, Jul 29, 2002 at 12:46:42PM -0700, Remco Treffkorn wrote:
> On Monday 29 July 2002 12:09, Dan Malek wrote:
> > or a mix of both.  The problems to solve are drivers fighting over minor
> > device numbers and assumptions about the system console.
> >
>
> Drivers need not fight about minor numbers. That can be simply handled:
>
> int get_new_serial_minor()
> {
>     static int minor;
>
>     return minor++;
> }
>
> Any serial driver can call this when it initializes a new uart.
> Hot pluggable drivers have to hang on to their minors, and
> re-use.

It's a possible solution, if we get the ability for drivers to hang
on to their minors.  However, I get the feeling that this isn't going
to happen before 2.6.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-07-29 20:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29  4:08 Serial core problems on embedded PPC David Gibson
2002-07-29  9:00 ` Russell King
2002-07-29 14:44   ` Tom Rini
2002-07-29 17:17     ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Russell King
2002-07-29 17:43       ` Tom Rini
2002-07-29 18:13         ` Benjamin Herrenschmidt
2002-07-29 19:07           ` Tom Rini
2002-07-29 19:09           ` 3 Serial issues up for discussion (was: " Dan Malek
2002-07-29 19:46             ` Remco Treffkorn
2002-07-29 20:18               ` Russell King [this message]
2002-07-30  2:54               ` 3 Serial issues up for discussion David S. Miller
2002-07-29 18:15         ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Matt Porter
2002-07-29 17:47       ` [parisc-linux] " Christoph Plattner
2002-07-29 22:19       ` Matthew Wilcox
2002-07-30  2:51       ` 3 Serial issues up for discussion David S. Miller
2002-08-02  6:01     ` symbol card with orinoco_cs on mpc823 shaowei dai
2002-08-02  6:23       ` David Gibson
2002-08-02  6:36         ` Matthew Locke
2002-08-02  7:01           ` shaowei dai
     [not found]       ` <3D4AC468.83BCD667@opensource.se>
2002-08-03  1:30         ` shaowei dai
2002-07-30  1:12   ` Serial core problems on embedded PPC David Gibson

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=20020729211829.F25451@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=remco@rvt.com \
    --cc=trini@kernel.crashing.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).