Once you overcome the learning curve, you will be going downhill. The curve
in my definition is how to build a driver, setup a debugger and load the
driver with debugger attached.
Writing driver (apart from dealing with the device technologies specific to
your hardware), is no more than RTFM and DISASM. The first part tells you
what have been said that one must know and remember. The latter tells you
what have not been said but you will need at some point of time.
Having reasonable understand of how the OS works will help you make sense of
what the documents say hence you could remember it and turn it into your
mother nature. Once you have the basic, you can learn anything in Windows
on your own.
Calvin
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of piyush jain
Sent: Friday, July 09, 2010 11:48 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] need advice learning driver development
I never at any point of time said that I will going a new project or i need
to write a driver from scratch. I need to learn driver development and I am
surrounded by quite a few experienced guys (mostly 5+ yrs) in driver
development.
Problem is that they don’t have time to babysit me (and their approach is
not easy to understand–knowing and ‘to be able to teach’ are 2 different
things) but they are happy to help me with doubts.
Now, my request was simple. i need to learn and how do i go about it. if u
see a person in my situation, how will u guide him? that all i asked, I
think only few like Peter provided help and how to go about it; and to me,
others are making unnecessary discussion !
Please do not take any offense. I just wanted to be clear and wanted to make
this tread useful even for others, who see it later.
On Fri, Jul 9, 2010 at 10:45 PM, Calvin Guan
wrote:
I believe OSR is good although I never have the luxury to get there.
I agree with Pavel’s point. If I were the manager to start a new project
that is critical, I would hire experienced who has been there and done that.
Initial quality and time to market are vital for a project to survive IMO.
Instead of sending a fresh man to OSR, it makes more sense to hire osr (or
whoever that is capable) to do the initial work.
For sustaining effort, it’s ok for less experienced given that the original
work does not require major overhaul or rewrite.
Calvin
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, July 09, 2010 8:22 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] need advice learning driver development
> From: Pavel A. [mailto:xxxxx@fastmail.fm]
> With all due respect to OSR courses and others, they teach generic
knowledge,
> a lot more than one needs for a specific project, that requires time
and
> effort to understand.
Have you actually taken an OSR class? Yes the knowledge is generic, but
most of it is applicable to many classes of drivers. The thing about
OSR and the other good instructors is not that they teach you the
subject matter, but they guide you into how to find the data you need.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer