To: linux-kernel@vger.kernel.org
From: Matthieu CASTET <castet.matthieu@free.fr>
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 23:07:54 +0100
Message-ID: <pan.2006.02.25.22.07.53.810642@free.fr>
References: <43FF88E6.6020603@linux.intel.com> <20060225084139.GB22109@infradead.org> <200602250549.47547.gene.heskett@verizon.net> <Pine.LNX.4.61.0602251518200.31692@yvahk01.tjqt.qr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux))
Cc: netdev@vger.kernel.org
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 906
Lines: 20

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/