Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- From: max <mzennaro@xxxxxxx>
- Date: Fri, 24 Oct 2008 04:55:43 -0700 (PDT)
Thank you Paul,
your solution was my first version of the driver.
It manages dma, qci and i2c to get frames from a camera. Some
measurements made by a test application showed that instead of 15
frames per second (the maximum speed at which the camera acquires) I
get only 8.
I think it was caused by the copy of the 600 KB from the dma buffer to
the application buffer, so I decided to share the dma buffer. Now the
application shows the images at full speed.
But, with the debug version of the os, I found the logs of my previous
message. It seems that Hal... and Mm... are not the correct functions
to use, but I do not know what other memory management api I must
use.
Usuallly debug checks are warnings about something getting wrong, and
I would like to know what it is.
Can you help me?
.
- Follow-Ups:
- Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- From: Paul, Chao
- Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- References:
- HalAllocateCommonBuffer & MmMapIoSpace problem
- From: max
- Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- From: max
- Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- From: Paul, Chao
- HalAllocateCommonBuffer & MmMapIoSpace problem
- Prev by Date: Fast performing Timer APIs in WinCE...
- Next by Date: Re: Profiler tools for WinCE 6.0 device
- Previous by thread: Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- Next by thread: Re: HalAllocateCommonBuffer & MmMapIoSpace problem
- Index(es):
Relevant Pages
|