2010/2/28 Nathan Schulte <rekl...@gmail.com>: > On Sat, Feb 27, 2010 at 7:03 PM, Nathan Schulte <rekl...@gmail.com> wrote: >> 2010/2/27 Larry Finger <larry.fin...@lwfinger.net>: >>> The printk's I sent yesterday can have timing info, but the timestamps >>> would not >>> be exactly coordinated - printk values seem to be generated when logged, not >>> when requested. >> I modified mmiotrace to log via printk as well, which should give the >> desired results. >> >> I will post the same mmiotraces as requested before, once I complete them. > http://vulcan.ist.unomaha.edu/~nmschulte/mmiotraces_syslog.tar.bz2 > > *_syslog contains mmiotrace and pci read/write synchronously merged > via printk to syslog. The log messages were prefixed with ~~, and are > in context with the rest of syslog. A simple awk should be able to > remove the context, but there's not much of it (and what there is is > relevant to the drivers in question), so I left it in. > > -Nate >
OK, this dump shows the 0x280a write happening with core 3, i.e. PCIE, active. So, it is indeed probably the "PCIE misc configuration" routine. Why it's 0x280a is still a mystery to me, it should be 0x100a according to the specs. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
