From: Stefan Rompf <stefan@loplof.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: gene.heskett@verizononline.net,
James Ketrenos <jketreno@linux.intel.com>,
NetDev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 13:29:03 +0100 [thread overview]
Message-ID: <200602251329.03933.stefan@loplof.de> (raw)
In-Reply-To: <20060225105340.GA23643@infradead.org>
Am Samstag 25 Februar 2006 11:53 schrieb Christoph Hellwig:
>From a short glance over the driver code, the protocol between the _open
source_ driver and the binary user space daemon seems to be quite defined and
unobfuscated. Obviously, someone owning the device has to verify that the
daemon doesn't tamper the hardware beyond the driver's back.
> We have support for other software radios.
There is a difference. As kernel developers, we can put the responsibility to
verify that a device can be operated legally on the user, as you said. A
manufacturer, especially a huge one as Intel, is obligated to take this
burden from their customers - obligated may be by law, may be by company
policy.
> If intel doesn't do the right
> thing support for their hardware will have to wait until someone has
> reverse-engineered their daemon [1].
If someone else reverse engineers and replaces the daemon, it may not be
Intel's problem anymore - but that's all not the point.
Actually, Intel invested a lot of time to avoid shipping a binary only driver
or a HAL like madwifi does. So however this settles, they deserve at least to
be adressed in a less insulting tone than you do in your mails.
Thanks,
Stefan
next prev parent reply other threads:[~2006-02-25 12:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 22:29 [Announce] Intel PRO/Wireless 3945ABG Network Connection James Ketrenos
2006-02-24 23:34 ` Dax Kelson
2006-02-24 23:48 ` Jeff V. Merkey
2006-02-25 13:26 ` Michael Buesch
2006-02-25 8:41 ` Christoph Hellwig
2006-02-25 10:49 ` Gene Heskett
2006-02-25 10:53 ` Christoph Hellwig
2006-02-25 11:19 ` Gene Heskett
2006-02-25 13:19 ` Michael Buesch
2006-02-26 1:09 ` Stephen Evanchik
2006-02-25 12:29 ` Stefan Rompf [this message]
2006-02-25 14:19 ` Jan Engelhardt
2006-02-25 22:07 ` Matthieu CASTET
2006-02-25 22:19 ` John Stoffel
2006-02-25 22:28 ` matthieu castet
2006-02-25 22:47 ` Larry Finger
2006-02-26 20:20 ` Alejandro Bonilla
2006-02-26 0:58 ` Alan Cox
2006-02-27 17:10 ` Christoph Hellwig
2006-02-27 17:34 ` Stephen Hemminger
2006-03-03 20:04 ` Kasper Sandberg
2006-03-03 20:31 ` Jeff Garzik
2006-02-26 17:54 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602251329.03933.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=gene.heskett@verizononline.net \
--cc=hch@infradead.org \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).