On 9/7/06, Martin Langer <[EMAIL PROTECTED]> wrote: > On Thu, Sep 07, 2006 at 02:28:53PM +0200, Bin Zhang wrote: > > On 9/7/06, Martin Langer <[EMAIL PROTECTED]> wrote: > > >On Wed, Sep 06, 2006 at 04:51:08PM -0500, Larry Finger wrote: > > >> Martin Langer wrote: > > >> > Those old microcodes 2 and 4 seem to have a different instruction set > > >in > > >> > their firmware than later ones. So I'm afraid that those old bcm43xx > > >> > cores are based on a different microprocessor. And if they are really > > >> > based on a different microprocessor then their drivers will probably > > >> > have different problems. But this theory will only fit if your problems > > >> > are limited to the 0x812 rev2/rev4 world. Just my $0.02. > > > I have this problem. This is the line in my syslog : > > bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled > > Ok, this will load bcm43xx_microcode5.fw which is one of the newer ones. > So we can forget that idea. It can not related to those rare old ones > only. > grep "bcm43xx: Core" /var/log/syslog gives me other numbers
Sep 7 14:44:17 localhost kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled Sep 7 14:44:17 localhost kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled Sep 7 14:44:17 localhost kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled Sep 7 14:44:17 localhost kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled Sep 7 14:44:17 localhost kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled Thanks, Bin > Martin > > PS: Don't forget to send a copy of your mail to [EMAIL PROTECTED] > next time. > _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
