From: David Brownell <david-b@pacbell.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Greg KH <greg@kroah.com>, Torrey Hoffman <thoffman@arnor.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: usb+driverfs [was depmod problem for 2.5.2-dj4]
Date: Thu, 24 Jan 2002 07:27:41 -0800 [thread overview]
Message-ID: <00bd01c1a4eb$aac399e0$6800000a@brownell.org> (raw)
In-Reply-To: <1011744752.2440.0.camel@shire.arnor.net> <20020123045405.GA12060@kroah.com> <20020123094414.D5170@suse.cz> <20020123212435.GB15259@kroah.com> <003701c1a470$86b6bda0$6800000a@brownell.org> <20020124100154.A8622@suse.cz>
Quoth "Vojtech Pavlik" <vojtech@suse.cz>:
> On Wed, Jan 23, 2002 at 04:46:13PM -0800, David Brownell wrote:
> > What's the story on "driverfs" happening, by the way? Last I knew, the
> > PCI bits weren't yet ready.
>
> I'm not absolutely sure about the status of the PCI support, but it
> should be close to working. Anyway, the driverfs infrastructure itself
> is in place in 2.5, so even if the PCI part wasn't there, still we can
> convert USB and Input to it.
Since all the USB HCDs use PCI, I think the 2.5.3-pre4 updates
(well timed :) are necessary to convert USB: HCDs first, then the
hub driver, then input. Or at least, that's how I understand things
right now -- I was waiting for a "finished" example to read! :)
> > strncpy (buf, dev->devpath, min_t(size_t, size, sizeof dev->devpath));
> >
> > Use like you'd use pci_dev->slot_name ... no mallocation necessary.
> > It's just the path from root hub down to device, /2/1/7 and so on: the
> > physical path, which stays the same so long as you don't recable your
> > tree of USB devices and hubs.
> >
> > I'd expect the typical "driverfs" path for a USB device to be the
> > path for the root hub (normally a PCI slot like 00:0f.3) followed by
> > what "devpath" now shows.
>
> Ahh, I see. This "devpath" entry wasn't available at the time I wrote
> the 'usb_make_path' function. This is of course much better. What's not
> very convenient for me right now is that it uses slashes instead of
> dots, which the input subsystem uses for delimiting busses from each
> other, like:
>
> isa0060/serio0/input0 - AT keyboard
> pci0:7.3/usb1:2.2/input0 - USB keboard
>
> Using slashes in place of the dots would make it quite a mess. The
> slashes are probably there because of usbdevfs, right?
Driverfs -- since the hubs are part of the device hierarchy,
which shows up in the filesystem. Also that's what the code
it replaced did (in the hub driver). Maybe it should change
to use driverfs directly... :)
- Dave
> Note that the PCI "slot_name" doesn't use slashes ...
>
> --
> Vojtech Pavlik
> SuSE Labs
next prev parent reply other threads:[~2002-01-24 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 0:12 depmod problem for 2.5.2-dj4 Torrey Hoffman
2002-01-23 4:54 ` Greg KH
2002-01-23 8:44 ` Vojtech Pavlik
2002-01-23 21:24 ` Greg KH
2002-01-23 22:22 ` Greg KH
2002-01-23 22:47 ` Vojtech Pavlik
2002-01-23 23:00 ` Greg KH
2002-01-24 0:46 ` [linux-usb-devel] " David Brownell
2002-01-24 9:01 ` Vojtech Pavlik
2002-01-24 9:20 ` Dave Jones
2002-01-24 15:27 ` David Brownell [this message]
2002-01-24 15:32 ` [linux-usb-devel] Re: usb+driverfs [was depmod problem for 2.5.2-dj4] Vojtech Pavlik
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='00bd01c1a4eb$aac399e0$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=thoffman@arnor.net \
--cc=vojtech@suse.cz \
/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
Powered by JetHome