public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Chris Wedgwood <cw@f00f.org>
Cc: Erik Jacobson <erikj@subway.americas.sgi.com>,
	Christoph Hellwig <hch@infradead.org>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	Andrew Morton <akpm@osdl.org>, Pat Gefre <pfg@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Altix serial driver
Date: Mon, 28 Jun 2004 02:14:39 +0100	[thread overview]
Message-ID: <20040628021439.A17654@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040628003311.GA23017@taniwha.stupidest.org>; from cw@f00f.org on Sun, Jun 27, 2004 at 05:33:11PM -0700

On Sun, Jun 27, 2004 at 05:33:11PM -0700, Chris Wedgwood wrote:
> On Sun, Jun 27, 2004 at 07:24:34PM -0500, Erik Jacobson wrote:
> > Maybe you can help me clear it up then.  When I feed serial core the
> > name ttyS with TTY_MAJOR and minor 64, the registration fails.  If I
> > disable 8250 in the kernel config, the registration works for us.
> 
> I'm not sure why the 8250 code reserves/registers ttyS0 on Altix when
> do such hardware exists.  I vaguely recall patching it to prevent this
> in a hacky way.
> 
> I would like to know why the 8250 code is registering a driver for
> hardware that doesn't exist and see that fixed.

It's the way its always been done, and the way the tty layer works.
You register a range of ttys that you're going to be driving, and
you own those ttys whether or not you actually have hardware for
them.

You can't say "ok, I have ttyS1 and ttyS3, I'll leave ttyS0 and ttyS2
available for someone else to use" because the tty layer just doesn't
work like that.  It has the notion of a single driver for a range of
non-overlapping ttys.

Yes, it would be nice to get rid of that limitation, but we're in a
stable kernel series and the tty layer doesn't have a maintainer to
do the work...

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-06-28  1:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 14:48 [PATCH 2.6] Altix serial driver Pat Gefre
2004-06-23 15:06 ` Christoph Hellwig
2004-06-23 21:38 ` Andrew Morton
2004-06-23 21:54   ` Jesse Barnes
2004-06-25  3:15     ` Erik Jacobson
2004-06-25  8:31       ` Christoph Hellwig
2004-06-25 12:46         ` Erik Jacobson
2004-06-25 12:48           ` Christoph Hellwig
2004-06-25 13:00             ` Erik Jacobson
2004-06-26 23:52               ` Chris Wedgwood
2004-06-28  0:24                 ` Erik Jacobson
2004-06-28  0:33                   ` Chris Wedgwood
2004-06-28  1:14                     ` Russell King [this message]
2004-06-28  1:44                       ` Chris Wedgwood
2004-06-28  7:54                         ` Russell King
2004-06-28  8:14                           ` Chris Wedgwood
2004-06-28  9:02                           ` Russell King
2004-06-28 12:28                           ` Erik Jacobson
2004-06-28 19:04                             ` Pat Gefre
2004-06-28 19:13                               ` Andrew Morton
2004-06-28 19:47                                 ` Russell King
2004-06-28 20:57                                   ` Andrew Morton
2004-06-28 22:09                                 ` Pat Gefre
2004-06-28 22:20                                   ` Andrew Morton
2004-06-28 23:10                                     ` Russell King
2004-06-25 15:10         ` Jesse Barnes
2004-06-25 15:53           ` Christoph Hellwig
2004-06-25 20:45             ` Andrew Morton
2004-06-25 20:46               ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2004-06-22 16:16 Pat Gefre
2004-06-22 18:24 ` Andrew Morton
2004-06-22 18:36   ` Christoph Hellwig
2004-06-23 14:42     ` Pat Gefre
2004-06-23 15:02       ` Christoph Hellwig
2004-06-23 15:07         ` Erik Jacobson

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=20040628021439.A17654@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=cw@f00f.org \
    --cc=erikj@subway.americas.sgi.com \
    --cc=hch@infradead.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox