Hi
Now i able to build in ARM side as well in DSP side. i get both
readwritegpp.bin as well as readwrite.out.
then i executed in following order
1. copied the dsplinkk.ko from the below location to
/opt/dsplink_140-05p1/packages/dsplink
gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko
2.i execute the below commands
*
$* cd /opt/dsplink
*$* insmod dsplinkk.ko *
$* mknod /dev/dsplink c 230 0
When iam inserting the module, iam getting the below message in prompt
*dsplinkk: no version for "struct_module" found: kernel tain
ted.
dsplinkk: module license 'DSP/BIOS(TM) LINK' taints kernel.
DSPLINK Module (1.40.05_p1) created on Date: Nov 20 2007 Time: 11:01:11*
3. i created a new directory namely *samples* in below link
*
*/opt/dsplink_140-05p1/packages/dsplink
4. copied the files readwritegpp,readwrite.out from the release directory
into samples directory
5.with this i tried to run using below command
./readwritegpp readwrite.out 0x8FFF 1024 2
But iam getting below error message as below
*= Sample Application : READWRITE ==
Entered RDWR_Create ()
PROC_load failed. Status: [0x80008009]
Leaving RDWR_Create ()
Create phase failed. Status: [0x80008009]
Entered RDWR_Delete ()
MSGQ_release () failed. Status = [0x8000800b]
MSGQ_transportClose () failed. Status = [0x8000800b]
Segmentation fault
*
i checked the dsplink in /dev.. it is present.
Apart from this, if i tried to build using *sh -f buildmodule.sh *i got lot
of error messges...
alternatively, i build the samples like below
cd $DSPLINK/gpp/src/samples
make -s release
Is this procedure ok?
Kindly advise me on this issues
Regards
Vijayabharathi C
On 8/2/09, davinci-linux-open-source-requ...@linux.davincidsp.com <
davinci-linux-open-source-requ...@linux.davincidsp.com> wrote:
>
> Send Davinci-linux-open-source mailing list submissions to
>davinci-linux-open-source@linux.davincidsp.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
> or, via email, send a message with subject or body 'help' to
>davinci-linux-open-source-requ...@linux.davincidsp.com
>
> You can reach the person managing the list at
>davinci-linux-open-source-ow...@linux.davincidsp.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Davinci-linux-open-source digest..."
>
>
> Today's Topics:
>
> 1. RE: saDisplay + DM6467 showing black an white image in SD
> Display (Jadav, Brijesh R)
> 2. Re: Problem regarding DSPLink build (Pablo Bitton)
>
>
> --
>
> Message: 1
> Date: Sat, 1 Aug 2009 23:34:24 +0530
> From: "Jadav, Brijesh R"
> Subject: RE: saDisplay + DM6467 showing black an white image in SD
>Display
> To: Deepika Makhija , Vinayagam
>Mariappan
> Cc: "Davinci-linux-open-source@linux.davincidsp.com"
>
> Message-ID:
><19f8576c6e063c45be387c64729e73940432853...@dbde02.ent.ti.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Deepika,
>
> As per the specs, VPIF cannot display planar YUV422 data. It says it takes
> Luma and Chroma data for top and bottom field for interlaced image and Luma
> and Chroma data for the Progressive image. Also there is no separate
> register even to specify buffer pointer for cb and cr data. This is also
> true for the VDCE. Can you please tell me where it says VPIF can display
> planar YUV422 images?
>
> Thanks,
> Brijesh Jadav
>
> From: davinci-linux-open-source-boun...@linux.davincidsp.com [
> davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
> Deepika Makhija [deepika.makh...@einfochips.com]
> Sent: Saturday, August 01, 2009 12:01 AM
> To: Vinayagam Mariappan
> Cc: Davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: saDisplay + DM6467 showing black an white image in SD Display
>
> Hi,
>
> DM6467 encode/decode supports 4:2:0 YUV semi planar mode only
> Capture driver supports 4:2:2 YUV semi planar and display supports
> 4:2:2 semi planar and planar.
> VDCE module performs conversion irrespective of planar/semi planar mode, it
> does resize and CCV conversion
>
> Assume you perform CCV conversion of 4:2:2 to 4:2:0 than
>
> * If input is 4:2:2 semi planar than output will be 4:2:0 semi planar
> * If input is 4:2:2 planar than output will be 4:2:0 planar
>
> Capture and display drivers allocate buffer for 1920x1080 resolution during
> initialization. Two buffers are located, one for luma and other for chroma.
> So, Chroma will be at the offset of 1920*1080
