From: m madhuker <mythri_madhuker@yahoo.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Your valuable Suggestions / Advise for Beginners in Device Driver Development under Embedded Linux P
Date: Sun, 11 Jul 2004 23:44:01 -0700 (PDT) [thread overview]
Message-ID: <20040712064401.25378.qmail@web13604.mail.yahoo.com> (raw)
I have been assigned some project based in Device
Driver Development for USB, Printers, IDE, Ethernet
under Embedded Linux. Since I am a beginner in this
area, I would like to know some details based on the
following clarifications.
1] Pre-requisite skills / knowledge and concepts to
understand before embarking on the above project.
2] Typical Project Environment for Device Driver
Development under Embedded Linux Platform.
3] Ups & Downs of Embedded Linux w.r.t other RTOSes
( VxWorks, Psos, Nucleus, QNX, OSEK etc . . . .)
Please highlight me about the Benchmark details.
4] Suppose I need to start off with the above
project ( Device Drivers for Printers, Scanners, PDAs,
LCDs,
Keypads ), what are the essential points to be
kept in mind for smooth running of the project.
5] What are the Initialization / Installation steps
to be done regarding Embedded Linux. Please declare
the latest version to be used. Upon selecting
the RTOS, how should I deal with the selection of
Target
Board along with the Supporting Tools ?
6] Is it sufficient to use C, ignoring C++ & Java
? Is Assembly Language essential ? Which part of C
is
commonly used in Device Drivers ?
7] Please let me know the typical driver size (
Footprint ) for Printer. What could be the duration
of the
project ?
8] Highlight me about some of the useful websites,
books / references and contact Email IDs of
Experienced
Professionals involved in such Projects.
9] How does the Testing / Debugging takes place ?
What are the Test / Debug Tools available for such
Operations ?
10] Please let me know the Optimization Techniques
involved in the Device Driver Development.
11] In this case of the Project, Linux Porting must
be done prior to writing Device Drivers. Am I right
? Kindly
comment.
12] What Technical details should I need to
understand under RTOS, C, Embedded Linux ? Is it
necessary to
know any Protocol for Device Driver
Development ?
13] How often do you use Oscillators / Logic Analyzer
? Please highlight me about the Connection /
Installation details.
Please furnish the above details as soon as possible
and oblige. Your assistance in this regard would
greatly benefit towards my successful career under
this area.
Looking forward to hear from you soon,
Appreciating your favorable response
Regards
Madhukar
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
** This list is shutting down 7/24/2004.
next reply other threads:[~2004-07-12 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 6:44 m madhuker [this message]
2004-07-12 7:56 ` Your valuable Suggestions / Advise for Beginners in Device Driver Development under Embedded Linux P Marc Leeman
2004-07-12 13:36 ` McMullan, Jason
2004-07-12 14:35 ` Your valuable Suggestions / Advise for Beginners in DeviceDriver " Kevin P. Dankwardt
2004-07-12 13:51 ` Your valuable Suggestions / Advise for Beginners in Device Driver " Mark Chambers
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=20040712064401.25378.qmail@web13604.mail.yahoo.com \
--to=mythri_madhuker@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.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.