Re: [GNU-linux-libre] Freedom issues with non-free firmware in external files

[Rubén Rodríguez Pérez]

El vie, 14-08-2009 a las 14:15 -0300, Diego Saravia escribió:
> >-Linux includes some -GPL'd- modules that load firmware files into the
> >devices. Most of that files are non free,
> 
> or only some?

I don't know the figures, but many.

> > -Newest linux-libre versions remove not only the embedded blobs, but
> > also the ability of the modules to request non-free firmware files.[2]
> 
> request?
> 
> or only print info about what is missing?

The vanilla kernel prints an error about the missing files if the
request fails. For the case of non-free blobs, linux-libre now prints
a /*DEBLOBBED*/ message, and the files are not actually requested.


> > -Should GPL modules that are useless without the non-free firmware files
> > be removed?
> 
> why?

(From now on, this is _my_ personal opinion)

If a driver needs a non-free firmware file to work, removing it renders
the driver useless, so you can remove it. Having non working drivers
looks pointless to me, and can -maybe in a subtle way- cause harm.

> > -Should they be kept, but disabling the file load call?
> 
> what if someone develops a free file replacement?

Then the maintainer of the freed version of the kernel can stop removing
that module.

> is there another way to detect that hardware?

All hardware can be detected. That part doesn't matter.

> is not usefull to know what hardware do not have frre software to work with?

Yes, but how is that related to the load call thing?

> >
> > -What is enough to comply with the Guidelines for Free System
> > Distributions? [3]
> 
> is this free guideline fine?

Is ok for me, but maybe it needs some clarifications (like this issue).

> >
> > Note that this issue was already discussed in January by Richard
> > Stallman, Alexandre Oliva et. al. at the linux-libre lists[4], leading
> > Alexandre to implement one of the discussed solutions in the linux-libre
> > deblobber. Other solutions are possible, so this new thread should focus
> > on what is _enough_ to achieve a fully free kernel.
> 
> is free-linux something usefull? or the removal can be done by a
> script running over a normal kernel?

I'm not sure if I'm getting your question. :|

> do free distros must have non-free-software-having-hardware detection
> procedures and user warnings?

Please, explain "non-free-software-having-hardware detection procedures"