From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: rol@witbe.net
Cc: "'Sergey Vlasov'" <vsu@altlinux.ru>, linux-kernel@vger.kernel.org
Subject: Re: [2.4.31] - USB device numbering in /proc/bus/usb
Date: Tue, 23 Aug 2005 17:31:09 +0100 [thread overview]
Message-ID: <200508231731.09099.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200508231551.j7NFpFD00513@tag.witbe.net>
On Tuesday 23 August 2005 16:51, Paul Rolland wrote:
> Hello Sergey,
>
> > Yes. Addresses for USB devices are assigned dynamically. If you
> > disconnect the modem from USB and connect it again, its address will
> > change.
>
> The problem I've is that nothing changed on the machine except that
> I did a reboot. Nothing (USB device) added, nothing removed, so with
> a stable hardware config, USB numbering should have stayed stable, IMHO.
Basically, no it shouldn't.
>
> > > I would have been expecting some more stability in the
> >
> > numbering across
> >
> > > reboot, the same way IDE disks numbers are stable.
> >
> > Use some other identifier which is stable - e.g., serial number of the
> > USB device (unfortunately, many devices don't have it).
>
> Well yes, I'm going to try to convert to some other identifiers space
> as this seems to be the only way to go.
>
> Thanks for the confirmation,
> Regards,
> Paul
/proc/bus/usb/devices (which tells you where a device is located in the tree).
This should work on 2.4 kernels, 2.6 kernels should be using sysfs by now.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
prev parent reply other threads:[~2005-08-23 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 13:14 Paul Rolland
2005-08-23 15:45 ` Sergey Vlasov
2005-08-23 15:51 ` Paul Rolland
2005-08-23 16:31 ` Alistair John Strachan [this message]
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=200508231731.09099.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@witbe.net \
--cc=vsu@altlinux.ru \
/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
all inboxes | Powered by JetHome®