Re: CE 5.0 Kernel question

From: K. S. Huang (ks_huang_at_AlphaNetworks.com_remove.this)
Date: 09/30/04


Date: Thu, 30 Sep 2004 12:05:34 +0800

Well,
I think you have better put your modified source code under your BSP
directory instead of the common directory.
Becasue the COMMON\SRC\X86 is shared for all of the x86 platforms, and other
platform may NOT have the ability of your own ioctl codes.

"Bryan" <anonymous@discussions.microsoft.com>
???????:40d801c4a69c$f45819e0$a501280a@phx.gbl...
Hi,

Thanks for you reply!!

Do you mean.....
If I wan to add a IOCTL call, such as IOCTL_HAL_UPDATE
and I have to do these...
1. // ioctl_tab.h
   .....................
   { IOCTL_HAL_UPDATE, 0, x86IoCtlUpdate },
   .............
2. Write a update.c program and put in the folder
    \wince500\platform\common\src\x86\common\ioctl\
   .....................
   bool x86IoCtlUpdate ( ...., ..., .... )
   { }

Am I right?

Thanks

Bryan 2004/09/30

>-----Original Message-----
>The CEPC BSP do NOT have \src\kernel\oal\ioctl.c nor the
\src\inc\ioctl.h.
>It only have a SRC\KERNEL\OAL\globals.c and it used the
pre-defined x86
>ioctl table ioctl_tab.h (COMMON\SRC\x86\INC).
>becase the last entry of ioctl_tab.h is all zero (the
End of Table), so
>we'll need to clone it into \src\inc (and have better
rename it into
>ioctl.h)!!
>Then add their own ioctl handler into the src\inc\ioctl.h
>
>
>"Yannick Chamming's [eMVP]"
<ychammings_nospam@adeset.com> ¼¶¼g©ó¶l¥ó·s»D
>:OA7$tMepEHA.3800@TK2MSFTNGP14.phx.gbl...
>> the PQOAL model of CE 5.0 implies that all CPU
specific code is in
>> Platform\Common. Only the board specific code is in
the BSP directory.
>> Consequently, the OEMIoControl function is no more
implemented as part of
>> the board specific code of the OAL. You only implement
specific ioctl
>> handlers.
>> To add your own ioctl, you can update the ioctl array
in inc\ioctl.h and
>add
>> your ioctl handler in kernel\oal\src\ioctl.c
>>
>>
>> --
>> -------------------------------------------------------
---------
>> Yannick Chamming's (eMVP)
>> ADESET
>> Windows Embedded Manager
>> ychammings AT adeset DOT com>
>> http://www.adeset.com
>> Tél : +33 (0)4.72.18.57.77
>> Fax : +33 (0)4.72.18.57.78
>> -------------------------------------------------------
---------
>>
>> "Bryan" <anonymous@discussions.microsoft.com> wrote in
message
>> news:337601c4a5c4$6d561e70$a501280a@phx.gbl...
>> > Hi all,
>> >
>> > I wrote some function in C:\WINCE420
>> > \PLATFORM\CEPC\KERNEL\HAL\oemioctl.c
>> > in CE 4.2.
>> >
>> > But I can not find the "oemioctl.c" in CE 5.0, where
can
>> > I put my code if I want to modify the kernel?
>> >
>> > Thanks,
>> > Bryan.
>> >
>> >
>> >
>> >
>>
>>
>
>
>.
>



Relevant Pages

  • Re: CE 5.0 Kernel question
    ... what you need to do is write your own ioctl handler and link it and the ... I have created another BSP to modify. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 5.0 Kernel question
    ... I forgot that for CEPC, the BSP ... > Then add their own ioctl handler into the src\inc\ioctl.h ... >> Yannick Chamming's ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 5.0 Kernel question
    ... I have created another BSP to modify. ... But if I put my ioctl code to my BSP folder, ... platforms, and other ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 5.0 Kernel question
    ... the OEMIoControl function is no more implemented as part of ... You only implement specific ioctl ... "Bryan" wrote in message ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 5.0 Kernel question
    ... Then add their own ioctl handler into the src\inc\ioctl.h ... > ychammings AT adeset DOT com> ...
    (microsoft.public.windowsce.platbuilder)