Linux wireless drivers development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Joe Perches <joe@perches.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Eduardo Costa <ecosta.tmp@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: another device working
Date: Tue, 14 Dec 2010 16:33:48 -0500	[thread overview]
Message-ID: <20101214213348.GD2389@tuxdriver.com> (raw)
In-Reply-To: <1292361712.26726.31.camel@Joe-Laptop>

On Tue, Dec 14, 2010 at 01:21:52PM -0800, Joe Perches wrote:
> On Tue, 2010-12-14 at 14:41 -0600, Larry Finger wrote:
> > On 12/14/2010 11:09 AM, Eduardo Costa wrote:
> > >  {USB_DEVICE (0x15a9, 0x0002)},   /* Gemtek WUBI-100GW 802.11g */
> > > And about the firmware, it does work with stock p54's
> > > `2.13.24.0.lm87.arm' found on the website, so I just had to copy it to
> > > `/lib/firmware' while renaming it to `isl3887usb'.
> > Thanks for the report. I just submitted a patch to wireless-testing with a copy
> > to you for this change to be included in kernel 2.6.37, and to be backported to
> > all stable and long-term kernels.
> 
> Perhaps it'd be sensible to add a
> module_param option like usb_device=x,y
> so new devices could be supported without recompilation.

Isn't that what new_id is for?

At any rate, it isn't a great substitute for a device id in the driver's table. :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-12-14 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 17:09 another device working Eduardo Costa
2010-12-14 20:41 ` Larry Finger
2010-12-14 21:05   ` Sedat Dilek
2010-12-15  9:06     ` Johannes Berg
2010-12-15  9:42       ` Sedat Dilek
2010-12-14 21:21   ` Joe Perches
2010-12-14 21:33     ` John W. Linville [this message]
2010-12-14 21:54       ` 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=20101214213348.GD2389@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=ecosta.tmp@gmail.com \
    --cc=joe@perches.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