Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: "Seehwan" <seehwan.yoo@xxxxxxxxx>
- Date: 28 Oct 2006 19:25:11 -0700
I am not sure whether I am understanding about your talk.
CE 6 provides much robustness in their architecture, in terms of VM and
Device drivers.
However, does that need indeed?
I agree on the new VM architecture because it provides more strict
separation among the process address space, and more robustness when
failure has occurred.
On the other hands, user mode device driver may not so appealing to me
because it still has too many restrictions and that as you pointed,
because most embedded systems are closed systems, there is little
portion to play a role for 3rd party.
Still, kernel mode device driver is the default option and I think it
is still far from reality.
Steve Maillet (eMVP) wrote:
ps. Still now, I see many restrictions on udevice architecture. e.g. noThose are in Kernel mode for performance reasons.
usb support, no filesystem support, no network driver support, etc.
The original post was essentially looking for a way to call
HalAllocCommonBuffer() from user mode code in CE V6.0 since the security
architecture of the kernel blocks that from user mode code. There are a LOT
of Embedded systems out there that used to party on the hardware with out
concern for security because they were completely closed systems. Those
devices now need to change to work on CE6.0. There are several options for
how you go about porting that kind of application in V6.0. A few of them
have been proposed in this thread.
--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com
.
- Follow-Ups:
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Steve Maillet \(eMVP\)
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- References:
- Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: somraj
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: seehwan.yoo@xxxxxxxxx
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: fd
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Dean Ramsier
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: somraj
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Steve Maillet \(eMVP\)
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: fd
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Steve Maillet \(eMVP\)
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: fd
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Steve Maillet \(eMVP\)
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Seehwan
- Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- From: Steve Maillet \(eMVP\)
- Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- Prev by Date: Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- Next by Date: Re: Problem Running ARMV4I-based emulator from platform builerder after ce 6.0 rtm install
- Previous by thread: Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- Next by thread: Re: Allocating and accessing physically contiguous memory in user mode in WinCE 6.0 Beta
- Index(es):
Relevant Pages
|