From: Adam Belay <abelay@novell.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>, Greg KH <gregkh@suse.de>
Subject: Re: IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.]
Date: Fri, 11 Mar 2005 22:31:31 -0500 [thread overview]
Message-ID: <1110598291.12485.269.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0502192000140.14916@ppc970.osdl.org>
On Sat, 2005-02-19 at 20:02 -0800, Linus Torvalds wrote:
>
> On Sat, 19 Feb 2005, Steven Rostedt wrote:
> >
> > On Sat, 2005-02-19 at 18:10 -0800, Linus Torvalds wrote:
> >
> > > I _think_ it's the code in arch/i386/pci/fixup.c that does this. See the
> > >
> > > static void __devinit pci_fixup_transparent_bridge(struct pci_dev *dev)
> > >
> > > thing, and try to disable it. Maybe that rule is wrong, and triggers much
> > > too often?
> > >
> >
> > Linus,
> >
> > Thank you very much! That was it. The following patch made everything
> > look good.
>
> Ok. I've fired off an email to some Intel people asking what the
> real rules are wrt Intel PCI-PCI bridges. It may be that it's not that
> particular chip, but some generic rule (like "all Intel bridges act like
> they are subtractive decode _except_ if they actually have the IO
> start/stop ranges set" or something like that).
>
> If anybody on the list can figure the Intel bridge decoding rules out,
> please holler..
>
> Linus
Actually, I've ran into a similar situation on my hardware. After
looking into it for a while, I'm pretty sure it's actually a transparent
bridge (despite it not indicating such in the programing interface class
code). Have you heard anything more?
Thanks,
Adam
next prev parent reply other threads:[~2005-03-12 3:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 0:22 IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.] Steven Rostedt
2005-02-20 0:59 ` Linus Torvalds
2005-02-20 1:36 ` Steven Rostedt
2005-02-20 2:10 ` Linus Torvalds
2005-02-20 3:38 ` Steven Rostedt
2005-02-20 4:02 ` Linus Torvalds
2005-03-12 3:31 ` Adam Belay [this message]
2005-02-20 6:51 ` Linus Torvalds
2005-02-20 7:06 ` Linus Torvalds
2005-02-20 11:48 ` Steven Rostedt
2005-02-20 8:22 ` Russell King
2005-02-20 10:20 ` Russell King
2005-02-20 11:59 ` Steven Rostedt
2005-02-20 11:54 ` Steven Rostedt
2005-02-20 17:23 ` Linus Torvalds
2005-02-20 17:56 ` Linus Torvalds
2005-02-20 21:26 ` IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI David Härdeman
2005-02-21 4:19 ` IBM Thinkpad G41 PCMCIA problems [Was: Yenta TI: ... no PCI interrupts. Fish. Please report.] Steven Rostedt
2005-03-12 3:36 ` Adam Belay
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=1110598291.12485.269.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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