[oe] Removal of the proprietary Intel IXP ethernet driver (ixp4{00, 25}-eth, ixp-osal, ixp4xx-csr) from OE

Rod Whitby rod at whitby.id.au
Tue Jan 23 19:56:02 UTC 2007


Robert Wörle wrote:
> 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 ?

The Intel code?  No.  It's horrible code.  Subscribe to
linux-arm-kernel, and follow the patch review of the ixp4xx ethernet
driver that's happening right now if you want to see a good example of a
GPL rewrite of proprietary code and how to load firmware.

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

The intel code does not load the firmware, it has it compiled into the
driver (which is what makes it unable to be linked to the kernel).  The
open source driver does load the firmware from a separate file or MTD
partition.  The open source driver is built by the ixp4xx-kernel
package, which remains in OE for your viewing pleasure.

> 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 ?

Go to the intel site.  Try to download the ixp4xx software, and then
read the license which is presented to you.  I am not a lawyer, so I
cannot explain it to you - you really need to accept it on your own
behalf, or have your lawyer explain it to you.

-- Rod




More information about the Openembedded-devel mailing list