linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: RUMI Szabolcs <rumi_ml@rtfm.hu>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: ath5k master (AP) mode
Date: Thu, 13 Nov 2008 23:59:28 +0100	[thread overview]
Message-ID: <20081113235928.3ed79ff6.rumi_ml@rtfm.hu> (raw)
In-Reply-To: <1226598550.5839.3.camel@johannes.berg>

On Thu, 13 Nov 2008 18:49:10 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:

> > I have compiled a kernel from wireless-testing git of today (2.6.28-rc4-wl)
> > then recompiled and tested hostapd-0.6.5 against that,
> 
> look, you need hostapd from git

If you look a bit further down in that email, I've also tried
exactly that afterwards but unfortunately it made no difference.

BTW I've made a diff -rduN between hostapd-0.6.5 and todays -git
but haven't spotted anything relevant to my problem anyway.

To summarize:

2.6.27 + hostapd-0.6.5 = NO
2.6.27 + OpenWRT hack + hostapd-0.6.5 = NO
compat-wireless-2008-11-12 + hostapd-0.6.5 = NO
wireless-testing-git + hostapd-0.6.5 = NO
wireless-testing-git + hostapd-git = NO

In fact I've also tried hostapd-0.6.4 and 0.5.10 at some point
but they didn't make anything better.

Thanks,

Sab

  reply	other threads:[~2008-11-13 22:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 21:48 ath5k master (AP) mode RUMI Szabolcs
2008-11-12 22:46 ` Pavel Roskin
2008-11-12 23:46   ` RUMI Szabolcs
2008-11-13 17:11     ` RUMI Szabolcs
2008-11-13 17:49       ` Johannes Berg
2008-11-13 22:59         ` RUMI Szabolcs [this message]
2008-11-13 23:03           ` Johannes Berg
2008-11-13 23:07           ` Nick Kossifidis
2008-11-14 10:15             ` RUMI Szabolcs
2009-02-10 12:14               ` RUMI Szabolcs
2009-02-11 21:49                 ` Nick Kossifidis
2009-02-12  2:11                   ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11 18:47 Norman Rieß
2009-02-11 21:04 ` Bob Copeland
2009-02-11 22:34   ` pat-lkml
2009-02-12  9:12   ` Norman Rieß
2009-02-13 21:28 Jeff Tchang
     [not found] <4dd58f490903041329p54ec56ceh1b64ab000027eac5@mail.gmail.com>
2009-03-04 21:33 ` Alexey Yudichev
2009-03-04 22:26   ` Christoph .J Thompson
2009-03-04 22:51     ` Alexey Yudichev
2009-03-04 22:25       ` Christoph J. Thompson
2009-03-05 22:49         ` Alexey Yudichev
2009-03-06  7:45           ` Christoph J. Thompson
2009-03-10 21:04             ` Alexey Yudichev
2009-03-10 21:37               ` Christoph .J Thompson
2009-03-10 21:58                 ` Bob Copeland
2009-03-11 21:51                   ` Alexey Yudichev
     [not found]                     ` <4dd58f490905310754g2f01b083sd35831747ff93d4f@mail.gmail.com>
2009-05-31 14:56                       ` Alexey Yudichev
2009-03-04 22:58       ` pat-lkml
2009-03-05 11:43         ` Dan Williams
2009-03-05 19:09           ` pat-lkml
2009-03-05 19:12             ` Ben Greear
2009-03-05 22:21               ` Gábor Stefanik

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=20081113235928.3ed79ff6.rumi_ml@rtfm.hu \
    --to=rumi_ml@rtfm.hu \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.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;
as well as URLs for NNTP newsgroup(s).