From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1a66e3020d7e65b0fdf8fd4a64e6d4b1@plan9.bell-labs.com>
To: rs_rlab@mail.ru, 9fans@cse.psu.edu
Subject: Re: [9fans] usb or lp
Date: Wed,  1 Dec 2004 12:20:40 -0500
From: Sape Mullender <sape@plan9.bell-labs.com>
In-Reply-To: <14816809671.20041130210859@mail.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: 
Topicbox-Message-UUID: 0fffee30-eace-11e9-9e20-41e7f4b1d025

> New usb driver not configure file epXdata for writing or inputing, old
> driver do this. Why this happen?
> 
> When I run usb/usbd -v -d I can see this:
> 
> .... maxpkt 64 interval 0ms [OUT] [Bulk]                       #usbd know about direction on this endpoint
> .... maxpkt 64 interval 0ms [IN] [Bulk]
> 
> But when I ls -l /dev/usb0/1 I get this:
> 
> --r--r--r U 0 rlab rlab 0 Sep 13 22:55 /dev/usb0/1/ep1data     #but not set direction for files
> --r--r--r U 0 rlab rlab 0 Sep 13 22:55 /dev/usb0/1/ep2data
> 
> In old installation this looks like:
> ---w--w--w- U 0 rlab rlab 0 Sep 13 22:55 /dev/usb0/1/ep1data
> --r--r--r-- U 0 rlab rlab 0 Sep 13 22:55 /dev/usb0/1/ep2data
> 
> When I set direction manually all works well:
> echo -n 'ep 1 bulk w 64 32' >/dev/usb0/1/ctl

This is not really a problem because you have to send a string like
	ep 1 bulk w 64 32
to the control device before you can use the endpoint anyway.

I fixed a problem in usbaudio related to checking maxpkt.  There's an update on
sources.

	Sape