linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scherping <richard@scherping.de>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath5k: 10 MHz channels?
Date: Wed, 28 May 2008 19:53:56 +0200	[thread overview]
Message-ID: <483D9C34.2020908@scherping.de> (raw)
In-Reply-To: <40f31dec0805280336r40b102ffx11cbd0c0d465c9f8@mail.gmail.com>

Nick Kossifidis schrieb:

> No work has been done for such features yet, other more important
> things are missing right now. If you want to rev. engineer
> half/quarter rate channels, i think you should start from nic_wakeup
> and reset functions (also check out rx/tx descriptors for the rate
> code). Mmiotrace is your friend ;-)

Thanks very much for your reply, Nick!

In fact I found the piece of code needed to get 10 MHz channels working with the Ubiquity cards today.
I do not have the full code at hand ATM, but it was not more than adding

clock |= 0x100

to hw.c:ath5k_hw_nic_wakeup.

madwifi-trace helped to find that single, but important bit ;-)

ath5k performance still is somewhat limited in ad-hoc mode, but I will try to work on that, too. Are there any ideas yet, that are not already implemented? I refer to the effect that a simple ping between two ath5k ad-hoc stations has only about 80 % success rate...

Thanks for your great work! With the full frequency range and free choice of channelwidths ath5k is about to exceed even specially modified MadWifi versions in functionality.

Richard

  reply	other threads:[~2008-05-28 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 20:05 ath5k: 10 MHz channels? Richard Scherping
2008-05-28 10:36 ` Nick Kossifidis
2008-05-28 17:53   ` Richard Scherping [this message]
2008-05-29  0:19     ` Nick Kossifidis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=483D9C34.2020908@scherping.de \
    --to=richard@scherping.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mickflemm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).