From: Pantelis Antoniou <panto@intracom.gr>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC][PATCH 2.6.12-rc2 3/3] FCC Ethernet PlatformDevice support for 82xx
Date: Thu, 05 May 2005 14:21:27 +0300 [thread overview]
Message-ID: <427A01B7.9090200@intracom.gr> (raw)
In-Reply-To: <4278DDBF.8080705@ru.mvista.com>
Vitaly Bordug wrote:
> This patch contains actual Ethernet driver on platform bus. Currently
> tested on MPC8272ADS (PQII) board.
>
[snip]
>
Hi Vitaly
Since I'm also working on this, lets try to merge our work in
one driver.
A few points regarding my driver.
1) It currently supports both 8xx FEC, 82xx FCCs.
2) It will also support SCC ENETS on both 8xx & 82xx, and
FECs on coldfire's & 52xx's.
3) We should treat the current MII logic as temporary since
Andy Flemming has a replacement by a MII bus.
Regarding your driver, there are a couple of things it
does arguably better than mine.
1) It has more complete platformization.
2) Adjustuble ring sizes.
And here are some gripes.
1) I'm not a proponent of having drivers configuring pins,
clocks & other things that are properties of each specific board.
I'd rather have the bootloader or the platform initialization
handle it once, and have the driver just use these settings.
Opinions on this matter differ however :).
2) There are a number of platform defines that are not needed.
Well, what do you think?
Regards
Pantelis
next prev parent reply other threads:[~2005-05-05 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 14:35 [RFC][PATCH 2.6.12-rc2 3/3] FCC Ethernet PlatformDevice support for 82xx Vitaly Bordug
2005-05-04 22:43 ` Dan Malek
2005-05-05 11:21 ` Pantelis Antoniou [this message]
2005-05-05 12:40 ` Vitaly Bordug
2005-05-05 12:36 ` Pantelis Antoniou
2005-05-05 13:19 ` Dan Malek
2005-05-05 13:27 ` Pantelis Antoniou
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=427A01B7.9090200@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.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).