From: Jan Kiszka <jan.kiszka@domain.hid>
To: ramv <vikesh.rambaran@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RTDM PCI development framework
Date: Tue, 05 Sep 2006 13:18:09 +0200 [thread overview]
Message-ID: <44FD5CF1.7000603@domain.hid> (raw)
In-Reply-To: <1157443250.4466.12.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
ramv wrote:
> hi
> how are you?
>
> This is my first attempt at writing a linux device driver. After reading
> through some of the "Linux Device Drivers 3rd edition", and through
> Xenomai RTDM, i thought a good place to start was a generic framework
> which detects and allocates PCI resources with the necessary error
> handling. It makes available callback functions as well as the allocated
> resources. The aim is to expand it to provide a framework for a standard
> linux char device driver. Thereafter update the framework to be RTDM
> compatible. I've spoken with Jan Kiska with regards to this and it may
> useful to others. There is still much work to be done on, especially to
> bring it up to the Xenomai/RTDM coding standard but attached please find
> a first attempt.
>
> Comments and constructive criticism would be greatly appreciated!
> [The Xenomai GPL file headers are included, hope you don't mind]
The idea to provide some template for (PCI) driver development is
definitely a good one. Your approach already look quite nice, but it is
generally wise to apply such templates at least on two different drivers
to see what may be missing, what needs refinement, or what is not required.
A few comments already: it would be nice to add kernel 2.4 support to
your Makefile. Keep an eye on potential "over-design", i.e. avoid
wrapping trivial things, rather concentrate on providing templates the
user can fill in stuff directly.
>
> Jan, i went away for a long weekend at the sea to visit my parents.
> Apologies for not replying earlier
There is life offline? ;)
(No need to apologise, we are all busy with various stuff.)
>
> *******************************************************************************************************
> Disclaimer: The information contained in this communication is confidential and may be legally privileged.
Mmm, was it illegal then to read your mail? Or the attachment?? ;)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-09-05 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 8:00 [Xenomai-help] RTDM PCI development framework ramv
2006-09-05 11:18 ` Jan Kiszka [this message]
2006-09-05 15:55 ` ramv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44FD5CF1.7000603@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=vikesh.rambaran@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.