> Having this conversation every rc1 is getting a bit silly.
Hmm, wouldn't the obvious thing than to add the driver in it's current
form into staging? Is it well-separated from the rest of Atheros
WLAN drivers ?
___
ath5k-devel mailing list
ath5k-devel
Okay, I admit that I cannot help you, I have no clue on the driver level.
But maybe I can help with the methodology. :-)
You mention 802.11p (car-to-car-communication). Is there any specific
reason you base it on ath5k and not on ath9k? If you look at the
number of commits, then you should see t
Nowhere.
ath5k is just the driver and sends the beacons that it should send.
It's not driver-specific, therefore this mailing list isn't the ideal
place.
The Linux subsystem that configures "what it should send" is mac80211,
so you better ask in the general linux wireless mailing list (see
http:/
No. And yes. That would be a layer violation. The question is like
asking "Will Goodmonths tires support driving to Paris?". The answer
is: the tires don't care. They are there to rotate.
Similarly, ath5k doesn't care. It's there to change frequency,
transmit and receive packets.
802.11k would h
You're probably 5 years too late. The MADWIFI driver is quite out of
fashion nowadays and few people are still hacking on it. I wouldn't base
any new development on it.
What you describe is a bit like diversity: receive with all antennas,
determine which antenna had the highest RSSI, use that ante
How to use "iw" is a googling away from you.
If you do nonstandard stuff, e.g. trying things out, I'd suggest
module parameters or the debugfs. "iw" isn't good for such
quick-n-dirty stuff, because iw goes the path
nl80211->cfg80211->mac80211->driver (or something like this). Lots of
hoops.
If yo
This question can't be answered. :-)
You cannot assume that everyone reading that list knows 802.11p in
detail. This also makes almost know no-one to know what has to be
changed to make ath5k 802.11p "enabled". It might very well be the
case that you don't need to change the driver at all, but ins
You can "rename" an interface with an UDEV rule at creation time.
I haven't checked if "ifrename" works, but I guess that'll do it, too.
A third option is this:
iw wlan0 interface add ath0 type station
iw wlan0 interface del wlan0
___
ath5k-devel maili
Hi, DH3HS here.
Madwifi source code is End-of-life here, I wouldn't recommend this.
There are amateur radio specific WLAN router distributions available,
you should go to one of them to ask for specifics (e.g. source code).
There are various project to build links all over the country, e.g.
HAMNE
> 1) if card is not able to run in adhoc mode why the iwconfig does not report
> error when i have used iwconfig command ?
Because "iwconfig" is the wrong tool. You should use "iw". See
http://wireless.kernel.org/en/users/Documentation/iw
For some hints on how to setup adhoc, see
http://wireless
> iw phy phy0 interface add wlan0 type adhoc
> iw wlan0 set channel 36
> iwconfig wlan0 channel 36
> iwconfig wlan0 essid txctest
I can't think of ANY reason why you do that. Use "iw", not "iwconfig".
All the last three commands should be replaced with one single "iw dev wlan0
ibss join myibss
> For research purpose, I want to make the Atheros wifi card to send out
Jin YunYe,
this is *NOT* targeted especially to you, so please don't be offended.
Can it be the case that "research" is a mostly a one-way road? Every other
week I read from someone "For a research we need to do this and
@@ -2770,7 +2767,7 @@ ath5k_intr(int irq, void *dev_id)
* RXE bit is written, but it doesn't work
at
* least on older hardware revs.
*/
- sc->rxlink = NULL;
+
> I know that ath5k = Madwifi with no HAL
What you "know" is plain wrong.
--
http://www.holgerschurig.de
___
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
> If you remove the antenna of your card, wind the receive gain down to the
> minimum possible value, your card card will receive the minimum of packets
> from other boxes.
Wouldn't it be even better to do a proper termination between ground and
signal, e.g. by a shielded 50 Ohm resistor?
(Not s
Some clients (including mac80211 as client) use probe requests (frame 59) to
the AP to find out if they're still connected, e.g. see net/mac80211/work.c
for IEEE80211_ASSOC_MAX_TRIES and friends.
After the probe without answer, there was still a successfull data exchange,
see the ARP query/resp
> i don't know where "Rx invalid nwid", etc. went unfortunately...
To limbo, as it's kind of useless. When you have SSID "BLAH" and receive a
beacon for SSID "MURPS", it's increasing.
As this doesn't say much that, I don't cry now it's gone. If I really want to
know about beacons, I'm using wir
> [ 2960.591578] ath5k phy0: noise floor calibration timeout
> (2422MHz)
If it happen only this and then, then no. That's why Bob Copeland
patched it away:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=commitdiff;h=e5e2647fd6ceef2cdc479954b84517535eb7febd
If it happens
> Have you even looked at the driver?
He first asked on the madwifi mailing list and was told to use
ath5k for his study project, so maybe he didn't really look. But
hey it's gread that he actually took the advice, so don't be
harsh with him :-)
Muhammand, you said in your subject just "Help!
> And if your IBSS and the AP already sent the coverage class
> through the country IE I am not sure if we should allow
> overriding it.
Hmm, I think a local setting should override some broadcasted
setting *IF* this cannot be used for some kind of
denial-of-service-attack on links farther away
On Tuesday 15 December 2009 10:46:00 Xavier Bestel wrote:
> > Try with "country_code=SE".
Oops, I meant "without", of course.
Also, the hostap mailing might be a much better forum for this
type of question: http://lists.shmoo.com/mailman/listinfo/hostap
--
http://www.holgerschurig.de
__
Some tips:
make sure that no udev rule renames the wlan0 to ath0. I once had
problems with a renamed device, but didn't investigate this
further.
when "ifconfig -a" shows you a "wlan0", change your hostapd.conf
and try again.
Set the log leven to debug. After all, you're debugging :-)
Try wi
> What about providing a higher abstraction, a "distance"
> parameter instead of acktimeout, csttimeout and slottime? For
> example 'iw phy0 set distance 3000'. Definitely at least ath9k
> hardware supports this feature.
Sounds like a plan --- but you should really ask/propose in
linux-wireless,
On Sunday 22 November 2009 01:36:43 Luis R. Rodriguez wrote:
> No, not all hardware can change this, we also don't want to
clobber iw
> with hw specific knobs.
I see it differently. Debugfs is for debugging, not for API. If
you'd use debugfs for it, then you'd force every embedded
developer to
> There are already other reports of this problem in discussion
forums.
> It seems, the old madwifi-driver works better with dhcp - so
people say.
I cannot second that. For me, ath5k works perfectly with DHCP,
with WEXT ("iwconfig") and NL80211 ("iw") and with
wpa_supplicant.
DHCP was NEVER an
> Hello !
Sound's cool.
However, to get your patch accepted, you'd need a real-name and a
proper Signed-off-by line.
The real-name is a legal requirement, but apart from legal I
personally find it IRC-kiddy-style to use nicknames in Linux
related mailing list. But thats, as I said it, a matte
On Sunday 26 October 2008 23:47:49 Nick Kossifidis wrote:
> O.K. let's use this one ;-)
> http://madwifi.org/wiki/About/ath5k/TODO
ath5k is part of the kernel, why not using the central place for
all in-kernel wireless modules, http://wireless.kernel.org ?
> Acked-by: Nick Kossifidis <[EMAIL PROTECTED]>
I don't think it is necessary to quote everything in such a
case ...
___
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
> now, if i only knew how to create some background noise, to
> get more samples... microwave ovens?
Would that work?
Use another madwifi card, with madwifi-dfs in continuous transmit
mode?
Have the noise-receiving card at channel 1, and use the other
card on channel 3, then 2, then 1 to incre
29 matches
Mail list logo
