On Friday 20 March 2009, Constantine Shulyupin wrote:
> I just finishing improved DM355 boot from SD.
> It can help you.
Yes, I was thinking that might be a component of an
upgrade path without Windows/DOS dependencies. Or
even just a testing aid.
_
I just finishing improved DM355 boot from SD.
It can help you.
On Thu, Mar 19, 2009 at 10:57 PM, David Brownell wrote:
> I've barely glanced at this so far ... but one question is
> how to test this with an existing DM355. (Some of the code
> can be reviewed without testing, of course.)
>
> My u
On Friday 20 March 2009, Narnakaje, Snehaprabha wrote:
> Dave,
>
> Does it bring up the need to support legacy layout
> in the git, for existing devices?
>
> What is your opinion on supporting the legacy layout
> on git, for existing dm355 devices?
I think the deciding factor is that GIT has n
On Friday 20 March 2009, Kevin Hilman wrote:
> I'm not sure if legacy support is as important as a clean transition.
For me, the issue is basically how to switch ... the key
feature of the existing flash is that it can fetch me a
kernel using ethernet. :)
__
On Thursday 19 March 2009, Narnakaje, Snehaprabha wrote:
> > My understanding is that if I run a kernel with these patches,
> > they'll want a "new style" badblock table, incompatible with
> > the one understood by current u-boot. So switching to this
> > code would be a one-way migration (except
David Brownell writes:
> From: David Brownell
>
> Minor tweak to the new DaVinci clock code: look at the PSC module
> to make sure the clock is enabled before reporting that it needs
> disabling. This improves the value of those diagnostics.
>
> Docs report a variety of power-up states for per
What about writing a linux utility that reads and saves the current
flash contents to disk/MMC/etc., and then reformats, writes the new
bootloader and then optionally restores the other partitions.
I'm not sure if legacy support is as important as a clean transition.
Kevin
"Narnakaje, Snehaprab
Dave,
Does it bring up the need to support legacy layout in the git, for existing
devices?
What is your opinion on supporting the legacy layout on git, for existing dm355
devices?
Basically some of davinci-nand 4-bit APIs need to be rewritten to support the
legacy layout. Then the question is
Sergei Shtylyov writes:
> DM646x has MUSB connected to IRQs 13 and 14 (unlike IRQ12 on other platforms),
> so pass the correct IRQ resources with the platform device.
>
> Signed-off-by: Dmitry Krivoschekov
> Signed-off-by: Sergei Shtylyov
>
> ---
> The patch is against the recent DaVinci tree..
As DaVinci DM646x has a dedicated CPPI DMA interrupt, replace cppi_completion()
(which has always been kind of layering violation) by a complete CPPI interrupt
handler.
Signed-off-by: Dmitry Krivoschekov
Signed-off-by: Sergei Shtylyov
---
The patch is against the recent DaVinci tree; untested..
DM646x has MUSB connected to IRQs 13 and 14 (unlike IRQ12 on other platforms),
so pass the correct IRQ resources with the platform device.
Signed-off-by: Dmitry Krivoschekov
Signed-off-by: Sergei Shtylyov
---
The patch is against the recent DaVinci tree...
arch/arm/mach-davinci/usb.c | 16 +
David Brownell wrote:
If this is only for the MUSB driver, it might be better to
stash this code in driver/usb/musb and generalize the
current CPPI glue there.
Generalize what? There's no way CPPI 3.0 and 4.1 can be "generalized",
they're too unlike.
If they're "too unlike" then they can't
David Brownell wrote:
If this is only for the MUSB driver, it might be better to
stash this code in driver/usb/musb and generalize the
current CPPI glue there.
Generalize what? There's no way CPPI 3.0 and 4.1 can be "generalized",
they're too unlike.
If they're "too unlike" then they can't
On Friday 20 March 2009, Sergei Shtylyov wrote:
> > If this is only for the MUSB driver, it might be better to
> > stash this code in driver/usb/musb and generalize the
> > current CPPI glue there.
>
> Generalize what? There's no way CPPI 3.0 and 4.1 can be "generalized",
> they're too unlike.
I
I'm using H.264 encode on DM357.
I don't know about two members of structure VIDENC_DynamicParams:
targetFrameRate and refFrameRate.
In the User Guide, it says, "targetFrameRate <= maxFrameRate.
refFrameRate <= maxFrameRate". My question is that if
targetFrameRate must equal to refFrameRate.
In m
Chaithrika U S writes:
> Remove the usage of cpu_is_xxx() macros from the EMAC driver.
>
> Add a member to the platform data to indicate the version of the EMAC.
> Use this information instead of the cpu_is_xxx() macros.
>
> This patch is dependent on the previous sets of patches submitted for EM
Chaithrika U S writes:
> EMAC driver changes to manipulate RMII spped mask , correct the interrupt mask
> for DM644x
>
> Signed-off-by: Chaithrika U S
>
> This patch set has two patches:
>
> Patch 1: RMII speed mask manipulation
> Patch 2: Fix interrupt mask - mask value to check only used chann
chaithr...@ti.com writes:
> EMAC driver, platform data, resource structure changes
>
> Signed-off-by: Chaithrika U S
>
> The patch set modifies the EMAC platform data to add more SoC specific and
> board specific information. The EMAC resource structure has been moved from
> devices.c to the resp
Chaithrika U S writes:
> Add pin mux definitions, display device setup, clock setup functions
>
> Add pin mux related code for the display device, also add platform device
> and resource structures. Also define a platform specific clock setup function
> that can be accessed by the driver to confi
Hi all,
According to the TI MPEG4 encoder specs this codec supports two types of
encoding : MPEG4 or H.263 and the encoding choice is performed by specifying
a different value of an extended configuration parameter.
We are having troubles using the MPEG4 encoder with the H.263 configuration
Stijn Devriendt wrote:
I'm trying to read out the DDR2 control registers
to obtain information about the DDR2 configuration.
I currently did something like
base = ioremap(0x200, PAGE_SIZE);
result = davinci_readl(0x2008);
Don't use davinci_readl() for for the regstees that we
On Fri, 2009-03-20 at 13:54 +0100, Stijn Devriendt wrote:
> I'm trying to read out the DDR2 control registers
> to obtain information about the DDR2 configuration.
>
> I currently did something like
> base = ioremap(0x200, PAGE_SIZE);
> result = davinci_readl(0x2008);
> iounmap(base)
Remove the usage of cpu_is_xxx() macros from the EMAC driver.
Add a member to the platform data to indicate the version of the EMAC.
Use this information instead of the cpu_is_xxx() macros.
This patch is dependent on the previous sets of patches submitted for EMAC.
The changes have been tested on
This patch is useful for OMAP-L137 based boards which may have RMII enabled.
EMAC on OMAP-L137 supports RMII and on enabling this the RMIISPEED MASK has to
be set/cleared for 100/10 Mbps operation respectively. A member has been added
to the EMAC platform data to indicate the type of interface.
S
EMAC driver changes to manipulate RMII spped mask , correct the interrupt mask
for DM644x
Signed-off-by: Chaithrika U S
This patch set has two patches:
Patch 1: RMII speed mask manipulation
Patch 2: Fix interrupt mask - mask value to check only used channel
These patches are dependent on the E
Set the trasnmit and receive interrupt masks for the used channels only.
Currently, the EMAC uses only channel 0. Set the interrupt masks accordingly.
Signed-off-by: Chaithrika U S
---
drivers/net/davinci_emac.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drive
I'm trying to read out the DDR2 control registers
to obtain information about the DDR2 configuration.
I currently did something like
base = ioremap(0x200, PAGE_SIZE);
result = davinci_readl(0x2008);
iounmap(base);
but this results on kernel Oopses.
I also tried to read base+8 which
Start from
http://wiki.davincidsp.com/index.php?title=Burn_any_image_to_NOR_flash
2009/3/20 Ondrej Pindroch :
> Can anybody write me, how to flash new uImage to NOR flash on DVEVM 6446
> I have found some indications how to do it. But it results only tu bad magic
> number. I have used adress 0x20
Can anybody write me, how to flash new uImage to NOR flash on DVEVM 6446
I have found some indications how to do it. But it results only tu bad magic
number. I have used adress 0x205 on flash.
Thanks
Ondrej Pindroch
SoftHard Technology ltd.
___
Davi
Hello.
David Brownell wrote:
Add support for Texas Instuments Communication Port Programming Interface 4.1
(CPPI 4.1) used on OMAP-L137/DA830.
At this moment, only the DMA controller and queue manager are supported.
Support for the buffer manager is lacking but this chip doesn't have it anyw
Hi folks
I am new to linux programing, kernel building and so on. I have installed
MV4.0.1 from DVSDK. I saw lots of patches on this forum.
My question is how to use this all patches, or it is possible to download
patched kernnel with drivers?
Thank you for your answer.
Ondrej Pindroch
Hi,
Can we configure McBSP on DM355 to support PCM interface?
4 line interface:
PCMCLK
PCMSYNC
PCMI
PCMO
The PCM interface transmits and receives data at the PCMO and PCMI terminals
respectively. The data is
transmitted or received at the PCMCLK speed once every PCMSYN cycle.
If we can
Hi All,
Can we configure McBSP on DM355 to support PCM interface?
4 line interface:
PCMCLK
PCMSYNC
PCMI
PCMO
The PCM interface transmits and receives data at the PCMO and PCMI terminals
respectively. The data is
transmitted or received at the PCMCLK speed once every PCMSYN cycle.
If we ca
Dave,
There are other peripherals such as EMAC (on other platforms not in the
community tree) that use this version of CPPI. I am not aware whether TI would
want to support those platforms through a community tree.
In the context of OMAP-L137/DA830 type of devices USB is the onl
On Wednesday 18 March 2009, Sergei Shtylyov wrote:
> Add support for Texas Instuments Communication Port Programming Interface 4.1
> (CPPI 4.1) used on OMAP-L137/DA830.
>
> At this moment, only the DMA controller and queue manager are supported.
> Support for the buffer manager is lacking but this
Hi All,
I need to configure McBSP for PCM interface.
Is it possible to configure McBSP for PCM interface?
If it is possible then please let me know how to configure McBSP?
-Azam
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@lin
36 matches
Mail list logo
