From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: mj@suse.cz
Subject: PCI IRQ routing on buggy BIOSes
Date: Mon, 8 Jan 2001 23:27:13 MET-1 [thread overview]
Message-ID: <1206565040F1@vcnet.vc.cvut.cz> (raw)
Hi,
following happened on my well-known SMP VIA based GA6VXD7 motherboard.
Last week on Thursday I decided to connect printer to the box. To do that
I had to switch parallel port mode from ECP to Normal (because of I
had problems with that printer). Today I found, that since that time
(Thu 3:57) my second bttv, which is used for teletext grabbing, stopped
functioning.
After some testing I found that correct IRQ is 19, and not 18... And after
turning some options in BIOS I found that it is related to parallel port
setting:
Parallel port setting: Normal ECP driver/location
B0,I7,P3 18 19 usb 00:07.2 (not used)
B0,I7,P3 18 19 usb 00:07.3 (not used)
B0,I10,P0 18 18 bttv0 0:0a.0
B0,I11,P0 18 19 bttv1-video 0:0b.0
B0,I11,P0 18 19 bttv1-audio 0:0b.1
B0,I13,P0 17 17 eth0 0:0d.0
B0,I14,P0 18 18 dsp0 0:0e.0
B1,I0,P0 16 16 dri0 1:00.0
Of course table reported for ECP mode is correct one. Anybody have any
idea how to get it to work in Normal/EPP mode without hardwiring this
routing table to kernel? There are no complaints in system dmesg.
Every IRQ in BIOS is selected as PCI/PnP, as there are no ISA devices
in box (except on-board southbridge COM/LPT). PnP OS setting does not
matter.
There is also one difference at BIOS info screen: in first case (normal),
it prints _all_ these devices on IRQ10, while in ECP mode some devices
use IRQ5. Probably another bug in Award core, they generate wrong
PIRQ routing table when couple (all 4) PIRQ are routed to same 8259 IRQ :-(
This leaves open why all devices use IRQ10 in 8259 mode - are other really
used by onboard unshareable ACPI/RTC/IDE/COM/LPT/PS2/KBD/TIMER/FLOPPY?!
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-08 22:28 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=1206565040F1@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@suse.cz \
/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®