[lkml]   [2002]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Kernel module ethics.

> The other compromise is to write a closed source part that would not permit
> the driver to work with another card supporting the same chipset. Is this
> kind of practice generally accepted or is it frowned upon? The motive of
> the company is quite clear. If people want to "improve" the driver, they
> can only improve it for their hardware, not the competitors. There is also
> a big marketing sales pitch that goes like "we support linux, the others
> don’t..."

If you can detect that it is indeed your company's card and not the
competitors (who seemingly uses the same chipset), perhaps your
closed-source userland firmware load utility could take advantage of this to
refuse to load the firmware if the right implementation of the device is not
found? This'd allow you to keep the kernel driver open and still satisfy the
requirement of "screw the competition".

Just my 2¢.

-- Cyrille


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.100 / U:4.392 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site