On Thu, Aug 09, 2007 at 04:35:53PM +0200, Michael Buesch wrote:
> On Thursday 09 August 2007 16:09:53 Larry Finger wrote:
> > Michael Buesch wrote:
> > > It turns out that it's better to extend the device
> > > support in bcm4301 due to more difficulties in reverse
> > > engineering the newer bcm drivers.
> > > Newer drivers don't contain support for wireless core ref < 5
> > > anymore. So I suggest we support <5 devices with the legacy
> > > driver using v3 firmware. And anything above with v4 firmware
> > > with upstream bcm43xx-mac80211.
> > > That's actually a nice cutoff point, as rev 5 is when they
> > > started using the new microcode format.
> > > 
> > > So, that said, I want to rename all the drivers.
> > > My plan was to rename "bcm43xx-mac80211" to "b43", so
> > > you could probably rename bcm4301 to b43-legacy or something
> > > shorter like b43-leg or maybe even b43-old.
> > > 
> > > Any comments?
> > > 
> > 
> > I like the idea of b43 and b43-legacy. As a "senior citizen", I'm beginning 
> > to dislike the adjective 
> 
> Feel free to drop the -.
> I think b43legacy is even better (to type, to read, it's shorter..)

I wouldn't call it b43. Please add some letters here. 

BCM is still developing their bcm43xx platform. So it's possible that we 
will find another point in the future where we have to split b43 again. 
b43 is more a common name in my eyes and b43something would be better. 

I think b43legacy, b43something, b43nextgeneration,... as parts of the 
b43 family sounds much clearer to me. There should be a difference 
between the driver and the family.

But unfortunately I don't have a good idea for the right name. 

Just my $0.02
Martin
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to