From: Gao Guanhua
The filelen should be signed type, not unsigned type.
otherwise, The condition as below never take.
if (filelen < 0)
Signed-off-by: Gao Guanhua
Signed-off-by: Dave Liu
---
common/cmd_ext2.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/co
On Monday 13 April 2009 19:02:05 Scott Wood wrote:
> Mike Frysinger wrote:
> > On Monday 13 April 2009 17:42:00 Scott Wood wrote:
> >> You're defining the interface -- there are no existing users.
> >
> > just because *my* device needs it doesnt mean every device needs it. i
> > was trying to be n
On Monday 13 April 2009, Jean-Christophe PLAGNIOL-VILLARD wrote:
> please move this to the Makefile
= CUT HERE
From: David Brownell
Don't needlessly include lowlevel init code; that's only really
needed with boot-from NOR (not boot-from-NAND). The 2nd stage
loader (UBL) handles that before
Mike Frysinger wrote:
> On Monday 13 April 2009 17:42:00 Scott Wood wrote:
>> You're defining the interface -- there are no existing users.
>
> just because *my* device needs it doesnt mean every device needs it. i was
> trying to be nice from the get go.
Every device that is a reasonable candi
On 16:01 Wed 08 Apr , ong wrote:
> Hi,
>
> May i know how to build the u-boot environment for my board?
you will not build it
you will built where will be store the env
> Whats the different below. I would like to know how to build u-boot
> environment. As i know its different with u-boot.bi
On 11:52 Tue 07 Apr , E Robertson wrote:
> Hi all,
> Is their a problem using udelay in board_init functions?
actually yes
I'll send some patch to cleanuo the timer/interrupt init this week
> When I do this on my at91, arm926ejs board, it seems to be in an endless loop.
> I thought this was a t
On 22:31 Thu 09 Apr , Prafulla Wadaskar wrote:
> Chips supported:-
> 1. 88E6161 6 port gbe swtich with 5 integrated PHYs
> 2. 88E6165 6 port gbe swtich with 5 integrated PHYs
> 2. 88E6132 3 port gbe swtich with 2 integrated PHYs
>
> Note: This driver is supported and tested against
> kirkwood
On 14:28 Fri 10 Apr , Renato Andreola wrote:
> From 6cc63851e5e4c16012d9afad70cedb41b7340de7 Mon Sep 17 00:00:00 2001
> From: Renato Andreola
> Date: Fri, 10 Apr 2009 12:52:55 +0200
> Subject: drivers/mtd/cfi_flash: precision and underflow problem in tout
> calculation
>
> With old configur
On 14:04 Mon 06 Apr , Eric BENARD wrote:
> Jean-Christophe PLAGNIOL-VILLARD a écrit :
>> The timer has been rewrote with a precision at ~0,18%
>>
> works fine on an 9260 and solves TFTP timeout problem.
Thanks for the test
btw: could you specify on wich boards?
I'll send a pull request for it
On 22:48 Fri 10 Apr , Sergey Lapin wrote:
> On Sat, Apr 04, 2009 at 04:06:34PM +0200, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > The timer has been rewrote with a precision at ~0,18%
> Works perfectly with afeb9260
> >
> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Tested-by: Serge
On 15:46 Sun 12 Apr , David Brownell wrote:
> From: David Brownell
>
> Don't needlessly include lowlevel init code; that's only really
> needed with boot-from NOR (not boot-from-NAND). The 2nd stage
> loader (UBL) handles that before it loads U-Boot.
>
> Signed-off-by: David Brownell
>
>
On 09:56 Mon 06 Apr , Daniel Gorsulowski wrote:
> Hi Jean-Christophe,
>
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 10:24 Fri 27 Mar , Daniel Gorsulowski wrote:
>>> This patch adds support for MEESC board from esd gmbh.
>>> The MEESC is based on an Atmel AT91SAM9263 SoC.
>>>
>>> Signed-
On 16:50 Mon 13 Apr , Peter Tyser wrote:
> On Sat, 2009-04-04 at 01:08 +0200, Wolfgang Denk wrote:
> > Dear Peter Tyser,
> >
> > In message <1236988492-21295-6-git-send-email-pty...@xes-inc.com> you wrote:
> > > Some systems have zlib.h installed in /usr/include/. This isn't the
> > > desired
On Monday 13 April 2009 17:42:00 Scott Wood wrote:
> Mike Frysinger wrote:
> > On Monday 13 April 2009 11:59:30 Scott Wood wrote:
> >> On Sat, Apr 11, 2009 at 09:26:42PM -0400, Mike Frysinger wrote:
> >>> +#ifdef NAND_PLAT_WRITE_CMD
> >>
> >> Why would a user select this driver without providing th
On Sat, 2009-04-04 at 01:09 +0200, Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1236988492-21295-7-git-send-email-pty...@xes-inc.com> you wrote:
> > Some systems have bzlib.h installed in /usr/include/. This isn't the
> > desired file (we want the one in include/bzlib.h). Moving U-Bo
On Monday 13 April 2009 11:01:02 Steve Reckamp wrote:
> In looking for offensive language in our source code, we came across
> several occurrences in u-boot code:
I found some PHP under tools/bddb; some people consider that an
offensive language.
-Scott
__
On Sat, 2009-04-04 at 01:08 +0200, Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1236988492-21295-6-git-send-email-pty...@xes-inc.com> you wrote:
> > Some systems have zlib.h installed in /usr/include/. This isn't the
> > desired file (we want the one in include/zlib.h). Moving U-Boot
Mike Frysinger wrote:
> On Monday 13 April 2009 11:59:30 Scott Wood wrote:
>> On Sat, Apr 11, 2009 at 09:26:42PM -0400, Mike Frysinger wrote:
>>> +#ifdef NAND_PLAT_WRITE_CMD
>> Why would a user select this driver without providing the necessary
>> definitions -- and if they do, why do you want anyt
On Monday 13 April 2009 11:01:02 Steve Reckamp wrote:
> In looking for offensive language in our source code, we came across
> several occurrences in u-boot code:
dont you have any real work to do ? like protecting us from the internet ?
-mike
signature.asc
Description: This is a digitally sign
On Monday 13 April 2009 11:59:30 Scott Wood wrote:
> On Sat, Apr 11, 2009 at 09:26:42PM -0400, Mike Frysinger wrote:
> > +#ifdef NAND_PLAT_WRITE_CMD
>
> Why would a user select this driver without providing the necessary
> definitions -- and if they do, why do you want anything other than
> a compi
NAND timing is defaulted to Micron NAND. To support
varied boards, this is not scalable.
This patch introduces compile time option to select
the timing to select at the same time allows
platforms to build with custom timing params
Signed-off-by: Nishanth Menon
---
cpu/arm_cortexa8/omap3/mem.c
NAND CS is assumed to be CS0 while we could have
choice b/w 0 to 7. This patch enables board files
to handle varied CS on a need basis.
Signed-off-by: Nishanth Menon
---
cpu/arm_cortexa8/omap3/mem.c |8 +---
include/asm-arm/arch-omap3/mem.h |8
2 files changed, 9 inserti
Dear Kumar,
In message <019c200b-ecc7-47b8-8ad0-06deaf85c...@kernel.crashing.org> you wrote:
>
> On Apr 13, 2009, at 11:11 AM, Justin Waters wrote:
>
> > I've taken the liberty of sanitizing the U-Boot source code. Please
> > consider this patch for inclusion into the next release.
> >
> > Sign
Hi,
The following patch series provides cleanup for making
OMAP3 NAND support more generic. This consists of:
a) OMAP3:NAND: Change the NAND timing assignment
b) OMAP3:NAND: Change the NAND CS handling
c) OMAP3:NAND: rename SMNAND_ENV_OFFSET
Regards,
Nishanth Menon
SMNAND_ENV_OFFSET is more specific to Samsung
NAND, rename it to NAND_ENV_OFFSET
Signed-off-by: Nishanth Menon
---
cpu/arm_cortexa8/omap3/mem.c|2 +-
include/configs/omap3_beagle.h |4 ++--
include/configs/omap3_evm.h |2 +-
include/configs/omap3_overo.h |4 ++--
inclu
On Mon, Apr 13, 2009 at 11:25:51AM -0700, Qingyu Song wrote:
> I have a ported u-boot base on 8548CDS for my 8548 board. The U-Boot version
> is 2008.10.
> the u-boot boot up was successful. I am trying to use BDI2000 do some
> debuging.
>
> the BDI2000 config file is as below. with this config fi
Actually, it hangs changing gd pointer, before set_tlb() call. In my older
u-boot version, it was made in cpu_init_f function.
/* Pointer is writable since we allocated a register for it */
gd = (gd_t *) (CONFIG_SYS_INIT_RAM_ADDR + CONFIG_SYS_GBL_DATA_OFFSET);
On Thu, Apr 9, 2009 at 3:03
I have a ported u-boot base on 8548CDS for my 8548 board. The U-Boot version
is 2008.10.
the u-boot boot up was successful. I am trying to use BDI2000 do some
debuging.
the BDI2000 config file is as below. with this config file, I can flash
program and bring up my board. However, when I try to set
On Apr 13, 2009, at 11:11 AM, Justin Waters wrote:
>
> I've taken the liberty of sanitizing the U-Boot source code. Please
> consider this patch for inclusion into the next release.
>
> Signed-off-by: Justin Waters
I vote this as best patch of 2009.
- k
___
2009/4/13 alfred steele :
> Hi Magnus,
>
> For that matter, I can dump memory between 0x and 0x0100
> though. However memory dump at 0x10 also fails.
>
> Can you point out which pages in the Reference manual point to the same?
Chapter 2-1 "Memory map". in MCIMX31RM "Reference Manual".
On Mon, 2009-04-13 at 11:01 -0400, Steve Reckamp wrote:
> In looking for offensive language in our source code, we came across
> several occurrences in u-boot code:
>
>
>
> \u-boot-1.3.3\board\netphone\phone_console.cLine 987
>
> \u-boot-1.3.3\tools\gdb\ serial.c
> Line 113
>
> \u-b
On Mon, Apr 13, 2009 at 10:01:02AM -0500, Steve Reckamp wrote:
> In looking for offensive language in our source code, we came across
> several occurrences in u-boot code:
You forgot to attach the patch where you removed them all...
John
--
John W. LinvilleSomeday the world will
On Sat, Apr 11, 2009 at 09:26:42PM -0400, Mike Frysinger wrote:
> +#ifdef NAND_PLAT_WRITE_CMD
Why would a user select this driver without providing the necessary
definitions -- and if they do, why do you want anything other than
a compilation error to result?
+ /* Drain the writebuffer */
+
Hi Stefan,
As a follow up, This hack seems to fix the issue.
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index 631b969..d386143 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -1691,7 +1691,7 @@ static int __flash_detect_cfi (flash_info_t * info,
struct c
In looking for offensive language in our source code, we came across
several occurrences in u-boot code:
\u-boot-1.3.3\board\netphone\phone_console.cLine 987
\u-boot-1.3.3\tools\gdb\ serial.c
Line 113
\u-boot-1.3.3\lib_generic\vsprintf.c
Line 9
\u-boot-1.3.3\board\w7o\flash.c
Line
From: David Brownell
Fix dependency goofage: it should certainly be possible to have the
partition support without bringing in UBI commands.
Signed-off-by: David Brownell
---
drivers/mtd/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/mtd/Makefile
+++ b/driver
Wolfgang Denk wrote:
> Dear Jerry Van Baren,
>
> In message <49e335bb.4050...@ge.com> you wrote:
>>> - it works only on NOR flash, not on any media that can be accessed
>>> only in blocks
>> Not true: the offset merely needs to be aligned to the next block in
>> that case:
>> [u
Hi Magnus,
For that matter, I can dump memory between 0x and 0x0100
though. However memory dump at 0x10 also fails.
Can you point out which pages in the Reference manual point to the same?
Thanks,
Alfred.
On Thu, Apr 9, 2009 at 12:53 PM, Magnus Lilja wrote:
> Hi
>
> 2009/4/9 alfre
On Monday 13 April 2009 09:11:59 Jerry Van Baren wrote:
> Mike Frysinger wrote:
> > On Monday 13 April 2009 08:12:44 Jerry Van Baren wrote:
> >> Mike Frysinger wrote:
> >>> On Monday 13 April 2009 06:15:24 Wolfgang Denk wrote:
> In message Mike wrote:
> > currently the env code will erase
Mike Frysinger wrote:
> On Monday 13 April 2009 08:12:44 Jerry Van Baren wrote:
>> Mike Frysinger wrote:
>>> On Monday 13 April 2009 06:15:24 Wolfgang Denk wrote:
In message Mike wrote:
> currently the env code will erase the entire env storage before writing
> back out the current env
Dear Jerry Van Baren,
In message <49e335bb.4050...@ge.com> you wrote:
>
> > - it works only on NOR flash, not on any media that can be accessed
> > only in blocks
>
> Not true: the offset merely needs to be aligned to the next block in
> that case:
> [undefined]
> offse
Dear Mike,
In message <200904130834.35359.vap...@gentoo.org> you wrote:
>
> > Since flash can change 1s to 0s, but cannot change them back, you could
> > redefine the env storage to be
> >[undefined]
> > (note the added at the start). By definition, the valid env's
> > =3D=3D 0x. T
Hi,
With OneNAND ipl reading CONFIG_SYS_MONITOR_LEN , Environment Area
should start after CONFIG_SYS_MONITOR_LEN.
Environment is made Bad Block cpapable too. These are done in the patch.
And fix 'onenand test' command to skip Bootloader and Environment Blocks.
With Regards
Moorthy
Makes
Wolfgang Denk wrote:
> Dear Jerry Van Baren,
>
> In message <49e32c3c.8090...@ge.com> you wrote:
>> Since flash can change 1s to 0s, but cannot change them back, you could
>> redefine the env storage to be
>>[undefined]
>> (note the added at the start). By definition, the valid env's
>> =
On Monday 13 April 2009 08:12:44 Jerry Van Baren wrote:
> Mike Frysinger wrote:
> > On Monday 13 April 2009 06:15:24 Wolfgang Denk wrote:
> >> In message Mike wrote:
> >>> currently the env code will erase the entire env storage before writing
> >>> back out the current env, even if the env storage
Dear Jerry Van Baren,
In message <49e32c3c.8090...@ge.com> you wrote:
>
> Since flash can change 1s to 0s, but cannot change them back, you could
> redefine the env storage to be
>[undefined]
> (note the added at the start). By definition, the valid env's
> == 0x. To write a new
Mike Frysinger wrote:
> On Monday 13 April 2009 06:15:24 Wolfgang Denk wrote:
>> In message Mike wrote:
>>> currently the env code will erase the entire env storage before writing
>>> back out the current env, even if the env storage has enough empty space
>>> to store the current env. for example
On Monday 13 April 2009 06:15:24 Wolfgang Denk wrote:
> In message Mike wrote:
> > currently the env code will erase the entire env storage before writing
> > back out the current env, even if the env storage has enough empty space
> > to store the current env. for example, if CONFIG_ENV_SIZE is d
Dear Mike,
In message <200904130609.08060.vap...@gentoo.org> you wrote:
>
> currently the env code will erase the entire env storage before writing back
> out the current env, even if the env storage has enough empty space to store
> the current env. for example, if CONFIG_ENV_SIZE is declared
currently the env code will erase the entire env storage before writing back
out the current env, even if the env storage has enough empty space to store
the current env. for example, if CONFIG_ENV_SIZE is declared as 0x2000 but
the current env only takes up ~0x300 bytes, the whole 0x2000 is er
50 matches
Mail list logo
