Re: Shared PCI NIC for KITL and NDIS
- From: "Helge Kruse" <Helge.Kruse-nospam@xxxxxxx>
- Date: Mon, 4 Feb 2008 08:10:37 +0100
Unfortunately no NKDeleteRegKey or similar is available in OAL. See
pkfuncs.h line 1117
/Helge
"Luca Calligaris" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uW6ihu%23YIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
But do you fail to delete the key in OALKitlInitRegistry?
--
Luca Calligaris
www.eurotech.it
"Helge Kruse" <Helge.Kruse-nospam@xxxxxxx> ha scritto nel messaggio
news:eIwOqN%23YIHA.5348@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
Yes I am using a CEPC like BSP. Thank you for the advise, but the
registry key is already in the registry, since it's stored in the
persistent registry. So it makes no difference if you call PCIReg via
OALKitlInitRegistry or not.
The PCIBUS enumerator checks only for stale drivers where the device is
not present anymore. It cannot deal with a PCI NIC that is used for KITL
or NDIS alternatively. Unfortunately the PCIBUS driver holds an open key
of the registry value. So you cannot delete it. (see below)
All QFEs have been installed. So this seems like an open bug.
/Helge
"K. S. Huang" <k_Underln_s_Underln_huang_AT_yahoo_DOT_com> wrote in
message
news:%23IifKAtYIHA.3964@xxxxxxxxxxxxxxxxxxxxxxx
Are you using a PC (x86) based platform with CEPC or CEPC like BSP with
PQOAL?
If so, the registry is created by OALKitlInitRegistry
($(_WINCEROOT)\PLATFORM\COMMON\SRC\COMMON\KITL\registry.c), try to track
and make sure the function is not called during booting.
In general, the PCIBus.dll will clean up the
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance] everytime on bootup so
that this key should be complete empty at initial and then OAL will
create
a the sub key KITL under there with proper parameter to pvent the PCIBus
to load the driver.
BTW, have you obtained the latest QFE for your CE, it seems that the CE
4.x did have the PCI instance registry uncleaned issue, and I am not
sure
if it still an issue on CE5 and fixed with QFEs.
"Helge Kruse" <Helge.Kruse-nospam@xxxxxxx> wrote in message
news:eNs8$cpYIHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I need to share a PCI NIC for KITL and NDIS. A boot flag controls, if
KITL is active and VMINI is loaded. When the boot flag disables KITL
the
NDIS miniport driver should be loaded.
When the KITL driver is active, the PCIBUS enumerator creates a
registry
key [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\KITL] with
appropriate values including vendor id and device id. The miniport
drvier
is not loaded. That's ok so far.
When the boot flag is changed, the PCI vendor id and device id from the
registry is found, since the NIC is still in the system. But as long as
the registry key is present, it prevents the miniport driver from
loading.
I tried to delete the registry key
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\KITL] but this failed
with error 0x05.
What is the best way to get rid of this orphaned registry key, when
KITL
is disabled?
OS is Windows CE 5.0
Regards, Helge
--
Time is an ocean but it ends at the shore
.
- Prev by Date: Audio Multi channel selection.
- Next by Date: VLAN support in WinCE
- Previous by thread: Audio Multi channel selection.
- Next by thread: VLAN support in WinCE
- Index(es):
Relevant Pages
|
