[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#493925: binary firmware in drivers/char/drm/mga_ucode.h



severity 493925 wishlist
stop

On Wed, 06 Aug 2008, Robert Millan wrote:

> Now that it seems clear 2.6.26 will be the version used for the release, I'd
> like to bring back attention on pruning it from code under DFSG violation,
> GPL-incompatible, or unlicensed blobs.

as always stupid Debian wolf crying - disconnected from upstream work.
checkout 2.6.27-rcX they already ported several drivers to
request_firmware and if you *had* checked out linux-next you would
see that even more is in the pipe. 2.6.26 is not the right cut off.
and if you really cared why did nobody chime in there?

also you seem to not have checkout documented past efforts or asked
any upstream vendor to relicense, both requiring *real* work.
http://wiki.debian.org/KernelFirmwareLicensing
 
> Based on maks mail in:
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242866#308
> 
>   "file a separate report on each issue that you find and we'll analyse your
>   findings"
> 
> I'll file a separate report on each issue I find.  Will try to make them as
> detailed as possible.

ack, thanks.
 
> --------------------------------------------------------------------------------
> 
> drivers/char/drm/mga_ucode.h (licensed under BSD-style terms) is entirely
> composed of binary code, such as:

*BSD* license right.
 
> static unsigned char warp_g200_tgz[] = {
> 
>         0x00, 0x80, 0x00, 0xE8,
>         0x00, 0x80, 0x00, 0xE8,
> 	[...]
> 
> drivers/char/drm/mga_warp.c relies on those chunks of non-free code.
> 
> Since the licensing terms allow redistribution, shipping it is not illegal but
> is a DFSG violation.

why?

-- 
maks



Reply to: