hello alan...

* Alan Stern <[EMAIL PROTECTED]> [2004-06-01 18:19 +0200]:
> On Mon, 31 May 2004, Sebastian Henschel wrote:
> 
> > > > topology: portNumber, count
> > > 
> > > The port # is available as the last part of the directory name, the part
> > > following the final '-' or '.'.
> > 
> > really? 
> > 
> > a directory named "1-1" in sysfs should mean bus# 1 and port# 1?
> 
> That's right.
> 
> > but this devices shows port# 0 in proc.
> 
> I'm not sure if that's deliberate or a bug in the procfs interface.  The 
> port numbers in /proc/bus/usb/devices use origin 0; the port numbers in 
> sysfs use origin 1.

ok, with different origins, everything is fine. :)

[...]

> > > > is it somewhat planned to include these?
> > > 
> > > I don't know what anybody else is planning, but I don't have any plans to 
> > > change the way this works.
> > 
> > so the current "way this works" is, that this info is unavailable in
> > sysfs?
> 
> That's right.  Part of it is understandable, since sysfs only reports 
> information about devices that exist.  Interfaces for non-active 
> configurations and non-active altsettings don't exist as devices, so they 
> shouldn't have entries in sysfs.
> 

[...]

> The information in sysfs shows the device's _current_ settings.  The 
> information in procfs shows _all the available_ settings.  So naturally 
> there's an unavoidable overlap.

ok, when only _current_ settings are displayed, i can see the reason why
some info is not available in sysfs. though i still have to get a good
manifest which explains the existance of sysfs.

> Some of the things you mentioned, such as bandwidth allocation 
> information, could easily be added to sysfs (and maybe it should be).  It 
> would be available only in the directory for the root hub, though -- 
> the kernel doesn't keep track of bandwidth allocation by individual 
> device but only per bus.

do you see the endpoint data for the current configuration/setting as
something which should be available in sysfs?

bye,
 sebastian
-- 
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

Attachment: signature.asc
Description: Digital signature

Reply via email to