Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932133AbZDIJtc (ORCPT ); Thu, 9 Apr 2009 05:49:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762821AbZDIJtN (ORCPT ); Thu, 9 Apr 2009 05:49:13 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:51933 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759172AbZDIJtL (ORCPT ); Thu, 9 Apr 2009 05:49:11 -0400 Date: Thu, 9 Apr 2009 10:49:30 +0100 From: Alan Cox To: fangxiaozhi 00110321 Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, gregkh@suse.de, greg@kroah.com Subject: Re: The problems for driver module loading Message-ID: <20090409104930.59485167@lxorguk.ukuu.org.uk> In-Reply-To: References: X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 809 Lines: 18 > Because cdc_ether.ko driver can not support our QMI protocol, so we want the Linux system can always attach our driver to our device, but not cdc_ether.ko driver. > > How can I do for this? The easiest way is probably to submit some changes to cdc_ether to add QMI support, or when submitting the QMI driver to also submit a patch to cdc_ether to make it leave the device alone. That doesn't help with exising systems however. What do the descriptors for the hardware look like as cdc_* do actually try to avoid vendor specific modem intefaces ? Alan -- 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/