From: James Curbo <phoenix@sandwich.net>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: small fix for nforce ide chipset driver in 2.5.54
Date: Wed, 8 Jan 2003 01:55:39 -0600 [thread overview]
Message-ID: <20030108075539.GA4128@carthage> (raw)
I recently acquired an Epox 8RDA motherboard, which uses the Nforce2
chipset. While trying to compile 2.5.54 I ran across an error in
drivers/ide/pci/nvidia.c. Several times the define
PCI_DEVICE_ID_NVIDIA_NFORCE_IDE is referenced, but is not defined
anywhere. It seems it is missing from include/linux/pci_ids.h. On my
board it shows up as:
00:09.0 IDE interface: nVidia Corporation: Unknown device 0065 (rev a2)
(prog-if 8a [Master SecP PriP])
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.
thanks, James
--
James Curbo <hannibal@adtrw.org> <phoenix@sandwich.net>
next reply other threads:[~2003-01-08 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 7:55 James Curbo [this message]
2003-01-08 13:53 ` small fix for nforce ide chipset driver in 2.5.54 Alan Cox
2003-01-09 6:56 ` James Curbo
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=20030108075539.GA4128@carthage \
--to=phoenix@sandwich.net \
--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