2008/6/11 Geoffrey McRae <[EMAIL PROTECTED]>:
> I made some fresh traces, here they are attached (I didn't realise they
> would compress this well :)), I hope they help. I have also included my
> EEPROM dump, hope there is no licence problem in doing so, I didn't see
> any copyright info in the dum
2008/6/11 Geoffrey McRae <[EMAIL PROTECTED]>:
> I am more then happy to share the trace... Unfortunately compat-trace
> does not compile on a 2.6.25 kernel properly (missing syms), so I am
> using compat-wireless with my kernel patched with the mmio-trace patch.
> This means that my traces, are mis
I am more then happy to share the trace... Unfortunately compat-trace
does not compile on a 2.6.25 kernel properly (missing syms), so I am
using compat-wireless with my kernel patched with the mmio-trace patch.
This means that my traces, are missing the ath_hal function names. Let
me know where you
On Wed, 2008-06-11 at 10:05 +1000, Geoffrey McRae wrote:
> Hi everyone,
>
> I am new to hardware hacking and I am looking to get the AR2454 device
> working in ath5k, however, due to my lack of understanding of the terms
> used (ie, what is a PHY?), I am finding it very hard to reverse engineer
>
2008/6/11 Geoffrey McRae <[EMAIL PROTECTED]>:
> Hi everyone,
>
Hello and thanks for the feedback ;-)
> I am new to hardware hacking and I am looking to get the AR2454 device
> working in ath5k, however, due to my lack of understanding of the terms
> used (ie, what is a PHY?), I am finding it very
Hi everyone,
I am new to hardware hacking and I am looking to get the AR2454 device
working in ath5k, however, due to my lack of understanding of the terms
used (ie, what is a PHY?), I am finding it very hard to reverse engineer
from trace dumps.
I have managed to add mmiotrace to a x86_64 2.6.25
