Michael Buesch wrote: > On Sunday 20 April 2008 22:41:27 Larry Finger wrote:
--snip-- >> +Obtaining a disk copy of the sprom contents >> +------------------------------------------- >> + >> +This file name for the sprom contents depends on the bus layout of >> +the specific computer being used and will be something cryptic like >> + >> +/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.0/ssb_sprom >> + >> +It is not recommended that you try to type the name. Instead, you >> +should use the following commands to get the working copy: >> + >> +SSB_SPROM=$(find /sys -name ssb_sprom) >> +sudo cat $SSB_SPROM > ssb_sprom_copy > > This is _dangerous_, if the person doing this has two SSB based > cards in the machine. It is extremely dangerous, if there's a b44 and b43 > card in the machine! > We should instead go the way down explaining what this "cryptic" (no it's > not cryptic) path means and explain how to derive it from lspci info. If the above commands were run on a machine with more than one SSB-based device, I expect that SSB_SPROM would have one line for each. Is this correct? > >> +Modifying the contents of the working copy >> +------------------------------------------ >> + >> +You may now look at the contents of your sprom with the command >> + >> +ssb-sprom -i ssb_sprom_copy -P >> + >> +As an example, let us suppose that you have purchased a Dell mini-pci >> +card to use in an HP laptop. The HP BIOS refuses to use the card when >> +the pcivendor is Dell (code 0x1028), not HP (code 0x103C). From the >> +dump above, we learn that the pcivendor code is a 16-bit quantity >> +stored at 0x06. To change that code, we use the commands >> + >> +ssb-sprom -i ssb_sprom_copy -o ssb_sprom_copy -s 0x06,0x3C >> +ssb-sprom -i ssb_sprom_copy -o ssb_sprom_copy -s 0x07,0x10 > > This can be done in an easier way: > > ssb-sprom -i ssb_sprom_copy -o ssb_sprom_copy --subv 0x103C > >> +to write the two bytes separately. The documentation implies that >> +these data could be written as a single 16-bit quantity; however, >> +that doesn't work at the moment. > > I'm not sure which part of the documentation does imply that. When I originally wrote this, I couldn't get the --subv switch to work. It does now and this section has already been rewritten. See V2 in your mailbox. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
