Quanta Building MIT's $100 Laptops (eWeek) [LWN.net]

Quanta Building MIT's $100 Laptops (eWeek)

Posted Dec 16, 2005 11:09 UTC (Fri) by khim (subscriber, #9252) [Link]

Do not mix free driver and free firmware. Yes, situation with free drivers is better today, but situation with firmware is not: most free drivers for cheap cards include some "blob" to be loaded in card on startup; more expensive models include flash where firmware is stored - then driver is truly free.

Since blob is in fact computer program (even if for specialized CPU and compiled with specialized, usually not freely-available, tools) Debian claims it's not enough to have this blob and open-source driver: you need sources for firmware too. Not something ODM will ever bother with: it's not even executed on CPU, it's not related to Linux is any way (the only relation is that Linux system must have this blob to initialize card), there are no need to ever port it (even if you'll put card in your Mac with PowerPC main CPU specialized CPU on card itself will be the same), so noone except Debian are bothered by that...

Quanta Building MIT's $100 Laptops (eWeek)

Posted Dec 16, 2005 14:00 UTC (Fri) by vonbrand (subscriber, #4458) [Link]

Fedora doesn't ship the firmware for the intel ipw2100 and 2200 WiFi cards either, for exactly the same reasons as Debian.

Quanta Building MIT's $100 Laptops (eWeek)

Posted Dec 16, 2005 21:14 UTC (Fri) by drag (subscriber, #31333) [Link]

No!

Fedora and Debian can't include the Intel Firmware because Intel forbids redistribution of it. Debian maybe stinkers about it since most firmware forbids modifications and such, but they'd still distribute it in non-free.

It's Intel that is the problem, not Debian, not Fedora.

Also cards that don't require firmware are not nessicarially more expensive. Ralink rt2500 style cards do not require a loadable firmware to operate and they are _still_ cheaper AND they have fully open sourced drivers provided by the manufactures!

Go ask the OpenBSD people if you don't beleive me.

Any distro offering firmware images as part of their normal install for Intel wireless cards can face a lawsuit from Intel unless they have a prior licensing agreement, which you cannot use youself.

Also:

Firmware != Binary blob.

Firmware is not the same as compiled code. It's a specific item for a specific peice of hardware and is completely architecture and OS independant.

You can use the same firmware images for Linux on PowerPC, on Linux on x86, on OS X, on Windows XP, on OpenBSD. It doesn't matter.

Binary blobs are kernel code, based on Linux kernel developer's code, compiled from C source code before they are made aviable to you and when they are used become part of the Kernel code running on your system. You can't use the same binary blob on a x86 Linux as on a PowerPC linux, for instance.

There is some 'glue' code that people provide with binary blobs, but it exists only to shoehorn generic kernel code into a specific kernel (aka the one your running).

There is a huge difference between binary blobs and actual firmware.

Beware that some manufacturers want to cloud the issues or mislead people by giving the name 'firmware' to things that are not firmware. For instance on the Linksys they call the OS that they load on the onboard flash drive 'firmware upgrades' when in reality it's just a striped down Linux or Vxware OS.

Quanta Building MIT's $100 Laptops (eWeek)

Posted Dec 18, 2005 4:42 UTC (Sun) by khim (subscriber, #9252) [Link]

For instance on the Linksys they call the OS that they load on the onboard flash drive 'firmware upgrades' when in reality it's just a striped down Linux or Vxware OS.

If it does not run on main CPU - it's still firmware. It does not matter if it's full-blown OS or not. If it's Linux - you are entitled to sources, if it's Vxware OS - you are not, but either way from PC's point of view it's still firmware.