Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934262AbZJMUp7 (ORCPT ); Tue, 13 Oct 2009 16:45:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934034AbZJMUp6 (ORCPT ); Tue, 13 Oct 2009 16:45:58 -0400 Received: from mail-fx0-f227.google.com ([209.85.220.227]:36636 "EHLO mail-fx0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933949AbZJMUp5 convert rfc822-to-8bit (ORCPT ); Tue, 13 Oct 2009 16:45:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=VM7Dn+OqzQZ/Is3Zg4V6SSqM3Twr1Dv9QBVVqRIHjIUOyUrfHSvSn4llcjmZTJgf7s k5t74oycNeI0IzYtS0eHSj6NxiZy+dmVHiBtIDmpbXfg2rySJUT4G77r9WjcIvTL216G KIqfJ3tqs560P51WtqwqrQxTef/1rBTfqaogg= From: Bartlomiej Zolnierkiewicz To: Ozan =?utf-8?q?=C3=87a=C4=9Flayan?= Subject: Re: Current status of rt2800usb and staging/rt2870 Date: Tue, 13 Oct 2009 22:44:32 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31-rc2-00251-gd8c9210; KDE/4.3.1; x86_64; ; ) Cc: linux-wireless@vger.kernel.org, "linux-kernel" References: <4AD46380.9020308@pardus.org.tr> <200910131844.58983.bzolnier@gmail.com> <4AD4E60E.5030005@pardus.org.tr> In-Reply-To: <4AD4E60E.5030005@pardus.org.tr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Message-Id: <200910132244.32835.bzolnier@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1017 Lines: 26 On Tuesday 13 October 2009 22:41:50 Ozan Çağlayan wrote: > 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? Yes but rather using /etc/modprobe.d/blacklist.conf than clearing id tables so it is easier to switch drivers.. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/