Re: Free Linux Driver Development!

On Thu, Feb 01, 2007 at 09:45:06AM -0500, Lennart Sorensen wrote:
On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
I can't remember that kind of corruption ever being reported to the
bcm43xx-dev mailing list.

Well I assumed it messed up the eeprom settings, since we had to go into
the advanced driver settings and change it from 802.11b only back to
auto mode and I would think those settings are stored in the eeprom if
booting a 2.6.18 kernel and loading the bcm43xx driver can cause it to
stop working, then it has to be an eeprom setting.

Actually I suppose the other posibility is that you simply have to power
cycle before booting windows after linux to avoid any left over settings
in the chip from being a problem. That may be what I did. Given I
couldn't get the card to connect using the bcm43xx driver anyhow, I
didn't spend too much time trying (I am fairly sure I set the AP to
802.11g only though which may have been a problem).

That's what my laptop needs. Not for the wireless card, but somehow
windows locks up if I just reboot the machine. Of course no nice Oops
message or so.

Excellent. Is the bcm43xx planning to get 802.11g mode working at some
point?

Most certainly, the plans are there for quite some time, but...

Is broadcom ever going to help out with any specs for their
hardware or do they still mistakenly believe that end users are not
their customers?

... the documentation isn't. Right now the only available documentation
comes from reverse engineering. It's actually rather amazing that the
authors came this far, no vendor documentation yet still a lot of
supported cards.

Given the behaviour of broadcom over the years I know
I don't intend to buy anything with a broadcom chip in it again, which
means broadcom's behaviour directly means they will get less sales to the
laptop makers, since some people will actively avoid anything with
broadcom's hardware in it. :)

That's my take as well. They already lost us on the Gig ethernet cards.
A couple of years ago we considered Broadcom based cards, but given the
lack of vendor driver support, we got Intel E1000 based cards instead.
We also considered NatSemi gigE cards, but the Intels were much faster.
Right now we use about 15 E1000's with probably more to come (they go
in every new machine). Not a high figure but still a lost sale for
Broadcom.

As for wireless, for personal use I needed a wireless PCMCIA/CardBus
card and a Linksys bcm4318 based card was the only reasonably supported
card I could get. It works but still has its peculiarities.


Erik

--
+-- Erik Mouw -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Eigen lab: Delftechpark 26, 2628 XH, Delft, Nederland
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: 802.11 WLAN CF card support on WinCE42
    ... and those settings are reasonable for your hardware? ... I'd fix that first and then try to get card drivers to work. ... PCMCIA set and using that value in another call... ... there are a few lines failed in PCMCIA driver ...
    (microsoft.public.windowsce.platbuilder)
  • Re: glxgears question
    ... > driver versions, I decided to upgrade the video card in my ... as it only had an nVidia MX420 card and I ... This could be down to the individual settings for each card, ... Maybe the middle machine has the sync to blank set and is using your ...
    (alt.os.linux.suse)
  • Re: 802.11 WLAN CF card support on WinCE42
    ... Verify that the slot settings for the PCMCIA ... driver are correct and recheck those for the new card. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Free Linux Driver Development!
    ... Well I assumed it messed up the eeprom settings, since we had to go into ... booting a 2.6.18 kernel and loading the bcm43xx driver can cause it to ...
    (Linux-Kernel)
  • RE: [UPDATED PATCH] EFI support for ia32 kernels
    ... >> reuse a single driver image for multiple architectures assuming there ... As one of the people responsible for the EFI Specification and our ... Perhaps the UNDI network card interface that Intel developed ... BIOS can't shadow that much ROM code. ...
    (Linux-Kernel)