The latest kernel seems to be broken for DM646x EVM.
It does not boot on the DM646x EVM but runs on DM644x EVM. It has not been
tested on DM355.
The kernel image was built using both the generic and DM646x specific defconfig
files.
Compiling with low level kernel debug messages did not help eith
On Sun, 14 Dec 2008 19:54:04 -0800, David Brownell
wrote:
> On Sunday 14 December 2008, R. Simning wrote:
>> in chapter 11, section 11.1.1 (page 150), i have found that nand
>> devices supported allows a maximum page size of 2048 bytes.
>
> Supported by the ROM boot loader. I don't think there
On Sunday 14 December 2008, shaofeng zhang wrote:
> I want to know how the OS can detect the MMC/SD when the system
> is working.
The MMC/SD driver uses the board-specific callback
provided in the dm6446evm_mmc_config platform data.
That's in the current GIT tree.
> The second question is: ...
Logically, I doubt there's any register linkage between the two distinct
functions you're talking about - have you checked to see if your board
design has a mistake on it? Perhaps some coupling? Board defects?
Schematic errors?
Also, ensure that when you're setting that register, you're not set
Hello, Everyone,
Now I have two qustions about DM6446 EVM.
the First is:I want to know how the OS can detect the MMC/SD when the system
is working.
We know that the MMC/SD Card Detect pin is connected to the MSP430
P2.1/INCLK pin. So I want to know the reasons about it.
Because on our board we dir
On Mon, 15 Dec 2008 16:23:22 +0530, "Subrahmanya, Chaithrika"
wrote:
> The latest kernel seems to be broken for DM646x EVM.
> It does not boot on the DM646x EVM but runs on DM644x EVM. It has not
been
> tested on DM355.
> The kernel image was built using both the generic and DM646x specific
> de
Hi Sudhakar,
On Mon, 15 Dec 2008 12:15:21 +0530, "Rajashekhara, Sudhakar"
wrote:
> I am not seeing the above errors. I am using the checkpatch.pl script
> which comes along with the kernel in scripts folder.
enable --strict ;-)
--
Best Regards,
Felipe Balbi
http://blog.felipebalbi.com
m...@fe
Hello,
I faced the same problem, check how your ubuntu box is installed
# unaeme -a
Linux darkstar 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008
x86_64 GNU/Linux
If your linux is compiled in 64 bits, trying to run 32 bits binaries can
result in "No such file or directory" message.
If you
"Rajashekhara, Sudhakar" writes:
> Dave,
>
>> I'll disagree with a few of Felipe's points here, and offer
>> a few other comments.
>>
>>
>> On Wednesday 10 December 2008, Felipe Balbi wrote:
>> > On Wed, Dec 10, 2008 at 03:35:28PM +0530, Sudhakar Rajashekhara wrote:
>> > > Generalizes dm644x pi
"Subrahmanya, Chaithrika" writes:
> The latest kernel seems to be broken for DM646x EVM.
> It does not boot on the DM646x EVM but runs on DM644x EVM. It has not been
> tested on DM355.
> The kernel image was built using both the generic and DM646x specific
> defconfig files.
>
> Compiling with
From: Felipe Balbi
Fix most of checkpatch.pl ERRORS with davinci_mmc.c. Also
fix up a few comments in the beggining of the file.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 36 ++--
1 files changed, 14 insertions(+), 22 deletions(-)
diff
From: Felipe Balbi
updates to davinci mmc driver. Mostly cleanups. The only
important change is the reimplementation of read/write fifo
in C, removing the old one written in assembly.
everything seems to be working as it was before these patches,
tested with use_dma = 0.
<6>mmc1: new SDHC card
From: Felipe Balbi
There were a bunch of useless function prototypes in
davinci_mmc.h. Remove them and reorganize the file
so we don't really need those.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 394
drivers/mmc/host/davinci_mmc
From: Felipe Balbi
Add missing __init and __exit where appropriate.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/mmc/host/davinci_mmc.c b/drivers/mmc/host/davinci_mmc.c
index 87e3b7e..5
From: Felipe Balbi
Make rw_threshold and use_dma a module parameter,
thus getting rid of struct mmcsd_config_def.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 50 ---
drivers/mmc/host/davinci_mmc.h |5
2 files changed, 26 inser
From: Felipe Balbi
Mostly tab fixes, but also removing some extra lines and
putting module_init() close to its argument function.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 46 ++-
1 files changed, 21 insertions(+), 25 deletions(-)
d
From: Felipe Balbi
That define was only used for polling for card presence,
which now we let mmc core do it in a more reliable way.
No need to keep that define here.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
From: Felipe Balbi
It's easier to follow and to maintain.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 122 +---
1 files changed, 64 insertions(+), 58 deletions(-)
diff --git a/drivers/mmc/host/davinci_mmc.c b/drivers/mmc/host/davinci_m
From: Felipe Balbi
There's no need for a file included only once, remove it
and move the register definition to davinci_mmc.c.
Signed-off-by: Felipe Balbi
---
drivers/mmc/host/davinci_mmc.c | 169 -
drivers/mmc/host/davinci_mmc.h | 209
David Brownell writes:
> From: David Brownell
>
> CC drivers/net/davinci_emac.o
> drivers/net/davinci_emac.c: In function 'emac_adjust_link':
> drivers/net/davinci_emac.c:2323: error: incompatible type for argument 1 of
> '_spin_lock_irqsave'
> make[2]: *** [drivers/net/davinci_emac.o] E
David Brownell writes:
> From: David Brownell
>
> Do spinlock initialization during davinci_emac::probe(), when
> the lock is allocated, not each time it's opened. That's the
> correct place to do such work.
>
> More significantly, fix a bug: one of the three spinlocks was
> never getting initi
David Brownell writes:
> From: David Brownell
>
> Fix about half the warnings from "make C=1" (sparse), and start on
> the __iomem issues associated with the CPPI buffer descriptor data.
> All of the remaining warnings come from address space issues. For
> this driver, fixing all those issues w
On Monday 15 December 2008, Felipe Balbi wrote:
> > #define NAND_MAX_OOBSIZE 64
> > #define NAND_MAX_PAGESIZE 2048
> >
> > So you'd need to change that to use a bigger page size.
>
> That should probably come via the platform_data and passed
> down to struct nand_chip. Imagine a case
On Mon, Dec 15, 2008 at 10:51:37AM -0800, David Brownell wrote:
> The actual page size of the chip comes from probing
> the chip. Those constants just affect how the NAND
> framework allocates things.
yeah, saw that. nand_scan() does that right ? But then again, what would
have to be changed in o
On Monday 15 December 2008, Felipe Balbi wrote:
> From: Felipe Balbi
>
> It's easier to follow and to maintain.
>
> ...
> +static void davinci_mmc_read_fifo(struct mmc_davinci_host *host,
> + u16 len, u8 *dest)
> +{
> + void __iomem *fifo = host->base + DAVINCI_MMCDRR;
> + u1
On Monday 15 December 2008, Felipe Balbi wrote:
> @@ -1240,12 +1241,12 @@ static struct platform_driver davinci_mmcsd_driver = {
> .owner = THIS_MODULE,
> },
> .probe = davinci_mmcsd_probe,
> - .remove = davinci_mmcsd_remove,
> + .remove
Medisetty, Naresh wrote:
> Troy,
>
>
>> -Original Message-
>> From: davinci-linux-open-source-boun...@linux.davincidsp.com
>> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf
>> Of Troy Kisky
>> Sent: Saturday, December 13, 2008 8:39 AM
>> To: davinci-linux-open-s
On Mon, Dec 15, 2008 at 11:13:40AM -0800, David Brownell wrote:
> On Monday 15 December 2008, Felipe Balbi wrote:
> > From: Felipe Balbi
> >
> > It's easier to follow and to maintain.
> >
> > ...
> > +static void davinci_mmc_read_fifo(struct mmc_davinci_host *host,
> > + u16 len, u8 *d
On Monday 15 December 2008, Felipe Balbi wrote:
> Make rw_threshold and use_dma a module parameter,
> thus getting rid of struct mmcsd_config_def.
DMA threshold should default to whichever one gives
the highest throughput on the EVM ... and let the
platform_data override it, if e.g. it needs help
On Mon, Dec 15, 2008 at 11:22:23AM -0800, David Brownell wrote:
> On Monday 15 December 2008, Felipe Balbi wrote:
> > Make rw_threshold and use_dma a module parameter,
> > thus getting rid of struct mmcsd_config_def.
>
> DMA threshold should default to whichever one gives
> the highest throughput
On Mon, Dec 15, 2008 at 09:19:05PM +0200, Felipe Balbi wrote:
> cool, will fix :-)
>
> good catch with the missing branch, thanks
here you are
cut here
>From 43fbab69f7d19e39c7c270c4aa1652b0efea0a8f Mon Sep 17 00:00:00 2001
From: Felipe Balbi
Date: Mon
On Monday 15 December 2008, Felipe Balbi wrote:
> Sure, but this patch is only getting rid of that structure. Later
> patches could come to update this part, right ?
certainly.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.
On Mon, Dec 15, 2008 at 11:15:54AM -0800, David Brownell wrote:
> Should be platform_driver_probe() since you made davinci_mmcsd_probe()
> live in the __init section.
here you are:
cut here
>From 5f6cdc58a34e0f1a7c6eded1aff8e744cae22688 Mon Sep 17 00:00:
Felipe Balbi wrote:
> From: Felipe Balbi
>
> It's easier to follow and to maintain.
>
> Signed-off-by: Felipe Balbi
> ---
> drivers/mmc/host/davinci_mmc.c | 122
> +---
> 1 files changed, 64 insertions(+), 58 deletions(-)
>
>
You need to post performance
You will definitely need to change the NAND_MAX_OOBSIZE to 128 for 4K pages.
You may also need to change the FFCHARS definition to 4096 to be safe.
Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: chase.mau...@ti.com
phone: (281) 274-3285
> -Original Message-
>
On Mon, Dec 15, 2008 at 02:19:24PM -0600, Maupin, Chase wrote:
> You will definitely need to change the NAND_MAX_OOBSIZE to 128 for 4K pages.
> You may also need to change the FFCHARS definition to 4096 to be safe.
sure, that's an easy guess. But is that really enough in the end ? I
hope so :-)
Hi,
I am getting an error of undefined reference to 'IMGENC1_create' I have added
the appropriate header file #include to the code,
I suspect that something in the cfg file may be not correct to make it not link
to the proper libraries?
This is my cfg file I am using! Thank in advance
Hi Troy,
On Mon, Dec 15, 2008 at 01:15:02PM -0700, Troy Kisky wrote:
> You need to post performance tests pre and post patch to
> let us know how much this degrades performance. Remember
> to turn off dma before the test. I personally don't
> like this patch. But I'm biased, as I added the assembl
Felipe Balbi wrote:
> Hi Troy,
>
> On Mon, Dec 15, 2008 at 01:15:02PM -0700, Troy Kisky wrote:
>> You need to post performance tests pre and post patch to
>> let us know how much this degrades performance. Remember
>> to turn off dma before the test. I personally don't
>> like this patch. But I'm
On Mon, Dec 15, 2008 at 03:21:58PM -0700, Troy Kisky wrote:
> Yeah, I expected a much greater difference. 10ns for every
> 32 bytes is trivial.
That's what I thought... I think it would be better now to get dma up
and running. At least on dm355 doesn't work at all. Not even card
detection :-s
Wil
On Monday 15 December 2008, Felipe Balbi wrote:
> At least on dm355 doesn't work at all. Not even card
> detection :-s
I think the controller would probably like to be reset
at various key points. :)
___
Davinci-linux-open-source mailing list
Davinci
As they say, "A clean driver is a happy driver!"
- use io{read,write}{8,16,32}_rep() for faster i/o
- update/bugfix partition config handling
- update/bugfix ecc (1-bit) config handling
- separate dm355evm and dm6446evm specifics
- partial ALE/CLE parameterization
This doesn't yet creat
From: David Brownell
Update/bugfix hardware ECC config handling. The driver should still
be able to build without that support enabled (else remove its Kconfig
option!); remove frowned-upon inline #ifdeffery.
Also suffix all the original ECC logic with _1bit to distinguish it
from the DM355's e
From: David Brownell
Speed up transfers between NAND and RAM by using the io{read,write}*_rep()
calls to replace a more limited read-only I/O loop. On a similar arm926
board this gave a significant speedup (ISTR 16%) in a userspace "dd"
benchmark.
Also add a comment explaining some key assumpti
From: David Brownell
Start splitting out the board-specific NAND support better,
by having board-specific flash init functions. DM355 EVM
has a newer and faster chip.
It's still in the wrong place, but at least it's better
factored now ... which will help later when it's moved to
the board-*.c
From: David Brownell
Partially parameterize the ALE and CLE masks; there's a bunch of
other stuff that should come from platform_data too, but this
patch doesn't change that stuff.
While we're doing this ... fix the related "sparse" errors.
Signed-off-by: David Brownell
---
drivers/mtd/nand/d
From: David Brownell
Update/bugfix partition config handling. This removes some inlines in
the body of the driver, bugfixes cmdlinepart handling, bugfixes the
"no partitions" cases, and cleans up properly on driver removal.
Yes, these bugs are common in MTD drivers; I think the MTD framework
sh
All,
I'm currently working on adding a driver for an RTC into our kernel.
The chip I'm working with is the Dallas Semiconductor DS1340 and I've
seen drivers for the ds1337 and ds1338 so they're of the same flavor.
I'm not worried about the actual implementation of the driver, but I
want to ma
On Monday 15 December 2008, BJ Opp wrote:
> All,
>
> I'm currently working on adding a driver for an RTC into our kernel.
> The chip I'm working with is the Dallas Semiconductor DS1340 and I've
> seen drivers for the ds1337 and ds1338 so they're of the same flavor.
And drivers/rtc/rtc-ds1307.c
Hi Dave, thanks for the reply. Some more questions/comments inline.
David Brownell wrote:
On Monday 15 December 2008, BJ Opp wrote:
All,
I'm currently working on adding a driver for an RTC into our kernel.
The chip I'm working with is the Dallas Semiconductor DS1340 and I've
seen drivers for
Either the application .cfg file or some included package would need to do:
xdc.useModule('ti.sdo.ce.image1.IIMGENC1');
to bring in the library containing IMGENC1_create().
I'm not familiar with the details of the ti.sdo.codecs.jpegenc.dm355.ce.JPEGENC
module so I can't check that out, but pe
HI,
I`m using dm355 and i want change fps(frame per second) mpeg4 data on streaming.
and I`m using tvp5150am1.
so i waw try to change dynamicParams.targetFrameRate,
dynamicParams.refFrameRate in dynamicParams struct.
but it was not working.
Are there any one know that problem..
and what is t
On Monday 15 December 2008, BJ Opp wrote:
>
> > The RTC framework makes most of this stuff painless.
> >
> > In the current 2.6.28-rc code there are around sixty
> > drivers (maybe a few are queued in -mm), and when you
> > use it with udev (or mdev/busybox) you'll get the
> > right /dev/rtcX nod
Hmm, the kernel that we're using is the latest dm355 supported kernel from
montavista as of April 2008 and I have no drivers/rtc directory tree
whatsoever. Maybe the kernel that has the driver/rtc model is actually the TI
version? I know there has been some disconnect in the past between those
Not quite. You shouldn't do xdc.useModule('ti.sdo.ce.image1.IIMGENC1') because
IIMGENC1 is an Interface, not a Module. Kind of the right idea - we need to
get that ti.sdo.ce.image1 support package brought into the executable.
What really should happen is that ti.sdo.codecs.jpegenc.dm355.ce.JPE
HI, everbody!
I am using the TI Davinci dm6446 DVEVM to do some development. I use the tftp +
NFS to boot the uImage and filesystem before.
But now As I want the board to run the application all by itself without the
host PC. So I have to add my new uImage and some applications in the filesystem
Greetings to the list users!,
I am using DVEVM DM6446 board. I have studied the TI demo program
encodedecode. What I have observed is, there is no way to know or ensure that
the number of frames captured is equal to 25 or 30 frames per second. For that
matter X frames per second. Has any one c
dear all:
I am developing in the montavista linux2.6.10 version os,and the hard platforms
are dm355 evm and ths8200 evm ,I want to output 480p format image to a VGA
Monitor.I find a ths8200 driver(ths8200_encoder.c) in the linux driver
source,but when i used it,It shows no two I2c device( such a
Hello,
I have also observed similar problem in Fedora 9 core. Essentially, the
packages from TI website download does not get installed. To work around this,
I have installed the packages to RHEL 4 and then used the tar balls to get that
installed on FC9. This way it worked well for me and I am
Hi, Phil,
Thank you very much for your kind help. My nfs mount sometimes work and
sometimes fail.
The error log message is as the following. Could you help me analyse what is
the problem? Thank you very much for your help.
Dec 8 11:25:31 localhost syslogd 1.4.1: restart.
Dec 8 12:02:04 lo
Hi all,
When I use DM6446, I can download u-boot loader into the flash using DVFlasher
and serial port(UART).
By the same way, I want to download u-boot loader into the flash in DM355 using
serial port(UART).
Is it possible to program u-boot loader into the flash by using serial
port(UART) in D
61 matches
Mail list logo
