Hello,
I am trying to get the example davinci decode application to work on a custom
designed dm6446 board.
I have added TraceUtils{_start,_stop} calls in the application for dspside
debugging. But when the application starts i get the follow messages at the
TraceUtils_start() call.
DSP-side
Hello, I wrote:
This patch updates the busy field to reflect the current status of the
endpoint. This fix is critical to enable the request queuing logic to
prevent
a queued request from overwriting/interfering in-flight request.
Frankly speaking, I'm not seeing how a newly queued
Hello,
im using a custom designed board running dvsdk 1.30.24.
i have written an h264 decoder application using the h264decode algorithm.
when i run the application on the customized board the algorithm gets loaded
successfully. but when i call VIDDEC_process() it never returns. if i try to
From: David Brownell [EMAIL PROTECTED]
Update the DaVinci GPIO code to work better on non-dm6446 parts,
notably the dm355:
- Only handle the number of GPIOs the chip actually has. So
for example on dm6467, GPIO-42 is the last GPIO, and trying
to use GPIO-43 now fails cleanly; or GPIO-72
Following this are several patches that IMO make a useful
leap in functionality for the dm355 and its EVM:
- GPIO bugfixes. The other chips probably didn't care,
but for dm355 correctly written drivers could oops;
and they certainly wouldn't get the IRQs they needed.
- Support the
From: David Brownell [EMAIL PROTECTED]
Simple input driver support for the events reported by the
MSP430 firmware on the DM355 EVM. Verified using the remote
included with the kit; docs weren't quite right. Some of
the keycode selections might need improvement; I'm hoping
I implemented the
From: David Brownell [EMAIL PROTECTED]
Simple RTC driver for the MSP430 firmware on the DM355 EVM board.
Other than not supporting atomic reads/writes of all four bytes,
this is quite reasonable as a basic no-alarm RTC.
Signed-off-by: David Brownell [EMAIL PROTECTED]
---
Depends on the patch for
From: David Brownell [EMAIL PROTECTED]
Basic MFD framework for the MSP430 microcontroller firmware used
on the dm355evm board:
- Provides an interface for other drivers: register read/write
utilities, and register declarations.
- Directly exports:
* Many signals through the GPIO
From: David Brownell [EMAIL PROTECTED]
Board support for the dm355evm_msp MFD driver. This provides I2C
initialization for new-style drivers, as used by that MFD driver
and by mainline drivers for this board's audio and video codecs.
It also updates the I2C bus to use 400 kHz. The 20 kHz value
Hi Dave,
only one comment below.
On Sun, Dec 07, 2008 at 11:59:50AM -0800, David Brownell wrote:
+static int __devinit dm355evm_keys_probe(struct platform_device *pdev)
+{
+ struct dm355evm_keys*keys;
+ int status = -ENOMEM;
+ struct input_dev
On Sunday 07 December 2008, Felipe Balbi wrote:
+ platform_set_drvdata(pdev, keys);
+ keys-pdev = pdev;
you could be holding only the device pointer.
keys-dev = pdev-dev;
then, if you really happen to need the pdev pointer you can use
to_platform_device(keys-dev);
On Sun, Dec 07, 2008 at 12:28:38PM -0800, David Brownell wrote:
True, that would be a bit simpler; the device handle is what's
normally needed, e.g. for dev_dbg(). I'd take an update patch;
but for now I'll avoid a re-test cycle. :)
Sure, I'm in the testing your patches right now. Will send
On Sunday 07 December 2008, David Brownell wrote:
- Supports power-off system call. Use the reset button to power
the board back up; the power supply LED will be on, but the
MSP430 waits to re-activate the regulators.
And for the next person who hacks that msp430 firmware,
here's a
On Sun, Dec 07, 2008 at 12:00:08PM -0800, David Brownell wrote:
From: David Brownell [EMAIL PROTECTED]
Let the DM355 EVM use its dm9000 ethernet controller; just
declare it. Relies on the patch fixing GPIO IRQs.
hmm, could you mount nfs root with this patch ? I'm getting:
IP-Config: Unable
On Sunday 07 December 2008, Felipe Balbi wrote:
hmm, could you mount nfs root with this patch ?
Didn't configure one for this board yet ... being able
to talk on the network was an important precursor! :)
I'm getting:
IP-Config: Unable to set interface netmask (-22).
Looking up port
On Sunday 07 December 2008, David Brownell wrote:
- sound/soc/codecs/tlv320aic3x.c ... this is the audio
codec on the board, but sound/soc/davinci seems to not
have support for the dm355 ASP (just McBSP). Which of
course makes it hard to imagine board glue hooking up
the codec
Alan,
You are right w.r.t a gadget driver stalling an endpoint. Agreed that
a properly written drive may not stall an endpoint with inflight and queued
request's.
While working on DaVinci and other platforms that are utilizing the
Mentor controller and the Linux MUSB stack we
Sameer,
Please look here:
http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues
Regards,
Mugdha
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Naik
Sent: Sunday, December 07, 2008 9:55 PM
To:
Sameer,
This wouldn't be the same issue ... this is relevant only for DM6467. We have
never seen this with DM6446.
Regards,
Mugdha
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Naik
Sent: Sunday, December 07, 2008 10:06 PM
To:
19 matches
Mail list logo
