Hi,
In that case the description is wrong. It states:
the USB support for all AT91SAM9261 based boards doesn't work.
Look at the word 'ALL', that mislead me here...
ok I've not tick on the all
why not replace with
the USB support for all AT91SAM9261 based boards will only work if the PLLB
On 14:41 Sat 02 May , Prafulla Wadaskar wrote:
Thanks Jean for your review...
diff --git a/cpu/arm926ejs/kirkwood/kwcore.c
b/cpu/arm926ejs/kirkwood/kwcore.c new file mode 100644 index
000..9eaaab6
--- /dev/null
+++ b/cpu/arm926ejs/kirkwood/kwcore.c
please cpu.c
Okay
On 14:32 Sat 02 May , Prafulla Wadaskar wrote:
Thanks Jean...
+
+#include common.h
+#include ../drivers/net/phy/mv88e61xx.h
Ben I not sure it's clean
any better idea?
+#include netdev.h
+#include mv88f6281gtw_ge.h
+
index 000..9695f3f
--- /dev/null
+++
Some boards do not have SROM support for the DM9000 network adapter.
Instead of listing these board names in the driver code, make this
option configurable from the board config file.
It also removes a build warning for the at91sam9261ek board:
'dm9000x.c:545: warning: 'read_srom_word' defined
On 11:26 Sun 03 May , Remy Bohmer wrote:
Some boards do not have SROM support for the DM9000 network adapter.
Instead of listing these board names in the driver code, make this
option configurable from the board config file.
It also removes a build warning for the at91sam9261ek board:
Hello,
2009/5/3 Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com:
On 11:26 Sun 03 May , Remy Bohmer wrote:
Some boards do not have SROM support for the DM9000 network adapter.
Instead of listing these board names in the driver code, make this
option configurable from the board
V2: reworked comments from Jean-Christophe PLAGNIOL-VILLARD
Some boards do not have SROM support for the DM9000 network adapter.
Instead of listing these board names in the driver code, make this
option configurable from the board config file.
It also removes a build warning for the
--- /dev/null
+++ b/include/dm9000.h
Ben what do you think to do as usb have a dir to store all net header
include/net/
I have chosen the same location as the dm9161.h, other similar headers
are there as well.
If it has to be changed, I suggest making it a separate patch.
sure
I've
Dear Jean-Christophe,
in message 20090502215903.894e78342...@gemini.denx.de I wrote:
Actually For ARM we ask us tp use it so to simplify the import from linux
this helper are also imported
I don't know who we is, but you don;t have my ACK for this, and as
long as it's not even correct
-Original Message-
From: Jean-Christophe PLAGNIOL-VILLARD [mailto:plagn...@jcrosoft.com]
Sent: Sunday, May 03, 2009 2:02 PM
To: Prafulla Wadaskar
Cc: u-boot@lists.denx.de; Ashish Karkare; Prabhanjan Sarnaik;
Ronen Shitrit
Subject: Re: [U-Boot] [PATCH v4] Marvell Kirkwood family
actually the console API use the following naming convention
---Extract---
typedef struct device_t;
intdevice_register (device_t * dev);
intdevices_init (void);
intdevice_deregister(char *devname);
struct list_head* device_get_list(void);
device_t* device_get_by_name(char* name);
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ */
+
+#include common.h
+#include ../drivers/net/phy/mv88e61xx.h
If this header is
Hi Jean-Christophe,
2009/5/3 Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com:
diff --git a/drivers/mtd/ubi/build.c b/drivers/mtd/ubi/build.c
index f4b01a9..9b94ddc 100644
--- a/drivers/mtd/ubi/build.c
+++ b/drivers/mtd/ubi/build.c
@@ -291,7 +291,7 @@ static int ubi_sysfs_init(struct
All,
How do i get a snapshot of commit
dfc91c33957c95da34e3888dc87912d5c15a7603 from the GIT web. I tried
clicking on tree after putting the commit no in the text box but the
commit tarball i got wasn't the one i intended to.
Thanks for your help
-Alfred.
Once the Davinci watchdog has been enabled, the timeout
value cannot be changed. If the timeout in use is long,
it can take a long time for card to reset. By writing
an invalid service key, we can trigger an immediate reset.
Signed-off-by: Thomas Lange tho...@corelatus.se
---
On 19:54 Sun 03 May , Magnus Lilja wrote:
Hi Jean-Christophe,
diff --git a/drivers/mtd/ubi/vmt.c b/drivers/mtd/ubi/vmt.c
index 061da64..2b6b137 100644
--- a/drivers/mtd/ubi/vmt.c
+++ b/drivers/mtd/ubi/vmt.c
@@ -337,7 +337,7 @@ int ubi_create_volume(struct ubi_device *ubi, struct
NAND module should not modify EMIF registers unrelated to CS2
that is used for NAND, i.e. do not modify EWAIT config register
or registers for other Chip Selects.
Without this patch, EMIF configurations made in board_init()
will be invalidated.
Signed-off-by: Thomas Lange tho...@corelatus.se
---
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 1241371349-2140-1-git-send-email-plagn...@jcrosoft.com you wrote:
actually the console API use the following naming convention
---Extract---
typedef struct device_t;
intdevice_register (device_t * dev);
intdevices_init (void);
Dear alfred steele,
In message 528f13590905031057q43549224h1cf1e214f20bb...@mail.gmail.com you
wrote:
How do i get a snapshot of commit
dfc91c33957c95da34e3888dc87912d5c15a7603 from the GIT web. I tried
The best way of course is to use git clone and then git checkout.
clicking on tree
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090503180519.gx25...@game.jcrosoft.org you wrote:
I've use script to generate the patch for the RFC
Hmm... you should have looked at the results before posting, it seems.
btw this is one of the confusing point of the current implementation
On 20:41 Sun 03 May , Wolfgang Denk wrote:
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 1241371349-2140-1-git-send-email-plagn...@jcrosoft.com you wrote:
actually the console API use the following naming convention
---Extract---
typedef struct device_t;
int
Hi all,
I have now updated the i.MX31 NAND boot patches. It applies to the -next
tree (aka v2009.06-rc1) as of now.
I've taken care of most of the comments/questions that were sent to
Maxim Artamonov when he posted his latest (last?) patch. The comments
received on my parts has been taken care
This patch adds the NAND SPL framework needed to boot i.MX31 boards
from NAND.
The patch is based on the work by Maxim Artamonov
scn1874 at yandex.ru (which was signed-off-by him).
Signed-off-by: Magnus Lilja lilja.mag...@gmail.com
---
cpu/arm1136/start.S | 29 +++--
Add support for Freescale's i.MX31 PDK board (a.k.a. 3 stack board).
This patch assumes that some other program performs the actual
NAND boot.
Signed-off-by: Magnus Lilja lilja.mag...@gmail.com
---
MAKEALL |1 +
Makefile|3
Signed-off-by: Magnus Lilja lilja.mag...@gmail.com
---
MAKEALL |3 +-
Makefile|9 ++-
board/freescale/mx31pdk/config.mk |4 +
board/freescale/mx31pdk/lowlevel_init.S | 93
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090503184226.gy25...@game.jcrosoft.org you wrote:
we now switch to console_XX and console_device_t
---^^
Actually there is even a direct name conflict - console_init() is
already in use (in
Dear Prafulla Wadaskar,
In message 73173d32e9439e4abb5151606c3e19e201cd5cf...@sc-vexch1.marvell.com
you wrote:
In case of kirkwood specially in some board version if we use Kirkwood
without internal BootROM we need to configure DRAM before setting stack in
DRAM, this should be done in
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090503083923.gs25...@game.jcrosoft.org you wrote:
3) I'm in favor as Mike to have the tool to build the final flashable bin
in the tree as done for the blackfin with a new target and a new extention
as .kwd (or any other)
You know my
Dear Ben Warren,
In message f8328f7c0905021949w5e8a050cg98e34ab05b436...@mail.gmail.com you
wrote:
Wolfgang could help us on this?
You mean like that:
http://git.denx.de/?p=u-boot.git;a=shortlog;h=refs/heads/next
?
I'm sorry, I looked before sending this e-mail, but must have
On 22:05 Sun 03 May , Wolfgang Denk wrote:
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090503184226.gy25...@game.jcrosoft.org you wrote:
we now switch to console_XX and console_device_t
---^^
Actually there is even a direct name conflict -
On 10:16 Sun 03 May , Prafulla Wadaskar wrote:
-Original Message-
From: Jean-Christophe PLAGNIOL-VILLARD [mailto:plagn...@jcrosoft.com]
Sent: Sunday, May 03, 2009 2:02 PM
To: Prafulla Wadaskar
Cc: u-boot@lists.denx.de; Ashish Karkare; Prabhanjan Sarnaik;
Ronen
On Sun, May 03, 2009 at 12:11:40PM +0200, Remy Bohmer wrote:
Some boards do not have SROM support for the DM9000 network adapter.
Instead of listing these board names in the driver code, make this
option configurable from the board config file.
It also removes a build warning for the
Does this help at all: at any rate, it is a bit of the history of the
u-boot code:
http://lists.denx.de/pipermail/u-boot/2008-August/039679.html
Stephen Irons
David Brownell wrote:
I was looking at the DaVinci NAND support in current U-Boot
code (i.e. 2009.03 plus patches merged since that
On Sunday 03 May 2009, Stephen Irons wrote:
Does this help at all
Not quite; since when I looked at the MontaVista code,
I didn't see anything like that brokeness. It's possible
that some old MV kernels had that. If so, more recent
stuff seems to have been cured.
at any rate, it is a bit of
Hi J-C,
On Sun, May 3, 2009 at 3:21 AM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
--- /dev/null
+++ b/include/dm9000.h
Ben what do you think to do as usb have a dir to store all net header
include/net/
I have chosen the same location as the dm9161.h, other
Hi Prafulla,
On Sun, May 3, 2009 at 10:27 AM, Prafulla Wadaskar prafu...@marvell.comwrote:
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ */
+
+#include common.h
+#include ../drivers/net/phy/mv88e61xx.h
If this header is meant to be public it should be in
include. Sorry I didn't catch that earlier.
snip
This header has some public and some driver specific
On Sun, May 3, 2009 at 8:45 PM, Prafulla Wadaskar prafu...@marvell.comwrote:
+#include common.h
+#include ../drivers/net/phy/mv88e61xx.h
If this header is meant to be public it should be in
include. Sorry I didn't catch that
Stefan and Grant,
I have made some progess, Linux can boot normally with 1 GB memory now.
The following is what I did:
1.Chang Maximum low memory size from 0x3000(768M) to 0x2000(512M) and
enable High Memory support for Linux kernel configuration.
2.Add CONFIG_VERY_BIG_RAM to U-Boot
39 matches
Mail list logo
