When VIDDEC_process() hangs, do you have tracing enabled? If so, does
it also hang when there is no tracing enabled? I'm grasping at straws,
but we've seen several occasions where the servers were built with stack
sizes so close to the edge that even turning on trace will cause them to
overrun
Bernard,
I agree with you, but this should be done in u-boot (or other bootloader),
not in linux, because u-boot makes I2C accesses before the kernel. If I
remember, u-boot can implement this I2C-fix.
Olivier DAVID
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De
I have I problem writing to the spi controller of daVinci .I have four
bytes I want to send on the bus using 8-bits words, but I only get the
first out of the dm6446. Here is the routine I'm using in a kernel
module. I think I'm missing some kind of synchronization but I don't
understand
Hi Pierre,
2008/4/17 Pierre - Emmanuel GAILLARDON [EMAIL PROTECTED]:
Hello,
I tried to use the PWM1 TI driver to access the PWM1 of the DaVinci6446 with
the TI kernel but it doesn't work properly.
Here is some lines of the code where I configure the PWM driver via the
ioctrl function :
Hi Bernard,
On Fri, Apr 18, 2008 at 8:04 AM, Bernard Blackham
[EMAIL PROTECTED] wrote:
I2C device has some board-specific parameters such as bus frequency
and per-transaction setup delay. The DM6446 DVEVM, for example,
requires a much lower bus frequency of 20kHz and a setup delay of
100us
Quoting [EMAIL PROTECTED]:
I have I problem writing to the spi controller of daVinci .I have four
bytes I want to send on the bus using 8-bits words, but I only get the
first out of the dm6446. Here is the routine I'm using in a kernel
module. I think I'm missing some kind of synchronization
Trilok Soni wrote:
I think above change can be done in better way, as we can't move
resource structure to board specific file, as it going to common for
all boards. We should better API similar to we have done OMAP. Please
check arch/arm/plat-omap/i2c.c and omap_register_i2c_bus, which
fulfills
Hi Guys,
Does anyone know if there is a native Linux (or just vanilla C) version
of DVFlasher in existence?
If so, please let me know!
Andrew
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
Andrew Armstrong wrote:
Hi Guys,
Does anyone know if there is a native Linux (or just vanilla C) version
of DVFlasher in existence?
I guess not.
You may like to have a look to
http://wiki.davincidsp.com/index.php?title=RBL_UBL_and_host_program
for possible Linux based alternatives.
Dirk
Dear all,
I am a newby of Davinci technology and of TMS320DM355 DVEVM. I followed the
Getting Started Guide when I tried to test the shared file system between my
laptop runing Ubuntu Linux and the board. However, after I saved the three
setenv as in the guide and boot, the board runs until
You need to set up IPv4 dhcpd on your server. The board won't boot off of IPv6.
C
On Fri, Apr 18, 2008 at 7:34 AM, YangZhijun [EMAIL PROTECTED] wrote:
Dear all,
I am a newby of Davinci technology and of TMS320DM355 DVEVM. I followed the
Getting Started Guide when I tried to test the
Hi,
First you need to get the board back booting the kernel. As u-boot is trying to
tell you - there is no such command as 0x205 which is what you told it to
use.
Break into the u-boot sequence restore the original value of bootcmd...
setenv bootcmd nboot 0x8070 0 0x40; bootm
I don't know about mii-tool, but if you check the source to ifconfig,
you might find out how ifconfig determines whether the interface is
up.
2008/4/18 António Silva [EMAIL PROTECTED]:
Hi all,
How can I check the ETH link status on the EVMDM355??
If we unplug the cable we see a message
Hi all,
I'm running the demo applications for the DM355, but the encode and
encodedecode demos die when I have a black and white imager connected.
The interface gets drawn on my display, but then the capture thread dies
on the VIDIOC_QUERYSTD ioctl done on /dev/video0.
(e.g. VIDIOC_QUERYSTD
olivier.david wrote:
Bernard,
I agree with you, but this should be done in u-boot (or other bootloader),
not in linux, because u-boot makes I2C accesses before the kernel. If I
remember, u-boot can implement this I2C-fix.
Olivier DAVID
For the dvevm, this might be true. But our device
Troy Kisky wrote:
olivier.david wrote:
I agree with you, but this should be done in u-boot (or other bootloader),
not in linux, because u-boot makes I2C accesses before the kernel. If I
remember, u-boot can implement this I2C-fix.
For the dvevm, this might be true. But our device has no
Bernard Blackham wrote:
Troy Kisky wrote:
olivier.david wrote:
I agree with you, but this should be done in u-boot (or other bootloader),
not in linux, because u-boot makes I2C accesses before the kernel. If I
remember, u-boot can implement this I2C-fix.
For the dvevm, this might be true.
Troy Kisky wrote:
Bernard Blackham wrote:
Troy Kisky wrote:
olivier.david wrote:
I agree with you, but this should be done in u-boot (or other bootloader),
not in linux, because u-boot makes I2C accesses before the kernel. If I
remember, u-boot can implement this I2C-fix.
For the dvevm,
18 matches
Mail list logo
