linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Raffaele Recalcati <lamiaposta71@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wl0084a / wl1271 understanding
Date: Sat, 17 Dec 2011 10:05:48 -0600	[thread overview]
Message-ID: <4EECBDDC.5070908@lwfinger.net> (raw)
In-Reply-To: <CAFU7RzPF7NKRkY70Vp_b55AUeDip+ePxk=zqJ_K=SsXUfse7Jw@mail.gmail.com>

On 12/16/2011 10:54 PM, Raffaele Recalcati wrote:
> I'm an embedded developer and I really want opensource development for
> wireless, to be sure to maintain it in many kernel versions I will
> have.
> I'm not an wifi expert and so I can have done some mistakes here below.
>
> wl0084a
> =============
> grep -rin wl008 drivers
> give no result on kernel 3.2-rc6.
> What is the normal approach to take in account?
> I have to immediately change the usb wifi dongle due to the lacking of
> information to develop e proper driver or maybe
> there is some possibility?
> Here I can find Logilink drivers
> http://www.logilink.eu/content/support/download.htm?seticlanguage=en
> They confirm support for LINUX (kernel 2.6.18 ~ 2.6.33)
> Looking into drivers files ... yes , they are proprietary.

Some of the Logilink devices have Realtek chips. If this is a USB device, please 
post the output of 'lsusb'. If it is PCI, post the output of 'lspci -nnv' - we 
only need the part that describes the wireless device.

Larry


  parent reply	other threads:[~2011-12-17 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17  4:54 wl0084a / wl1271 understanding Raffaele Recalcati
2011-12-17  9:35 ` Luciano Coelho
2011-12-17 16:05 ` Larry Finger [this message]
2011-12-18  4:56   ` Raffaele Recalcati
2011-12-18 17:16     ` Larry Finger

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=4EECBDDC.5070908@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=lamiaposta71@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).