Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Andrey Yurovsky <yurovsky@gmail.com>
Cc: Darko Makreshanski <d.makreshanski@jacobs-university.de>,
	linux-wireless@vger.kernel.org
Subject: Re: Mesh support for gumstix's wireless (Marvell 88W8385 wireless chip with CF interface)
Date: Fri, 05 Mar 2010 22:35:49 -0800	[thread overview]
Message-ID: <1267857349.2243.158.camel@localhost.localdomain> (raw)
In-Reply-To: <c1545bb51003041638v28e5fe9me336735fc940e1ea@mail.gmail.com>

On Thu, 2010-03-04 at 16:38 -0800, Andrey Yurovsky wrote:
> On Thu, Mar 4, 2010 at 1:23 PM, Darko Makreshanski
> <d.makreshanski@jacobs-university.de> wrote:
> > 1. will mesh networking work with the 88W8385 chip on gumstix with the
> > libertas driver?
> 
> No.  The OLPC uses an 88w8288 with in-firmware mesh on the USB
> variant.  That firmware won't run on other chips.

I assume you mean 88w8388 :)

Dan

> > 3. if not, is it possible to make the libertas_tf driver work with this
> > chip?
> 
> No.  That driver only supports the 88w8388 USB variant with special
> firmware.  Your chip is a full-MAC device and therefore cannot use the
> mac80211 mesh stack (and there isn't a special firmware to make it do
> something else).
> 
>   -Andrey
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2010-03-06  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 21:23 Mesh support for gumstix's wireless (Marvell 88W8385 wireless chip with CF interface) Darko Makreshanski
2010-03-05  0:38 ` Andrey Yurovsky
2010-03-06  6:35   ` Dan Williams [this message]
2010-03-07 17:21     ` Andrey Yurovsky

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=1267857349.2243.158.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=d.makreshanski@jacobs-university.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yurovsky@gmail.com \
    /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