From: Greg KH <greg@kroah.com>
To: Nate <stoddarn@msoe.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Restricting CDC-ACM devices
Date: Tue, 21 Aug 2007 22:46:15 -0700 [thread overview]
Message-ID: <20070822054615.GA23336@kroah.com> (raw)
In-Reply-To: <39877.198.169.188.225.1187733834.squirrel@myweb.msoe.edu>
On Tue, Aug 21, 2007 at 05:03:54PM -0500, Nate wrote:
> I would like to use the cdc-acm driver in the Linux kernel (2.6.22-rc1),
> but restrict the access to only my VID/PID devices. Is there an easy way
> to do with without modifying cdc-acm.c?
Why do you not want to modify the driver?
> In a past prototype I made a simple wrapper driver for usb serial by
> adding my VID/PID numbers to the wrapper driver's id_table. Then when
> that usb driver was accessed on connection, the driver just pointed to the
> usb_serial_* functions (probe, disconnect, etc). I tried to do the same
> with the cdc-acm driver, but the cdc-acm driver's probe function was
> called before my driver's probe. I noticed that the cdc-amc driver will
> attach when it detects the two CDC-ACM interfaces, so I removed the
> cdc-acm driver with "make menuconfig". This didn't work because the
> cdc-acm functions I was attempting to call from my driver do not exist.
You can disconnect the device from the driver from userspace for any
device you just don't want to have connected by using the sysfs
bind/unbind files. That doesn't require any kernel changes at all.
Why do you want to do this, what are you expecting to achieve with such
a change?
thanks,
greg k-h
next prev parent reply other threads:[~2007-08-22 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1187716018.731090.165620@j4g2000prf.googlegroups.com>
[not found] ` <20070821171018.C964B5F778@attila.bofh.it>
2007-08-21 22:03 ` Restricting CDC-ACM devices Nate
2007-08-22 5:46 ` Greg KH [this message]
2007-08-22 14:41 ` Nate
2007-08-22 18:55 ` Greg KH
2007-08-22 21:52 ` Nate
2007-08-22 21:47 ` Greg KH
2007-08-27 15:58 ` Nate
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=20070822054615.GA23336@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stoddarn@msoe.edu \
/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