From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 23:07:54 +0100 [thread overview]
Message-ID: <pan.2006.02.25.22.07.53.810642@free.fr> (raw)
In-Reply-To: Pine.LNX.4.61.0602251518200.31692@yvahk01.tjqt.qr
Hi everybody,
Le Sat, 25 Feb 2006 15:19:40 +0100, Jan Engelhardt a écrit :
>>If the modules crc changes,
>>it must do an instant disable of the transmitter functions and exit or
>>crash, thereby precluding any 'hot rodding' of the chipset.
>>
> Would not it be easiest to have the chipset enforce the acceptable bands?
> So that software can't switch the chipset to 1337 GHz no matter how hard
> you forward/reverse-engineer it.
>
I will say, why not put the restriction of the firmware binary blob ?
It run on the device so it will be difficult for people to analyse it.
Also the firmware could be on a eeprom and transparent for the user.
Matthieu
next prev parent reply other threads:[~2006-02-25 22:07 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
2006-02-25 14:19 ` Jan Engelhardt
2006-02-25 22:07 ` Matthieu CASTET [this message]
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=pan.2006.02.25.22.07.53.810642@free.fr \
--to=castet.matthieu@free.fr \
--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).