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
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_m68k
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
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
the feature was removed as part of the new uImage cleanup and rather than
touching the bootm prototype twice (once for lmb and once for autostart) we
just do it once.
We don't actually use either the lmb or autostart flag with this patch.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
common
+ CFG_BOOTMAPSZ.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
common/cmd_bootm.c |8 +++
common/image.c | 134 ++-
include/image.h| 13 ++---
lib_m68k/bootm.c | 29
lib_ppc/bootm.c| 78 ++
5
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]
---
This patch superseded my previous
A few duplicate of the ARRAY_SIZE macro sneaked in since we put
the define in common.h.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
include/asm-ppc/fsl_law.h |1 -
include/asm-ppc/mmu.h |1 -
2 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/include/asm-ppc/fsl_law.h
the offset in
physical memory that the bootmap is located at. This is used for
allocations of the cmdline, kernel bd, and device tree as they should
be contained within bootmap_base and bootmap_base + CFG_BOOTMAPSZ.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
This requires the 'ppc: Allow boards
On Feb 15, 2008, at 1:29 AM, Mike Frysinger wrote:
On Friday 15 February 2008, Haavard Skinnemoen wrote:
Mike Frysinger [EMAIL PROTECTED] wrote:
if someone can tell me what the number of args are for each arch we
can see about providing this everywhere.
are you sure you actually need to
delete index - Delete a mem reserves
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
common/cmd_fdt.c | 111 ++
1 files changed, 111 insertions(+), 0 deletions(-)
diff --git a/common/cmd_fdt.c b/common/cmd_fdt.c
index 9cd22ee..d0f8c27
delete index - Delete a mem reserves
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
fix help white space
be more explicit in arg checking for memory vs memrsv
common/cmd_fdt.c | 112 ++
1 files changed, 112 insertions(+), 0 deletions
On Feb 15, 2008, at 8:09 AM, Jerry Van Baren wrote:
Kumar Gala wrote:
fdt header - Display header info
fdt bootcpu id- Set boot cpuid
fdt memory addr size- Add/Update memory node
fdt memrsv print- Show current mem
Do the fdt before the ramdisk allows us to grow the fdt w/o concern
however it does me we have to go in and fixup the initrd info since
we dont know where it will be.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
Patch against u-boot-testing new-image branch.
lib_ppc/bootm.c | 38
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]
---
patch against u-boot-testing new-image branch
lib_ppc/bootm.c | 25 -
1 files changed, 20 insertions(+), 5
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]
---
Patch against new-image u-boot-testing branch
common/image.c
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 capble of doing up to 2G).
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
lib_ppc/board.c |7 ++-
1
On Feb 15, 2008, at 3:44 PM, Jerry Van Baren wrote:
Kumar Gala wrote:
fdt header - Display header info
fdt bootcpu id- Set boot cpuid
fdt memory addr size- Add/Update memory node
fdt memrsv print- Show current mem
From e76f97d16c5932d19d698e42c6376d6bbdca2ecf Mon Sep 17 00:00:00 2001
From: Kumar Gala [EMAIL PROTECTED]
Date: Fri, 15 Feb 2008 03:34:36 -0600
Subject: [PATCH] Add sub-commands to fdt
fdt header - Display header info
fdt bootcpu id- Set boot cpuid
fdt
Does anyone have any bright ideas on how to know what the BSS size of
the kernel will be from a uImage. It seems we just hope and pray that
u-boot doesn't load things (ramdisk, bd_t, device tree, etc).
Clearly the new uImage work should encompass this information, but I'm
looking for ideas
On Feb 15, 2008, at 4:15 PM, Marcel Moolenaar wrote:
All,
I've just pulled the 1.3.2-rc1 snapshot from GIT and I run
into a link failure right out of the box (ok, after changing
the Makefile to the right cross-compiler :-)
Build machine: FreeBSD-6.1
apg-bbuild09% gmake distclean
find:
On Feb 15, 2008, at 5:14 PM, Marcel Moolenaar wrote:
On Feb 15, 2008, at 2:59 PM, Kumar Gala wrote:
On Feb 15, 2008, at 4:15 PM, Marcel Moolenaar wrote:
I've just pulled the 1.3.2-rc1 snapshot from GIT and I run
into a link failure right out of the box (ok, after changing
the Makefile
On Feb 14, 2008, at 6:41 AM, Jerry Van Baren wrote:
Kumar Gala wrote:
On Feb 13, 2008, at 5:07 PM, Wolfgang Denk wrote:
In message Pine.LNX. [EMAIL PROTECTED]
you wrote:
Add a simple expr style command that will set an env variable as
the result
of the command. This allows us to do
Add a simple expr style command that will set an env variable as the result
of the command. This allows us to do simple math in shell. The following
operations are supported: , |, ^, +, -, *, /.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
docs will be added online since that appears
On Feb 14, 2008, at 11:54 PM, Mike Frysinger wrote:
On Friday 15 February 2008, Kumar Gala wrote:
--- /dev/null
+++ b/lib_ppc/cmd_call.c
there's nothing ppc specific about this
I'm not familiar w/other architecture ABIs to say if that's true or
not. Clearly the upper limit may vary
r3)
void func(unsigned long r3, unsigned long r4)
...
void func(unsigned long r3, unsigned long r4, ... unsigned long r10)
The maximum number of 'arg's is 8. There are no arguments passed on
a stack, no floating point or vector arguments.
Signed-off-by: Kumar Gala [EMAIL PROTECTED
On Feb 13, 2008, at 4:11 AM, Bartlomiej Sieka wrote:
Kumar Gala wrote:
'imload' provides a more direct means to load from an image file.
Also created a load_image routine out of the code in do_bootm() that
is shared between do_bootm() and do_imload().
Signed-off-by: Kumar Gala [EMAIL
Add a simple expr command that will set an env variable as the result
of the command. This allows us to do simple math in shell. The following
operations are supported: , |, +, -, *, /.
---
I'd like to add this to the default command set in include/config_cmd_default.h
but wanted to get
On Feb 13, 2008, at 10:35 AM, Kim Phillips wrote:
On Wed, 13 Feb 2008 09:54:31 -0600 (CST)
Kumar Gala [EMAIL PROTECTED] wrote:
+}
+
+U_BOOT_CMD(
+expr, 5, 0, do_expr,
+expr- set environment variable as the result of eval
expression\n,
+name value1 op value2\n
On Feb 13, 2008, at 1:55 PM, Bartlomiej Sieka wrote:
Kumar Gala wrote:
On Feb 13, 2008, at 4:11 AM, Bartlomiej Sieka wrote:
Kumar Gala wrote:
'imload' provides a more direct means to load from an image file.
Also created a load_image routine out of the code in do_bootm()
that
is shared
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
Wolfgang, would like to see this go into mainline as it fixes building.
common/fdt_support.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/common/fdt_support.c b/common/fdt_support.c
index 92f1c7f..69eb667 100644
On Feb 13, 2008, at 4:31 PM, Wolfgang Denk wrote:
In message Pine.LNX.
[EMAIL PROTECTED] you wrote:
'imload' provides a more direct means to load from an image file.
What exactly is an image file here (which sorts of images are
allowed?) and what does load mean (which actions are
Add a simple expr style command that will set an env variable as the result
of the command. This allows us to do simple math in shell. The following
operations are supported: , |, ^, +, -, *, /.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
this was the expr patch, but renamed based
: , |, ^, +, -, *, /.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
this was the expr patch, but renamed based on comments on the list.
grumble
Well, *my* command was *not* to rename it.
sorry, saw your post after I sent this :)
/grumble
At least, please don't make it a default command
On Feb 13, 2008, at 5:01 PM, Wolfgang Denk wrote:
In message 7DB626E7-34A4-4EAA-B470-
[EMAIL PROTECTED] you wrote:
What exactly is an image file here (which sorts of images are
allowed?) and what does load mean (which actions are performed on
the file)?
its suppose to be a 'uImage' not
This patch is just a quick work up to see how to handle a particular
problem I've got. The idea is that I want finer control over what happens
when I 'go' to piece of code. The idea is it looks more like a native
function call than the current go which is more main() like.
The calling
On Feb 13, 2008, at 6:40 PM, Wolfgang Denk wrote:
In message Pine.LNX.
[EMAIL PROTECTED] you wrote:
This patch is just a quick work up to see how to handle a particular
problem I've got. The idea is that I want finer control over what
happens
when I 'go' to piece of code. The idea is
+switch (image_get_comp (hdr)) {
+case IH_COMP_NONE:
+if (dst == (ulong)hdr) {
+printf ( XIP %s ... , type_name);
This is an ugly hack in the old code that should be removed by the new
implementation.
can you explain this further, I'm happy to git
On Feb 12, 2008, at 4:59 PM, Wolfgang Denk wrote:
In message F8B63E55-0B77-44DD-
[EMAIL PROTECTED] you wrote:
For example, I don't believe we have a way today to just decompress a
uImage file.
Um... it you try hard enough there is one. See
Signed-off-by: James Yang [EMAIL PROTECTED]
Signed-off-by: Jon Loeliger [EMAIL PROTECTED]
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
in my git tree.
include/asm-ppc/immap_85xx.h | 25 +
1 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/include/asm
Yang
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
in my git tree.
cpu/mpc85xx/speed.c | 21 +
include/asm-ppc/global_data.h |2 --
2 files changed, 5 insertions(+), 18 deletions(-)
diff --git a/cpu/mpc85xx/speed.c b/cpu/mpc85xx/speed.c
index 952f30c..343316e
On Feb 7, 2008, at 10:15 AM, Bartlomiej Sieka wrote:
Kumar Gala wrote:
Here is a rough patch to common/cmd_bootm.c that passed load_end
down to
the do_bootm_* commands. I haven't updated the lib_*/bootm.c at this
point.
I think this is useful to help the bootm commands know exactly what
Here is a rough patch to common/cmd_bootm.c that passed load_end down to
the do_bootm_* commands. I haven't updated the lib_*/bootm.c at this
point.
I think this is useful to help the bootm commands know exactly what memory
is used and what is freed. There are situations that I'd like to get
On Feb 1, 2008, at 7:24 AM, Clemens Koller wrote:
Leonid schrieb:
Hi:
I am not new in u-boot, but this is the first time I must deal with
Freescale CPU, namely mpc8544 (I have been working so far with
Microblaze, ARM9, ppc440 and ppc405). My board is going to be very
close
to Interpid
Added the cpu command that provides a generic mechanism to get status,
reset, and release secondary cores in multicore processors.
Added support for using the ePAPR defined spin-table mechanism on 85xx.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
as usually, this is in the mpc85xx branch
On Jan 25, 2008, at 9:20 AM, Joakim Tjernlund wrote:
Seems to me that mpc83xx now needs to have alias nodes in dts to
assign
MAC addresses to eth devices when booting linux. Seems a bit
premature to drop the old way so soon.
Maybe I am missing something?
Maybe. but if you are going to
On Jan 23, 2008, at 8:43 AM, Marian Balakowicz wrote:
Hi,
This is a second patchset for new uImage, it includes architecture
file
renames, removals of OF_FLAT_TREE and standalone application support
and
further code refactoring.
This patchset is based on patchset1. MAKEALL was run
Here's an updated version based on Andy's ide of just having additional
[args] to release and letting that be handled by arch specific code.
Let me know if there are any other comments, if not.. I'll create a proper
patch for the 85xx maintainer tree for the next merge window.
- k
an example of
I was hoping to get some feed back on this patch that will add support for
booting the multiprocessor 85xx chips. The boot mechanism is based on the
forth coming ePAPR spec (based on how device tree, linux
booting-without-of spec).
The biggest feedback I'm hoping for is related to the command
On Jan 22, 2008, at 2:59 AM, Wolfgang Denk wrote:
In message Pine.LNX.
[EMAIL PROTECTED] you wrote:
I was hoping to get some feed back on this patch that will add
support for
booting the multiprocessor 85xx chips. The boot mechanism is based
on the
forth coming ePAPR spec (based on
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8544ds/Makefile |4 +-
board/freescale/mpc8544ds/init.S | 174 --
board/freescale/mpc8544ds/tlb.c | 99 +++
board/freescale/mpc8544ds/u-boot.lds |2 -
include
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8540ads/Makefile |3 +-
board/freescale/mpc8540ads/init.S | 212
board/freescale/mpc8540ads/tlb.c | 130
board/freescale/mpc8540ads/u-boot.lds |2 -
board
Move the flat device tree setup for QE related devices into
a common file shared between 83xx 85xx platforms that have QE's.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
common/fdt_support.c | 48 --
cpu/mpc83xx/fdt.c| 13 ++-
cpu/mpc85xx/fdt.c|8
Move the initialization of the LAWs into C code and provide an API
to allow modification of LAWs after init.
Board code is responsible to provide a law_table and num_law_entries.
We should be able to use the same code on 86xx as well.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
This whole
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8544ds/Makefile |2 +-
board/freescale/mpc8544ds/init.S | 48
board/freescale/mpc8544ds/law.c| 42 +++
include/configs/MPC8544DS.h|2 +
4
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8540ads/Makefile |3 +-
board/freescale/mpc8540ads/init.S | 53
board/freescale/mpc8540ads/law.c| 58 +++
board/freescale/mpc8560ads/Makefile |3
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8541cds/Makefile |2 +-
board/freescale/mpc8541cds/init.S | 51
board/freescale/mpc8541cds/law.c| 58 +++
board/freescale/mpc8548cds/Makefile |2 +-
board
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/sbc8548/Makefile|3 +-
board/sbc8548/init.S | 48
board/sbc8548/law.c | 57 ++
board/sbc8560/Makefile|3 +-
board/sbc8560/init.S
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/pm854/Makefile|3 +-
board/pm854/init.S | 53 --
board/pm854/law.c | 58 +++
board/pm856/Makefile|3 +-
board/pm856/init.S
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/stxgp3/Makefile|3 +-
board/stxgp3/init.S | 53
board/stxgp3/law.c | 58
board/stxssa/Makefile|2 +-
board/stxssa/init.S
All boards are now using the new fsl_law code so we can drop the old version.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
cpu/mpc85xx/spd_sdram.c | 10 --
cpu/mpc85xx/start.S | 18 --
2 files changed, 0 insertions(+), 28 deletions(-)
diff --git a/cpu/mpc85xx
We should be using the _MEM_PHYS for LAW and TLB setup and not _MEM_BASE.
While _MEM_BASE _MEM_PHYS are normally the same, _MEM_BASE should only
be used for configuring the PCI ATMU.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8540ads/init.S |8
board
Add a set of functions to manipulate TLB entries:
* set_tlb() - write a tlb entry
* invalidate_tlb() - invalidate a tlb array
* disable_tlb() - disable a variable size tlb entry
* init_tlbs() - setup initial tlbs based on static table
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
cpu
to 4G) must map to
the code that is currently executing.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
cpu/mpc85xx/cpu_init.c | 56 +++--
cpu/mpc85xx/start.S| 131 +++-
2 files changed, 115 insertions(+), 72 deletions(-)
diff
Move the initialization of the LAWs into C code and provide an API
to allow modification of LAWs after init.
Board code is responsible to provide a law_table and num_law_entries.
We should be able to use the same code on 86xx as well.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
In my git
201 - 265 of 265 matches
Mail list logo
