From: James Curbo <phoenix@sandwich.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andre Hedrick <andre@linux-ide.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: small fix for nforce ide chipset driver in 2.5.54
Date: Thu, 9 Jan 2003 00:56:42 -0600 [thread overview]
Message-ID: <20030109065642.GA6251@carthage> (raw)
In-Reply-To: <1042034033.24099.2.camel@irongate.swansea.linux.org.uk>
On Jan 08, Alan Cox wrote:
> On Wed, 2003-01-08 at 07:55, James Curbo wrote:
> > so I added a #define for PCI_DEVICE_ID_NVIDIA_NFORCE_IDE as 0x0065. It
> > compiled fine and I am in fact running that kernel now. I would have
> > just sent a patch but I am new to kernel hacking, this is just a one
> > liner and I'm sure you know where it goes better than I do.
>
> Someone deleted it about 2.5.50, and though I sent in the fix twice Linus
> still hasn't applied it 8(
Well, I thought this deal was over but apparently not. My 2.5.54 kernel
is still working fine, but when I compiled 2.4.20-ac2, it didn't pick up
my Nforce2 IDE. On a whim I checked include/linux/pci_ids.h and it has a
different PCI ID for PCI_DEVICE_ID_NVIDIA_NFORCE_IDE, namely 0x01bc.
(lspci -v reports 0x0065 here). Perhaps 0x01bc is the nforce1 ide
chipset and 0x0065 is the nforce2 ide chipset?
--
James Curbo <hannibal@adtrw.org> <phoenix@sandwich.net>
GPG public key available at http://sandwich.net/~phoenix/keys/
next prev parent reply other threads:[~2003-01-09 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 7:55 small fix for nforce ide chipset driver in 2.5.54 James Curbo
2003-01-08 13:53 ` Alan Cox
2003-01-09 6:56 ` James Curbo [this message]
2003-01-09 17:49 ` Alan Cox
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=20030109065642.GA6251@carthage \
--to=phoenix@sandwich.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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