Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread Michael Renzmann
Hi. > i have just created a madwifi branch prepared for tracing > (madwifi/branches/madwifi-trace) and checked in my scripts to make tracing > easier. so getting register traces is really easy now. Tarballs for this new branch are now automatically created and available for download. For downloa

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread bruno randolf
hello! i have just created a madwifi branch prepared for tracing (madwifi/branches/madwifi-trace) and checked in my scripts to make tracing easier. so getting register traces is really easy now. it's all documented here: http://madwifi.org/wiki/DevDocs/MadwifiTrace i uploaded the trace informa

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread Nick Kossifidis
2007/10/31, bruno randolf <[EMAIL PROTECTED]>: > On Wednesday 31 October 2007 00:50:28 Luis R. Rodriguez wrote: > > Nice, how about we start an svn branch on madwifi with this stuff, it > > might be easier for users. I understand the current instructions are > > pretty involved. > > yep, that's fin

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread bruno randolf
On Wednesday 31 October 2007 00:50:28 Luis R. Rodriguez wrote: > Nice, how about we start an svn branch on madwifi with this stuff, it > might be easier for users. I understand the current instructions are > pretty involved. yep, that's fine with me. i'd also like to add my trace and decode scrip

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread Luis R. Rodriguez
On 10/30/07, bruno randolf <[EMAIL PROTECTED]> wrote: > hi luis! > > adding the following patch lets us log the calling function names as well! > which makes it much easier to make sense to the traces :) > > and i added ALQ=1 MMIOTRACE=1 and the objdump command to the Makefile as well > to avoid fo

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread Luis R. Rodriguez
On 10/30/07, Dan Williams <[EMAIL PROTECTED]> wrote: > On Tue, 2007-10-30 at 17:49 +0900, bruno randolf wrote: > > hi luis! > > > > adding the following patch lets us log the calling function names as well! > > which makes it much easier to make sense to the traces :) > > > > and i added ALQ=1 MMIO

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread Dan Williams
On Tue, 2007-10-30 at 17:49 +0900, bruno randolf wrote: > hi luis! > > adding the following patch lets us log the calling function names as well! > which makes it much easier to make sense to the traces :) > > and i added ALQ=1 MMIOTRACE=1 and the objdump command to the Makefile as well > to av

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread bruno randolf
hi luis! adding the following patch lets us log the calling function names as well! which makes it much easier to make sense to the traces :) and i added ALQ=1 MMIOTRACE=1 and the objdump command to the Makefile as well to avoid forgetting that. cheers, bruno this time the patch is included,

Re: [ath5k-devel] MadWifi HAL register dumps - help reverse engineering

2007-10-30 Thread bruno randolf
hi luis! adding the following patch lets us log the calling function names as well! which makes it much easier to make sense to the traces :) and i added ALQ=1 MMIOTRACE=1 and the objdump command to the Makefile as well to avoid forgetting that. cheers, bruno On Saturday 20 October 2007 04: