public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Tue, 13 Oct 2009 23:41:50 +0300	[thread overview]
Message-ID: <4AD4E60E.5030005@pardus.org.tr> (raw)
In-Reply-To: <200910131844.58983.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> On Tuesday 13 October 2009 13:24:48 Ozan Çağlayan wrote:
>   
>> Hi,
>>
>> In 2.6.31, there are USB device IDs common between both drivers. Should
>> a distribution enable both drivers? What do you suggest? Are there any
>> *known issues* stuff for one of them?
>>     
>
> My advice to distributions for such situations is to ship both but make
> one driver the default one.  

By saying to make one driver the default one, you mean avoiding the
other from getting probed automatically by clearing the device id tables?



  reply	other threads:[~2009-10-13 20:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27   ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17     ` Ivo van Doorn
2009-10-13 19:21       ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00         ` Ivo van Doorn
2009-10-13 20:42           ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15         ` Dan Williams
2009-10-13 21:57           ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21             ` Luis Correia
2009-10-14 14:14               ` John W. Linville
2009-10-13 22:24             ` Dan Williams
2009-10-13 22:42               ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15                 ` John W. Linville
2009-10-14  1:58             ` Thomas Fjellstrom
2009-10-14 13:51             ` Ivo van Doorn
2009-10-14 14:09             ` John W. Linville
2009-10-14 14:52               ` Bartlomiej Zolnierkiewicz
2009-10-14 14:56                 ` John W. Linville
2009-10-14 15:28                   ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47                     ` John W. Linville
2009-10-14 17:33                       ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26                         ` Luis Correia
2009-10-14 20:41                           ` Bartlomiej Zolnierkiewicz
2009-10-14 18:56                         ` Ivo van Doorn
2009-10-14 20:10                           ` Bartlomiej Zolnierkiewicz
2009-10-15  6:28                             ` Gertjan van Wingerde
2009-10-15  9:47                               ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55                     ` Luis R. Rodriguez
2009-10-15 14:47                       ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06                         ` Luis R. Rodriguez
2009-10-16 17:13                           ` Bartlomiej Zolnierkiewicz
2009-10-14  1:52         ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41   ` Ozan Çağlayan [this message]
2009-10-13 20:44     ` Bartlomiej Zolnierkiewicz

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=4AD4E60E.5030005@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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