[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: user-space device drivers - hurd

From: Shakthi Kannan
Subject: Re: user-space device drivers - hurd
Date: Thu, 15 Sep 2005 08:13:48 -0700 (PDT)


--- Marco Gerards <metgerards@student.han.nl> wrote:
> Somehow the
> kernel figures out
> which driver is responsible for the device with a
> specific name.

Thanks for this hint.

In gnumach-1-branch/i386/i386at there is a conf.c file
where this name is registered. I overlooked it the
last time :).

I wrote a dummy lpr.c driver in i386/i386at and added
an entry in struct dev_ops dev_name_list in conf.c as

{ lprname, lpropen, lprclose, lprread,
  lprwrite,      0,        0,   nomap,
  nodev,     nulldev,      0,       0,
  nodev },

In all the functions in lpr.c I just gave a printf :)

On GNU Hurd, I wrote a simple lrp-test.c file:

- To obtain device master port privileges
- open device

It printed the printf specified in the driver. Voila!


1. I believe Thomas Schwinge is working on
reorganizing the build process in GNUMach? Will you be
updating to gnumach CVS? or can you send me any

2. I want to try to setup a config script (n-curses
based) like "make menuconfig" for a front-end for
config options.

3. I want to try to strip down the gnumach kernel and
drivers to a minimal. Or is the default one the
minimum? I'd appreciate developers' inputs and their
experience they had on what makes GNUMach slow and
what needs to be fixed or what cannot be fixed. I am
particularly interested only in hardware and device

4. Do we write drivers in user-space or should I try
to use the existing device driver interface for
writing drivers? 

I'd appreciate any thoughts on the above,

Thanks again,


Shakthi Kannan, MS
Software Engineer, Specsoft (Hexaware Technologies)
[E]: shaks@shakthimaan.com           [M]: (91) 98407-87007
[W]: http://www.shakthimaan.com      [L]: Chennai, India

Yahoo! Mail - PC Magazine Editors' Choice 2005 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]