linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wi-fi.org certification with libertas + 8686
Date: Mon, 10 Nov 2008 16:40:18 -0500	[thread overview]
Message-ID: <1226353218.8146.21.camel@localhost.localdomain> (raw)
In-Reply-To: <f96d234e0811101325u9851ea1l636c46cf38aa2695@mail.gmail.com>

On Mon, 2008-11-10 at 16:25 -0500, Cliff Brake wrote:
> Hello,
> 
> Has anyone been through wifi certification with the libertas driver
> and the 8686 chipset (or any Linux driver + wpa_supplicant for that
> matter)?  Just trying to get a rough idea how painful this is.

Marvell has probably certified their libertas vendor driver (which isn't
the upstream libertas driver).  With the possible exceptions of Intel
and Atheros (which are both heavily involved in the upstream drivers for
their hardware), none of the upstream kernel drivers have been through
validation or certification that I know of.

Dan



  reply	other threads:[~2008-11-10 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 21:25 wi-fi.org certification with libertas + 8686 Cliff Brake
2008-11-10 21:40 ` Dan Williams [this message]
2008-11-11  7:49   ` Kalle Valo

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=1226353218.8146.21.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=cliff.brake@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).