linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Pavel Machek <pavel@ucw.cz>,
	David Gnedt <david.gnedt@davizone.at>,
	freemangordon@abv.bg
Subject: Re: [PATCH 0/4] wl1251 IBSS fixes
Date: Fri, 30 May 2014 18:18:12 +0200	[thread overview]
Message-ID: <201405301818.13260@pali> (raw)
In-Reply-To: <201405101428.45185@pali>

[-- Attachment #1: Type: Text/Plain, Size: 1572 bytes --]

On Saturday 10 May 2014 14:28:45 Pali Rohár wrote:
> On Friday 09 May 2014 22:03:00 Pali Rohár wrote:
> > On Friday 09 May 2014 02:21:21 Grazvydas Ignotas wrote:
> > > On Tue, Apr 22, 2014 at 3:09 AM, Grazvydas Ignotas
> > 
> > <notasas@gmail.com> wrote:
> > > > IBSS mode is currently advertised by wl1251 driver but
> > > > is totally broken. First there is a disconnect hack for
> > > > monitor mode that was recently merged, it abuses
> > > > mac80211 and causes corruption in IBSS mode, so I think
> > > > should be reverted. Then there are several cases of
> > > > station-only mac80211 functions called carelessly, what
> > > > is also fixed.
> > > 
> > > Ping.
> > > This driver is orphan and hardware carrying it is
> > > outdated, so acks / tested-bys are unlikely..
> > 
> > Now I'm testing these patches on wireless-testing git tree
> > from year 2010 compiled against patched maemo 2.6.28 kernel.
> > 
> > Reason for using these historical wireless-testing version
> > is that this version can be compiled against kernel which
> > working with default Maemo system in Nokia N900.
> > 
> > It looks like your patches fixed some kernel oops when
> > iwconfig changing mode to ad-hoc.
> 
> Looks like everything working fine except power save mode. In
> dmesg I see only these message:
> 
> wl1251: ERROR Power save entry failed, giving up
> 
> If you are OK with fact that I tested your patches with older
> kernel (not last upstream), you can add my Tested-by.
 
Grazvydas: PING

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-05-30 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  0:09 [PATCH 0/4] wl1251 IBSS fixes Grazvydas Ignotas
2014-04-22  0:09 ` [PATCH 1/4] Revert "wl1251: enforce changed hw encryption support on monitor state change" Grazvydas Ignotas
2014-04-22  0:09 ` [PATCH 2/4] wl1251: fix null data for IBSS Grazvydas Ignotas
2014-04-22  0:09 ` [PATCH 3/4] wl1251: fix mixed up args for join Grazvydas Ignotas
2014-04-22  0:09 ` [PATCH 4/4] wl1251: only call ieee80211_beacon_loss in managed mode Grazvydas Ignotas
2014-05-09  0:21 ` [PATCH 0/4] wl1251 IBSS fixes Grazvydas Ignotas
2014-05-09 20:03   ` Pali Rohár
2014-05-10 12:28     ` Pali Rohár
2014-05-30 16:18       ` Pali Rohár [this message]
2014-05-31 13:15         ` Grazvydas Ignotas
2014-05-31 13:20           ` Pali Rohár

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=201405301818.13260@pali \
    --to=pali.rohar@gmail.com \
    --cc=david.gnedt@davizone.at \
    --cc=freemangordon@abv.bg \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=notasas@gmail.com \
    --cc=pavel@ucw.cz \
    /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).