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 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. Martin _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
