public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] IXP425 ethernet & NPE microcode
Date: Thu, 10 May 2007 07:16:50 +0200	[thread overview]
Message-ID: <200705100716.50252.sr@denx.de> (raw)
In-Reply-To: <7EDC24AB1ED682439657D3B7790609D39398AA@deepthought.Elpro.local>

On Thursday 10 May 2007, Jonathan Pratt wrote:
> I was not aware of the project. They merely point out that it's a
> necessary evil. The Intel redistribution restrictions seem rather
> draconian, however.
>
> I'm not sure about the conflict with u-boot (GPL), however, and whether
> the issues are more than philosophical.

You can include the NPE binary into U-Boot as you did, but this violates the 
GPL and therefore you are not allowed to ship products using this resulting 
image.

The best solution for this problem right now, if to not included the NPE 
binary in the U-Boot build process, but program it into a separate FLASH 
sector, and let the NPE ethernet driver load the NPE's with the binary from 
this location. This way we don't have link the NPE binary into the U-Boot 
image. Unfortunately nobody found the time to implement this solution till 
now.

And furthermore, it would be very desireable to drop the current NPE U-Boot 
ethernet driver implementation based on the original Intel code with the 
complex and ugly Intel access library completely, and re-implement the driver 
based on the new Linux IXP4xx NPE ethernet drivers. There are currently 2 
completely new drivers without the Intel access library which will result in 
lower memory footprint and much less and cleaner code.

Patches welcome! :-)

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
=====================================================================

  reply	other threads:[~2007-05-10  5:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  4:39 [U-Boot-Users] U-boot & MonteJade start up Jonathan Pratt
2007-05-02  5:16 ` Stefan Roese
2007-05-02  6:22   ` Jonathan Pratt
2007-05-09  7:17   ` [U-Boot-Users] IXP425 ethernet & NPE microcode Jonathan Pratt
2007-05-09  9:16     ` Eric BENARD
2007-05-09  9:52     ` Stefan Roese
2007-05-09 20:32       ` Jonathan Pratt
2007-05-09 22:37     ` Wolfgang Denk
2007-05-09 22:55       ` Jonathan Pratt
2007-05-09 23:16         ` David Hawkins
2007-05-10  1:50           ` Jonathan Pratt
2007-05-10  5:16             ` Stefan Roese [this message]
2007-05-10  9:04               ` Øyvind Repvik
2007-05-10 11:25                 ` Stefan Roese
  -- strict thread matches above, loose matches on Subject: below --
2007-05-10 13:08 Martijn de Gouw
2007-05-10 17:53 ` Stefan Roese
2007-05-10 13:46 Martijn de Gouw
2007-05-10 16:39 ` Wolfgang Denk
2007-05-11  7:05 Martijn de Gouw
2007-05-11  8:00 ` Stefan Roese
     [not found] <4CD35CD1F8085945B597F80EEC8942135FA60A@exc01.bk.prodrive.nl>
2007-06-06 12:21 ` Stefan Roese

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=200705100716.50252.sr@denx.de \
    --to=sr@denx.de \
    --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