hi nick! i just checked in changes to the script which i hope do what you want.
use it like: ./ath-reg-decode.pl --init rf regs a b g ta tg ./ath-reg-decode.pl --init mode regs a b g ta tg the reg file should have a '\n' at the end. hope that helps, bruno On Saturday 01 December 2007 01:44:44 Nick Kossifidis wrote: > 2007/11/30, bruno randolf <[EMAIL PROTECTED]>: > > hi nick! > > > > you wiki plans sound good! > > > > since you mentioned writing specs, what use would they be of, since we > > don't do "clean room" reverse engineering anyways? (i wonder since a > > while where that puts us legally and why other drivers chose that method > > instead.) > > > > i think the txpower stuff is very important. this week i made distance > > tests with ath5k (AR5212) and they were pretty disappointing. i stopped > > them at 80 meters :( > > > > concerning turbog dumps for 5414 i want to do that but i just can't > > configure turbo g on madwifi anymore. any pointers on how to set up > > turbog on madwifi would be helpful (i know > > http://madwifi.org/wiki/UserDocs/TurboMode but that doesnt work for g). > > maybe i have the wrong regdomain/countrycode (i tried 0/0 and 0/840)? > > > > i'm willing to work on improving the script, but don't quite understand > > what you want exactly (yet). do you mean: take testbed connection traces, > > search for last reset cycle, and print it out as > > ath5k_ini_mode/ath5k_ini_rf tables? that should be easy enough to do. but > > which parts go into ath5k_ini_mode and which into ath5k_ini_rf? please > > clarify, what you need, i'll do it :) > > > > bruno > > I mean something much simpler because i prefer to pick dumps manualy, > do diffs to understand how it works etc so feeding the script with > traces of reset function wouldn't help much. What i mean is something > like this: > > I have a file "regs" which contains the register addresses, eg. > > 0x001 > 0x002 > 0x003 > > and 5 files, one for each mode (a/b/g/turboa/turbog) that contain the > values for these registers, eg > > mode_a: > > 0x01a > 0x02a > 0x03a > > mode_b: > > 0x01b > 0x02b > 0x03b > > etc.. > > We feed all files to the script, pass the paramerer -rf for ini_rf and > -mode for ini_mode table and script creates tables like this... > > -mode: > > { 0x001, > /* a/XR aTurbo b ...*/ > { 0x01a, 0x01af, 0x01b, ..., ... } }, > { 0x002, > { 0x02a, 0x01af, 0x02b,..., ... } }, > { 0x003, > { 0x03a, 0x01af, 0x03b, ..., ... } }, > > -rf: > > { 0, 0x001, > /* a/XR aTurbo b ...*/ > { 0x01a, 0x01af, 0x01b, ..., ... } }, > { 0, 0x002, > { 0x02a, 0x01af, 0x02b,..., ... } }, > { 0, 0x003, > { 0x03a, 0x01af, 0x03b, ..., ... } }, > > > If you are up to something more automated you can do diffs between > reset's traces, see what register (which are only written as part of > initialization -> static values) values change between modes and > create an ini_mode table. For ini_rf table you grab dumps that start > with RF_BUFFER and end with a RF_BUFFER_CONTROL_X or directly writes > on RF_BUFFER_CONTROL_X. Anyway it's more complicated than that, what i > want is a simple script to create the tables so i don't have to create > them manualy (i create the files easily by c/p parts of traces etc so > i'm not afraid of doing mistakes there, my only problem is putting > them together). _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
