R: poulsbo pins

NTDEV
1

If I am the first, what is the role of acpi.sys, marked as Fido by DevView?

I am new to win driver development so I don’t know if there are other ways
to install a filter, or if DevView has a bug or if I didn’ understood the
difference between Fido and a filter.

Thank you for your patience

-----Messaggio originale-----
Da: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] Per conto di Tim Roberts
Inviato: mercoled? 21 gennaio 2009 18.47
A: Windows System Software Devs Interest List
Oggetto: Re: [ntdev] poulsbo pins

xxxxx@texa.it wrote:

I am working with an Eurotech board with atom/poulsbo with a windows
embedded standard (wes) os generated by me. I am new to windows embedded
studio and wdf.

I need to use some of the poulsbo pins both for input (interrupt) and
output.

I know that there is an existing device (wes knows atom/poulsbo) so I know
that I must implement a filter driver and I must do the job by hand (page
790 of W. Oney book)

The poulsbo manual tells me that gpio base address belongs to the pci
device 8086/8119, so I went to the registry and found the hardware key:
…\enum\pci\ven…\3&… but it lacks of UpperFilters.

DevView tells me that there is a stack with a pdo (pci.sys), fdo
(isapnp.sys) and fido (acpi.sys): where can I find the UpperFilter key?

If the device doesn’t have any filters, there won’t be an UpperFilters
or LowerFilters value. If you are the first, you have to add it.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

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

2

Acpi is special, ignore it. It gets into stacks as a bus filter driver, which is a rather advanced and undocumented subject

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Massimo Zennaro
Sent: Wednesday, January 21, 2009 11:27 PM
To: Windows System Software Devs Interest List
Subject: R: [ntdev] poulsbo pins

If I am the first, what is the role of acpi.sys, marked as Fido by DevView?

I am new to win driver development so I don’t know if there are other ways
to install a filter, or if DevView has a bug or if I didn’ understood the
difference between Fido and a filter.

Thank you for your patience

-----Messaggio originale-----
Da: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] Per conto di Tim Roberts
Inviato: mercoled? 21 gennaio 2009 18.47
A: Windows System Software Devs Interest List
Oggetto: Re: [ntdev] poulsbo pins

xxxxx@texa.it wrote:
> I am working with an Eurotech board with atom/poulsbo with a windows
embedded standard (wes) os generated by me. I am new to windows embedded
studio and wdf.
>
> I need to use some of the poulsbo pins both for input (interrupt) and
output.
>
> I know that there is an existing device (wes knows atom/poulsbo) so I know
that I must implement a filter driver and I must do the job by hand (page
790 of W. Oney book)
>
> The poulsbo manual tells me that gpio base address belongs to the pci
device 8086/8119, so I went to the registry and found the hardware key:
…\enum\pci\ven…\3&… but it lacks of UpperFilters.
>
> DevView tells me that there is a stack with a pdo (pci.sys), fdo
(isapnp.sys) and fido (acpi.sys): where can I find the UpperFilter key?
>

If the device doesn’t have any filters, there won’t be an UpperFilters
or LowerFilters value. If you are the first, you have to add it.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
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

3

Thank you Doron for your clarification.

The Oney book uses this technique: the driver add a runonce key to call a
dll function that updates the upperfilters/lowerfilters key.

My peculiar alternative is to add the key in target designer, so I need your
help: there is a sequence to follow or the driver installation and the
upperfilter addition can be interchanged?

-----Messaggio originale-----
Da: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] Per conto di Doron Holan
Inviato: gioved? 22 gennaio 2009 8.41
A: Windows System Software Devs Interest List
Oggetto: RE: [ntdev] poulsbo pins

Acpi is special, ignore it. It gets into stacks as a bus filter driver,
which is a rather advanced and undocumented subject

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Massimo Zennaro
Sent: Wednesday, January 21, 2009 11:27 PM
To: Windows System Software Devs Interest List
Subject: R: [ntdev] poulsbo pins

If I am the first, what is the role of acpi.sys, marked as Fido by DevView?

I am new to win driver development so I don’t know if there are other ways
to install a filter, or if DevView has a bug or if I didn’ understood the
difference between Fido and a filter.

Thank you for your patience

-----Messaggio originale-----
Da: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] Per conto di Tim Roberts
Inviato: mercoled? 21 gennaio 2009 18.47
A: Windows System Software Devs Interest List
Oggetto: Re: [ntdev] poulsbo pins

xxxxx@texa.it wrote:
> I am working with an Eurotech board with atom/poulsbo with a windows
embedded standard (wes) os generated by me. I am new to windows embedded
studio and wdf.
>
> I need to use some of the poulsbo pins both for input (interrupt) and
output.
>
> I know that there is an existing device (wes knows atom/poulsbo) so I know
that I must implement a filter driver and I must do the job by hand (page
790 of W. Oney book)
>
> The poulsbo manual tells me that gpio base address belongs to the pci
device 8086/8119, so I went to the registry and found the hardware key:
…\enum\pci\ven…\3&… but it lacks of UpperFilters.
>
> DevView tells me that there is a stack with a pdo (pci.sys), fdo
(isapnp.sys) and fido (acpi.sys): where can I find the UpperFilter key?
>

If the device doesn’t have any filters, there won’t be an UpperFilters
or LowerFilters value. If you are the first, you have to add it.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
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

4

Massimo Zennaro wrote:

The Oney book uses this technique: the driver add a runonce key to call a
dll function that updates the upperfilters/lowerfilters key.

My peculiar alternative is to add the key in target designer, so I need your
help: there is a sequence to follow or the driver installation and the
upperfilter addition can be interchanged?

There are very few people on this list with experience in Target
Designer, but the UpperFilters and LowerFilters values are just ordinary
REG_MULTI_SZ registry values. There’s no magic involved. As long as
the device or class registry entry exists, you can add the value to it.
The value won’t be used until the system finally boots, so I can’t see
why there should be any “sequence” issues.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

5

Tim, there could be this issue: os starts, loads the driver with the UpperFilter key, reads the key and finds that the driver does not exist (because it is not installed): now the os can ignore the error or complain and take some action like remove the whole driver stack.

Remember that I am new to driver development and none of my colleagues can help me.

6

xxxxx@texa.it wrote:

Tim, there could be this issue: os starts, loads the driver with the UpperFilter key, reads the key and finds that the driver does not exist (because it is not installed): now the os can ignore the error or complain and take some action like remove the whole driver stack.

Remember that I am new to driver development and none of my colleagues can help me.

As far as I can remember, if a device launches and a filter driver
cannot be found, it simply skips the filter and moves on. This would,
however, be pretty easy to test.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.