From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3451a36c456129ca677defc7c9d8658b@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: usbd - revision (Was: [9fans] USB developments)
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
In-Reply-To: <20040115211012.K25947@cackle.proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jan 2004 08:38:46 +0100
Topicbox-Message-UUID: ba8a9d20-eacc-11e9-9e20-41e7f4b1d025

Besides usbd / driver issues, there's an interesting idea from paurea
that I think is worth raising here.

Since you may have a resource (say a mouse) that speaks the same
protocol and is to be handled in the same way in several different devices
(say usbmouse and usbhid). it might have sense to split the driver level
in two parts so that:

- usbd starts device drivers
- device drivers configure the devices and locate resources
- resource drivers speak the protocols and provide the services
 (perhaps this third level could be just a library and not a different process).

Paurea's aim was to share the code for stuff found in multiple kind of
devices.