From: Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: rt73usb Access point status
Date: Tue, 12 May 2009 09:16:12 +0100 [thread overview]
Message-ID: <wf4ovqrb1v.fsf@calligramme.charmers> (raw)
In-Reply-To: 20090511035515.83c21b0c.cjsthompson@gmail.com
"Christoph .J Thompson"
<cjsthompson@gmail.com>
writes:
> On Sat, 2 May 2009 11:34:31 +0100
> Luis Correia <luis.f.correia@gmail.com> wrote:
>> No, the bug is not in hostapd.
>>=20
>> As Johannes says, the bug is in the driver.
>> Apparently, the driver is unable to get the ACK from the hardware an=
d
>> thus unable to report that ACK back to hostapd.
>>=20
>> So the hostapd hack works, as long as there are enough room for
>> retransmit supposely lost frames.
>>=20
>> I can't explain this well enough in English, sorry.
>
> Apparently there is no bug in neither hostapd nor the
> driver. From what I understood the hardware is incapable
> of doing it or the firmware needs to be fixed.
Is there any prospec of persuading Ralink either to release
a mended version of the firmware or to free the old version?
What is it that Alexandre Becholey is doing, though? It
looked promising to me.
>> To be completely honest with you in this whole AP issue, here's what=
I
>> used to say to my friends: "if you need an AP working flawlessly und=
er
>> Linux, got with the Atheros b/g hardware".
>> But that was in the madwifi days, I haven't tested it with the curre=
nt
>> mac80211 based driver.
>
> But if he can't use anything else than a USB dongle than
> Atheros is useless.
Quite. No free PCI slots, for example.
> In my case I can't use anything else than a USB dongle on
> my AP because there's only one case you can use for this
> embedded board (ALIX 2d3) and it doesn't have a hole for
> an external antenna as it's the model with 3 ethernet
> ports.
I think my solution to that would involve HSS tools, but
your point is a good one.
--=20
J=C3=B3n Fairbairn Jon.Fairbairn@cl.cam=
=2Eac.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-12 8:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 13:41 rt73usb Access point status Joerg Pommnitz
2009-04-30 13:55 ` Johannes Berg
2009-04-30 13:56 ` Luis Correia
2009-05-02 10:18 ` Jon Fairbairn
2009-05-02 10:34 ` Luis Correia
2009-05-11 1:55 ` Christoph .J Thompson
2009-05-12 8:16 ` Jon Fairbairn [this message]
2009-05-12 19:58 ` Christoph .J Thompson
2009-05-16 8:58 ` Jon Fairbairn
2009-05-16 9:32 ` Ivo van Doorn
2009-05-17 8:47 ` Jon Fairbairn
2009-05-17 12:51 ` Christoph .J Thompson
2009-05-17 14:31 ` Jon Fairbairn
2009-05-17 16:33 ` Gábor Stefanik
2009-05-18 11:12 ` Alexandre Becholey
2009-05-30 8:12 ` Russell Senior
2009-05-30 15:06 ` Christoph .J Thompson
-- strict thread matches above, loose matches on Subject: below --
2009-04-25 14:44 Edimax EW-7318USG as Access Point? Jon Fairbairn
2009-04-30 9:39 ` rt73usb Access point status Jon Fairbairn
2009-04-30 9:51 ` Luis Correia
2009-04-30 9:58 ` Luis Correia
2009-04-30 10:05 ` Johannes Berg
2009-05-11 1:40 ` Christoph .J Thompson
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=wf4ovqrb1v.fsf@calligramme.charmers \
--to=jon.fairbairn@cl.cam.ac.uk \
--cc=linux-wireless@vger.kernel.org \
/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