From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net, mingo@redhat.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: PCI MAINTAINER change
Date: Mon, 21 Apr 2008 09:18:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0804210914030.2779@woody.linux-foundation.org> (raw)
In-Reply-To: <200804210855.28405.jbarnes@virtuousgeek.org>
On Mon, 21 Apr 2008, Jesse Barnes wrote:
>
> And now I get to figure out just how much trouble I've gotten myself into...
Mwhahahaaa! Sucker. You'll find out.
The good news is that most of the time, the PCI code works fine. The bad
news is that when it doesn't work, it's usually due to something *really*
odd, like some magic motherboard device that has magic resources that
aren't part of the standard PCI resource set and that clash with some of
our resource allocation.
And they don't show up in the PnP lists because Windows never put anything
that could clash with them, so there was no reason for the BIOS engineers
to bother.
IOW, it's usually almost totally undebuggable crud like "driver X doesn't
work on my machine", and then it turns out that it only happens on that
particular motherboard that is totally identical to all other motherboards
_except_ for that BIOS table not having the right reserved IO regions.
.. and then there's the pluggable PCI stuff, of course. I'm not sure
whether you took that over too. That's a whole different set of issues.
Linus
next prev parent reply other threads:[~2008-04-21 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 6:21 [GIT PATCH] PCI patches for 2.6.25-git Greg KH
2008-04-21 6:28 ` PCI MAINTAINER change Greg KH
2008-04-21 15:55 ` Jesse Barnes
2008-04-21 16:18 ` Linus Torvalds [this message]
2008-04-21 16:22 ` Ingo Molnar
2008-04-21 16:28 ` Jesse Barnes
[not found] <fa.TS+5+HinmGrscLiHGCM7C9dFSbk@ifi.uio.no>
[not found] ` <fa.EEEat9giRPyWOGUiYHgSIStt6vw@ifi.uio.no>
[not found] ` <fa.zR5oiQ1hgiLPwoqLOEK2ySOHKLA@ifi.uio.no>
[not found] ` <fa.vh1MNsau5uBs7WyWWCN0Huvxe98@ifi.uio.no>
[not found] ` <fa.JwWRxW97po7bp7uP8gASvgGakFc@ifi.uio.no>
2008-04-22 1:27 ` Robert Hancock
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=alpine.LFD.1.10.0804210914030.2779@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mingo@redhat.com \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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®