From: Adam Belay <ambx1@neo.rr.com>
To: Amit Gurdasani <amitg@alumni.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EISA ID for PnP modem and resource allocation
Date: Mon, 29 Dec 2003 14:37:11 +0000 [thread overview]
Message-ID: <20031229143711.GA3176@neo.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0312261610200.1798@athena>
On Fri, Dec 26, 2003 at 04:51:53PM +0400, Amit Gurdasani wrote:
> I have a PROLiNK 1456VH internal Rockwell-based ISA PnP K56flex fax modem
> whose EISA ID seems not to be known to 8250_pnp.c. The ID is AEI0250 as
> reported in /sys/devices/pnp1/01:01/01:01.00/id and adding this into the
> pnp_dev_table[] allows the device to be found and enabled properly by the
> 8250 serial driver.
>
> A query: I'm using the serial IRQ autodetection and sharing support. In
> 2.4.23, the serial driver was able to get the first serial port (ttyS0) and
> this modem (ttyS2) to share IRQ 4. Now this is not happening, and each port
> (and modem) is claiming a unique IRQ. Am I doing anything wrong?
Without special hardware modifications, it is usually unsafe to share irqs
between isa devices.
>
> The reason I ask is that I also have a jumpered SB16 on IRQ 5, and loading
> the 8250 driver before the snd_sb16 driver results in the SB16's IRQ being
> allocated for the modem, which prevents the SB16 driver from loading.
> Loading the SB16 driver first results in resource starvation for the modem,
> and the 8250 driver is only able to set up the onboard serial ports ttyS0
> and ttyS1.
You may want to try changing the jumper on your SB16 to allow for PnP
autoconfiguration.
>
> In the meantime, I'm using the isapnptools to set up the modem with IRQ 4
> before loading either driver. The result is that the SB16 driver gets IRQ 5
> as needed, and ttyS0 is set up with IRQ 0 (is this OK?), but I'd really like
> to use the kernel ISA PnP support.
Could I please see a copy of your /proc/interrupts.
>
> (Kernel 2.4.23's kernel ISA PnP support and serial driver would
> automatically assign IRQ 4 to both ttyS0 and the modem [ttyS2].)
The 2.4 series was not always aware of motherboard devices such as serial ports.
Were you able to use ttyS0 and your modem at the same time?
Thanks,
Adam
next prev parent reply other threads:[~2003-12-29 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 12:51 EISA ID for PnP modem and resource allocation Amit Gurdasani
2003-12-29 14:37 ` Adam Belay [this message]
2003-12-29 23:59 ` Amit Gurdasani
2003-12-29 22:50 ` Adam Belay
2004-01-04 16:26 ` Russell King
2004-01-05 13:23 ` Amit Gurdasani
2004-01-26 19:22 ` Adam Belay
2004-01-29 6:57 ` Amit Gurdasani
2004-01-30 0:26 ` Adam Belay
2004-01-30 11:55 ` Amit Gurdasani
2004-02-01 23:37 ` Adam Belay
2003-12-30 16:20 ` Amit Gurdasani
2004-01-04 16:27 ` Russell King
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=20031229143711.GA3176@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=amitg@alumni.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/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