lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 7 Jul 2008 21:45:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	Oliver Endriss <o.endriss@....de>, linux-dvb@...uxtv.org,
	Jaswinder Singh <jaswinder@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	kernelnewbies <kernelnewbies@...linux.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware

> Having a binary firmware inside a GPL'd file seems to be (at least for some
> people) a GPL violation, since the firmware source code should also be released
> with GPL (please read [1] for a good article about this).

The firmware is usually a separate program, running on a separate
processor communicating by a standard API and is used by Linux, Windows
and other OS's. Thats not quite the same as say the Nvidia driver.

If it happens to keep the GPL zealots happier then fine, but there are
good sound technical reasons for doing it

- compiled in firmware isn't pageable
- compiled in firmware can't be updated separately
- it makes it really hard for end users told to "try the new firmware" -
especially in the enterprise space.

Clearly there are some cases that is less relevant - drivers where the
firmware/OS pair must match such as aic7xxx where you don't really want
firmware floating around loose.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ