How do I get KernelIoControl and associated definitions (DEVICE_ID,
IOCTL_HAL_GET_DEVICEID, etc) into an SDK for my custom platform?

In the Pocket PC 2003 SDK there's a "uniqueid.h" header file that has
some of these definitions in it. There is no such header file in the SDK
I generated from my platform.

I want users of my SDK to be able to get Device Id, Platform Type, etc.
Is there a way to expose these from the SDK?

Thanks,
Dave

Re: Exposing KernelIoControl by Bruce

Bruce
Mon Jun 27 15:57:19 CDT 2005

You can specify a file to be included in the SDK in the configure dialog.
Or a couple of times I have posted a way to use makefile.inc to solve this.

http://groups-beta.google.com/groups?as_q=makefile.inc&num=10&as_scoring=r&hl=en&btnG=Google+Search&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uauthors=eitman&as_umsgid=&lr=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1981&as_maxd=27&as_maxm=6&as_maxy=2005&safe=images

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member


"Dave Findlay" <BLAHdfindlayBLAH@BLAHvocollectBLAH.com> wrote in message
news:OL5$oi1eFHA.2556@TK2MSFTNGP10.phx.gbl...
> How do I get KernelIoControl and associated definitions (DEVICE_ID,
> IOCTL_HAL_GET_DEVICEID, etc) into an SDK for my custom platform?
>
> In the Pocket PC 2003 SDK there's a "uniqueid.h" header file that has
> some of these definitions in it. There is no such header file in the SDK
> I generated from my platform.
>
> I want users of my SDK to be able to get Device Id, Platform Type, etc.
> Is there a way to expose these from the SDK?
>
> Thanks,
> Dave



Re: Exposing KernelIoControl by Dave

Dave
Tue Jun 28 07:32:33 CDT 2005

Bruce Eitman (eMVP) wrote:
> You can specify a file to be included in the SDK in the configure dialog.
> Or a couple of times I have posted a way to use makefile.inc to solve this.
>
> http://groups-beta.google.com/groups?as_q=makefile.inc&num=10&as_scoring=r&hl=en&btnG=Google+Search&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uauthors=eitman&as_umsgid=&lr=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1981&as_maxd=27&as_maxm=6&as_maxy=2005&safe=images
>
Bruce,

That makes perfect sense if I am attempting to add my own custom files
to the SDK - and it's come in very handy, thanks!

But in this case, this is KernelIoControl and standard IOCTL definitions
from pkfuncs.h we're talking about. Why isn't this stuff in the SDK by
default? I don't have to cut and paste OS function definitions into my
own headers for anything else.

Am I missing something?

Thanks,
Dave

Re: Exposing KernelIoControl by Bruce

Bruce
Tue Jun 28 09:16:01 CDT 2005

Sorry, I did not understand that part of your question. You were clear on
it though.

For some reason, MS determined that these IOCTLs were not needed by
application programmers. Like you I don't agree, but to make up for it, you
must do one of my earlier suggestions.

Alternatively, many BSP developers create a set of APIs that abstract the
KernelIoControl calls so that application developers never need the IOCTLs.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member


"Dave Findlay" <BLAHdfindlayBLAH@BLAHvocollectBLAH.com> wrote in message
news:OHwl819eFHA.900@TK2MSFTNGP10.phx.gbl...
> Bruce Eitman (eMVP) wrote:
> > You can specify a file to be included in the SDK in the configure
dialog.
> > Or a couple of times I have posted a way to use makefile.inc to solve
this.
> >
> >
http://groups-beta.google.com/groups?as_q=makefile.inc&num=10&as_scoring=r&hl=en&btnG=Google+Search&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uauthors=eitman&as_umsgid=&lr=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1981&as_maxd=27&as_maxm=6&as_maxy=2005&safe=images
> >
> Bruce,
>
> That makes perfect sense if I am attempting to add my own custom files
> to the SDK - and it's come in very handy, thanks!
>
> But in this case, this is KernelIoControl and standard IOCTL definitions
> from pkfuncs.h we're talking about. Why isn't this stuff in the SDK by
> default? I don't have to cut and paste OS function definitions into my
> own headers for anything else.
>
> Am I missing something?
>
> Thanks,
> Dave



Re: Exposing KernelIoControl by Steve

Steve
Tue Jun 28 11:30:22 CDT 2005

"Alternatively, many BSP developers create a set of APIs that abstract the
KernelIoControl calls so that application developers never need the IOCTLs."

This would be the approach I would recommend. You can then include your own
header for this and there is no need to deal with the issues of stuffing
param into a data structure to pass to KernelIoControl. It also allows you
to change or enhance the internal implementation without effecting existing
clients.


--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com