[lkml]   [2007]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Free Linux Driver Development!
On Tuesday 30 January 2007 23:23, Lennart Sorensen wrote:
> On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
> And seems to do 802.11b only and screw up the eeprom settings so that
> the windows driver gets confused next time you boot windows. Lovely

Nah, why do you think it will screw up the eeprom?
Did you try to completely power off the machine before rebooting
into windows?

I _really_ _really_ _really_ think that there is no chance of writing
the eeprom by accident. It is protected by some write-enable bit in
PCI config space. There is only one place where we enable that bit
and where we actually _write_ to the eeprom shadow mmio space. That's
the eeprom writing code. It will output _lots_ of kernelmessages that
you really can't miss when that happens. And it's only called on behalf
of a private ioctl user request. _And_ it verifies the data with a CRC
check. So you really can't call it by accident.

But prove me wrong and show the code that writes to eeprom. :)

> driver. If the bios on the laptop in question would let me change the
> minipci card I would. To something with a ralink on it.
> Seems the ralink driver maintainers are doing a lot of the work on the
> core wifi infastructure too. Lots of work beyond just the driver then.

Are you suggesting that bcm43xx people don't, or what?
Are you living on another planet than me? Mine is called "Earth".

Greetings Michael.
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: 2007-02-01 16:51    [W:0.199 / U:0.816 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site