albertrichardchang
Mon Apr 05 10:24:10 CDT 2004
Dear David,
As I know, the last step I can control (for warm-boot) is to prepare
the starting address. I even can not set the "jump" command to re-run
the WinCE image, let alone "the Reset".
I assumed the warm-boot is to jump to the starting address to re-run
the WinCE image once again. If I am wrong, please correct me.
Would you please explain your comment in more details ?
The Reset means the PCI reset, but not the WinCE reset, right ?
How can I make sure the Reset is issued during warm-boot ?
Please advise.
Thanks in advance.
"David Liao \(MS\)" <davli@online.microsoft.com> wrote in message news:<406cc1d1$1@news.microsoft.com>...
> Are you sure the Reset is issue during warm-boot?
> If not, of cause, some PCI devices may not work.
> David Liao
> "Seung Yi" <seungyi@codetelligence_NOSPAMMERS_.com> wrote in message
> news:opr5sqjxjhswt9p6@localhost...
> If the BIOS or bootloader configures the PCI bus resources on PCI devices,
> then NOConfig should be set to 1. Otherwise if you want to let the PCIBus
> driver configure the PCI bridge device and configure all downstream PCI
> devices you can set this to 0. ALthough I would recommend the BIOS or
> bootloader do it since PCI slot assignments are board specific
> (specifically interrupt resources).
>
>
> On 1 Apr 2004 12:30:54 -0800, Albert C. <albertrichardchang@hotmail.com>
> wrote:
>
> > Hi, I am working on NS/Geode platform.
> >
> > In WinCE.NET 4.2, I got the NIC device not loaded after a warm-boot;
> > while it is OK in WinCE.NET 4.0.
> >
> > After tracking, I found the devices under PCI\Template were all
> > failed, but it works after changing the registry key(NoConfig) from 0
> > to 1.
> >
> > I just wonder how we decided to use NoConfig=0 or 1. That is, under
> > which situation we should set NoConfig=0 ? And when we should set
> > NoConfig=1 ?
> >
> > Please advise.