Re: [Prex-devel] Drivers messages exchanges

[Kohsuke O. <ko...@us...>]

Hi,

Applications, kernel and drivers can communicate by using following 
interfaces.

Application -> Kernel ... Kernel API
Application -> Driver ... Device I/O API (eg. device_read() etc.)
Application -> Application ... IPC, shared memory, exception, etc.
Driver -> Kernel ... DKI (Driver Kernel Interface)
Kernel -> Driver ... Event broadcast. (device_broadcast())
Driver -> Driver ... Event broadcast. or direct function call.

The Prex driver model is very monolithic design for now. This means that 
all drivers are linked into single binary module, and so, your driver 
can directly call any global functions of another driver.

However, initial driver design of Prex was a little different before. 
That was - the drivers communicate each other via "device object". This 
is obviously more flexible and elegant, and I want to change the driver 
model to such design in the future.

- Kohsuke

Christophe Gimenez wrote:
> Hello, I wonder how a driver can communicate with another driver without 
> a glue code in the kernel or in the application ?
> For example, a mouse driver making serial driver calls (ioctl)
> 
> Thanks
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Prex-devel mailing list
> Pre...@li...
> https://lists.sourceforge.net/lists/listinfo/prex-devel
> 
> 
>