Bug 23953 - setserial changes irq setting for irq 9
Summary: setserial changes irq setting for irq 9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: setserial
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-13 16:39 UTC by Bill Gorder
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-19 13:03:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Bill Gorder 2001-01-13 16:39:24 UTC
I have a PCI modem (US Robotics model 3CP5610A).  The bus walk places 
the modem at port 0xd400 and irq 9 (from /proc/pci).  I use setserial 
to set the port and irq values, but setserial changes my irq 9 request 
to irq 2.  The man page for setserial has the statement, "On AT class 
machines, IRQ2 is seen as IRQ9 and Linux will interpret it in this 
way."  This may be fine for AT class machines, but this is disaster for 
PCI - irq 2 is assigned to the process controller for cascade 
interrupts.

This technique for configuring PCI modems is documented at 
http://www.o2.net/~gromitkc/3cp5610.txt with a pointer to this page 
from Red Hat.

Comment 1 Tim Waugh 2001-10-19 13:02:59 UTC
What exactly are the bad effects that you see? 


Comment 2 Tim Waugh 2001-10-19 13:36:49 UTC
Apprently this works fine in 7.1.  Closing.



Note You need to log in before you can comment on or make changes to this bug.