All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@googlemail.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH] libertas: add auto auth mode feature
Date: Fri, 26 Feb 2010 13:55:06 +0100	[thread overview]
Message-ID: <201002261355.06127.holgerschurig@gmail.com> (raw)
In-Reply-To: <1267146996-3725-1-git-send-email-bzhao@marvell.com>

> Auto auth mode is enabled by default. If user doesn't specify the
> auth mode, while association driver will first try with open mode
> and then with shared key mode. If user specifies an auth mode,
> auto auth is disabled and driver will not try association with
> another auth mode.

I'd rather would like if you guys chime in into the cfg80211 port rather 
than adding stuff to assoc.c and wext.c, which hopefully get's removed 
really soon now.


As a side note: I'm now inclined to get rid of Libertas' proprietary mesh 
support in the driver. I don't know no one except OLPC that uses it, and 
even they don't seem work with upstream. For me, this mesh stuff is the last 
obstacle for cfg80211 support in libertas.

  reply	other threads:[~2010-02-26 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  1:16 [PATCH] libertas: add auto auth mode feature Bing Zhao
2010-02-26 12:55 ` Holger Schurig [this message]
     [not found]   ` <c1545bb51002261210h27ba9868tca0261742b848e51@mail.gmail.com>
     [not found]     ` <1267225266.14995.7.camel@localhost.localdomain>
2010-03-01 19:59       ` Deepak Saxena
2010-03-02 12:02         ` Holger Schurig
2010-03-03 18:52           ` Deepak Saxena
2010-03-03 19:06             ` Nicolas Pitre
2010-02-26 13:08 ` Marcel Holtmann
2010-02-26 13:21   ` Johannes Berg
2010-02-26 23:02     ` Dan Williams

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=201002261355.06127.holgerschurig@gmail.com \
    --to=holgerschurig@googlemail.com \
    --cc=akarwar@marvell.com \
    --cc=bzhao@marvell.com \
    --cc=libertas-dev@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.