NT to WDM conversion

Hi All,

I have a simple Windows NT legacy driver for a PCI board, Which uses HalXXx
functions for getting/assigning the hardware resources. Is there a simple
way to convert the same to WDM driver ( I am looking at a day to 2 days of
work). Could anybody provide any pointers on the same.

Thanks in advance

-Nattu

Nattu wrote:

I have a simple Windows NT legacy driver for a PCI board, Which uses HalXXx
functions for getting/assigning the hardware resources. Is there a simple
way to convert the same to WDM driver ( I am looking at a day to 2 days of
work). Could anybody provide any pointers on the same.

The only way I know of to do something like this in one to two days is
to hire an experienced consultant who is (a) free at the time, and (b)
right next door so you don’t waste time shipping boards back and forth.


Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com

Even then doing it in two days will only be the case if the driver is
simple.
And that sure doesn’t count running all the tests on it. Maybe Walter can
do it in two days, I would place it at least two weeks if you want things
solid with full PNP testing (of course you could get lucky).

Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

----- Original Message -----
From: “Walter Oney”
Newsgroups: ntdev
To: “Windows System Software Developers Interest List”
Sent: Saturday, August 23, 2003 4:49 AM
Subject: [ntdev] Re: NT to WDM conversion

> Nattu wrote:
> > I have a simple Windows NT legacy driver for a PCI board, Which uses
HalXXx
> > functions for getting/assigning the hardware resources. Is there a
simple
> > way to convert the same to WDM driver ( I am looking at a day to 2 days
of
> > work). Could anybody provide any pointers on the same.
>
> The only way I know of to do something like this in one to two days is
> to hire an experienced consultant who is (a) free at the time, and (b)
> right next door so you don’t waste time shipping boards back and forth.
>
> –
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Check out our schedule at http://www.oneysoft.com
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@acm.org
> To unsubscribe send a blank email to xxxxx@lists.osr.com

Now Don, remember that “two weeks” is the shoot from the hip estimation and
very seldom is ever correct. Sight unseen, I wouldn’t take it for less than
30 man-days.


Gary G. Little
Seagate Technologies, LLC

“Don Burn” wrote in message news:xxxxx@ntdev…
>
> Even then doing it in two days will only be the case if the driver is
> simple.
> And that sure doesn’t count running all the tests on it. Maybe Walter can
> do it in two days, I would place it at least two weeks if you want things
> solid with full PNP testing (of course you could get lucky).
>
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>
> ----- Original Message -----
> From: “Walter Oney”
> Newsgroups: ntdev
> To: “Windows System Software Developers Interest List”

> Sent: Saturday, August 23, 2003 4:49 AM
> Subject: [ntdev] Re: NT to WDM conversion
>
>
> > Nattu wrote:
> > > I have a simple Windows NT legacy driver for a PCI board, Which uses
> HalXXx
> > > functions for getting/assigning the hardware resources. Is there a
> simple
> > > way to convert the same to WDM driver ( I am looking at a day to 2
days
> of
> > > work). Could anybody provide any pointers on the same.
> >
> > The only way I know of to do something like this in one to two days is
> > to hire an experienced consultant who is (a) free at the time, and (b)
> > right next door so you don’t waste time shipping boards back and forth.
> >
> > –
> > Walter Oney, Consulting and Training
> > Basic and Advanced Driver Programming Seminars
> > Check out our schedule at http://www.oneysoft.com
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@acm.org
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>

“Gary G. Little” wrote in message
news:xxxxx@ntdev…
>
> Sight unseen, I wouldn’t take it for less than
> 30 man-days.
>

I agree with Gary.

I think 30 engineering days of effort for converting a driver from NT to WDM
is very reasonable and maybe even conservative.

There are multiple possible issues that can arise, and the testing burden
alone is significant.

Peter
OSR

I am curious as to where the one to two days timeframe originated? Was this
mandated, or something you thought would be reasonable?

I would suggest, if you are going at this alone, you tell your boss 2 months
minimum. If you get done in less, great. I don’t know your skill level on
this, but you have to add PnP and Power management to this driver. This is
no small task and you better find a good code base to borrow from and not
try to reinvent the wheel here. If you want to be enterprising and write
your own PnP and power code, you better add about 3 more months to the
estimate again depending on your skill level.


Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm

“Nattu” wrote in message news:xxxxx@ntdev…
>
> Hi All,
>
> I have a simple Windows NT legacy driver for a PCI board, Which uses
HalXXx
> functions for getting/assigning the hardware resources. Is there a simple
> way to convert the same to WDM driver ( I am looking at a day to 2 days of
> work). Could anybody provide any pointers on the same.
>
> Thanks in advance
>
> -Nattu
>
>
>
>

The driver I am refering is just a small kernel module, which basically
programs a couple of registers during boot time and does nothing after that.
The main function itself is only between 250 to 300 lines of code. We, are
talking about device which doesn’t even need an ISR :).

I could live with this legacy driver but the problem is that I see a
resource conflict (Which should be eliminated if go to WDM). I thought it
was reasonable to have 3 to 4 days of workaround for this .

Thanks
Nattu

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
Sent: Wednesday, August 27, 2003 8:30 AM
To: Windows System Software Developers Interest List
Subject: [ntdev] Re: NT to WDM conversion

I am curious as to where the one to two days timeframe originated? Was this
mandated, or something you thought would be reasonable?

I would suggest, if you are going at this alone, you tell your boss 2 months
minimum. If you get done in less, great. I don’t know your skill level on
this, but you have to add PnP and Power management to this driver. This is
no small task and you better find a good code base to borrow from and not
try to reinvent the wheel here. If you want to be enterprising and write
your own PnP and power code, you better add about 3 more months to the
estimate again depending on your skill level.


Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm

“Nattu” wrote in message news:xxxxx@ntdev…
>
> Hi All,
>
> I have a simple Windows NT legacy driver for a PCI board, Which uses
HalXXx
> functions for getting/assigning the hardware resources. Is there a simple
> way to convert the same to WDM driver ( I am looking at a day to 2 days of
> work). Could anybody provide any pointers on the same.
>
> Thanks in advance
>
> -Nattu
>
>
>
>


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@lsil.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

But …

You are not accounting for the complexity of PnP, power management, and then
instaslling all of then in stalling all of the above using a brand spanking
new INF file. Contrary to what non-driver-writing managers think, device
drivers do NOT get written in a vacuum. Each one presents its own special
challenge and WDM must play well in PnP and Power management.

Use Walter’s wizard to create a template for a driver you think might do the
trick. Total the number of lines in each module and divide by 40. That’s a
reasonable estimate for a novice WDM developer to use. Yes, if you use his
template you may not have to WRITE all those lines, but you will have to
support them and that means you will have know them and own them as if they
were your own.


Gary G. Little
Seagate Technologies, LLC

“Nattu” wrote in message news:xxxxx@ntdev…
>
> The driver I am refering is just a small kernel module, which basically
> programs a couple of registers during boot time and does nothing after
that.
> The main function itself is only between 250 to 300 lines of code. We, are
> talking about device which doesn’t even need an ISR :).
>
> I could live with this legacy driver but the problem is that I see a
> resource conflict (Which should be eliminated if go to WDM). I thought it
> was reasonable to have 3 to 4 days of workaround for this .
>
> Thanks
> Nattu
>
>
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
> Sent: Wednesday, August 27, 2003 8:30 AM
> To: Windows System Software Developers Interest List
> Subject: [ntdev] Re: NT to WDM conversion
>
>
> I am curious as to where the one to two days timeframe originated? Was
this
> mandated, or something you thought would be reasonable?
>
> I would suggest, if you are going at this alone, you tell your boss 2
months
> minimum. If you get done in less, great. I don’t know your skill level
on
> this, but you have to add PnP and Power management to this driver. This
is
> no small task and you better find a good code base to borrow from and not
> try to reinvent the wheel here. If you want to be enterprising and write
> your own PnP and power code, you better add about 3 more months to the
> estimate again depending on your skill level.
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Nattu” wrote in message news:xxxxx@ntdev…
> >
> > Hi All,
> >
> > I have a simple Windows NT legacy driver for a PCI board, Which uses
> HalXXx
> > functions for getting/assigning the hardware resources. Is there a
simple
> > way to convert the same to WDM driver ( I am looking at a day to 2 days
of
> > work). Could anybody provide any pointers on the same.
> >
> > Thanks in advance
> >
> > -Nattu
> >
> >
> >
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@lsil.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>