---
board/davinci/dm365evm/dm365evm.c | 68
include/configs/davinci_dm365evm.h | 11 ++
2 files changed, 79 insertions(+), 0 deletions(-)
diff --git a/board/davinci/dm365evm/dm365evm.c
b/board/davinci/dm365evm/dm365evm.c
index ac54106..fb05019 100644
---
tools/ublimage.c | 19 +++
tools/ublimage.h |2 ++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/tools/ublimage.c b/tools/ublimage.c
index d6b4017..527b1a4 100644
--- a/tools/ublimage.c
+++ b/tools/ublimage.c
@@ -36,6 +36,10 @@
#include
#include "ubli
more chips than the dm365 but I was hoping
someone from TI might be able to tell me that. In any case, it's better
to have support for one chip than for none.
Best Regards,
Stijn
On 05/21/2012 08:17 AM, Heiko Schocher wrote:
Hello Stijn,
Stijn Souffriau wrote:
---
board/davinc
On 05/20/2012 08:59 PM, Mike Frysinger wrote:
On Sunday 20 May 2012 12:50:40 Stijn Souffriau wrote:
--- a/board/davinci/dm365evm/dm365evm.c
+++ b/board/davinci/dm365evm/dm365evm.c
+#ifdef CONFIG_HW_WATCHDOG
+static struct davinci_timer * const wdttimer =
+(struct davinci_timer
On 05/21/2012 08:30 AM, Heiko Schocher wrote:
Hello Stijn,
Stijn Souffriau wrote:
---
tools/ublimage.c | 19 +++
tools/ublimage.h |2 ++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/tools/ublimage.c b/tools/ublimage.c
index d6b4017..527b1a4 100644
---
arch/arm/cpu/arm926ejs/davinci/dm365.c | 61
arch/arm/include/asm/arch-davinci/timer_defs.h |2 +
board/davinci/dm365evm/dm365evm.c | 19
include/configs/davinci_dm365evm.h | 11 +
4 files changed, 93 insertions(+
---
tools/mkimage.h |6 ++
tools/ublimage.c | 29 +++--
tools/ublimage.h |2 ++
3 files changed, 35 insertions(+), 2 deletions(-)
diff --git a/tools/mkimage.h b/tools/mkimage.h
index 5fe1a48..cd835f0 100644
--- a/tools/mkimage.h
+++ b/tools/mkimage.h
@@ -140
Fixed a comment
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
---
tools/mkimage.h |6 ++
tools/ublimage.c | 31 +--
tools/ublimage.h |2 ++
3 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/tools/mkimage.h b/tools/mkimage.h
index 5fe1a48..cd835f0 100644
--- a/tools/mkimage.h
+++ b/tools/mkimage.h
@@ -1
Hi all,
I want to read files from an ext2 filesystem stored in a flash that is mapped
to a physical address range. To be able to use the ext2 commands I think what I
need is a block device (block_dev_desc_t) that treats an address range as a
block device.
Does something like this already exist
10 matches
Mail list logo