public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] net: ll_temac: Add LL TEMAC driver to u-boot
Date: Wed, 28 Mar 2012 09:53:54 +0200	[thread overview]
Message-ID: <4F72C392.7090306@monstr.eu> (raw)
In-Reply-To: <CANr=Z=ZOm8igXEH2N-nftSkvtT5QANfaD1m-skAJsUNeYKVC4w@mail.gmail.com>

Hi Joe,

>> Stephan Linz wrote:
>>> Xilinx LocalLink Tri-Mode Ether MAC driver can be
>>> used by Xilinx Microblaze or Xilinx ppc405/440 in
>>> SDMA and FIFO mode. DCR or XPS bus can be used.
>> Joe, Wolfgang: I don't agree with this driver because it is doing the same
>> things as my origin
>> version but on 800 lines instead of 1860lines. The next thing is that plb
>> bus on Xilinx fpgas
>> is getting obsolete.
> 
> Are you meaning that you already have a driver in u-boot that works on
> this hardware or do you mean the original version somewhere else, like
> Linux?

There is really long history about this u-boot driver. The origin version for ppc was sent to mailing list
April 26, 2008 by Yoshio Kashiwagi. I have tried to add it to mainline several times
and my latest attempts end with result that I didn't want to follow u-boot coding style because
of ppc/microblaze differences (not using offset with structure because of ppc/microblaze differences - dcr/plb access).
That driver has 800 lines.
Based on this strict rule I decided not to continue to push this driver to mainline
because it is just a lot of work to change it and especially test it. My origin driver is used by many our customers
on microblaze and ppc and none reported any problem with it.

After this Stephan decided to change it to be acceptable to mainline submission.


> As for plb being near obsolescence, are you recommending a change to
> the driver to drop support for that bus option? Or do you mean for
> that reason the driver itself should be omitted?

should be obsolete in a year or so and if you add it to mainline it will be there
but in 2013 there will be minimal number of users for it.

>> I am not going to add it to my microblaze custodian tree.
>> If you like this patch please add it to u-boot-net tree or directly to
>> mainline.
> 
> I was actually going to recommend that it go through the microblaze
> branch if it is primarily for microblaze targets.  If you don't want
> it, then I think Stephan needs to work to convince you by making
> revisions.

None can convince me that 1860 code lines which fulfill all u-boot rules
is better than origin well tested 800 code lines (and commercially used)
which break one u-boot rule.
I agree with rules but none can expect that I will assist and help to add
it to mainline. I don't want to have responsibility for that.

BTW: Target is also ppc because there is DCR support.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2012-03-28  7:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 10:48 [U-Boot] [PATCH 1/4] net: ll_temac: Add LL TEMAC driver to u-boot Stephan Linz
2012-02-25 10:48 ` [U-Boot] [PATCH 2/4] microblaze: Enable several ethernet driver compilation Stephan Linz
2012-02-25 11:06   ` Stephan Linz
2012-04-04 16:14     ` Joe Hershberger
2012-02-25 10:48 ` [U-Boot] [PATCH 3/4] microblaze: Add faked LL_TEMAC driver configuration Stephan Linz
2012-04-04 16:14   ` Joe Hershberger
2012-02-25 10:48 ` [U-Boot] [PATCH 4/4] microblaze: Wire up LL_TEMAC driver initialization Stephan Linz
2012-04-04 16:15   ` Joe Hershberger
2012-03-27 12:25 ` [U-Boot] [PATCH 1/4] net: ll_temac: Add LL TEMAC driver to u-boot Michal Simek
2012-03-27 16:22   ` Joe Hershberger
2012-03-28  7:53     ` Michal Simek [this message]
2012-03-30 22:07       ` Stephan Linz
2012-04-04 16:12         ` Joe Hershberger

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=4F72C392.7090306@monstr.eu \
    --to=monstr@monstr.eu \
    --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