catch the oops details, I reboot but they have
not appeared in the logs, it must be crashing so hard that the kernel
does not get a chance to write them out.
On Thu, 2009-03-12 at 13:19 +1100, Geoffrey McRae wrote:
> Patched, compiled and running with it now...
>
> Throughput is still
ng, but no error in
dmesg/syslog/debug logs.
-Geoff
On Thu, 2009-03-12 at 03:07 +0200, Nick Kossifidis wrote:
> 2009/3/12 Geoffrey McRae :
> > Hi All,
> >
> > I have a laptop with an AR2425 in it, which the latest compat-wireless
> > works great on, all except for the t
Hi All,
I have a laptop with an AR2425 in it, which the latest compat-wireless
works great on, all except for the throughput.
If I leave the rate to auto, it seems to settle at 36M, but if I force
it to 54M, I loose all RX/TX, even though I am less then one meter from
the AP.
When I do a xfer fr
Isn't that patch slightly wrong anyway?
If the length of the ssid is 0 why check its first byte? Without looking
at the surrounding code, if that buffer is not allocated and we check
the bytes value, it could cause a seg fault.
I would think that the better way to write this would be:
if ((ssid_
I agree, was just pointing out what seemed to be the problem with the
code.
On Thu, 2008-09-25 at 22:39 -0400, Bob Copeland wrote:
> On Fri, Sep 26, 2008 at 09:26:10AM +1000, Geoffrey McRae wrote:
> > I can see the reason why this seg faults...
> >
> > ani_state =
I can see the reason why this seg faults...
ani_state = kzalloc(sizeof(struct ath5k_ani_state), GFP_KERNEL);
shoud be
*ani_state = kzalloc(sizeof(struct ath5k_ani_state), GFP_KERNEL);
On Wed, 2008-09-24 at 08:49 -0400, Bob Copeland wrote:
> > b) During attach i do a bad memory allocation
> >
Hi All,
I have one of these devices in a DLink DWL-G520M, it is currently not
supported according to the madwifi wiki in ath5k. I have had a quick
look through the source, and it looks to not be supported there either,
can anyone please confirm.
If not, I will try to provide some traces over the
Hey All,
I am using nick's patched driver with ar2425 support. iwconfig is
reporting that my TX power is 27dBm, thats about 500mw, is this correct,
can this device actually transmit at those levels? In Australia the max
legal limit is 100mw as far as I know.
Can anyone clear this up? I mean, it w
WBA: 65535, TU: 0x10bf (+3211215)
TIMER3: 0x0031, ATIM:49, TU: 0x108f0031 (+1)
TSF: 0x00423940cd67, TSFTU: 20531, TU: 0x108e5033
BEACON: 0x
LAST_TSTP: 0xb335b180
On Wed, 2008-06-11 at 08:06 +0300, Nick Kossifidis wrote:
> 2008/6/11 Geoffrey McRae <[EMAIL PROTECTED]&g
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
10 matches
Mail list logo
