All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darko Makreshanski <d.makreshanski@jacobs-university.de>
To: linux-wireless@vger.kernel.org
Subject: Mesh support for gumstix's wireless (Marvell 88W8385 wireless chip with CF interface)
Date: Thu, 4 Mar 2010 22:23:42 +0100	[thread overview]
Message-ID: <4B9024DE.308@jacobs-university.de> (raw)

Dear all,

I would like to ask a quick question to anybody that is familiar in this 
area.

I would like to know if I can use a mesh networking with the wifi chip 
used for gumstix (88W8385 with most probably CF interface).

I am aware that the XO (OLPC) laptops have a Marvell 88W8388 chip (with 
USB interface) which is used with the libertas_tf driver, has support 
for mesh networking through open80211s.

Couple of things that I have found out:

1. on the linux-wireless website it is stated that libertas_tf driver 
supports only 88W8388 driver and libertas driver supports both 88W8385 
and 88W8388
2. also at linux-wireless it is also stated that both libertas_tf and 
libertas are supported for mesh networking
3. on the open80211s website at the drivers page only the libertas_tf is 
present.
4. i have read somewhere that the libertas driver is not based on the 
mac80211 layer, so it cannot work with open80211s.

What I would like to ask:

1. will mesh networking work with the 88W8385 chip on gumstix with the 
libertas driver?
2. if yes, is it open80211s or something else?
3. if not, is it possible to make the libertas_tf driver work with this 
chip?

Best regards,
Darko

             reply	other threads:[~2010-03-05  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 21:23 Darko Makreshanski [this message]
2010-03-05  0:38 ` Mesh support for gumstix's wireless (Marvell 88W8385 wireless chip with CF interface) Andrey Yurovsky
2010-03-06  6:35   ` Dan Williams
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=4B9024DE.308@jacobs-university.de \
    --to=d.makreshanski@jacobs-university.de \
    --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.