Hi All,
Some VERY good questions.
A *LOW* level interface would seem like a good beginning. i.e.- So
anyone can confirm what is really going on at the RF level and confirm
things are working as expected.
Maybe that is a called a debug interface ??!!
IMHO - there is a LOT of
Hi All,
I notice that the wireless driver version in xpud works reliably,
while the version in puppy does not? The puppy version comes up OK, but
then dies after a short time (minutes)?
I wonder if the wireless driver can (easily?) be arranged to be kernel
version independent? It would
Hi,
You can be *SURE* that the hardware has the capability of measuring
lots of things about the incoming signal(s).
Some of the manufacturer provided drivers may give clues as to what and
where these are.
I have always felt that a real-time monitoring of the memory used by
the driver
Hi All,
preaching
The chip *FOR SURE* *CANNOT* measure the thermal noise level!! It isn't
that sensitive. That said under some conditions it CAN measure the
local interference level which IS useful.
I am *VERY MUCH* in favor of making real time level measurements of
various parts of
Hi,
I see occasional junk as reported signal strength too !!
Buggy Atheros code or hardware I assume.
Regards,
Wiz
On Thu, 11 Mar 2010, yingqiang Ma wrote:
[NON-Text Body part not included]
___
ath9k-devel mailing list
Hi,
So is the problem with 5/10 operation JUST in software?
Is the hardware capable of 5/10 ?
Thanks.
On Tue, 15 Dec 2009, Luis R. Rodriguez wrote:
On Tue, Dec 15, 2009 at 01:16:29AM -0800, Robert Budde wrote:
On Mon, Dec 14, 2009 at 11:19:47AM -0800, Luis R. Rodriguez wrote:
Hi All,
It seems to me that this WHOLE wireless mesh business began when
someone at MIT hacked the Atheros driver I assume they either had
sources or a good MIPS reverse compiler? Maybe both?
The openwrt.org 'more or less' open Atheros driver doesn't work
reliably on my Meraki Minis
