-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi!
Ok, I tried to debug following bug on a friends iBook (late 2004/early 2005): bcm43xx driver 0.0.1 bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: PHY connected bcm43xx: InitVals written bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x00000800 bcm43xx: DMA reasons: 0x00000000, 0x00000000, 0x00000000, 0x00000000 bcm43xx: DMA TX status: 0x00002000, 0x00002000, 0x00002000, 0x00002000 bcm43xx: 80211 cores initialized bcm43xx: Keys cleared bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x00004800 bcm43xx: DMA reasons: 0x00000000, 0x00000000, 0x00000000, 0x00000000 bcm43xx: DMA TX status: 0x00002000, 0x00002000, 0x00002000, 0x00002000 The last error repeats several times. Now, this looks very familiar. We had the same problem with writing to template ram before (FATAL ERROR), and the fact that the first IRQ Reason is missing 0x00004000 (which is initially written by the driver itself) led me to dummy_transmission(); dummy_transmission is definitely called _before_ the Generic IRQ Reason register is written with 0x00004000. After some playing around, i checked the Status Bitfield inside the bcm43xx_ram_write function _after_ the BCM43xx_SBF_XFER_REG_BYTESWAP should be enabled. Guess what? It wasn't enabled by the write32. Switching firmware didn't help, and my attempts on byteswapping didn't help either. So, reverse engineering peeps: What do you think? Could you have a closer look at the code to write to Template Ram? Is this probably an endianess problem? Danny - -- Danny van Dyk <[EMAIL PROTECTED]> Gentoo/AMD64 Project, Gentoo Scientific Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDta7raVNL8NrtU6IRAhwRAJsFfswtzIMlu6ctElnZf+wPnz2RrwCggXvm y6cSHNFrmerdNyP1SlsEPYU= =YzUn -----END PGP SIGNATURE----- _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
