linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Piter PUNK <piterpunk@unitednerds.org>
Cc: Jason Self <jason.self@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Realtek wireless 8187se
Date: Tue, 6 Jan 2009 15:29:36 -0500	[thread overview]
Message-ID: <20090106202936.GF3544@tuxdriver.com> (raw)
In-Reply-To: <4957202A.5010706@unitednerds.org>

On Sun, Dec 28, 2008 at 04:43:54AM -0200, Piter PUNK wrote:
> John W. Linville wrote:
>> On Mon, Dec 15, 2008 at 06:41:01PM -0800, Jason Self wrote:
>>> On Dec 15, 2008, at 5:26 PM, "John W. Linville" 
>>> <linville@tuxdriver.com> wrote:
>>>> I have acquired an MSI Wind equipped with this device, I have
>>>> multiple variations of the vendor driver to support the hardware, and
>>>> I have a datasheet the covers at least some of the hardware involved.
>>>> I'm working on it...
>>> Why not share your work?
>>
>> What I have (which is barely anything) is on the "linville" branch
>> of wireless-testing...
>
> Hi John,
>
> I am using that branch on mine Positivo Mobo White (MSI Wind OEM). It
> loads the rtl8180 module, the wlan0 device appears but nothing more
> happens. No scans, no associations, etc.

There really is nothing there to activate the device, just some
infrastructure bits.

> I'm really lost looking the code, and vendor code is very very different
> of kernel code (at least to my eyes), isn't an easy job to "look vendor
> code -> adapt code to kernel". What can I do to help? Any special
> test case? Any log? Any tip to do the un-easy job?

Now that we are done with the holidays, hopefully I can make some
progress on this soon.  Until then, there isn't much for you to do...

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2009-01-06 20:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  2:41 Realtek wireless 8187se Jason Self
2008-12-16 14:02 ` John W. Linville
2008-12-28  6:43   ` Piter PUNK
2009-01-06 20:29     ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-15 21:29 Jason Self
2008-12-15 21:55 ` Stefanik Gábor
     [not found]   ` <b76df900812151413u32cdca95qd7122ca688a8a8d8@mail.gmail.com>
     [not found]     ` <b76df900812151414n21e21876q47c858f1c417a667@mail.gmail.com>
2008-12-15 22:25       ` Stefanik Gábor
2008-12-16  1:26   ` John W. Linville
2008-12-16  3:00     ` Larry Finger
2008-12-16 14:03       ` John W. Linville
2008-12-16  3:53     ` Piter PUNK
2008-11-04 13:01 Wilson Ribeiro
2008-11-04 16:52 ` Stefanik Gábor
2008-11-04 18:02   ` Larry Finger
2008-11-05 18:22     ` John W. Linville
     [not found]     ` <740646d0811041021qd4ab88bs434ddb8d1ad65a80@mail.gmail.com>
2008-11-07  0:48       ` 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=20090106202936.GF3544@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jason.self@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=piterpunk@unitednerds.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).