linux-kernel - Re: The problems for driver module loading

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Apr 2009 10:49:30 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	fangxiaozhi 00110321 <huananhu@...wei.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	gregkh@...e.de, greg@...ah.com
Subject: Re: The problems for driver module loading

>    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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/