CE/NT .. maybe;
  http://www.keinet.tv/linux/ipaq/install-j.html
  http://www.cotw.com/projects/nino/port/boot-loader.html

Oooh ..
  http://developer.intel.com/design/wireless/telematics/designcenter/3501TBPB.pdf


Aaah;
  
http://unicoi.kennesaw.edu/ase/ase02_01/bookcase/sprpts/microsoft_reports/extreme/ntece
.doc

Hardware Design

Windows NT Embedded 4.0 runs on standard PC hardware, allowing developers to realize
fast time-to-market. Non-standard hardware is also supported using a custom hardware 
abstraction layer (HAL) for added flexibility. A HAL Development Kit is available from
Microsoft for this purpose. Developing a HAL requires a significant development effort 
using
highly technical software developers. Therefore, it is expected that most OEMs will 
use the
standard HAL that ships with Windows NT Embedded 4.0. The standard Windows NT loader
and HAL require that the platform include a PC-compatible BIOS.

Windows CE 2.12 is designed to be very flexible for hardware design. In addition to 
being 
able to run on a standard PC hardware design, Windows CE 2.12 can also run on custom
hardware designs. Windows CE achieves this flexibility by requiring that the OEM 
implement
a thin layer of code in the kernel called the OEM Adaptation Layer (OAL). Implementing 
the
 Windows CE OAL requires a small amount of development effort compared to that required
for the Windows NT HAL. The OEM is also responsible for implementing the Windows CE
bootloader. Because the OEM implements both the OAL and the bootloader, a PC-compatible
BIOS is not required. This allows Windows CE to achieve faster boot times than Windows
NT Embedded.





  ----- Original Message -----
>From: <[EMAIL PROTECTED]>, <Eric W. Biederman>
>To: "K.M. Liu" <[EMAIL PROTECTED]>
>Subject:  Re: WinCE Loader
>Date: Thu, 21 Feb 2002 22:53:03 -0700
>
> "K.M. Liu" <[EMAIL PROTECTED]> writes:
> 
> > We load WinCE bootloader via the ELF bootloader.
> > If your product want to use the WinCE, we can provide the bootloader for you.
> 
> Good, providing for a wider audience can only help LinuxBIOS in the long run.
> 
> In this case my interest is as a LinuxBIOS architect.  If any strange
> dependencies or requirements crop up with Windows CE please let me
> know.  I do not expect to touch Windows CE but I do plan to ensure the
> LinuxBIOS interface remains stable and capable of supporting Windows CE
> along with other operating systems.  Though I primarily about care
> about Linux.
> 
> Eric
> 

Reply via email to