Hi,
Please execute below program in your davinci board. It seems there is a
toolchain bug when processing unsigned long long.
I'm using tool-chain shipped with DVEVM 1.00 and the details are:
# arm_v5t_le-gcc --version
arm_v5t_le-gcc (GCC) 3.4.3 (MontaVista 3.4.3-25.0.30.0501131 2005-07-23)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
---
#include <stdio.h>
#define A 0x00000001ULL
#define B 0x00000002ULL
#define C 0x00000004ULL
#define D 0x00000008ULL
#define E 0x00000010ULL
int main(void)
{
unsigned long long x = 0x00000004ULL;
switch(x)
{
case A: printf("x == A\n"); break;
case B: printf("x == B\n"); break;
case D: printf("x == D\n"); break;
case C: printf("x == C\n"); break;
case E: printf("x == E\n"); break;
default : printf("x : Case :: Default\n");
}
return 0;
}
----- Original Message ----
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, November 27, 2006 2:21:14 PM
Subject: Davinci-linux-open-source Digest, Vol 11, Issue 71
Send Davinci-linux-open-source mailing list submissions to
[email protected]
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
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
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: Your message to Davinci-linux-open-source awaits
moderatorapproval (Bhattacharya, Rishi)
2. VCL cross compile error (Will Tucker)
3. Re: SPI issue (Carlos Ojea)
4. RE: Query on the memcopy of the decoded video buffer
(Anderberg, Niclas)
----------------------------------------------------------------------
Message: 1
Date: Sun, 26 Nov 2006 15:43:41 -0600
From: "Bhattacharya, Rishi" <[EMAIL PROTECTED]>
Subject: RE: Your message to Davinci-linux-open-source awaits
moderatorapproval
To: "Ring, Chris" <[EMAIL PROTECTED]>,
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="US-ASCII"
I've increased the limit to 250KB (which is extremely generous, given
that most open-source mailing lists have a *much* smaller quota).
Anything larger than this that needs to be sent to all members should be
posted via an online fileserver/weblink.
Take care,
Rishi
-----Original Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
com] On Behalf Of Ring, Chris
Sent: Saturday, November 25, 2006 11:55 AM
To: [email protected]
Subject: RE: Your message to Davinci-linux-open-source awaits
moderatorapproval
BTW, I posted a response to Zhou's cache question. I think he got a
copy, but no one else did because of the notification below. I've
attached my response, modulo the pdf... we'll see if the moderator
ultimately approves.
List members, is this 100KB limit "too low"?
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Saturday, November 25, 2006 9:41 AM
> To: Ring, Chris
> Subject: Your message to Davinci-linux-open-source awaits
> moderator approval
>
> Your mail to 'Davinci-linux-open-source' with the subject
>
> RE: cache coherency problem
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Message body is too big: 303472 bytes with a limit of 100 KB
>
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision. If you would like to cancel
> this posting, please visit the following URL:
<chop>
------------------------------
Message: 2
Date: Sun, 26 Nov 2006 20:57:43 -0800 (PST)
From: Will Tucker <[EMAIL PROTECTED]>
Subject: VCL cross compile error
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
I got to here and I don't know how to solve this cross compile issue.
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
could not read symbols: File in wrong format
collect2: ld returned 1 exit status
Please help.
Thanks,
Will
make[3]: Entering directory `/home/guest/0_videoLan/vlc-trunk/src'
make[4]: Entering directory `/home/guest/0_videoLan/vlc-trunk/src'
/bin/sh ../libtool --tag=CXX --mode=link g++
-L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib -o libvlc.la
-rpath /home/guest/0_out/lib `top_builddir=".." ../vlc-config --libs vlc`
-no-undefined -export-symbols libvlc.sym -version-info 0:0:0
libvlc_la-libvlc.lo libvlc_la-libvlc-common.lo interface/libvlc_la-interface.lo
interface/libvlc_la-intf_eject.lo interface/libvlc_la-interaction.lo
playlist/libvlc_la-thread.lo playlist/libvlc_la-control.lo
playlist/libvlc_la-engine.lo playlist/libvlc_la-sort.lo
playlist/libvlc_la-loadsave.lo playlist/libvlc_la-tree.lo
playlist/libvlc_la-item.lo playlist/libvlc_la-search.lo
playlist/libvlc_la-services_discovery.lo input/libvlc_la-item.lo
input/libvlc_la-access.lo input/libvlc_la-clock.lo input/libvlc_la-control.lo
input/libvlc_la-decoder.lo input/libvlc_la-demux.lo input/libvlc_la-es_out.lo
input/libvlc_la-input.lo input/libvlc_la-meta.lo input/libvlc_la-stream.lo
input/libvlc_la-mem_stream.lo
input/libvlc_la-subtitles.lo input/libvlc_la-var.lo
video_output/libvlc_la-video_output.lo video_output/libvlc_la-vout_pictures.lo
video_output/libvlc_la-video_text.lo video_output/libvlc_la-video_widgets.lo
video_output/libvlc_la-vout_subpictures.lo
video_output/libvlc_la-vout_synchro.lo video_output/libvlc_la-vout_intf.lo
audio_output/libvlc_la-common.lo audio_output/libvlc_la-dec.lo
audio_output/libvlc_la-filters.lo audio_output/libvlc_la-input.lo
audio_output/libvlc_la-mixer.lo audio_output/libvlc_la-output.lo
audio_output/libvlc_la-intf.lo stream_output/libvlc_la-stream_output.lo
stream_output/libvlc_la-announce.lo stream_output/libvlc_la-profiles.lo
stream_output/libvlc_la-sap.lo osd/libvlc_la-osd.lo osd/libvlc_la-osd_parser.lo
osd/libvlc_la-osd_text.lo osd/libvlc_la-osd_widgets.lo network/libvlc_la-acl.lo
network/libvlc_la-getaddrinfo.lo network/libvlc_la-io.lo
network/libvlc_la-error.lo network/libvlc_la-tcp.lo network/libvlc_la-udp.lo
network/libvlc_la-httpd.lo
network/libvlc_la-rootwrap.lo network/libvlc_la-tls.lo
misc/libvlc_la-charset.lo misc/libvlc_la-md5.lo misc/libvlc_la-mtime.lo
misc/libvlc_la-block.lo misc/libvlc_la-modules.lo misc/libvlc_la-threads.lo
misc/libvlc_la-stats.lo misc/libvlc_la-strings.lo misc/libvlc_la-unicode.lo
misc/libvlc_la-cpu.lo misc/libvlc_la-configuration.lo
misc/libvlc_la-configuration_chain.lo misc/libvlc_la-image.lo
misc/libvlc_la-iso_lang.lo misc/libvlc_la-messages.lo misc/libvlc_la-objects.lo
misc/libvlc_la-variables.lo misc/libvlc_la-error.lo misc/libvlc_la-update.lo
misc/libvlc_la-vlm.lo misc/libvlc_la-xml.lo misc/libvlc_la-dict.lo
misc/libvlc_la-devices.lo extras/libvlc_la-libc.lo
g++ -shared -nostdlib
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crti.o
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/numa-note.o
.libs/libvlc_la-libvlc.o .libs/libvlc_la-libvlc-common.o
interface/.libs/libvlc_la-interface.o interface/.libs/libvlc_la-intf_eject.o
interface/.libs/libvlc_la-interaction.o playlist/.libs/libvlc_la-thread.o
playlist/.libs/libvlc_la-control.o playlist/.libs/libvlc_la-engine.o
playlist/.libs/libvlc_la-sort.o playlist/.libs/libvlc_la-loadsave.o
playlist/.libs/libvlc_la-tree.o playlist/.libs/libvlc_la-item.o
playlist/.libs/libvlc_la-search.o playlist/.libs/libvlc_la-services_discovery.o
input/.libs/libvlc_la-item.o input/.libs/libvlc_la-access.o
input/.libs/libvlc_la-clock.o input/.libs/libvlc_la-control.o
input/.libs/libvlc_la-decoder.o
input/.libs/libvlc_la-demux.o input/.libs/libvlc_la-es_out.o
input/.libs/libvlc_la-input.o input/.libs/libvlc_la-meta.o
input/.libs/libvlc_la-stream.o input/.libs/libvlc_la-mem_stream.o
input/.libs/libvlc_la-subtitles.o input/.libs/libvlc_la-var.o
video_output/.libs/libvlc_la-video_output.o
video_output/.libs/libvlc_la-vout_pictures.o
video_output/.libs/libvlc_la-video_text.o
video_output/.libs/libvlc_la-video_widgets.o
video_output/.libs/libvlc_la-vout_subpictures.o
video_output/.libs/libvlc_la-vout_synchro.o
video_output/.libs/libvlc_la-vout_intf.o audio_output/.libs/libvlc_la-common.o
audio_output/.libs/libvlc_la-dec.o audio_output/.libs/libvlc_la-filters.o
audio_output/.libs/libvlc_la-input.o audio_output/.libs/libvlc_la-mixer.o
audio_output/.libs/libvlc_la-output.o audio_output/.libs/libvlc_la-intf.o
stream_output/.libs/libvlc_la-stream_output.o
stream_output/.libs/libvlc_la-announce.o
stream_output/.libs/libvlc_la-profiles.o stream_output/.libs/libvlc_la-sap.o
osd/.libs/libvlc_la-osd.o osd/.libs/libvlc_la-osd_parser.o
osd/.libs/libvlc_la-osd_text.o osd/.libs/libvlc_la-osd_widgets.o
network/.libs/libvlc_la-acl.o network/.libs/libvlc_la-getaddrinfo.o
network/.libs/libvlc_la-io.o network/.libs/libvlc_la-error.o
network/.libs/libvlc_la-tcp.o network/.libs/libvlc_la-udp.o
network/.libs/libvlc_la-httpd.o network/.libs/libvlc_la-rootwrap.o
network/.libs/libvlc_la-tls.o misc/.libs/libvlc_la-charset.o
misc/.libs/libvlc_la-md5.o misc/.libs/libvlc_la-mtime.o
misc/.libs/libvlc_la-block.o misc/.libs/libvlc_la-modules.o
misc/.libs/libvlc_la-threads.o misc/.libs/libvlc_la-stats.o
misc/.libs/libvlc_la-strings.o misc/.libs/libvlc_la-unicode.o
misc/.libs/libvlc_la-cpu.o misc/.libs/libvlc_la-configuration.o
misc/.libs/libvlc_la-configuration_chain.o misc/.libs/libvlc_la-image.o
misc/.libs/libvlc_la-iso_lang.o misc/.libs/libvlc_la-messages.o
misc/.libs/libvlc_la-objects.o misc/.libs/libvlc_la-variables.o
misc/.libs/libvlc_la-error.o
misc/.libs/libvlc_la-update.o misc/.libs/libvlc_la-vlm.o
misc/.libs/libvlc_la-xml.o misc/.libs/libvlc_la-dict.o
misc/.libs/libvlc_la-devices.o extras/.libs/libvlc_la-libc.o
-L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib
-L/home/guest/0_out/lib -lrt -lpthread -ldl
-L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3
-L/usr/lib/gcc/i586-suse-linux/4.0.2
-L/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/lib
/usr/lib/libstdc++.so -lm -lc -lgcc_s
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtendS.o
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtn.o
-Wl,-soname -Wl,libvlc.so.0 -Wl,-retain-symbols-file -Wl,libvlc.sym -o
.libs/libvlc.so.0.0.0
/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
Relocations in generic ELF (EM: 40)
/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
Relocations in generic ELF (EM: 40)
/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
Relocations in generic ELF (EM: 40)
/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
Relocations in generic ELF (EM: 40)
/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/crtbeginS.o:
could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[4]: *** [libvlc.la] Error 1
make[4]: Leaving directory `/home/guest/0_videoLan/vlc-trunk/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/guest/0_videoLan/vlc-trunk/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/guest/0_videoLan/vlc-trunk/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/guest/0_videoLan/vlc-trunk'
make: *** [all] Error 2
[EMAIL PROTECTED]:~/0_videoLan/vlc-trunk>
---------------------------------
Want to start your own business? Learn how on Yahoo! Small Business.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20061126/9817fe47/attachment-0001.htm
------------------------------
Message: 3
Date: Mon, 27 Nov 2006 09:42:24 +0100
From: "Carlos Ojea" <[EMAIL PROTECTED]>
Subject: Re: SPI issue
To: "Kirill Sukhonosenko" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Few weeks ago I did a test transmitting only 100 bytes via SPI but I
didn't see the 'several secods' delay though.
How many bytes do you transmit before you can see the delay?
Regards,
Carlos
------------------------------
Message: 4
Date: Mon, 27 Nov 2006 02:51:11 -0600
From: "Anderberg, Niclas" <[EMAIL PROTECTED]>
Subject: RE: Query on the memcopy of the decoded video buffer
To: "Balasubramanya B" <[EMAIL PROTECTED]>,
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="US-ASCII"
Bala,
In the DVEVM 1.10 demos the video thread has been broken into a separate
video processing thread and a display thread to decouple the processing
from the display. This allows for buffering between the processing and
display, and allows a few frames (depending on your buffering / latency)
to exceed their budgets (33 ms for NTSC and 40 ms for PAL).
In the DVEVM 1.00 if a frame was too expensive you would drop a frame,
which to many is unacceptable. I agree the memcpy() is unfortunate, but
the LSP the demos had to work with had no VPSS resizer support or user
mode DMA support. Both of these are of course preferred in a production
system.
For more information on the design decisions of the decode demo see the
doc:
http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?ab
stractName=spraag9
Regards,
Niclas
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Balasubramanya B
Sent: Friday, November 24, 2006 3:28 PM
To: [email protected]
Subject: Query on the memcopy of the decoded video buffer
hi,
In the dvevm 1_10 demo decode(demo/decode) code, the entire
decoded output buffer is copied to the display buffer. Why is this
required? Is this not too much of an overhead in a practical player
decoder application?
In the corresponding dvevm 1_00 demo code, the decoder directly
writes the decoded frame to the display buffer and hence there is no
memory copy in the application.
Secondly, i found that the display is not proper when a non NTSC or PAL
resolution clip is decoded in dvevm 1_00 demo application. But it is
fine in dvevm 1_10 demo. Is the above memcopy is used to take care this
display problem? plz clarify,
thanks and regards,
bala
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 11, Issue 71
*********************************************************
____________________________________________________________________________________
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
