From: "Mark A. Greer" <mgreer@mvista.com>
To: Brian Waite <bwaite@irobot.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: GT64260_eth (Ethernet) Driver
Date: Tue, 20 Sep 2005 11:32:57 -0700 [thread overview]
Message-ID: <20050920183257.GD5756@mag.az.mvista.com> (raw)
In-Reply-To: <200509201313.48945.bwaite@irobot.com>
On Tue, Sep 20, 2005 at 01:13:48PM -0400, Brian Waite wrote:
> On Tuesday 20 September 2005 12:02 pm, Earl Olsen wrote:
> platform using the 64260 chip, besides the eval board, was the cpci690.c. I
> would look and see ifthis is still a working platform and base your platform
> code off of that.
The cpci690 is a working platform but it does not use the embedded enet
ctlr because there is no driver.
> > Dieu,
> >
> > You should sync up with Brian Waite (look at CC: list) who has been
> > looking at writing a new enet driver for the 2.6 kernel using the latest
> > bridge support code. You can get a look at the latest support code by
> > cloning bk://source.mvista.com/linux-2.5-marvell.
> No. Only use mainline kernel.org for latest support. Nothing else is working
> 100%. In the kernel.org tree the MPSC driver is working along with the 360
> ethernet device.
This is from a very, very old email that is no longer accurate. It
should be ignored. This is no tree except the mainline/mm tree and there
is not gt64260 enet driver in the mainline/mm tree (that I know of).
> > Note the the mpsc
> > driver that's there still isn't working correctly.
> I haven't loked at the 64260 for well over a year since we went to the 64360.
> The 260 was just too bad in too many respects. I was willing to test the 260
> code with my old hardware if there was a merged driver and even develop the
> merged driver, but it became obvious the merged driver was going to be ugly
Ditto.
Mark
next prev parent reply other threads:[~2005-09-20 18:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 16:02 GT64260_eth (Ethernet) Driver Earl Olsen
2005-09-20 17:13 ` Brian Waite
2005-09-20 18:32 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 18:53 Earl Olsen
2004-06-20 20:27 Dieu Morales
2004-06-23 22:39 ` Mark A. Greer
2004-06-24 8:37 ` David Woodhouse
2004-06-24 11:23 ` Brian Waite
2004-06-24 18:46 ` Mark A. Greer
2004-06-24 19:02 ` Mark A. Greer
2004-06-25 7:10 ` David Woodhouse
2004-06-25 22:05 ` Mark A. Greer
2004-06-25 23:43 ` David Woodhouse
2004-06-26 0:07 ` Mark A. Greer
2004-06-26 0:41 ` Paul Mackerras
2004-06-26 1:47 ` Mark A. Greer
2004-07-29 3:19 ` Dieu Morales
2004-07-29 17:28 ` Mark A. Greer
2004-06-29 14:08 ` David Woodhouse
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=20050920183257.GD5756@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=bwaite@irobot.com \
--cc=linuxppc-embedded@ozlabs.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 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.