From: "Christian P. Schmidt" <charlie@digadd.de>
To: linux-kernel@vger.kernel.org
Subject: serial_pci and AC'97 Softmodems
Date: Thu, 05 Jul 2007 14:22:49 +0300 [thread overview]
Message-ID: <468CD489.8010205@digadd.de> (raw)
Hi,
Apparently the serial_pci module detects a lot of (non-existent?) serial
ports on my laptop:
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKG] -> GSI 3 (level, low)
-> IRQ 3
0000:00:08.0: ttyS1 at I/O 0x8828 (irq = 3) is a 8250
0000:00:08.0: ttyS2 at I/O 0x8840 (irq = 3) is a 8250
0000:00:08.0: ttyS3 at I/O 0x8850 (irq = 3) is a 8250
0000:00:08.0: ttyS4 at I/O 0x8860 (irq = 3) is a 8250
0000:00:08.0: ttyS5 at I/O 0x8870 (irq = 3) is a 8250
These are not serial ports, as
00:08.0 0703: 10b9:5457 (prog-if 00 [Generic])
Subsystem: 103c:0024
00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller (prog-if 00
[Generic])
Subsystem: Hewlett-Packard Company Pavilion ze4400 builtin Modem
Device
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 3
Region 0: Memory at d0016000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at 8800 [size=256]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Would it make sense to include a blacklist for these kind of "modem"
devices? I currently can only avoid those bogus serial ports by loading
the hsfmodem driver to block the IO region (yeah, 2.6.22 will bring the
possibility to leave 8250_pci out, I know...)
Regards,
Chris
reply other threads:[~2007-07-05 11:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=468CD489.8010205@digadd.de \
--to=charlie@digadd.de \
--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 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.