From: James Ketrenos <[email protected]>
Date: Tue, 11 Jul 2006 17:35:48 -0700
> The obvious distinction between scsi firmware and the regulatory
> daemon blob being discussed here is that the regulatory daemon runs
> on the host vs. an adapter. However, if you consider the
> communication interface between the kernel and the user space daemon
> to be analogous to the communication interface between the kernel
> driver and the firmware that runs on an adapter, then the
> distinction of running on the host is irrelevant.
The core issue is whether the userland blob could stand alone and is
something that could exist independant of Linux and the kernel side
GPL'd driver.
Difficult areas arise when you design a set of interfaces specifically
to talk to the binary blob, and which exist for no other purpose and
do not provide some well defined "standard" API such as the SCSI
command set, as an example. It is just a backdoor into the binary
blob, and therefore this could make it more likely to be considered
a derivative work.
Firmware that runs on the card is also a tricky area, and not everyone
agrees on that issue as well.
Unfortunately, none of this is fun stuff :-/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
