From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE
Date: Tue, 23 Jan 2007 20:23:07 +0100 [thread overview]
Message-ID: <45B6609B.5080909@linuxdevelopment.de> (raw)
In-Reply-To: <45B59FD0.1000207@whitby.id.au>
Rod Whitby schrieb:
> For a long time, the only way to use the internal ethernet port for
> ixp4xx devices was to use the proprietary intel driver. The driver
> could not be linked with the kernel, and tainted the kernel.
>
> Thankfully, that has now changed with the development of the open source
> ixp npe kernel driver, which is GPL and can be freely linked with the
> kernel. Note that the microcode firmware blob (ixp4xx-npe) which needs
> to be loaded by the driver is still Intel Proprietary and requires a
> click-through license on any firmware image that includes it.
>
Dear Rod
Im not having such hardware but i am interested in this drivers setup.
Do you think this code can be of any example ? I am in a similar
situation where i am confronted with a propriatory hardware driver.
Maybe that intel code as such is able to show me an good example of a
"firmware loading gpl module" and i could alter my code in such similar
way . Maybe the manufacturer looks at this and can go free with it also .
Could you explain to me the "click-through" license ? Does one need to
agree on that on every module load or when will this come to play ?
kind regards
rob_w
next prev parent reply other threads:[~2007-01-23 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 0:12 RFC: Adding a new global MACHINE_ENDIAN variable Rod Whitby
2007-01-22 17:01 ` Koen Kooi
2007-01-22 19:14 ` Rod Whitby
2007-01-22 20:03 ` Koen Kooi
2007-01-23 0:10 ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Rod Whitby
2007-01-23 5:40 ` Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE Rod Whitby
2007-01-23 19:23 ` Robert Wörle [this message]
2007-01-23 19:56 ` Rod Whitby
2007-01-25 3:15 ` RFC: customisable pivot-root functionality Rod Whitby
2007-01-25 3:53 ` Justin Patrin
2007-01-25 12:45 ` Cliff Brake
2007-01-25 16:54 ` Hans Henry von Tresckow
2009-04-20 5:52 ` Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE Rod Whitby
2007-01-23 11:13 ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Richard Purdie
2007-01-23 19:37 ` Rod Whitby
2007-01-23 20:34 ` Richard Purdie
2007-01-24 6:41 ` SITEINFO_ENDIAN(N)ESS (NN, not N) Rod Whitby
2007-01-24 6:44 ` Rod Whitby
2007-01-28 12:41 ` Deprecating ixp4xx, nslu2 in favour of endian-specific machine settings (Was: RFC on MACHINE_ENDIAN) Rod Whitby
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=45B6609B.5080909@linuxdevelopment.de \
--to=robert@linuxdevelopment.de \
--cc=openembedded-devel@lists.openembedded.org \
/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.