From: Andrew Morton <akpm@osdl.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, Leo Li <leoli@freescale.com>,
Alexandre Bastos <alebas@televes.com>,
"Balasaygun, Oray (Oray)" <oray@lucent.com>
Subject: Re: [PATCH] ppc32: Update 8260_io/fcc_enet.c to function again
Date: Tue, 15 Mar 2005 22:31:43 -0800 [thread overview]
Message-ID: <20050315223143.229275b6.akpm@osdl.org> (raw)
In-Reply-To: <20050315182537.GW8345@smtp.west.cox.net>
Tom Rini <trini@kernel.crashing.org> wrote:
>
> There's too many things in here that've sat too long (I'd been hoping to
> just delete the driver, but that hasn't happened yet, so). A cobbled
> together list of changes is:
>
> - Update MDIO support for workqueues.
> - Make use of <linux/mii.h>
> - Add RPX6 support.
> - Comment out set_multicast_list (broken).
> - Rework tx_ring stuff so we have tx_free, not tx_Full/n_pkts.
> - Other PHY updates/fixes.
> - Leo Li: Rework FCC clock configuration, make it easier.
> - 2.4 : VLAN header room, other misc bits.
> - Kill MII_REG_NNN in favor of defines from <linux/mii.h>
> - DM9161 PHY support (2.4, Myself & alebas@televes.com)
> - PQ2ADS and PQ2FADS support bits (Myself & alebas@televes.com
>
> From: Leo Li <leoli@freescale.com>
> Signed-off-by: Tom Rini <trini@kernel.crashing.org>
> Signed-off-by: Alexandre Bastos <alebas@televes.com>
That's unfortunate - Oray sent a patch in just a few days ago which also
fixes up this driver. See
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm3/broken-out/ppc-8260-fcc-ethernet-driver-cannot-read-lxt971-phy-id.patch
What should we do?
next prev parent reply other threads:[~2005-03-16 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 18:25 Tom Rini
2005-03-16 6:31 ` Andrew Morton [this message]
2005-03-16 18:43 ` Jeff Garzik
2005-03-16 8:00 Bastos Fernandez Alexandre
2005-03-16 14:54 ` Tom Rini
2005-03-16 15:04 Balasaygun, Oray (Oray)
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=20050315223143.229275b6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alebas@televes.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oray@lucent.com \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®