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 08:54:30 +0100 [thread overview]
Message-ID: <20040628085429.C32206@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040628014443.GA24247@taniwha.stupidest.org>; from cw@f00f.org on Sun, Jun 27, 2004 at 06:44:43PM -0700
On Sun, Jun 27, 2004 at 06:44:43PM -0700, Chris Wedgwood wrote:
> On Mon, Jun 28, 2004 at 02:14:39AM +0100, Russell King wrote:
> > 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.
>
> How about this (yes, it's a hack but it's really not that bad and will
> get things working until we can fix this up in 2.7.x):
If you're going to do that, why not just disable 8250 in the kernels
configuration? It has exactly the same effect. With the change you
propose, you can't even use 8250 for PCMCIA serial cards.
--
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
next prev parent reply other threads:[~2004-06-28 7:54 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
2004-06-28 1:44 ` Chris Wedgwood
2004-06-28 7:54 ` Russell King [this message]
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=20040628085429.C32206@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