From: "Mark A. Greer" <mgreer@mvista•com>
To: Sven Luther <sven.luther@wanadoo•fr>
Cc: nd@bplan-gmbh•de, Embedded PPC Linux list <linuxppc-embedded@ozlabs•org>
Subject: Re: [PATCH][PPC32] mv64x60 updates
Date: Thu, 24 Feb 2005 10:08:35 -0700 [thread overview]
Message-ID: <421E0A13.7060309@mvista.com> (raw)
In-Reply-To: <20050224160411.GA11197@pegasos>
Sven Luther wrote:
>On Thu, Feb 24, 2005 at 08:28:56AM -0700, Mark A. Greer wrote:
>
>
>>Sven Luther wrote:
>>
>>
>>
>>>On Tue, Jan 25, 2005 at 05:14:25PM -0700, Mark A. Greer wrote:
>>>
>>>
>>>
>>>
>>has spent a lot of time making it work on both MIPS and PPC. The code
>>you see in the mv64x60.c file is a part of that. I believe that Dale's
>>
>>
>
>Ok, so the code in question is in addition to the existing driver from the
>mips guys and works with it ?
>
If "the code in question" == the enet related code in mv64x60.c then
yes. However, the only enet related code in mv64x60 is platform_data
setup and setup of the bridge's windows between the enet ctlr and system
memory.
> I had the impression that it was a separate
>driver development or something.
>
Nope.
>
>
>
>>patch(es) have been accepted and are queued to go into the mainline tree
>>at some point.
>>
>>
>
>Ok. Do you know if Dale's patches are available separatedly while they are not
>yet in mainline, so Nicolas Det can work on them and make sure they also work
>on the Pegasos board, which is not an embedded board but from the chrp
>lineage. Nicolas already did some mv643xx ethernet driver work last summer,
>but apparently had trouble integrating this in the mainline kernel, and it
>seems his work has now been redone by Dale or something. Do you know who the
>right person to communicate with about this would be ? The MIPS folk didn't
>reply to any of our mails about this subject.
>
Nicolas has emailed me off-line and he & Dale are now in contact. FYI,
this is part of the email from Dale to Nicolas:
> Please see bk://dfarnsworth@bkbits.net/linux-2.5-mv643xx-enet. Most of this is
> in netdev and mm, and on track to go into linux-2.5.
>>Did I answer your question?
>>
>>
>
>I think so. I was just surprised to see this 64x6x work go to arch/ppc instead
>to drivers/net.
>
There is no "driver" functionality in arch/ppc. There is only
platform_data setup which is used by the driver and the ensuring the
bridge's windows between the enet ctlr and system memory are set up
correctly.
Mark
next prev parent reply other threads:[~2005-02-24 17:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:14 [PATCH][PPC32] mv64x60 updates Mark A. Greer
2005-02-24 8:25 ` Sven Luther
2005-02-24 15:28 ` Mark A. Greer
2005-02-24 16:04 ` Sven Luther
2005-02-24 17:08 ` Mark A. Greer [this message]
2005-02-24 17:05 ` Sven Luther
2005-02-24 17:24 ` Dale Farnsworth
2005-03-05 19:27 ` Sven Luther
2005-03-05 20:32 ` Sven Luther
2005-03-05 22:51 ` Dale Farnsworth
2005-03-06 7:02 ` Sven Luther
2005-03-06 10:29 ` Dale Farnsworth
2005-03-06 19:10 ` Sven Luther
2005-03-06 19:48 ` Nicolas DET
2005-03-07 1:00 ` [PATCH][PPC32] " Dale Farnsworth
2005-03-07 6:52 ` Sven Luther
2005-03-07 10:56 ` Nicolas DET
2005-03-07 10:58 ` Nicolas DET
2005-03-07 12:30 ` James Chapman
2005-03-07 12:46 ` Sven Luther
2005-03-07 12:57 ` Nicolas DET
2005-03-07 13:20 ` Sven Luther
2005-03-07 17:24 ` Mark A. Greer
2005-03-07 13:23 ` Linwoes
2005-03-07 22:54 ` mv643xx_eth SA_SHIRQ support patch Dale Farnsworth
2005-03-08 6:49 ` Sven Luther
2005-03-08 7:27 ` Benjamin Herrenschmidt
2005-03-08 12:20 ` Dale Farnsworth
2005-03-08 12:15 ` Sven Luther
2005-03-08 12:42 ` Sven Luther
[not found] ` <20050308164310.GA9891@pegasos>
2005-03-08 22:31 ` Benjamin Herrenschmidt
2005-03-09 7:17 ` Sven Luther
2005-03-09 7:39 ` Benjamin Herrenschmidt
2005-03-09 7:40 ` Sven Luther
2005-03-08 18:19 ` Mark A. Greer
2005-03-08 18:19 ` Sven Luther
2005-03-08 19:28 ` [PATCH] final mv643xx_eth pegasos patch set Sven Luther
2005-03-08 19:52 ` Sven Luther
2005-03-08 23:18 ` Nicolas DET
2005-03-09 2:03 ` mv64x60 updates Benjamin Herrenschmidt
2005-03-09 2:01 ` Benjamin Herrenschmidt
2005-03-09 15:59 ` Chris Friesen
2005-03-05 21:58 ` [PATCH][PPC32] " Dale Farnsworth
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=421E0A13.7060309@mvista.com \
--to=mgreer@mvista$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=nd@bplan-gmbh$(echo .)de \
--cc=sven.luther@wanadoo$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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