[RFC] Some new generic device features.

[Hans Petter Selasky]

Hi,

Some general comments:

Must be detach safe.

Does it support non-giant enabled input drivers?

How does it handle mutexes?

--HPS

On Thursday 31 January 2008, Maxim Zhuravlev wrote:
> Hi.
>
> I'm currently working on project named *Enhanced NewBus*. It's a
> successor of *Generic Input Device Layer Project* I've been working on
> for GSoC2007 [1].
> As the project is to be quite an extensive one, I would like to get
> some comments/suggestions on the design[2] first. It can be found
> here:http://wiki.freebsd.org/EnhancedNewBus.
>
> In brief, the design suggests to implement in-kernel device piping.
> There are two types of devices: logical (ex. console device, demuxing
> device) and hardware (mices, displays). I suggest to add logical
> devices to NewBus domain. Side effect is that device tree will
> transform to a graph (ex. two mice can be parents of a demuxing
> device, while being children of a same bus). The approach lets to
> implement a generic way of ex. device demuxing, cause it's obvious
> that functionality, provided by logical devices may be useful not just
> for input devices, while some kind of devices may require some
> specific features. Also it will be easier to implement such complex
> device drivers, like a console driver is, by abstracting work with
> underlying devices. To make it possible one needs to implement a way
> to track input/output requests through the graph. The generic device
> input/output subsystem is internally asynchronous for the sake of
> flexibility. New logical drivers require a new more intellectual
> autoconfiguration process.
>
> More here: [2].
>
> [1] http://wiki.freebsd.org/GenericInputDeviceLayer
> [2] http://wiki.freebsd.org/EnhancedNewBus
>
> --
> Maxim Zhuravlev
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"