Hi Ketan,
Just adding others, as well.
Yeah. I was aware of this, before I had gone for this option. I am using EXT3
only. But still it gives me error.
I am aware of Memory alignment issues too. But what more can I do for a memory
malloc'd from RAM. I have CMEM allocations to try. But I will
Subrahmanya, Chaithrika chaithr...@ti.com writes:
Kevin,
Below is a version of the patch that actually compiles. :/
This should now apply directly to the current davinci git head since
I've pushed the base patch.
Chaithrika, this driver currently requests several memory regions
On DM355, I'm noticing that U-Boot (1.2.0 supplied with EVM) doesn't
correctly deal with bad blocks when reading the kernel image, my
understanding is that nboot isn't aware of them and just reads bad
data.
Having a look at the latest U-Boot sources on the project's gitweb, it's
not clear if this
David Brownell davi...@pacbell.net writes:
On Friday 06 February 2009, Kevin Hilman wrote:
arch/arm/mach-davinci/Makefile | 2 +-
arch/arm/mach-davinci/dm355.c | 45 -
arch/arm/mach-davinci/dm644x.c | 56 ++-
if you're trying to align malloc'ed memory to an x-byte boundary, you
can try to do this:
e.g, aligning to a 2-byte boundary,
unaligned_addr = malloc(size + 0x3);
aligned_addr = ((unaligned_addr+0x3) (~0x3));
This should allow you to request the maximum possible size, and then
allow
Hello Jon,
You wrote:
If anyone has been here before and has any clues, they would be welcome.
So far in production we've seen about 2% NAND chips with bad blocks
where we want to put kernel images, so it looks like I might be learning
a lot more about U-Boot than I care to.
I have patches
David Brownell davi...@pacbell.net writes:
From: David Brownell dbrown...@users.sourceforge.net
Decouple ASP clk_*() calls from pinmmux for DM355 and DM6446.
This removes the need for dm355_psc_mux(), and is a net minor
source and runtime code shrink.
Note that this keeps the ASoC-related
David Brownell davi...@pacbell.net writes:
This should actually preced the patch I sent a few moments ago,
splitting ASP muxing out from the PSC operations; whoops!
- Generic dm355 init for spi0 device. Is this more or less
how we want to do such device setup?
Yes, this is where I'm
Kevin Hilman khil...@deeprootsystems.com writes:
Updates from v1/v2:
- add CLK_PSC flag (set at init for clks with 'lpsc' filled out)
- blindly dropped the remaining boot-time PSC inits
- more lowercase clock names, and removal of '_clk' suffix in strings
and from Dave:
- Add PSC_DSP
How can I build the uImage using da vinci git code (not the mvl401) for DM355
evm ?
I tried first doing config:
make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig
but this results into error with lots of unknown options.
Can anyone help ?
Greetings,
First of all, I apologize to the list for providing these as attachments,
but I just know that the client is going to shred them (and we don't have
mail on other network).
OK, there are four patches provided here to enable robust booting from NAND
with DM644x devices.
The first
Oops, forgot to include header file change for the TI flasher utilities
functions.
See attached...
Regards,
David
--
DAVID A. KONDRAD
Software Design Engineer
On-Q/Legrand
Telephone (800) 321-2343 x311
www.onqlegrand.com
(See attached file: ti_flash_tools_util_functions_h.patch)
From: David Brownell dbrown...@users.sourceforge.net
Support the 4-bit ECC engine found on DM355 and OMAP-L137 chips.
This is limited to small-page flash for now; there are separate
issues specific to large page. Note that the DM355 EVM uses a
large-page chip -- unless you swap socketed chips.
On Monday 09 February 2009, Kevin Hilman wrote:
commit 3e853c2ac5734813ccd7b881d01d919c20dadb09
Author: Kevin Hilman khil...@deeprootsystems.com
Date: Fri Feb 6 12:32:19 2009 -0800
davinci: mux: move pin setup into device-specific init
Signed-off-by: Kevin Hilman
Large page support with the 4-bit ECC hardware.
- OOB layout
* construct layout descriptors to match NAND core's algorithm
(the defaults are wrong, but are still used blindly)
- Bad Block handling
* prevent scanning, since the manufacturer's markings get clobbered
*
This is working moderately well for me now, well enough to
circulate to see if other folk have the same results.
Test platform is DM355 EVM.
These three patches go on top of current GIT code (including
the 07190aa9f93b2ff107c15ef2e6c2c4a6dd266275 cleanup patch):
1) Support dm355 4-bit ECC as
From: David Brownell dbrown...@users.sourceforge.net
The syndrome based page read/write routines store ECC, and possibly
other OOB data, right after each chunk of ECC'd data. With ECC
chunk size of 512 bytes and a large page (2KB) NAND, the layout is:
data-0 OOB-0 data-1 OOB-1 data-2 OOB-2
On Monday 09 February 2009, Kevin Hilman wrote:
Thanks, pushing this series.
Great, needs a small fix though (my goof):
=== Cut Here
From: David Brownell dbrown...@users.sourceforge.net
The clock names are now doing LESS SHOUTING so this one needed
to be changed.
Signed-off-by: David
On Monday 09 February 2009, you wrote:
How can I build the uImage using da vinci git code (not the mvl401) for DM355
evm ?
I tried first doing config:
make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig
but this results into error with lots of unknown options.
Can anyone
David,
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf
Of David Brownell
Sent: Monday, February 09, 2009 3:43 PM
To: DaVinci
Subject: [patch davinci-git 2/3] NAND: Fix raw
On Monday 09 February 2009, Narnakaje, Snehaprabha wrote:
The syndrome based page read/write routines store ECC, and possibly
other OOB data, right after each chunk of ECC'd data. With ECC
chunk size of 512 bytes and a large page (2KB) NAND, the layout is:
data-0 OOB-0 data-1 OOB-1
David Brownell davi...@pacbell.net writes:
On Monday 09 February 2009, Kevin Hilman wrote:
commit 3e853c2ac5734813ccd7b881d01d919c20dadb09
Author: Kevin Hilman khil...@deeprootsystems.com
Date: Fri Feb 6 12:32:19 2009 -0800
davinci: mux: move pin setup into device-specific init
I updated kernel for mounting file system on Nand flash.
I need to write the camera configuration information to nand flash.
I wrote configuration information after mounting file system on Nand flash.
But i found while reading the information from Flash memory and displaying
in web page its
This path is likely incorrect:
/home/rtalbot/dvevm_2_21/dsplink_1_60/packages
You need to do one of the following to fix it:
1) Root through the various makefiles to figure out where they define XDCPATH
and delete the extra packages they are appending to the dsplink path.
- OR -
2) Add a
From: Sneha Narnakaje nsnehapra...@ti.com
This patch fixes the NETDEV WATCHDOG timeout issue with dm9000 ethernet
driver on DM355, while using the NFS as root filesystem.
In the patch I have replaced the spin_lock/spin_unlock calls with dm9000
specific disable/enable interrupt calls, in the
Hi ,
While working with 2.6.10 MV kernel ,i found that MTD doesnt support more than
4GB size (since mtd-size is a 32 bit type) .My NF is of 4 GB(total size=4GB
,2GB each device ,page size 4K)size .just to be supported by existing kernel i
reduced total mtd-size by 1 block initially but i got
Thanks, Brad, that seems to have cleared that roadblock. I hadn't
noticed that difference between the two releases... downloading each
component separately really is proving to be a pain.
David, thanks again for your input earlier; I was in the process of
implementing it when Brad's solution
27 matches
Mail list logo
