From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Interesting tidbit: NetMos 9835 card, IRQ, and ACPI
Date: Fri, 25 Mar 2005 11:15:56 -0700 [thread overview]
Message-ID: <200503251115.56413.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <42431B0A.2000407@tls.msk.ru>
On Thursday 24 March 2005 12:54 pm, Michael Tokarev wrote:
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 193
> ttyS4 at I/O 0xa400 (irq = 193) is a 16550A
> ttyS5 at I/O 0xa000 (irq = 193) is a 16550A
>
> And oh.. now the ports are at ttyS[45], I used for them
> to be at ttyS[23]... Oh well...
Someday maybe we should make serial rely on PNP, and only
use the compiled-in table when PNP isn't available or is
turned off. Then ports would just be numbered sequentially
as they're discovered. And it would also help with the
current situation where ttyS0/1 are often discovered two
or three times.
> The patch does not apply to 2.6.11 - several hunks, notable
> all the parport stuff, fails. I'll dig into this a bit
> later today (hopefully). 8250 changes are enouth for the
> serial port to work, parallel port still does not work --
> without the missing patch hunks.
My patch was against the -mm tree, and I think one of the
differences between 2.5.11 and the -mm tree was the
removal of 9835 from parport_pc. Sounds like you've
figured that out already :-)
prev parent reply other threads:[~2005-03-25 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 19:02 Michael Tokarev
2005-03-24 19:16 ` Russell King
2005-03-24 19:54 ` Michael Tokarev
2005-03-25 18:15 ` Bjorn Helgaas [this message]
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=200503251115.56413.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=rmk+lkml@arm.linux.org.uk \
/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®