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 v7] net: ll_temac: Add LL TEMAC driver to u-boot
Date: Thu, 12 Jan 2012 17:05:35 +0100	[thread overview]
Message-ID: <1326384335.18981.113.camel@keto> (raw)
In-Reply-To: <4F0EBB9E.2040609@monstr.eu>

Am Donnerstag, den 12.01.2012, 11:53 +0100 schrieb Michal Simek: 
> Wolfgang Denk wrote:
> > Dear Stephan Linz,
> > 
> > >> But what would be the best implementation for unspecified targets here?
> > 
> > The question is actually a very simple one here: is there any board
> > configuration in mainline that will actually compile and link against
> > this driver?  If yes, then everything is fine.  If not, we would not
> > even know if there were gross syntax errors in that code, and we would
> > never notce when changes to other parts break compatibility with it.
> > 
> > This is why I will not add any code that is not used in mainline -
> > out-of-tree users don't help a bit.
> 
> OK. Stephan, please send v8 with suggested changes with all patches or link to patches which are necessary
> to use.
> Please also define fake address XILINX_LLTEMAC_BASEADDR in xparameters.h to be compiled.
> The same we will do for axi emac driver.
> 
> Stephan if you like I can add that changes to my custodian git tree and do final testing
> before we ask Wolfgang to merge.

I can release the v8 patch next week. I will do some tests on weekend
before I post the results here on list. The next release will be
prepared to support more than one TEMAC cores (LL_TEMAC0 nad LL_TEMAC1).
So I need a little bit more time to test ....


-- 
Best regards,
Stephan Linz
______________________________________________________________________________
MB-Ref: http://www.li-pro.de/xilinx_mb:mbref:start
OpenDCC: http://www.li-pro.net/opendcc.phtml
PC/M: http://www.li-pro.net/pcm.phtml
Sourceforge: http://sourceforge.net/users/slz
Gitorious: https://gitorious.org/~slz

  reply	other threads:[~2012-01-12 16:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 20:39 [U-Boot] LL TEMAC V7 refactored Stephan Linz
2011-12-01 20:39 ` [U-Boot] [PATCH v7] net: ll_temac: Add LL TEMAC driver to u-boot Stephan Linz
2011-12-20 22:56   ` Wolfgang Denk
2011-12-21 19:22     ` Stephan Linz
2011-12-21 19:28     ` [U-Boot] [PATCH 1/3] microblaze: Enable several ethernet driver compilation Stephan Linz
2011-12-21 19:28     ` [U-Boot] [PATCH 2/3] microblaze: Enable phylib and mii support Stephan Linz
2011-12-21 19:28     ` [U-Boot] [PATCH 3/3] microblaze: Wire up LL_TEMAC driver initialization Stephan Linz
2011-12-22  9:02     ` [U-Boot] [PATCH v7] net: ll_temac: Add LL TEMAC driver to u-boot Michal Simek
2012-01-05 16:10       ` Wolfgang Denk
2012-01-05 17:11         ` Stephan Linz
2012-01-05 19:19           ` Wolfgang Denk
2012-01-07 17:12             ` Stephan Linz
2012-01-11 12:05               ` Michal Simek
2012-01-11 16:07               ` Wolfgang Denk
2012-01-12 10:53                 ` Michal Simek
2012-01-12 16:05                   ` Stephan Linz [this message]
2011-12-29 17:57   ` Andy Fleming

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=1326384335.18981.113.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