On Tue, 18 Feb 2014, Valentina Manea wrote:
> I managed to get it working but I think what I did is rather flawed.
>
> The problem is where I get that struct dev_state *owner parameter
> from. The closest to this I found to be the filelist member in struct
> usb_device. So I got the owner as:
>
Hi,
On Sun, Feb 16, 2014 at 12:42 AM, Alan Stern wrote:
>
> That's true when it is invoked from userspace. It can also be invoked
> directly by a kernel driver; in that case no file is needed.
>
I managed to get it working but I think what I did is rather flawed.
The problem is where I get tha
On Sat, 15 Feb 2014, Valentina Manea wrote:
> Hi,
>
> Thank you both for your replies, I managed to solve the /dev issues,
> it seems it was related to tmpfs.
>
> Related to the port claim mechanism, as far as I can see,
> usb_hub_claim_port is called from a ioctl and, thus, needs a file to
> be
On Sat, Feb 1, 2014 at 12:00 AM, Alan Stern wrote:
> On Fri, 31 Jan 2014, Sarah Sharp wrote:
>
>> Why exactly do you want the device to not show up in /dev? I would
>> think what you really want is for the device drivers on the server side
>> to not bind to the device, since the client side drive
On Fri, 31 Jan 2014, Sarah Sharp wrote:
> > 2. This question somehow resembles the previous. When a device is
> > shared, I don't want it to be available on the host it is physically
> > attached to anymore.
>
> What do you mean by this? Do you mean that when the stub driver on the
> server star
[Cc-ing the USB mailing list as well.]
On Mon, Jan 27, 2014 at 06:13:57PM +0200, Valentina Manea wrote:
> Hi Sarah,
Hi Valentina,
> As you probably know, I am working on a set of drivers called USB/IP.
> These drivers have some issues that I'm not sure how to approach and
> since you are working
