Hi,
We are using taishan based board having 1GB DDR.
In u-boot code we found that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to
768MB hence "if (size < bootm_size)" condition becomes true and u-boot throw
"WARNING: adjusting available memory to 0x3000" message on console.
Let me know will it pos
Hi,
While using u-boot for ppc440 based board we are getting "*** Warning - bad
CRC, using default environment" message.
On denx site we came to know that message is printed because the flash
sector or ERPROM containing the environment variables has never been
initialized yet.
Is there any fix to
On 12-05-10 18:09, Wolfgang Denk wrote:
> I just see that my mail client wrapped the lines again on send. I'll see
>> how I can fix this. I don't think it's a problem right now, I doubt the
>> patch will be completely fine this time.
>>
> Yes, it is a problem, because I cannot apply it for te
On Tue, 18 May 2010 09:39:54 +0200
Remco Poelstra wrote:
> On 12-05-10 18:09, Wolfgang Denk wrote:
> > I just see that my mail client wrapped the lines again on send. I'll see
> >> how I can fix this. I don't think it's a problem right now, I doubt the
> >> patch will be completely fine this time
On Tuesday 18 May 2010 09:11:16 anup behare wrote:
> While using u-boot for ppc440 based board we are getting "*** Warning - bad
> CRC, using default environment" message.
> On denx site we came to know that message is printed because the flash
> sector or ERPROM containing the environment variable
Hi Anup,
On Tuesday 18 May 2010 09:03:25 anup behare wrote:
> We are using taishan based board having 1GB DDR.
> In u-boot code we found that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to
> 768MB hence "if (size < bootm_size)" condition becomes true and u-boot
> throw "WARNING: adjusting available me
On Monday 17 May 2010 16:11:22 Timur Tabi wrote:
> Stefan Roese wrote:
> > This protection is chip specific. IIRC, then some Intel (Strata) chips
> > either protect all sectors or have a sectore-wise protection mechanism.
> > You need to check your FLASH documentation for the exact behaviour.
> > W
Hi Mark,
On Tuesday 18 May 2010 07:26:34 Mark Tomlinson wrote:
> Our hardware has part of the flash mapped in two address ranges.
> The CONFIG_SYS_MONITOR_BASE is in the upper 'boot' area, whereas
> the CONFIG_SYS_FLASH_BANKS_LIST has the full flash available at
> a lower address.
Just to be sure
Signed-off-by: Horst Kronstorfer
---
arch/powerpc/cpu/mpc83xx/start.S |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/cpu/mpc83xx/start.S b/arch/powerpc/cpu/mpc83xx/start.S
index a7c8079..aa263e3 100644
--- a/arch/powerpc/cpu/mpc83xx/start.S
+++ b/arch/po
Hi Wolfgang,
> The top level Makefile is growing and growing. Once, wehn we suppoted
> only a few tens of boards, it was possible to implement board
> configuration logic in the Makefile, but it quickly turned out that
> this doesn't scale. Also, it is not really needed (at least not any
> more) -
Stefan,
I don't want to change the behavior and I can't use
CONFIG_ENV_IS_NOWHERE because we may change the environment variable and
save it.
Here my intention was to remove the warning runtime.
~Anup
On Tue, May 18, 2010 at 1:25 PM, Stefan Roese wrote:
> On Tuesday 18 May 2010 09:11:16
On Tuesday 18 May 2010 11:12:26 anup behare wrote:
> I don't want to change the behavior and I can't use
> CONFIG_ENV_IS_NOWHERE because we may change the environment variable and
> save it.
And this usually happens upon board bring-up and/or factory testing. So in the
"normal" use-case this warn
Hi Stefan,
My intention was only to remove this warning.
My Linux is booting correctly and it is not causing any trouble but I
observed "WARNING: adjusting available memory to 0x3000" on u-boot
console.
I have couple of question here with 768MB:
1. Is that mean u-boot will use only 768MB
I removing the console warning and this is one of the warning.
On Tue, May 18, 2010 at 2:53 PM, Stefan Roese wrote:
> On Tuesday 18 May 2010 11:12:26 anup behare wrote:
> > I don't want to change the behavior and I can't use
> > CONFIG_ENV_IS_NOWHERE because we may change the environment variabl
Hi Anup,
On Tuesday 18 May 2010 11:24:42 anup behare wrote:
> My intention was only to remove this warning.
Perhaps it makes sense, to change this "WARNUNG:" to "NOTE:". I suggest you
send a patch for this and we might accept it.
> My Linux is booting correctly and it is not causing any troubl
Hi Delio,
On Thu, May 13, 2010 at 18:27:51, Delio Brignoli wrote:
> Reduce the number of reads per byte transferred on the BUF register from 2 to
> 1 and
> take advantage of the TX buffer in the SPI module.
The patch looks good to me.
Can you please publish some sort of numbers in the
patch de
Wolfgang Denk wrote:
> Assume the case that the DTB is stored in NOR flash, and I pass the
> NOR flash address to the bootm command...
>
> I'm not sure if there is any guarantee for free room behind the DTB in
> this case.
We can never guarantee this. The code that calls fdt_increase_size() wil
Signed-off-by: Daniel Hellstrom
---
arch/sparc/include/asm/byteorder.h |1 +
arch/sparc/include/asm/unaligned.h | 10 ++
2 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 arch/sparc/include/asm/unaligned.h
diff --git a/arch/sparc/include/asm/byteorder.h
b/arch/
Signed-off-by: Daniel Hellstrom
---
drivers/net/greth.c | 69 +++---
1 files changed, 43 insertions(+), 26 deletions(-)
diff --git a/drivers/net/greth.c b/drivers/net/greth.c
index 79bc4d9..a1a88f9 100644
--- a/drivers/net/greth.c
+++ b/drivers/net/g
Signed-off-by: Daniel Hellstrom
---
drivers/net/greth.c | 14 --
1 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/net/greth.c b/drivers/net/greth.c
index a1a88f9..143c773 100644
--- a/drivers/net/greth.c
+++ b/drivers/net/greth.c
@@ -146,13 +146,23 @@ int gret
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/Makefile |5 +-
arch/sparc/cpu/leon3/memcfg.c | 276 +
arch/sparc/cpu/leon3/memcfg.h | 106 ++
arch/sparc/cpu/leon3/memcfg_low.S | 270
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/cpu_init.c | 10 +--
arch/sparc/cpu/leon3/interrupts.c |7 +-
arch/sparc/cpu/leon3/memcfg.h |1 -
arch/sparc/cpu/leon3/prom.c |7 ++-
arch/sparc/cpu/leon3/serial.c | 16 ++--
drivers/net/greth.c
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/serial.c | 17 ++---
1 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/arch/sparc/cpu/leon3/serial.c b/arch/sparc/cpu/leon3/serial.c
index 8964310..1f17ede 100644
--- a/arch/sparc/cpu/leon3/serial.c
+++ b/arch/sp
Signed-off-by: Daniel Hellstrom
---
arch/sparc/include/asm/irq.h |3 +++
arch/sparc/lib/interrupts.c |7 +++
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/sparc/include/asm/irq.h b/arch/sparc/include/asm/irq.h
index c5538c0..ce78169 100644
--- a/arch/sparc/incl
Signed-off-by: Daniel Hellstrom
---
arch/sparc/lib/bootm.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/arch/sparc/lib/bootm.c b/arch/sparc/lib/bootm.c
index c62cf57..f517325 100644
--- a/arch/sparc/lib/bootm.c
+++ b/arch/sparc/lib/bootm.c
@@ -35,10 +35,6 @@ ext
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/cpu_init.c | 30 --
1 files changed, 28 insertions(+), 2 deletions(-)
diff --git a/arch/sparc/cpu/leon3/cpu_init.c b/arch/sparc/cpu/leon3/cpu_init.c
index fd3e757..1829a08 100644
--- a/arch/sparc/cpu/leon3/cpu
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/cpu.c | 42 +++-
arch/sparc/include/asm/leon3.h | 13
2 files changed, 54 insertions(+), 1 deletions(-)
diff --git a/arch/sparc/cpu/leon3/cpu.c b/arch/sparc/cpu/leon3/cpu.c
index 976
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/cpu_init.c | 14
arch/sparc/cpu/leon3/greth.c| 152 +++
2 files changed, 166 insertions(+), 0 deletions(-)
create mode 100644 arch/sparc/cpu/leon3/greth.c
diff --git a/arch/sparc/cpu/leon3/c
Signed-off-by: Daniel Hellstrom
---
arch/sparc/lib/board.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/sparc/lib/board.c b/arch/sparc/lib/board.c
index 11eea60..d829af0 100644
--- a/arch/sparc/lib/board.c
+++ b/arch/sparc/lib/board.c
@@ -65,6 +65,7 @@ extern
Signed-off-by: Daniel Hellstrom
---
arch/sparc/lib/board.c | 14 +++
drivers/spi/Makefile |1 +
drivers/spi/spimctrl_spi.c | 263
include/grlib/spimctrl.h | 69
4 files changed, 347 insertions(+), 0 deletions(-)
creat
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/prom.c | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/arch/sparc/cpu/leon3/prom.c b/arch/sparc/cpu/leon3/prom.c
index 86376bb..e0a69af 100644
--- a/arch/sparc/cpu/leon3/prom.c
+++ b/arch/sparc/cpu/l
Signed-off-by: Daniel Hellstrom
---
arch/powerpc/cpu/mpc85xx/cpu_init.c |2 +-
common/cmd_bootm.c |8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/powerpc/cpu/mpc85xx/cpu_init.c
b/arch/powerpc/cpu/mpc85xx/cpu_init.c
index e578b29..61dd7ad
Signed-off-by: Daniel Hellstrom
---
arch/sparc/cpu/leon3/Makefile |2 +-
arch/sparc/cpu/leon3/cpu.c | 10 ++-
arch/sparc/cpu/leon3/cpu_mp.c | 87 +++
arch/sparc/cpu/leon3/prom.c | 32 +++---
arch/sparc/cpu/leon3/start.S
Hello Sekhar,
On 18/05/2010, at 14:25, Nori, Sekhar wrote:
> The patch looks good to me.
>
> Can you please publish some sort of numbers in the
> patch description indicating the performance improvement
> achieved?
will do.
> A minor nit below:
[...]
>> + if((o_cnt == (len -
Dear Timur Tabi,
In message <4bf29fe9.1070...@freescale.com> you wrote:
> Wolfgang Denk wrote:
>
> > Assume the case that the DTB is stored in NOR flash, and I pass the
> > NOR flash address to the bootm command...
> >
> > I'm not sure if there is any guarantee for free room behind the DTB in
>
Wolfgang Denk wrote:
>> We can never guarantee this. The code that calls fdt_increase_size() will
>> just have to ensure that there is enough room.
>
> Such an "ensure that there is enough room" is exactly what I'm asking
> for.
Maybe I don't understand what you're getting at. My point is that
Hi Thirumalai
Am 18.05.2010 08:29, schrieb Thirumalai:
> Hi Matthias,
> I am going to use u-boot alone for my development. Which debugger is
> suitable for debugging u-boot and initial board bringup activity?
> My choice is BDI2000. Is it ok.
Yes. As I said. But I never used it to debug
Yes we do have 2 flash chips. Here's the mapping:
#define CONFIG_SYS_FLASH_BASE 0xf800 /* 2 chips*16M */
#define CONFIG_SYS_MONITOR_BASE TEXT_BASE /* start of monitor */
and in our config.mk file:
TEXT_BASE = 0xfff4
This is the same flash chip as that at 0xf800, but remap
Dear Timur Tabi,
In message <4bf2b302.2030...@freescale.com> you wrote:
>
> >> We can never guarantee this. The code that calls fdt_increase_size() will
> >> just have to ensure that there is enough room.
> >
> > Such an "ensure that there is enough room" is exactly what I'm asking
> > for.
>
On Tue, May 18, 2010 at 5:20 PM, Wolfgang Denk wrote:
>> And again, the point *I* am trying to make is that it's okay to put the onus
>> of that check on the *caller* of fdt_increase_size(), and not on
>> fdt_increase_size() itself.
>
> OK. I have no problem with that. I am just missing this othe
Thomas Chou wrote:
> An argument, verbose, is added to enable/disable the "Device not
> found" message. Because we need to query mmc devices in mmc_spi
> subcommand and don't want the message.
>
Please drop this one. Because I reduced the cmd_mmc_spi.c, so that the
query is not needed.
- Thomas
This patch supports mmc/sd card with spi interface. It is based on
the generic mmc framework. It works with SDHC and supports multi
blocks read/write.
The crc checksum on data packet is enabled with the def,
#define CONFIG_MMC_SPI_CRC_ON
There is a subcomamnd "mmc_spi" to setup spi bus and cs at
From: Mahavir Jain
Current PHY Software Reset operation in guruplug does not
poll reset bit in control register to go to 0(auto clearing)
for making sure reset was successful.This patch uses standard
miiphy call miiphy_reset to make sure proper PHY reset operation.
Signed-off-by: Mahavir Jain
-
On Tue, 2010-05-18 at 22:20 -0700, Mahavir Jain wrote:
> From: Mahavir Jain
>
> Current PHY Software Reset operation in guruplug does not
> poll reset bit in control register to go to 0(auto clearing)
> for making sure reset was successful.This patch uses standard
> miiphy call miiphy_reset to ma
Hi Matthias,
> Hi Thirumalai
>
> Am 18.05.2010 08:29, schrieb Thirumalai:
>> Hi Matthias,
>> I am going to use u-boot alone for my development. Which debugger
>> is
>> suitable for debugging u-boot and initial board bringup activity?
>> My choice is BDI2000. Is it ok.
>
> Yes. As I said.
Dear Timur Tabi,
In message you
wrote:
>
> >> And again, the point *I* am trying to make is that it's okay to put the
> >> onus
> >> of that check on the *caller* of fdt_increase_size(), and not on
> >> fdt_increase_size() itself.
> >
> > OK. I have no problem with that. I am just missing this
46 matches
Mail list logo