>>I think it'd be fine to have both device and interface level
>>hotplug events for USB, which might be implied by doing that
>>kind of thing at the driverfs level. That'd get rid of the
>>major technical wart in the current USB hotplug (the stuff
>>that "usbmodules" with usbfs addresses).
>
> T
On Tue, Jul 02, 2002 at 12:14:27AM -0700, David Brownell wrote:
> >And hopefully most of these hotplug calls will get merged together into
> >the driverfs core soon, and we remember to pay attention to the return
> >value there :)
>
> How would driverfs do that -- a new bus level callback to
> fi
> And hopefully most of these hotplug calls will get merged together into
> the driverfs core soon, and we remember to pay attention to the return
> value there :)
How would driverfs do that -- a new bus level callback to
fill out the environment and argv for hotplug events? Each
bus framework n
On Mon, Jul 01, 2002 at 11:59:04AM -0700, David Brownell wrote:
> >>- if (!hotplug_path [0])
> >>- return;
> >>- if (in_interrupt ()) {
> >>- dbg ("In_interrupt");
> >>- return;
> >>- }
> >>- if (!current->fs->root) {
> >>- /* statically linked USB i
>>- if (!hotplug_path [0])
>>- return;
>>- if (in_interrupt ()) {
>>- dbg ("In_interrupt");
>>- return;
>>- }
>>- if (!current->fs->root) {
>>- /* statically linked USB is initted rather early */
>>- dbg ("call_policy %s,
On Thu, Jun 27, 2002 at 12:52:30PM -0700, David Brownell wrote:
> This updates the doc and code to match what's been
> true since 2.4.0 (!) and keventd, removing some error
> checks that are now handled lower down as well as
> making a few messages less confusing ("kusbd" etc).
>
> Please merge t
