Yes. At least it is broken with old demos from all the vendors, including TI 
itself. Fixing those may not be hard at all though. 

--- On Thu, 5/15/08, Vim Venture <[EMAIL PROTECTED]> wrote:

> From: Vim Venture <[EMAIL PROTECTED]>
> Subject: Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot
> To: "gather bzbz" <[EMAIL PROTECTED]>
> Cc: "davinci" <davinci-linux-open-source@linux.davincidsp.com>
> Date: Thursday, May 15, 2008, 1:34 PM
> Thanks for the reply,
> 
> Are you saying that the SDK 1.3 demos just plain don't
> work yet?
> If that is the case, I should switch back to the SDK v1.2.
> 
> -Vim
> 
> 
> On May 15, 2008, at 1:26 PM, gather bzbz wrote:
> 
> > NO, u-boot has nothing to do with the IOCTL. it is the
> davincifb  
> > driver
> > in the OS that causes trouble. There are other
> compatibility issues
> > with the new SDK 1.3. Code migrations are needed.
> >
> >
> > --- On Thu, 5/15/08, Gbzbz Gbzbz
> <[EMAIL PROTECTED]> wrote:
> > From: Gbzbz Gbzbz <[EMAIL PROTECTED]>
> > Subject: Re: Demos not working in SDK 1.3, uBoot 1.2
> does not boot
> > To: "davinci"
> <davinci-linux-open-source@linux.davincidsp.com>,
> "Vim  
> > Venture" <[EMAIL PROTECTED]>
> > Date: Thursday, May 15, 2008, 1:10 PM
> >
> > NO, u-boot has nothing to do with the IOCTL. it is the
> davincifb  
> > driver in the OS that causes trouble. There are other
> compatibility  
> > issues with the new SDK 1.3. Code migrations are
> needed.
> >
> > --- On Thu, 5/15/08, Vim Venture
> <[EMAIL PROTECTED]> wrote:
> > From: Vim Venture <[EMAIL PROTECTED]>
> > Subject: Demos not working in SDK 1.3, uBoot 1.2 does
> not boot
> > To: "davinci"
> <davinci-linux-open-source@linux.davincidsp.com>
> > Date: Thursday, May 15, 2008, 7:30 PM
> >
> > Hi everyone,
> > I am using the SDK v1.30 release on the DM6446, and
> none of the demos
> > will run for me.
> > When I run the decode demo, I get the following
> > error.
> >
> >
> ----------------------------------------------------------
> > [EMAIL PROTECTED]:/opt/dvsdk/dm6446# ./decode -v data/
> > davincieffect_ntsc.m2v
> > Decode demo started.
> > Decode Error: Failed to get the requested screen size:
> 720x480 at 16  
> > bpp
> > Decode Error: Failed ioctl FBIOPUT_VSCREENINFO on
> /dev/fb/0
> >
> > Total I-frames: 1, P-frames: 2, B-frames: 0,
> IDR-frames: 0 rejected: 0
> > [EMAIL PROTECTED]:/opt/dvsdk/dm6446#
> >
> ----------------------------------------------------------
> >
> > Similar errors occur with the other demos.  I am
> currently using uBoot
> > 1.1.3.  The release notes for SDK 1.30 say that an
> upgrade to uBoot
> > 1.2 is needed, but my DM6446 EVM will not boot with
> uBoot 1.2.  It is
> > unresponsive and I have to revert back to 1.1.3 with
> DVFlasher to get
> > a proper boot.  I'm not sure if these 2 problems
> are related.  Could
> > the version of uBoot affect FBIOPUT_VSCREENINFO?
> >
> > My boot-time video args are
> > set as:
> > video
> > =
> > dm6446fb:vid0
> > =
> > 720x480x16,2025K
> > @0,0
> >
> :vid1=720x480,[EMAIL PROTECTED],0:osd0=720x480,[EMAIL 
> PROTECTED],0:osd1=720x480,[EMAIL PROTECTED],0
> >
> > Has anyone else bumped into this problem?
> >
> > Regards,
> > -Vim
> >
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> >
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> >
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
> >
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> >
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source


      
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to