On Thu, Jul 06, 2006 at 10:50:00AM -0400, Joseph Jezak wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Martin Langer wrote: > > On Thu, Jul 06, 2006 at 10:25:40AM -0400, Joseph Jezak wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> As far as I can tell, the 4.x firmware isn't all that different, > >> it's the initvals that are causing the trouble. > > > > Really? I can break my system if I use 3.130 files and replace _only_ my > > microde5 file with a 4.x one? That doesn't fit together. > > > > I don't understand what you're saying here. Does replacing your > firmware cause trouble? I didn't say anything about breaking your > system. :p
The driver will not work if I used mixed firmware files. If I use a 4.x microcode and 3.x initvals and a 3.x pcm file, I'll get bcm43xx error messages and the driver doesn't work. My conclusion was: The ucode is different. Another possibility is: This pair of initvals and ucode is different. So you have the impression that the initvals are wrong, but it has to be the pair (ucode and initvals). > >> I guess what I'm trying to say is that instead of assuming that a > >> certain type of initval follows another, perhaps it would be best to > >> keep the offset of each initval independent, like what is done for > >> the uCode. That and it would be nice to have the a/b/g/n/revision > >> for the initial values instead of the arbitrary numbering scheme we > >> have now. > > > > In the beginning of development I thought that the initvals are related > > to specific ucode releases. But now I think it doesn't change much > > during the time. Probably it would be better to remove the initvals > > extraction and write some init code in the driver. Then we do not have > > to think about extraction optimizations at all. > > The problem is that it does change a little. We don't know what > it's for. There's also binary code (the 0x0301 routing code values, > maybe pcm related, maybe something else) in the initial values. I'm > not sure about the legality of bundling this. I see. Thanks for the info. Martin _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
