linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dieu Morales <dieumorales@yahoo.com>,
	linuxppc-embedded@lists.linuxppc.org,
	Brian Waite <waite@skycomputers.com>
Subject: Re: GT64260_eth (Ethernet) Driver
Date: Thu, 24 Jun 2004 11:46:49 -0700	[thread overview]
Message-ID: <40DB2199.2050006@mvista.com> (raw)
In-Reply-To: <1088066228.18627.3352.camel@hades.cambridge.redhat.com>


David Woodhouse wrote:

>You are lost in a twisty maze of BK trees, all alike.
>
>On Wed, 2004-06-23 at 15:39 -0700, Mark A. Greer wrote:
>
>
>>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.  Note the the mpsc
>>driver that's there still isn't working correctly.
>>
>>
>
>Ooh look another one. What's in here that merits it having its own tree
>and prevents it from being accepted upstream?
>
It doesn't "merit" its own tree; it has its own tree because the code is
not yet ready to be passed upstream but others need to see the code.  If
you don't want to deal with the code in this tree, don't.  When it is
ready, and eventually [hopefully] accepted into the kernel.org tree,
this tree will disappear.

>
>Please be as specific as you can -- my task for the next few weeks
>involves making Dy-4 DMV-182 support happen.
>

This tree has a complete rewrite of the core code.  Look at
arch/ppc/syslib/.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-06-24 18:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 20:27 GT64260_eth (Ethernet) Driver 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 [this message]
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
2004-06-29 15:23                 ` BAT mapping Linh Dang
2004-06-29 17:59                   ` Linh Dang
  -- strict thread matches above, loose matches on Subject: below --
2005-09-19 18:53 GT64260_eth (Ethernet) Driver Earl Olsen
2005-09-20 16:02 Earl Olsen
2005-09-20 17:13 ` Brian Waite
2005-09-20 18:32   ` Mark A. Greer

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=40DB2199.2050006@mvista.com \
    --to=mgreer@mvista.com \
    --cc=dieumorales@yahoo.com \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=waite@skycomputers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).