All DaVinci platforms include a DSP or co-processor for
audio/video acceleration.
While creating memory for the DSP/co-processor, system
integrator can end up creating a hole in the memory map
of the sort:
This sort of configuration needs ARCH_HAS_HOLES_MEMORYMODEL
enabled. See further detail
Hello.
Greg KH wrote:
1/5 or 1/4?
1/4. Sorry for failing to fix that. :-<
thanks,
WBR, Sergei
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-
When programming the DMA engine, the next pointers must be
programmed with physical address as seen from the DMA master
address space. This address may be different from physical
address of the buffer RAM area. This patch abstracts the
buffer address translation logic.
Signed-off-by: Sriramakrishn
On certain SOCs, the EMAC controller is interfaced with a wrapper logic
for handling interrupts. This patch implements a platform
specific hook to cater to platforms that require custom interrupt
handling logic
Signed-off-by: Sriramakrishnan
Acked-by: Chaithrika U S
Acked-by: David S. Miller
-
The Davinci EMAC peripheral is also available on other TI platforms -
notably TI AM3517 SoC. The following series of patches modify the driver
suitably to make it platform agnostic.
This patch has been generated against the tip of linux-davinci git.
Sriramakrishnan (3):
TI Davinci EMAC : Re-us
Signed-off-by: Andrey Porodko
---
arch/arm/mach-davinci/board-neuros-osd2.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-davinci/board-neuros-osd2.c
b/arch/arm/mach-davinci/board-neuros-osd2.c
index bd9ca07..0949fa9 100644
--- a/arch/arm/mach-davinci/b
Signed-off-by: Andrey Porodko
---
drivers/mfd/Kconfig |9 +-
drivers/mfd/Makefile|2 +-
drivers/mfd/davinci_msp.c | 505 +++
include/linux/i2c/dm355evm_msp.h|7 +-
include/linux/i2c/neuros_osd2_msp.h | 45
The davinci EMAC peripheral is also available on other TI
platforms -notably TI AM3517 SoC. This patch modifies the
config option and the platform structure header files so that
the driver can be reused on non-davinci platforms as well.
Signed-off-by: Sriramakrishnan
Acked-by: Chaithrika U S
Ack
Hi, all,
I want to know the structure of the YUV raw data for the function
encodeVideoBuffer in the TI demos, such as:
/* the folloing codes is from \dvevm_1_20\demos\encodedecode\video.c(Line
571~577)*/
*/* Encode the buffer using H.264 */
DBG("Begin Encode the buffer using H.26
Hans,
My mistake. I had a confusion on if you had signed-off this patch
or the application diff that you had sent.
Could you add this to your tree and send a pull request to Mauro?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-
From: Muralidharan Karicheri
Forgot the V4L prefix in subject. Resending it...
This patch add a helper function to get description of a digital
video preset added by the video timing API. Hope this will be
usefull for drivers implementing the above API.
Signed-off-by: Muralidharan Karicheri
NO
From: Muralidharan Karicheri
This patch add a helper function to get description of a digital
video preset added by the video timing API. Hope this will be
usefull for drivers implementing the above API.
Signed-off-by: Muralidharan Karicheri
NOTE: depends on the patch that adds video timing API
Thanks Graham,
That was my plan anyway.
What I found is that some old version (from 2005) of the TI MMC/SD User Guide
listed 50 Mhz as the max value, while a more recent version (sprue30D, from May
2008) lists 25 Mhz.
This made me suspect that some limitation ha s been found on this, and I'd
Hi Dmitry,
+ if (pdata->device_enable) {
+ error = pdata->device_enable(dev);
+ if (error < 0) {
+ dev_dbg(dev, "device enable function failed\n");
+ return error;
+ }
+ }
+
Hi Miguel,
Does this need
e?
Does someone know where I can find in Davinci GIT or anywhere else a
good configuration of digital output for the davinci?
Best regards.
Stephane.
__ Information from ESET NOD32 Antivirus, version of virus
signature database 4622 (20091119) __
The message was check
Dmitry Torokhov wrote:
On Thu, Nov 19, 2009 at 10:32:21AM -0600, Miguel Aguilar wrote:
Hi Dmitry,
+ if (pdata->device_enable) {
+ error = pdata->device_enable(dev);
+ if (error < 0) {
+ dev_dbg(dev, "device enable function failed\n");
+
Dmitry Torokhov wrote:
On Thu, Nov 19, 2009 at 11:54:35AM -0600, Miguel Aguilar wrote:
Dmitry Torokhov wrote:
On Thu, Nov 19, 2009 at 10:32:21AM -0600, Miguel Aguilar wrote:
Hi Dmitry,
+ if (pdata->device_enable) {
+ error = pdata->device_enable(dev);
+ if (
[...]
> > How do you ensure that only one of these drivers is loaded at a time?
> > Or is the set of supported devices is board-specific (in which case the
> > board code should have an idea how to properly set the configuration for
> > the devices that are supported on that board)?
> The DM365 EV
yes, I also found this directory:
/montavista5/pro/devkit/arm/v5t_le/target/usr/include/freetype2
so I suppose MV5 support freetype also.
But I download the latest version from
http://ftp.twaren.net/Unix/NonGNU/freetype/
It can work.
My step is:
1, download the latest version
2, tar -jxvf freet
19 matches
Mail list logo
