From: Jon Mason <jdmason@us.ibm.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Richard Dawe <rich@phekda.gotadsl.co.uk>, netdev@oss.sgi.com
Subject: Re: [PATCH 2/3] r8169: code clean-up
Date: Sun, 20 Feb 2005 21:40:48 -0600 [thread overview]
Message-ID: <200502202140.48403.jdmason@us.ibm.com> (raw)
In-Reply-To: <20050221002827.GB14268@electric-eye.fr.zoreil.com>
On Sunday 20 February 2005 06:28 pm, Francois Romieu wrote:
> Richard Dawe <rich@phekda.gotadsl.co.uk> :
> [...]
>
> > I started working on adding netif_msg checks to the printks. How far
> > have you got? I don't want to duplicate your work.
>
> None so far. Go wild.
>
> > Incidentally, is there a to-do list somewhere for the r8169 driver?
>
> (without priority)
>
> - validate suspend/resume/wol
>
> - fix the dac issues on x64
> Weird. Pita. Status needs to be updated.
>
> - push jumbo frames beyond 7k
> see with Jon Mason
>
> - merge with the 8139cp driver
> always interrupted but I have not given up
>
> - fix the gcc 2.95.x miscompilations
> people upgrade their compiler and return to real life before it can be
> diagnosed. It should not be hard but I have not had the time to install
> a broken debian to reproduce it so far :o(
>
> - benchmark/improve the performances
> Executive summary by Lennert Buytenhek: it sucks. If someone could
> identify where the bottleneck is with hard numbers...
>
> - harvest the hopeless r8169 users on the web
> time consuming like hell but it really helps to figure if things are
> stable or not.
>
> - backport to 2.4
> RSN. Pending queue is available here and will be pushed once 2.6.x is
> up-to-date.
>
> - ask Ben Greear if he still experiences keyboard issues with its laptop
> when he uses the r8169 driver
> Pending for 5 months... Ahem.
>
> > Maybe I can help out with some of the things.
>
> Figure what's wrong with M. Gardiol setup ?
Fix ethtool statistics (amd64 only problem?)
next prev parent reply other threads:[~2005-02-21 3:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 0:23 [PATCH 2/3] r8169: code clean-up Jon Mason
2005-02-17 23:28 ` Francois Romieu
2005-02-18 4:00 ` Jon Mason
2005-02-20 17:52 ` Richard Dawe
2005-02-20 18:14 ` Jon Mason
2005-02-21 0:28 ` Francois Romieu
2005-02-21 3:40 ` Jon Mason [this message]
[not found] ` <200502181918.07859.jdmason@us.ibm.com>
[not found] ` <20050219104640.GA31035@electric-eye.fr.zoreil.com>
2005-02-19 17:47 ` Jon Mason
2005-02-19 22:30 ` Francois Romieu
2005-02-20 18:04 ` Jon Mason
2005-02-20 23:34 ` Francois Romieu
2005-02-21 4:54 ` Jon Mason
2005-02-21 8:16 ` 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=200502202140.48403.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=rich@phekda.gotadsl.co.uk \
--cc=romieu@fr.zoreil.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.