From: Manfred Spraul <manfred@colorfullife.com>
To: Brian Lazara <blazara@nvidia.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.28-pre4
Date: Mon, 11 Oct 2004 18:59:25 +0200 [thread overview]
Message-ID: <416ABBED.8020100@colorfullife.com> (raw)
In-Reply-To: <1097512373.6780.4.camel@localhost.localdomain>
Brian Lazara wrote:
>At some point, can we get forcedeth.c updated in 2.4.x? We've taken the
>latest from 2.6.8
>
The driver in 2.6.8 contains a critical bug that prevents the operation
on the non-GB board with a modularized driver.
See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128292
It's now fixed, I've written a backport of the 0.29 driver, it's at
http://marc.theaimsgroup.com/?l=linux-kernel&m=109439014812433&w=2
But that backport was stopped due to an oddity in your original backport:
>From http://www.uwsg.indiana.edu/hypermail/linux/kernel/0408.1/1523.html:
> #define PCI_DEVICE_ID_NVIDIA_NFORCE3 0x00d1
> #define PCI_DEVICE_ID_NVIDIA_NFORCE3_IDE 0x00d5
> +#define PCI_DEVICE_ID_NVIDIA_NVENET_3 0x00d5
> #define PCI_DEVICE_ID_NVIDIA_MCP3_AUDIO 0x00da
NVENET_3 can't have the id 0x00d5. I've asked Jane Liu a month ago to
double check the values and I'm still waiting for a reply.
For me, that's the only open point that prevents merging. What I'm
missing is a positive test report from a non-GB board, but that's not
mandatory - IMHO the code receives enough testing in 2.6.
--
Manfred
next prev parent reply other threads:[~2004-10-11 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 11:21 Linux 2.4.28-pre4 Marcelo Tosatti
2004-10-08 20:08 ` 2.4.28-pre4: e1000_main.c gcc 3.4 compile error Adrian Bunk
2004-10-09 22:58 ` Linux 2.4.28-pre4 mdew .
2004-10-11 16:32 ` Brian Lazara
2004-10-11 16:59 ` Manfred Spraul [this message]
2004-10-11 17:07 ` Jeff Garzik
2004-10-16 11:30 ` Barry K. Nathan
[not found] <bc8bcc5104100909425b84579a@mail.gmail.com>
2004-10-09 17:04 ` Martins Krikis
2004-10-09 15:51 ` Marcelo Tosatti
2004-10-09 20:11 ` Martins Krikis
2004-10-09 22:08 ` Jeff Garzik
2004-10-09 23:40 ` Martins Krikis
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 21:00 Brian Lazara
2004-10-12 14:37 Xose Vazquez Perez
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=416ABBED.8020100@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=blazara@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.