From: Chris Wedgwood <cw@f00f.org>
To: 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: Sun, 27 Jun 2004 18:44:43 -0700 [thread overview]
Message-ID: <20040628014443.GA24247@taniwha.stupidest.org> (raw)
In-Reply-To: <20040628021439.A17654@flint.arm.linux.org.uk>
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):
===== drivers/serial/8250.c 1.55 vs edited =====
--- 1.55/drivers/serial/8250.c 2004-04-17 02:48:54 -07:00
+++ edited/drivers/serial/8250.c 2004-06-27 18:42:55 -07:00
@@ -2175,6 +2175,12 @@
{
int ret, i;
+#if defined(__ia64__) && defined(ia64_platform_is)
+ /* SN2 cannot have 8250-like serial ports. */
+ if (ia64_platform_is("sn2"))
+ return -ENODEV;
+#endif
+
printk(KERN_INFO "Serial: 8250/16550 driver $Revision: 1.90 $ "
"%d ports, IRQ sharing %sabled\n", (int) UART_NR,
share_irqs ? "en" : "dis");
Completely untested of source, and we might want to move things around
a bit if early console stuff causes problems.
--cw
next prev parent reply other threads:[~2004-06-28 1:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:48 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 [this message]
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=20040628014443.GA24247@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®