All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prafulla Wadaskar <prafulla@marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Gbe Controller driver support for kirkwood SOCs
Date: Sun, 24 May 2009 22:36:10 -0700	[thread overview]
Message-ID: <73173D32E9439E4ABB5151606C3E19E201CF9E6A1D@SC-VEXCH1.marvell.com> (raw)
In-Reply-To: <4A092040.2000504@gmail.com>

Hi Ben,

How are you?
Seems to be very busy as usual.... :-)

Can you pls kindly take out some time to review these patches.
hopefully they are as per your requirements since we have invested considerable time to make them up to the mark.
May be-you can accept them :-) 
http://lists.denx.de/pipermail/u-boot/2009-May/053111.html
http://lists.denx.de/pipermail/u-boot/2009-May/052905.html
Just to share with you,
in netdev.h- though struct and enums defined looks similar-
I have used separate struct and enums for both mv88e61xx and mv88e1116 because only basic init support is available in those drives, but in coming time there will be more features added to them.
I think since these are initial drivers in net/phy/ we should provide common/phy.h and keep netdev.h untouched
What do you think?

Also you might be ready with review comments for this
http://lists.denx.de/pipermail/u-boot/2009-May/053113.html
Nothing much changed in v4 compared to patch version v1.
few global comments that I received for this patch from you are-
1. the code is too big.
2. can you strip down features to minimum
Just to reply these: 
the entire egiga driver is kept as separate driver .c and .h,
I am in progress to reuse the code from other drivers.
The features are kept minimal required but I can cut down some of features like "update network statistics" so as to make code size small and acceptable :-)
Still your comments will help me to provide better code...

Last but not least
Shall I resend above patches if you feel this is more comfortable for you?
 
Regards..
Prafulla. . .  

> -----Original Message-----
> From: Ben Warren [mailto:biggerbadderben at gmail.com] 
> Sent: Tuesday, May 12, 2009 12:38 PM
> To: Prafulla Wadaskar
> Cc: u-boot at lists.denx.de; Ashish Karkare; Prabhanjan Sarnaik; 
> Ronen Shitrit
> Subject: Re: [U-Boot] [PATCH v2] Gbe Controller driver 
> support for kirkwood SOCs
> 
> Hi Prafulla,
> 
> Prafulla Wadaskar wrote:
> > Hi All
> >
> > Ping....
> > I didn't here any feedback from anyone, waiting for your valued 
> > comments :-(
> >
> >   
> I've started reviewing this driver - it's a lot to digest 
> (2500 lines!?!).  Please think a little about what features 
> are really needed here.  For example, do you really need RMON 
> in a bootloader?  I'll try to provide more specific feedback soon.
> > Regards..
> > Prafulla . . 
> >
> >   
> regards,
> Ben
> 

  parent reply	other threads:[~2009-05-25  5:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 17:56 [U-Boot] [PATCH v2] Gbe Controller driver support for kirkwood SOCs Prafulla Wadaskar
2009-05-12  4:03 ` Prafulla Wadaskar
2009-05-12  7:07   ` Ben Warren
2009-05-13  7:02     ` Prafulla Wadaskar
2009-05-25  5:36     ` Prafulla Wadaskar [this message]
2009-05-25 20:03       ` Ben Warren
2009-05-26  6:37       ` Ben Warren
2009-06-05 10:12         ` Wolfgang Denk
2009-06-05 16:34           ` Ben Warren
2009-06-08  4:28             ` Prafulla Wadaskar

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=73173D32E9439E4ABB5151606C3E19E201CF9E6A1D@SC-VEXCH1.marvell.com \
    --to=prafulla@marvell.com \
    --cc=u-boot@lists.denx.de \
    /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.