public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephan Linz <linz@li-pro.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] net: ll_temac: Add LL TEMAC driver to u-boot
Date: Mon, 16 Jan 2012 18:46:53 +0100	[thread overview]
Message-ID: <1326736013.2717.25.camel@keto> (raw)
In-Reply-To: <20120116081446.D31F717133E2@gemini.denx.de>

Am Montag, den 16.01.2012, 09:14 +0100 schrieb Wolfgang Denk: 
> Dear Stephan Linz,

Hi Wolfgang,

you are right in all points. I'll go into the next round and handle all
new request.

br,
Stephan

> 
> In message <1326652166.18981.213.camel@keto> you wrote:
> >
> > > come code already declares PktBuf ... can't you use that ?
> > 
> > Hm, what do you mean exactly here?
> > 
> > These are the two DMA transfer buffers. I have no idea if there are
> > buffers in the upper layer (NET) and how I can use it for DMA transfers.
> 
> It's a bad thing not to look at common code, but thnings like that
> happen too easily.
> 
> However, now that this has been pointed out, you cannot simply ignore
> such a request.
> 
> > Therfore I create my own rx/tx buffers and copy data. That reduce the
> > performance a little bit, but it's OK. Furthermore I have to use DMA
> > safe buffers here (no cache, 32 byte alignment).
> 
> I could imagine this to be a pretty common requirement.
> 
> > > this looks like a struct that should get allocated on the fly based on 
> > > arguments given to the driver's registration func
> > 
> > OK, it wast a little bit RAM. We can optimize the code later. I want to
> > see more testing results on differnet Microblaze and PPC platforms.
> 
> we can fix this now, right?
> 
> > > the memory is already zero-ed by the call to calloc, so this for loop is 
> > > useless (and if it wasn't, you'd still use memset())
> > 
> > Sure, we can remove this part in one of the next code optimization.
> 
> No.  Please fix this now, and then add a cleaned up driver.  This is
> what the peer review process is all about.
> 
> Best regards,
> 
> Wolfgang Denk
> 

  reply	other threads:[~2012-01-16 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 15:41 [U-Boot] LL TEMAC V8 refactored Stephan Linz
2012-01-15 15:46 ` [U-Boot] [PATCH 1/5] net: ll_temac: Add LL TEMAC driver to u-boot Stephan Linz
2012-01-15 17:28   ` Mike Frysinger
2012-01-15 18:29     ` Stephan Linz
2012-01-15 18:47       ` Mike Frysinger
2012-01-15 19:41         ` Stephan Linz
2012-01-16  8:19           ` Wolfgang Denk
2012-01-17 20:19         ` Stephan Linz
2012-01-16  8:14       ` Wolfgang Denk
2012-01-16 17:46         ` Stephan Linz [this message]
2012-01-15 19:46   ` [U-Boot] [PATCH] net: ll_temac: Remove useless memory erasing Stephan Linz
2012-01-15 23:44     ` Mike Frysinger
2012-01-16 17:22       ` Stephan Linz
2012-01-16  8:06     ` Wolfgang Denk
2012-01-15 15:46 ` [U-Boot] [PATCH 2/5] microblaze: Enable several ethernet driver compilation Stephan Linz
2012-01-15 15:46 ` [U-Boot] [PATCH 3/5] microblaze: Wire up LL_TEMAC driver initialization Stephan Linz
2012-01-15 15:46 ` [U-Boot] [PATCH 4/5] microblaze: Enable phylib and mii support Stephan Linz
2012-01-15 15:46 ` [U-Boot] [PATCH 5/5] microblaze: Add faked LL_TEMAC driver configuration Stephan Linz

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=1326736013.2717.25.camel@keto \
    --to=linz@li-pro.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox