From: Chris Wedgwood <cw@f00f.org>
To: Erik Jacobson <erikj@subway.americas.sgi.com>
Cc: 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: Sun, 27 Jun 2004 17:33:11 -0700 [thread overview]
Message-ID: <20040628003311.GA23017@taniwha.stupidest.org> (raw)
In-Reply-To: <Pine.SGI.4.53.0406271908390.524706@subway.americas.sgi.com>
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.
> 1) You think we can some how use ttySX with our driver. I need more
> information for that as I couldn't get it to work with serial
> core.
You can, I did this. It was probably a horrible hack, I really can't
recall anymore. I don't know if that code ever got out or what
happened to it. Maybe there are some PVs about it somewhere? I'm
pretty sure the patches got sent out for vendor inclusion.
I would simply find out why the 8250 driver is preventing a
registration for you and go down that path.
The other issue is what if someone puts a serial-port/modem card in an
Altix so you do have 8250/16550-like hardware? I'm not sure that's
sensible though and they probably deserves to break.
I guess in general you have a bigger problem though, you can have tens
of serial ports on a large system and if you want to support them all
(or have the option of doing so) something more sensible needs to be
figure out.
--cw
next prev parent reply other threads:[~2004-06-28 0:34 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 [this message]
2004-06-28 1:14 ` Russell King
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=20040628003311.GA23017@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.