All,
I am trying to profile a component on ARM side of DM6446. VISA_Create
allocates memory for this component from CMEM area which is not cached
on ARM side. Because of this there is huge increase in the time taken
for processing.
Is there a way to cache this CMEM on ARM side as well? Or to
Hello,
I try to use the dhcpd-daemon provided by the montavista pro-tools
for windows. I edited the dhcpd.conf:
# dhcpd.conf
#
#deny unknown-clients;
ddns-update-style none;
allow bootp;
subnet 192.168.0.0 netmask 255.255.255.0 {
default-lease-time 1209600;# two weeks
Am Wed, 23 Jan 2008 12:26:07 +0100 schrieb Robert W. Kuhn:
Whe I try to start the service (via dhcpd start) I get in /var/log/dhcpd.log
the following error:
Can't open /opt/montavista/pro/bin//../var/tmp/dhcpd.leases for append.
What could be the problem and what could I do?
Okay, I
We do something BEFORE your code:
//- Clear reserved register 0x01C41A20 to prevent hangup on PTSTAT
testing.
//(Errata SPRUZ241D Advisory 1.3.22)
PSC-MDCTL[16] = 0;
//- Put the C64x+ Core into reset (if it's on)
PSC-MDCTL[39] = (~0x0100); // ask reset
BJ,
The link down message is normal, coming from the DM9000A Ethernet
driver, before actually trying out the link negotiation. You should then
see a link up message once the negotiation is complete.
eth0: link down
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 255.255.255.255, my
Hi David,
Thanks for the advice.
I already set PINMUX0.RGB666 register in video driver (it was one of the first
things that I did actually), but there are way to many other stuff that needs
to be set.
Right now, I'm trying to reduce the clock to 6,75MHz. If anyone had the similar
experience,
Stephen,
The package was built for the latest Montavista kernel on the DM6446
DVEVM. Some additional work may be needed to port this to the latest
community open source Linux kernel for DaVinci. Which OS version are you
using?
Thanks for pointing out the difference in the filename - I'll
Hi,
The problem is that cross-compiling with autotools avoids to run
certain test because it cannot detect the environment settings for the
target platform.
Many embedded distributions avoid such problems by running the
compilation inside a emulated ARM machine (which can be slow).
To
Can you help us understand your usage a little better (and which version
of CE you're using)?
VISA_create() is an SPI - System Programming Interface - used by
algorithm providers that are integrating non-xDM algorithms into the
Codec Engine environment. Is that what you're trying to do?
And
Hi all,
how do you modify the davincifb driver to allow sending RGB565 data to
the driver, thereby bypassing the YCbCr to RGB color space conversion by
the VPBE?
I am using the DM6446 DVEVM, with a digital LCD connected, and using the
decode_hd demos.
Demo works fine in the standard mode where
Chris,
Thanks a lot!
I am using CE 2.0, XDC_3_00_2, bios_5_31_08 for a non-VISA component. I
have written stubs/skeletons for this component based on example one
available for video component. Yes, I am trying to run the component
from ARM side as local.
As compared to the case when the
Davinci supports 4 hardawre planes, out of which 2 are OSD( supoprt
RGB565 graphics) and the other two support YCbCr data. If you want to
write RGB data to the driver you can use either OSD0 or OSD1 instead of
the Video planes. This could be done by using /fb0 and /fb2 instead of
/fb1 or /fb3.
There is a config param in the new ti.sdo.ce.alg.Settings module, very
poorly documented in CE 2.00, but we'll have better docs in future
releases. The config param you care about is .useCache, by default it's
false, but you can set it to true in your app's .cfg script. Something
like:
Chris,
Thanks again. It does work. :)
Is it possible to associate this setting at algorithm level only? That
is algo A has cache enabled and B does not and both run in the same
process.
How do you associate this setting with any particular process? Please
elaborate.
I had some more queries in
14 matches
Mail list logo
