Just to add a comment, the problem that was originally reported, "Bus
error", indicates a data-alignment problem. Here, mvL0 was assumed to
be 32-bit aligned...which is not necessary the case.
On Dec 2, 11:32 am, rktb <[EMAIL PROTECTED]> wrote:
> This is a quick fix. I am still not sure whether the same patch will
> be applied or not. But, here it is ..
>
> File: external/opencore/codecs_v2/video/avc_h264_old/enc/src/
> motion_est.cpp
> Function: void AVCMotionEstimation(AVCEncObject *encvid)
>
> mv_uint32 = ((mot_mb_16x16->y) << 16) | ((mot_mb_16x16->x) &
> 0xffff);
> for (k = 0; k < 32; k += 2)
> {
> ptr_mv = (void*)(&currMB->mvL0[k]);
> *((uint32*)ptr_mv) = mv_uint32;
> }
>
> to
>
> for (k = 0;k < 32; k+=2)
> {
> currMB->mvL0[k] = mot_mb_16x16->x & 0xFFFF;
> currMB->mvL0[k+1] = mot_mb_16x16->y;
> }
>
> On Dec 1, 11:27 am, "Ricardo Martinez" <[EMAIL PROTECTED]> wrote:
>
> > great!
>
> > Do you have a fix that I could apply until the patch is available?
>
> > BR,
> > Ricardo
>
> > On Mon, Dec 1, 2008 at 8:41 AM, rktb <[EMAIL PROTECTED]> wrote:
>
> > > I am able to reproduce this. I can see the problem and also have a
> > > fix. Will submit a patch soon.
>
> > > Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
