From: Roland Dreier <roland@topspin.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Terence Ripperda <tripperda@nvidia.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Michael Geithe <warpy@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mastergoon@gmail.com
Subject: Re: 2.6.8.1-mm2 (nvidia breakage)
Date: Tue, 24 Aug 2004 10:36:14 -0700 [thread overview]
Message-ID: <52vff8phf5.fsf@topspin.com> (raw)
In-Reply-To: <200408240926.42665.bjorn.helgaas@hp.com> (Bjorn Helgaas's message of "Tue, 24 Aug 2004 09:26:42 -0600")
Bjorn> To be pedantically clear about this, looking at
Bjorn> pci_dev->irq before calling pci_enable_device() is
Bjorn> *guaranteed* to fail, regardless of what the BIOS does. So
Bjorn> nvidia users will have to use "pci=routeirq" until there's
Bjorn> a new version of the nvidia driver.
Terence, correct me if I'm wrong, but the change to add
pci_enable_device() goes in the part of the nvidia driver that has
source available. So users can apply this patch themselves even
without another Nvidia release.
- Roland
next prev parent reply other threads:[~2004-08-24 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040819092654.27bb9adf.akpm@osdl.org>
2004-08-19 16:51 ` 2.6.8.1-mm2 (nvidia breakage) Bjorn Helgaas
2004-08-19 17:53 ` Alan Cox
2004-08-19 21:51 ` Terence Ripperda
2004-08-19 22:03 ` Bjorn Helgaas
2004-08-19 22:22 ` Alan Cox
2004-08-19 22:58 ` Terence Ripperda
2004-08-20 15:53 ` Bjorn Helgaas
2004-08-20 16:24 ` Michael Geithe
2004-08-20 19:04 ` Terence Ripperda
2004-08-23 15:30 ` Bjorn Helgaas
2004-08-23 19:01 ` Terence Ripperda
2004-08-24 15:26 ` Bjorn Helgaas
2004-08-24 17:22 ` Terence Ripperda
2004-08-24 17:36 ` Roland Dreier [this message]
2004-08-24 22:03 ` Terence Ripperda
2004-08-24 22:35 ` 2.6.8.1-mm2 (nvidia breakage) [u] Martin Schlemmer [c]
2004-08-24 5:17 2.6.8.1-mm2 (nvidia breakage) Michael Geithe
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=52vff8phf5.fsf@topspin.com \
--to=roland@topspin.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mastergoon@gmail.com \
--cc=tripperda@nvidia.com \
--cc=warpy@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.