Messages in this thread | | | Date | Sat, 9 Jun 2012 23:57:56 +0530 | Subject | Re: Code flow from device connection to device node in /dev creation | From | Anil Nair <> |
| |
Hi Prasanna,
On Sun, May 27, 2012 at 10:19 AM, prasannatsmkumar <prasannatsmkumar@gmail.com> wrote:
> If I open a device file (say a printer device) who determines the > correct driver and sends the call? How subsequent calls get processed > etc. Yes I know the init function will be called while the driver is > loaded (while running insmod driver.ko). How a open or write call > comes to the driver from user space? Who keeps track of the driver's > internal data (*dev) and sends that while calling methods in the > driver? I am more interested in things like that.
Drivers work in kernel address space. The implementation of the USB in userspace is through the library libusb, i guess you have visited its thread in mailing list. You will require a serious reading before jumping into coding. Sorry if you have done the required reading. :).
-- Regards, Anil Nair
| |