Re: [U-Boot-Users] ramdisk problem (once again?)

>Upload of kernel: tftp 0x26 linux.uboot >Upload of fs:tftp 0x3a root.uboot >Environment: >=> printenv >bootcmd=run bootflash >bootdelay=3 >baudrate=115200 >eth1addr=00:02:b3:02:02:02 >kernel_addr=5006 >ramdisk_addr=501A >bootflash=bootm $(kernel_addr) >stdin=serial >stdo

Re: [U-Boot-Users] FW: [PATCH][ARM] Rationalize ARM compiler options

> In message <[EMAIL PROTECTED]> you wrote: >> >> >> If so I'll put -msoft-float in all arm config.mk files. >> >> Please DON'T! >> This *forces* you to compile U-Boot with a compiler suite which is >> configured to generate soft-float. > > I think this is not correct. Even if your compiler is n

[U-Boot-Users] u-boot for MPC5121e

hi, Can i get u-boot source code configured for MPC5121e eval board..? thanks, Nethra -- View this message in context: http://www.nabble.com/u-boot-for-MPC5121e-tp15583126p15583126.html Sent from the Uboot - Users mailing list archive at Nabble.com. -

[U-Boot-Users] [PATCH] 85xx: Don't icbi when unlocking the cache

There is no reason to icbi when invalidating the temporary stack in the d-cache. Its impossible on e500 to have the i-cache contain any addresses in the temp stack and it can be problematic in generating transactions on the bus to non-valid addresses. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>

[U-Boot-Users] [PATCH 6/9] [new uImage] Introduce lmb from linux kernel for memory mgmt of boot images

Introduce the LMB lib used on PPC in the kernel as a clean way to manage the memory spaces used by various boot images and structures. This code will allow us to simplify the code in bootm and its support functions. Also, added passing autostart flag to bootm functions. This was done since the f

[U-Boot-Users] [PATCH 7/9] [new uImage] Use lmb for bootm allocations

Convert generic ramdisk_high(), get_boot_cmdline(), get_boot_kbd() functions over to using lmb for allocation of the ramdisk, command line and kernel bd info. Convert PPC specific get_fdt() to use lmb for allocation of the device tree. Provided a weak function that board code can call to do addit

[U-Boot-Users] [PATCH 9/9] [new uImage] Respect autostart setting in linux bootm

Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- lib_arm/bootm.c|3 +++ lib_avr32/bootm.c |3 +++ lib_blackfin/bootm.c |3 +++ lib_i386/bootm.c |3 +++ lib_m68k/bootm.c |5 - lib_microblaze/bootm.c |3 +++ lib_mips/bootm.c |3 +++ l

[U-Boot-Users] [PATCH 8/9] [new uImage] Provide ability to restrict region used for boot images

Allow the user to set 'bootm_low' and 'bootm_size' env vars as a way to restrict what memory range is used for bootm. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- common/cmd_bootm.c | 10 +- common/image.c | 26 ++ include/image.h|2 ++ lib_m68

[U-Boot-Users] [PATCH 4/9] [new uImage] rework error handling so common functions don't reset

Changed image_get_ramdisk() to just return NULL on error and have get_ramdisk() propogate that error to the caller. It's left to the caller to call do_reset() if it wants to. Also moved calling do_reset() in get_fdt() on ppc to a common location. In the future we will change get_fdt() to return s

[U-Boot-Users] [PATCH 5/9] [new uImage] ppc: Allow boards to specify effective amount of memory

For historical reasons we limited the stack to 256M because some boards could only map that much via BATS. However newer boards are capable of mapping more memory (for example 85xx is capable of doing up to 2G). Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- lib_ppc/board.c | 22 +++

[U-Boot-Users] [PATCH 3/9] [new uImage] ppc: Re-order ramdisk/fdt handling sequence

Doing the fdt before the ramdisk allows us to grow the fdt w/o concern however it does mean we have to go in and fixup the initrd info since we don't know where it will be. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- lib_ppc/bootm.c | 39 +++ 1 files ch

[U-Boot-Users] [PATCH 0/9] [new uImage] Add support for booting images at non-zero addresses

This is an updated set of patches that clean up some of the code in the new uImage branch of u-boot-testing and add the ability to boot images at non-zero addresses and constrain the locations the boot images use on PPC hosts. This work is also availabie in the new-image branch of: git://g

[U-Boot-Users] [PATCH 1/9] [new uImage] Don't pass kdb to ramdisk_high since we may not have one

We don't actually need the kdb param as we are just using it to get bd->bi_memsize which we can get from gd->bd->bi_memsize. Also, if we boot via OF we might not actually fill out a kdb. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- common/image.c |9 - include/image.h |2

[U-Boot-Users] [PATCH 2/9] [new uImage] ppc: Determine if we are booting an OF style

If we are bootin OF style than we can skip setting up some things that are used for the old boot method. Signed-off-by: Kumar Gala <[EMAIL PROTECTED]> --- lib_ppc/bootm.c | 25 - 1 files changed, 20 insertions(+), 5 deletions(-) diff --git a/lib_ppc/bootm.c b/lib_ppc/bo

[U-Boot-Users] read from serial port

Hi, I'm using u-boot-1.2.0 and want to know if there is easy way to read serial port. So here's what i'm trying to achieve, 1) my commands get called based on user's input on the serial port. but there on after as the my command i interactive i would want to read users input on the serial por

Re: [U-Boot-Users] U-boot Bus Fault Error while accessing NOR flash

On Tuesday 19 February 2008, Nikhil Gautam wrote: > Thanks for the information. My problem is that "md 0xE000" and any > other read command up to this address works fine. Its just when I try > to read @ 0x F000 I see this problem. This problem with accessing the last 4k after NAND booting

Re: [U-Boot-Users] U-boot Bus Fault Error while accessing NOR flash

Hi HTH, Thanks for the information. My problem is that "md 0xE000" and any other read command up to this address works fine. Its just when I try to read @ 0x F000 I see this problem. I didn't see any obvious problem with the global and static initialization. Nikhil > > Hi Nikhil, > > If

[U-Boot-Users] [PATCH] 8610HPCD: Fix typos in two PCI setup registers.

The two symbols MPC86xx_PORDEVSR_IO_SEL and MPC86xx_PORBMSR_HA were erroneously present as 85xx names and values, leftover from the clone wars. Fix this by removing the 85xx cruft from the 86xx codebase. Signed-off-by: Jon Loeliger <[EMAIL PROTECTED]> --- Wolfgang, I'll drop this in the -mpc86x

Re: [U-Boot-Users] [PATCH 1/2] NET: Add Vitesse VSC7385 firmware uploading

Ben Warren wrote: > Acked-by: Ben Warren <[EMAIL PROTECTED]> > > Kim - would you mind pulling this into your tree? Best to keep it with > part 2. FYI, if the 83xx part is applied without the NET part, all 83xx platforms with the 7385 will fail to compile. -- Timur Tabi Linux kernel developer

Re: [U-Boot-Users] FW: FW: [PATCH][ARM] Rationalize ARM compiler options

Dear Peter, in message <[EMAIL PROTECTED]> you wrote: > > My postion remains that U-Boot is supplied to build with the > latest ELDK toolchain. > Supporting all possible toolchains (and all possible builds > of those toolchains) is too much effort. I disagree here. We should really try (as

Re: [U-Boot-Users] FW: [PATCH][ARM] Rationalize ARM compiler options

In message <[EMAIL PROTECTED]> you wrote: > > >> If so I'll put -msoft-float in all arm config.mk files. > > Please DON'T! > This *forces* you to compile U-Boot with a compiler suite which is > configured to generate soft-float. I think this is not correct. Even if your compiler is not configure

Re: [U-Boot-Users] Au1550 U-boot debugging - a newbie question

RadekFisera wrote: > I'm using U-boot 1.3.0. The hardware breakpoint option is set in BDI2000 > configuration file in target part (initial memory controller registers > settings is also in this file) > [TARGET] > JTAGCLOCK 0 ;use 16 MHz JTAG clock > CPUTYPE AU1000;

[U-Boot-Users] FW: FW: [PATCH][ARM] Rationalize ARM compiler options

> -Original Message- > From: Peter Pearse [mailto:[EMAIL PROTECTED] > Sent: 19 February 2008 08:55 > To: 'Ulf Samuelsson' > Subject: RE: [U-Boot-Users] FW: [PATCH][ARM] Rationalize ARM > compiler options > > > -Original Message- > > From: Ulf Samuelsson [mailto:[EMAIL PROTECTE

Re: [U-Boot-Users] disable "." when ext2load

Ok, it works ! Thanks a lot Pierre -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de [EMAIL PROTECTED] Envoyé : lundi 18 février 2008 20:08 À : u-boot-users@lists.sourceforge.net Objet : Re: [U-Boot-Users] disable "." when ext2load > "U-Boot > ext2load mm