hi ~~
I have found the problem ~~ The 3'rd partner didn't give us the right
v4l2 driver. Thanks for your help ~~
Best wishes
在 2009-06-09二的 16:41 +0900，Dongsoo, Nathaniel Kim写道：
> Hi,
>
> Sorry I still don't get what the full frame means, but I might
> consider that is the maximum resolution-ed
Hi,
Sorry I still don't get what the full frame means, but I might
consider that is the maximum resolution-ed image data coming from
external camera module. And whatever it is, you might have no problem
getting data through memcpy with buf.byteused size.
Cheers,
Nate
On Tue, Jun 9, 2009 at 11:22
hi ~~ Dongsoo, Nathaniel ~
I am sorry for disturbing you, and not descripe the question clear ~
Thanks very much for your help ~~
I know that I must stop preview with streamoff and re-configure with
s_fmt ~~ I have asked to you before ~!~
The "full frame" means a complete frame ~Because I just
Hi,
Sorry I'm not an expert, you can expect expertise from maintainers not from me.
But before answering your question about capturing, I'm not sure about
what the "full frame" means. I just assume that you meant to say the
biggest resolution of image frame, right?
So, when you are to capture a f
Hi Dongsoo, Nathaniel ~
You must be expert on V4l2 ~ Thanks very much for your help and advice
~!~
I used the MXC camera interface driver from Fressscale ,I readed the
driver interface just now ,and have fouded that the driver not modified
the buf.lenth but buf.byteused . You are very right , I wil
Hello Xie,
I'm not sure which camera interface driver you are using, but it seems
to be camera interface driver's problem. Let me guess, are you using
pxa camera interface driver from Marvell?(proprietary but not in up
stream kernel)
It just looks like that camera interface driver is not returning
Dear all ~~
I have met a issue when I used the mmap method for previewing . I just
used the standard code as spec to get the image data :
status_t CameraHardwareProwave::V4l2Camera::v4l2CaptureMainloop()
{
LOG_FUNCTION_NAME
int rt ;
unsigned int i ;
fd_set fds ;
