All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad House <brad@mcve.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Brad House <brad_mssw@gentoo.org>, netdev@oss.sgi.com
Subject: Re: r8169 and tg3
Date: Mon, 17 Nov 2003 23:51:40 -0500	[thread overview]
Message-ID: <3FB9A55C.5090901@mcve.com> (raw)
In-Reply-To: <3FB9A277.70309@pobox.com>


Commenting below:
> 
> So, what needs to happen is somebody needs to look at the sis190 changes 
> that went in, and apply those same fixes to r8169.

Ok, cool. Didn't realize that, if you have a couple of references to
those discussions or patches, that would be awesome (so I don't have
to try to dig them up), otherwise, I'll research it some.
I was also going to look into merging the big endian patches I saw
posted earlier this month.

> 1) If you have problems with the tg3 driver, we need to get those bug 
> reports and fix them.  bcm5700 is not going to be merged into the 
> kernel.  Further, there was at least one serious x86-64 issue that was 
> fixed in tg3, and we need to make sure users are testing that driver, 
> not a non-standard driver with bugs of its own.

Ok, sounds like a plan. I'll get some testing on the latest tg3 driver
then, have those been merged into 2.6.0-test9-bk21, or is there another
patch I need to apply to my local tree (and in turn will be applied
to Gentoo's tree)?

> 
> 2) Please CC me on all net driver patches, since I am the dude that 
> actually puts those patches into the kernel.

Cool, no problem.
I just took over the amd64 port for Gentoo a couple months back,
so I'm having to get into some stuff I haven't had to do before.
But I'm starting to learn some of the kernel internals/driver
infrastructure, so hopefully I'll be of some actual help in the
near future, assuming my actual job doesn't get in the way ;)

-Brad

  reply	other threads:[~2003-11-18  4:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  4:08 [PATCH 2.6.0-test9-bk6] r8169.c update for 8110S support from RTL 1.6 version Brad House
2003-11-18  4:39 ` r8169 and tg3 Jeff Garzik
2003-11-18  4:51   ` Brad House [this message]
2003-11-18 10:00   ` Jan Oravec
2003-11-18 11:01     ` David S. Miller
2003-11-18 12:58   ` Francois Romieu
2003-11-19 17:24     ` Jeff Garzik
2003-11-19 18:44       ` Robert Olsson
2003-11-20  0:00       ` [patches] 2.6.0-test9 - r8169 DMA API conversion Francois Romieu
2003-11-20  0:08         ` Brad House
2003-11-20  0:45           ` Francois Romieu
2003-11-20  0:59             ` Brad House
2003-11-20  1:34               ` Andre Tomt
2003-11-20  1:35                 ` Brad House
2003-11-20  1:36                   ` Brad House
2003-11-20  1:36               ` Jeff Garzik
2003-11-21  0:36         ` Francois Romieu
2003-11-21  1:38           ` Jeff Garzik
2003-11-21 23:20             ` Francois Romieu

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=3FB9A55C.5090901@mcve.com \
    --to=brad@mcve.com \
    --cc=brad_mssw@gentoo.org \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.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.