>
> I don't know how fast the above will all work out, you are going to have
> to test it yourself, sorry.
>
> hope this helps,
It has. Thank you for answering all of my questions.
-Nate
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
On Wed, Aug 22, 2007 at 04:52:06PM -0500, Nate wrote:
> Thank you for your responses. Please don't take my repeated questioning
> of your answers as me being difficult, I'm just trying to get a better
> understanding.
>
>
> > Well, just messing with the device ids is not that tough of a patch to
Thank you for your responses. Please don't take my repeated questioning
of your answers as me being difficult, I'm just trying to get a better
understanding.
> Well, just messing with the device ids is not that tough of a patch to
> keep up to date over time, so you might just try that if necess
On Wed, Aug 22, 2007 at 09:41:33AM -0500, Nate wrote:
>
> > Why do you not want to modify the driver?
>
> Modifying the cdc-acm driver is an alternative; however, I would like to
> avoid that when I'm adding my vendor specific restrictions. My hope is
> that when patches are made to that file, I
> Why do you not want to modify the driver?
Modifying the cdc-acm driver is an alternative; however, I would like to
avoid that when I'm adding my vendor specific restrictions. My hope is
that when patches are made to that file, I don't need to worry about
someone merging them over the my previo
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 p
6 matches
Mail list logo
