On Sunday 06 March 2011 13:13:30 Fawaz wrote:
This patch adds another build target for the AMCC Canyonlands
PPC460Ex eval board. Using JTAG debugger(e.g. BDI2000/3000) configured
to setup the SDRAM.
here are TLB entries required by RAM-u-boot (for BDI2000/3000):
WTLB 0x0095
This is the mail system at host mx01.topica.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your
On Tuesday 08 March 2011 03:42 PM, Po-Yu Chuang wrote:
Hi Aneesh,
[snip ..]
+ __flash_image_end = .;
+
.bss __rel_dyn_start (OVERLAY) : {
__bss_start = .;
*(.bss)
There is a patch series which makes _end as end of image and
has been applied
make default implementation of cache_flush() weakly linked so that
sub-architectures can override it
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/lib/cache.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/arm/lib/cache.c b/arch/arm/lib/cache.c
index
With D-cache and MMU enabled for ARM in u-boot it becomes imperative to
support a minimal set of cache maintenance operations and necessary
initializations before enabling MMU.
This series of patches attempt to do the following for armv7:
* Necessary initialization sequence before enabling MMU
add utility macros for:
* bit field operations
* log2n functions
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/include/asm/utils.h | 80 ++
1 files changed, 80 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/include/asm/utils.h
diff
adapt s5pc1xx to the new layered cache maintenance framework
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/cpu/armv7/s5pc1xx/cache.S| 88 ++---
arch/arm/include/asm/arch-s5pc1xx/sys_proto.h |3 -
2 files changed, 7 insertions(+), 84 deletions(-)
diff
1. make sure that page table setup is not done multiple times
2. flush_dcache_all() is more appropriate while disabling cache
than a range flush on the entire memory(flush_cache())
Provide a default implementation for flush_dcache_all()
for backward compatibility and to avoid build
- Enable I-cache on bootup
- Enable MMU and D-cache immediately after relocation
- Do necessary initialization before enabling d-cache and MMU
- Changes to cleanup_before_linux()
- Make changes according to the new framework
Signed-off-by: Aneesh V ane...@ti.com
---
replace all occurences of CONFIG_L2_OFF with a more appropriate
CONFIG_SYS_NO_L2CACHE
CONFIG_SYS_NO_L2CACHE has been chosen to be in line with
CONFIG_SYS_NO_ICACHE and CONFIG_SYS_NO_DCACHE
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/cpu/armv7/cpu.c|6 +-
adapt omap3 to the new layered cache maintenance framework
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/cpu/armv7/omap3/Makefile |1 -
arch/arm/cpu/armv7/omap3/board.c| 138 --
arch/arm/cpu/armv7/omap3/cache.S| 263
- Add a framework for layered cache maintenance
- separate out SOC specific outer cache maintenance from
maintenance of caches known to CPU
- Add generic ARMv7 cache maintenance operations that affect all
caches known to ARMv7 CPUs. For instance in Cortex-A8 these
opertions
adapt omap4 to the new layered cache maintenance framework
Signed-off-by: Aneesh V ane...@ti.com
---
arch/arm/cpu/armv7/omap4/lowlevel_init.S| 18 ++
arch/arm/include/asm/arch-omap4/sys_proto.h |1 -
include/configs/omap4_panda.h |8 +---
PL310 is the L2$ controller from ARM used in many SoCs
including the Cortex-A9 based OMAP4430
Add support for some of the key PL310 operations
- Invalidate all
- Invalidate range
- Flush(clean invalidate) all
- Flush range
Signed-off-by: Aneesh V ane...@ti.com
Hello,
as I am actual trying to get the keymile boards in sync with actual
mainline u-boot, I faced the following Problem with an Intel Strata
Flash on the mgcoge (mpc8247 based board):
I couldn;t unprotect/erase/write/protect some (not all!) Flash sectors.
For Example, I could do this without
Normaly the PIGGY_MAC_ADRESS can be read directly from the
IVM on keymile boards. On mgcoge3 it differs. Because there
are two piggy boards deployed the second MAC adress must be
calculated with the IVM mac adress and an offset. This patch
allows to set such a offset in the board config.
From: Thomas Herzmann thomas.herzm...@keymile.com
In order to support boardId / hwkey lists, the u-boot default
environment has been updated: Added a script checkboardidlist
which checks the list of boardId / hwkey if the boadrId / hwkey
of the IVM is included in that list. This feature is used
This board is similar to keymile suen3.
Signed-off-by: Clive Stubbings clive.stubbi...@xentech.co.uk
Signed-off-by: Holger Brunck holger.bru...@keymile.com
Signed-off-by: Heiko Schocher h...@denx.de
cc: Prafulla Wadaskar prafu...@marvell.com
---
MAINTAINERS |1 +
boards.cfg
The Keymile SUPx5 board series is based on a PBEC8321 but
contains an additional PBUS FPGA (LPXF) on local bus CS2.
Signed-off-by: Thomas Reufer thomas.reu...@keymile.com
Signed-off-by: Heiko Schocher h...@denx.de
cc: Wolfgang Denk w...@denx.de
cc: Kim Phillips kim.phill...@freescale.com
cc:
The Kirwood based SUEN8 board from Keymile is at this stage
the same than the suen3 board. This patch adds the board
support for the suen8.
Signed-off-by: Holger Brunck holger.bru...@keymile.com
Signed-off-by: Heiko Schocher h...@denx.de
cc: Prafulla Wadaskar prafu...@marvell.com
---
MAINTAINERS
These new values were given by Clive Stubbings from Xentech.
According to him they should be used on all bobcat designs.
The changes are the following:
- enables UART0 and UART1 pins in MPP
- define some L2 cache settings
- changes a SDRAM timing to better fit the hardware
- removed three writes
From: Holger Brunck holger.bru...@keymile.com
Add:
- introduce bootrunner environment variable
This allows to execute consecutive different commands
specified in the list subbootcmd. If one command fails
the command serie will stop.
- introduce environment variable develop, ramfs
This patch renames the suen3 defines and functions to suenx
which is more generic and more precise, because these values
and functions where used by all suenX boards and not only sune3.
Signed-off-by: Lukas Roggli lukas.rog...@keymile.com
Signed-off-by: Valentin Longchamp
The following patchset updates the support for the keymile
boards.
- heavy rework of the headerfiles, common board code
- add support for 4 new mpc83xx based boards
- add support for 1 82xx based board
- add support for 2 new kirkwood based boards
- fix i2c deblocking for this boards
Patch
define KM_IVM_BUS and KM_ENV_BUS macros
KM_IVM_BUS is used to define the EEprom_ivm environment variable.
These macros allow the reuse of these I2C addresses in other code
locations.
remove unneeded code
On first HW versions the BOCO FPGA was behind a MUX device. These
HW versions are not
From: Huber, Andreas andreas.hu...@keymile.com
This reads the DIP switch register in the BFTICU (0x4089). If 'Full reset'
or 'DB erase' is selected, 'actual_bank' is set to 0. This loads the Bootloader
application who does the erase stuff.
Signed-off-by: Andreas Huber
This board is similar to suvd3 board. So most initialisation topics
are taken from suvd3 (UART1, Ethernet, piggy PHY, flash, ram) only the
application specific chip selects differ.
Signed-off-by: Lukas Roggli lukas.rog...@keymile.com
Signed-off-by: Holger Brunck holger.bru...@keymile.com
This patch fix the i2c deblocking facility with the i2c HW-Controller.
The required delays for byte reading, the enhanced criteria for stop
the dummy read and required 5 start/stop sequences are added.
Add i2c deblocking before ivm eeprom read.
Improve i2c deblocking sequence by respecting stop
- serial console on UART1
- Ethernet RMII over UCC4
- PHY SMSC LAN8700
- 64MB Flash
- 128 MB DDR2 RAM
- I2C
- bootcount
This board is similiar to the kmeter1 (8360) board,
so common config options are extracted into the
include/configs/km83xx-common.h file.
Signed-off-by: Heiko Schocher
- This patch reworks all headerfiles for keymile boards (coge, supx4,
eter1, suen3).
Furthermore, a refactoring on the whole environment variables has been
acomplished.
- Environment variables:
- grouped into logical blocks (#defines) based on the functionality/purpose
- short
From: Holger Brunck holger.bru...@keymile.com
Signed-off-by: Holger Brunck holger.bru...@keymile.com
cc: Wolfgang Denk w...@denx.de
cc: Valentin Longchamp valentin.longch...@keymile.com
cc: Heiko Schocher h...@denx.de
---
include/configs/keymile-common.h |9 +++--
1 files changed, 3
This board is similar to suvd3 board. So most initialisation topics
are taken from suvd3 (UART1, Ethernet, piggy PHY, flash, ram) only the
application specific chip selects differ.
Signed-off-by: Lukas Roggli lukas.rog...@keymile.com
Signed-off-by: Holger Brunck holger.bru...@keymile.com
This patch adds last_stage_init to all keymile boards. And
in the last stage init some environment variables for u-boot
were set. Currently these are pnvramaddr, pram and var address.
Signed-off-by: Holger Brunck holger.bru...@keymile.com
Signed-off-by: Heiko Schocher h...@denx.de
cc: Valentin
From: Thomas Reufer thomas.reu...@keymile.com
First step for a cleanup of all header files for km8321 boards.
Signed-off-by: Thomas Reufer thomas.reu...@keymile.com
cc: Wolfgang Denk w...@denx.de
cc: Kim Phillips kim.phill...@freescale.com
cc: Valentin Longchamp valentin.longch...@keymile.com
The mgcoge2 board from keymile deploys two different porcessors.
An ARM based Kirkwood for the unit part of the SW and a PPC for
the ne part of the SW. Therefore in Linux and U-Boot the names
for the board are mgcoge2un and mgcoge2ne. This patch adds the
mgcoge2ne part of the board. The ppc part
For the kmsupx5 a new header file was introduced km8321-common.h.
Now the common stuff from tuxa1, tuda1 and suvd3 was removed and
the new header file included.
The defines CONFIG_SYS_PIGGY_BASE and CONFIG_SYS_PIGGY_SIZE are
confusing. Because they actually describe the KMBEC FPGA values.
The
Flash address on Microblaze systems could be on higher
addresses then ram. This patch fixed this assumption
and flash can be located on any address.
Signed-off-by: Michal Simek mon...@monstr.eu
---
arch/microblaze/lib/board.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
Add the first axi_ethernet driver for little-endian Microblaze.
Signed-off-by: Michal Simek mon...@monstr.eu
---
v2:
- Fix return addreses
- Fix NULL pointer defer for priv structure
---
.../xilinx/microblaze-generic/microblaze-generic.c |4 +
drivers/net/Makefile
Fix return values for initialize/init/recv/send functions
Signed-off-by: Michal Simek mon...@monstr.eu
---
drivers/net/xilinx_emaclite.c | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/xilinx_emaclite.c b/drivers/net/xilinx_emaclite.c
index
Hello Heiko,
On Tue, Mar 08, 2011 at 02:08:26PM +0100, Heiko Schocher wrote:
Hello,
as I am actual trying to get the keymile boards in sync with actual
mainline u-boot, I faced the following Problem with an Intel Strata
Flash on the mgcoge (mpc8247 based board):
I couldn;t
Hi Kyle,
Kyle Moffett wrote:
The Nios-II port appears to use no generic hardware capability for
performing a CPU reset. Since all of the supported boards use the exact
same code to perform a jump-to-flash it goes into __arch_restart().
This means that Nios-II has a no-op
Hi!
On Mar 08, 2011, at 19:13, Scott McNutt wrote:
Hi Kyle,
Kyle Moffett wrote:
The Nios-II port appears to use no generic hardware capability for
performing a CPU reset. Since all of the supported boards use the exact
same code to perform a jump-to-flash it goes into __arch_restart().
Moffett, Kyle D wrote:
Hi!
On Mar 08, 2011, at 19:13, Scott McNutt wrote:
Hi Kyle,
Kyle Moffett wrote:
The Nios-II port appears to use no generic hardware capability for
performing a CPU reset. Since all of the supported boards use the exact
same code to perform a jump-to-flash it goes
Using u-boot-marvell.git, doing a make all
make[1]: Entering directory
`/src/IConnect/src/U-boot/u-boot-marvell.git/arch/arm/lib'
arm-gp2x-linux-gcc -g -Os -fno-common -ffixed-r8 -msoft-float
-D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x0100
On Mon, Feb 28, 2011 at 4:46 AM, Aneesh V ane...@ti.com wrote:
Calculate EMIF register values based on AC timing parameters
from the SDRAM datasheet and the DDR frequency rather than
using the hard-coded values.
For a new board the user doen't have to go through the tedious
process of
On Wednesday 09 March 2011 10:16 AM, John Rigby wrote:
On Mon, Feb 28, 2011 at 4:46 AM, Aneesh Vane...@ti.com wrote:
Calculate EMIF register values based on AC timing parameters
from the SDRAM datasheet and the DDR frequency rather than
using the hard-coded values.
For a new board the user
i m making crossmake on my host machine linux (x486/4.4.4) when i m in
process
of u boot compilation i found error given as bellow.
root@hamid:/home/u-boot-1.1.6# crossmake
for dir in tools examples post post/cpu ; do make -C $dir _depend ; done
make[1]: Entering directory
i m making crossmake on my host machine linux (x486/4.4.4) when i m in process
of u boot compilation i found error given as bellow.
root@hamid:/home/u-boot-1.1.6# crossmake
for dir in tools examples post post/cpu ; do make -C $dir _depend ; done
make[1]: Entering directory
On Sun, Mar 6, 2011 at 10:17 PM, Kumar Gala ga...@kernel.crashing.org wrote:
+ if (i2c_data 0x1) {
+ setbits_be32(gur-pmuxcr, MPC85xx_PMUXCR_SD_DATA);
+ puts(SD/MMC : 8-bit Mode\n);
+ puts(eSPI : Disabled\n);
+
Hello Philippe,
Philippe De Muyter wrote:
On Tue, Mar 08, 2011 at 02:08:26PM +0100, Heiko Schocher wrote:
Hello,
as I am actual trying to get the keymile boards in sync with actual
mainline u-boot, I faced the following Problem with an Intel Strata
Flash on the mgcoge (mpc8247 based board):
On Wednesday, March 09, 2011 00:58:23 mohd hamid khan wrote:
root@hamid:/home/u-boot-1.1.6# crossmake
two things:
- you're using u-boot-1.1.6 which is not supported. upgrade.
- crossmake has nothing to do with u-boot. ask whoever wrote it.
-mike
signature.asc
Description: This is a
On Friday, March 04, 2011 05:09:53 Michal Simek wrote:
Mike Frysinger wrote:
3. dev-init
return -1 - if init failed
return 0 - on success
ok
(here you are saying should be return # of devices)
no, i think you confused initialize with init in my feedback
ok. From my point
On Tuesday, March 08, 2011 09:25:52 Michal Simek wrote:
+int xilinx_axiemac_initialize(bd_t *bis, int base_addr, int dma_addr)
+{
+ struct eth_device *dev;
+ struct axidma_priv *dma;
+
+ dev = calloc(1, sizeof(struct eth_device));
+ if (dev == NULL)
+ return -1;
On Friday, March 04, 2011 05:09:53 Michal Simek wrote:
To finish this discuss - here is what you think that it is correct.
ad 2)
return -1 - if initialize failed
return 0 - never return
return 0 - # of devices
oh, and to clarify on the return 0, i think it's conceivable that if a
device
54 matches
Mail list logo
