From: Russell King <rmk@arm.linux.org.uk>
To: David Hinds <dhinds@sonic.net>
Cc: Jochen Friedrich <jochen@scram.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
dahinds@users.sourceforge.net
Subject: Re: PCI1410 Interrupt Problems
Date: Tue, 12 Aug 2003 09:59:18 +0100 [thread overview]
Message-ID: <20030812095918.A10895@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030811120048.A13992@sonic.net>; from dhinds@sonic.net on Mon, Aug 11, 2003 at 12:00:48PM -0700
On Mon, Aug 11, 2003 at 12:00:48PM -0700, David Hinds wrote:
> I do think there is room for having some sane default settings to be
> used when an unconfigured bridge is detected. For most of the TI
> bridges, there is only one reasonable default for how to enable PCI
> interrupt delivery. The important part here is "unconfigured bridge":
> never fool with interrupt delivery on a bridge that has been set up
> by the BIOS, which covers essentially all laptops.
Note that I will be looking into this shortly - I've been putting off
a lot of kernel work over the last week due to the rediculously high
temperatures we've been experiencing in the UK, not wanting to add
any extra heat from either people or machines to an already baking
house.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-08-12 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 20:15 PCI1410 Interrupt Problems Jochen Friedrich
2003-08-03 21:23 ` Russell King
2003-08-03 21:52 ` Jochen Friedrich
2003-08-06 23:09 ` Russell King
2003-08-08 5:40 ` Jochen Friedrich
2003-08-08 8:51 ` Russell King
2003-08-08 17:09 ` Jochen Friedrich
2003-08-11 18:33 ` Jochen Friedrich
2003-08-11 19:00 ` David Hinds
2003-08-12 8:59 ` Russell King [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=20030812095918.A10895@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dahinds@users.sourceforge.net \
--cc=dhinds@sonic.net \
--cc=jochen@scram.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox