public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@sonic.net>
To: Jochen Friedrich <jochen@scram.de>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	dahinds@users.sourceforge.net
Subject: Re: PCI1410 Interrupt Problems
Date: Mon, 11 Aug 2003 12:00:48 -0700	[thread overview]
Message-ID: <20030811120048.A13992@sonic.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0308112028300.10344-100000@gfrw1044.bocc.de>

On Mon, Aug 11, 2003 at 08:33:23PM +0200, Jochen Friedrich wrote:
> Hi Russell,
> 
> > Unfortunately, there are some hacks in the kernel at the moment which
> > mess up the Cardbus IRQ routing by touching this register - the kernel
> > should not be the one to play with hardware design specific register
> > settings, especially when they are applied without thought across
> > many hardware variants.
> 
> after thinking a bit, i believe, you're right here. Initially, i just
> wanted to have an option to mess with this register, but there is already
> the setpci tool which can do exactly this. So for now, i just added the
> setpci command to my modules.conf and i'm set.
> 
> It's just a shame that PCI/Cardbus bridge manufacturers try to save a few
> cents by not soldering the configuration EEPROM to their board and supply
> some specialized drivers for Win just to make their crap work. So if you
> place 2 different cards in the same PC with the same PCI1410 but different
> pin mapping, you're doomed...

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.

-- Dave

  reply	other threads:[~2003-08-11 19:13 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 [this message]
2003-08-12  8:59           ` 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=20030811120048.A13992@sonic.net \
    --to=dhinds@sonic.net \
    --cc=dahinds@users.sourceforge.net \
    --cc=jochen@scram.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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