linux-kernel - Re: [PATCH] USB: mark USB drivers as being GPL only

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080206222937.2aa69a2e@weinigel.se>
Date:	Wed, 6 Feb 2008 22:29:37 +0100
From:	Christer Weinigel <christer@...nigel.se>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Diego Zuccato <diego@...llo.alma.unibo.it>,
	David Newall <davidn@...idnewall.com>,
	Greg KH <greg@...ah.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only

On Wed, 06 Feb 2008 21:55:45 +0100
Marcel Holtmann <marcel@...tmann.org> wrote:

> > So how does that invalidate my point?  Intel did jump through a lot
> > of hoops to avoid giving away the code that controls their radio.
> > When the regulatory daemon stuff got too much complaints, they
> > finally redid their firmware to avoid the daemon.  But they still
> > have not exposed the details on how to control their radio.
> 
> find an Intel engineer that worked on it. There is a bigger story
> behind it and I am not telling it.
> 
> And btw. it is perfectly fine that Intel is not giving full access to
> their radios. Why should they?

I think it is perfectly within their rights to do so.  I think it's
kind of silly to try to hide it, if someone wants to boost the maximum
transmit power, they're going to hack the firmware anyway.  But if it
makes Intel happy, well... :-)

> > Yes, that is a nice solution.  Provided that you have any firmware
> > at all.  But price is everything, chips become dumber and dumber
> > and more control functions are pushed to the host.  If you want to
> > sell a device in Korea, price is everything; if you can shave off
> > 30 cents by putting the firmware in ROM, or by using 1.5 mbits of
> > flash instead of 2 mbits, that means an increase in market share or
> > profit margins.  
> 
> I heard this all before and I don't buy it anymore. At some point the
> companies in Asia will understand that the whole picture looks
> different and that not always cheap, cheap, cheap is best for their
> margins.

I've been hoping that they will understand that too.  So far it has
been a futile hope.  It is soo fun to write a design spec saying
"Whatever you do, do not use this chip, it sucks.  Yes, I know it is 50
cents cheaper than the competition, but it is not worth it." just too
see exactly that chip being put into the product.

> And btw. the fully supported Linux hardware is in a lot of cases not
> more expensive than the other ones.

Mmm.  I've actually put consulting on the shelf for a while and have
become employed by CSR instead.  They have a really nice, and as far as
I've understood, fairly good and price competitive WIFI chip for low
power systems such as mobile phones or PDAs.  I've gotten a
preliminary go ahead from the bosses to provide documentation under an
NDA to Linux developers that would like to write GPL drivers for it.  I
just haven't had time to do anything more about it yet.  And since I'm
fairly new to CSR and are located at a remote office, it takes time to
find the right people to talk to.

> > > Remember that nobody inside the community ever asked for any kind
> > > of IP or trade secrets. We only want specifications so we can
> > > write the drivers under an appropriate open source license. If the
> > > specification describes an API exposed via firmware then that is
> > > perfectly fine.
> > 
> > I definitely agree.  I think it's stupid of companies to hide away
> > their documentation out of fear of, well, something.  I find it
> > extremely frustrating when I bought a device touted as "the first
> > open Linux mobile", just to find out that it used a binary-only
> > kernel module for the M-Systems DiskOnChip.  A quite nice phone,
> > but due to that one module, it was completely impossible to use
> > anything but the ancient 2.4 kernel it came with.
> 
> You got one of the Greenphones ;)

How could you guess?  :-)  Actually, I got three of them, and all of
them lie unused in a box at work.

And the OpenMoko sucks.  Or actually, it doesn't suck at all, I'm
thinking of buying one just for fun, it's just that I like buttons on
a phone, and really don't want a touch screen.  So I like the OpenMoko
project in every way, it's just not the right phone for me.

  /Christer
--
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/