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
On Saturday 01 December 2007 01:44:44 Nick Kossifidis wrote:
> 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
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 t
2007/11/30, Michael Renzmann <[EMAIL PROTECTED]>:
> Hi.
>
> > I'm up for it but it'll take some time, also i don't know which wiki
> > to use (is ath5k.org's wiki ready or should i start on madwifi's wiki
> > and then move them ?).
>
> ath5k.org is not yet ready, but it's high up on my to-do list.
> We can also set up a separate Trac instance for that pretty easily and
> turn off stuff that isn't required (such as maybe the Subversion browser).
> It's probably easier to stay within one wiki syntax rather than getting
> used to that of another wiki implementation (at least for those who don'
Hi Bruno and all,
talking about distance tests - if you did that in 802.11a or g, there is
problem with ack timeouts and slottimes - in madwifi it has to be
adjusted manually for longer distances, and from my experience with
ath5k there are problems with acks even when distance is 0,5m, so mayb
Hi Bruno.
> concerning turbog dumps for 5414 i want to do that but i just can't
> configure turbo g on madwifi anymore.
FYI: There is a patch in ticket 1669 [1] that seems to enable dynamic
turbo modes in for 11g. You might want to try if that works.
Bye, Mike
[1] http://madwifi.org/ticket/1669
Nick,
When you get read for traces and dumps for the NDISWrapper, let me know
I have an AR5007EG, thats reported as a AR5006EG, that is working under
NDIS Wrapper at the moment.
Just send me some documention on what i need to do/compile/run, to get
the information needed.
Thanks
Dustin
On F
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 i
Hi.
> But we can use this for writing the specs, no there is wiki for it yet
> though. I had one on Johannes' box before but thought we'd want this
> on MadWifi after it was agreed ath5k would be the top priority. I can
> just move it back to that other wiki, its still up and a simple change
> is
Hi.
> I'm up for it but it'll take some time, also i don't know which wiki
> to use (is ath5k.org's wiki ready or should i start on madwifi's wiki
> and then move them ?).
ath5k.org is not yet ready, but it's high up on my to-do list. I'm
currently working on a draft of the charter for the madwif
On Nov 29, 2007 7:28 PM, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> d) (far away) Start writing specs from what we have.
I have openhal.org, currently it points to
http://madwifi.org/wiki/About/OpenHAL
But we can use this for writing the specs, no there is wiki for it yet
though. I had one on
Hello ppl ;-)
Sorry for not sending patches lately (i've got a few to send) but my
schedule is really tight (exams @ uni again + lab work). I've been
thinking we should start organizing wiki etc to better focus on
current problems:
a) Create a list of all hw-related functions and how well they
wo
13 matches
Mail list logo
