| Age | Commit message (Collapse) | Author |
|---|
|
DIU doesn't work on P1022DS RevB1 board in u-boot, it is because
there are two code bugs in DIU code.
1) We must clear the PMUXCR[eLBC_DIU] bits before we set the
eLBC_DIU=2'b01 for DIU mode.
The PMUXCR[eLBC_DIU] POR value is 2'b10 in RevB1 board, however
the eLBC_DIU is 2'b00 in RevA board due to design issue.
2) We must do dummy read to make sure the write FPGA PIXIS register
be completed.
Signed-off-by: Dave Liu <daveliu@freescale.com>
|
|
This patch enables DDR_SDRAM_CFG[HSE] for P1022DS.
This is needed mainly for higher frequencies but can
be left on for < 800MHz DDR frequency.
Disabled DDR_SDRAM_CFG[2T_EN] for 800MHz operation.
Also added debug prints for additional ddr registers.
Tested with the Hynix HMT125U7BFR8C-H9 and ELPIDA EBJ21EE8BAFA-DJ-E,
passed at 667MT/s or 800MT/s.
Tested-by: Jiang Yutang <B14898@freescale.com>
Signed-off-by: Srikanth Srinivasan <srikanth.srinivasan@freescale.com>
|
|
Enable ZQ calibration control by default for DDR3
for FSL DDRC driver.
Signed-off-by: Srikanth Srinivasan <srikanth.srinivasan@freescale.com>
|
|
For e500v2 toolchain, these IO read/write can't run rightly.
These patch has been built with e500mc and e500v2 toolchain, DIU can work.
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Signed-off-by: Dave Liu <daveliu@freescale.com>
|
|
FSL DIU (including DVI and LVDS) support
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Get the environment variable address
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Whether booting from MMC/SD card or not, the environment variables
can be saved on it, this patch add the operation support.
Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
|
|
If the environment variables are saved on the MMC/SD card,
env_relocat can't relocate env from MMC/SD card without mmc init.
Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
|
|
save the environment variable to eSDHC/eSPI
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Reset the eSDHC controller first before initialize the eSDHC controller.
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Enable the eLBC pads when booting from eSDHC
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Including boot from eSDHC and eSPI.
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
This patch is from MPC8536, and fixed some hunk failed error.
Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
Singed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
eSPI support for p1022ds
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
The max clock of MMC is 52MHz, and the clock mask is wrong.
Therefore, fixed them.
Signed-off-by: Jerry Huang <Changm-Ming.Huang@freescale.com>
|
|
Auto CMD12 command support for P1022DS eSDHC driver.
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
Multiple block read support
Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
|
|
1. Modified the tsec_mdio structure to include the new regs
2. Modified the MDIO_BASE_ADDR so that it will handle both
older version and new version of etsec.
Signed-off-by: Sandeep Kumar <Sandeep.Kumar@freescale.com>
|
|
Moved the mdio regs out of the tsec structure,and
provided different offsets for tsec base and mdio
base so that provision for etsec2.0 can be provided.
This patch helps in providing the support for etsec2.0
In etsec2.0, the MDIO register space and the etsec reg
space are different.
Also, moved the TSEC_BASE_ADDR and MDIO_BASE_ADDR definitons into
platform specific files.
Signed-off-by: Sandeep Kumar <Sandeep.Kumar@freescale.com>
|
|
In Rev 1.0 of P1022, in the esdhc Host Capabilities register
the 1.8V bit is set; it should not be. So we exclude this
setting in the driver.
Signed-off-by: Srikanth Srinivasan <srikanth.srinivasan@freescale.com>
|
|
On P1022, the data snoop bit (in the sata ip) is at bit 28.
Account for this. Additionally, change the mode to enterprise mode
since on reset, it is in legacy mode.
Signed-off-by: Srikanth Srinivasan <srikanth.srinivasan@freescale.com>
|
|
This patch adds support for P1022DS to u-boot. The following items
have been tested - DDR (spd-based), I2C, Flash, Vetsec1, 2, DIU,
PEX 1,2,3.
Signed-off-by: Srikanth Srinivasan <srikanth.srinivasan@freescale.com>
|
|
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
The gd->cpu pointer is set to an address located in flash when the
probecpu() function is called while U-Boot is executing from flash.
This pointer needs to be updated to point to an address in RAM after
relocation has occurred otherwise Linux may not be able to boot due to
"fdt board" crashing if flash has been erased or changed.
This bug was introduced in commit
a0e2066f392782730f0398095e583c87812d97f2.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Reported-by: Ed Swarthout <Ed.Swarthout@freescale.com>
Tested-by: Kumar Gala <galak@kernel.crashing.org>
Tested on MPC8527DS.
Tested by: Ed Swarthout <Ed.Swarthout@freescale.com>
|
|
Neither the MVBLUE nor its underlying architecture implement the
do_irqinfo() function which is required when CONFIG_CMD_IRQ is defined.
This change fixes the following MVBLUE compiler error:
-> ./MAKEALL MVBLUE
Configuring for MVBLUE board...
common/libcommon.a(cmd_irq.o):(.u_boot_cmd+0x24): undefined reference to `do_irqinfo'
make: *** [u-boot] Error 1
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Acked-by: Andre Schwarz <andre.schwarz@matrix-vision.de>
|
|
The support for this was silently dropped by a configuration
split during the merge of the imx27lite board support in commit
864aa034f3a0e10ce710e8bbda171df3cab59414 (cmd_mtdparts: Move to common
handling of FLASH devices via MTD layer).
Signed-off-by: Detlev Zundel <dzu@denx.de>
|
|
Currently, the last block of NAND devices can't be accessed. This patch
fixes this issue by correcting the boundary checking (off-by-one error).
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Scott Wood <scottwood@freescale.com>
Cc: Wolfgang Denk <wd@denx.de>
|
|
Commit c7190f02 (retain POR values of non-configured ACR, SPCR, SCCR,
and LCRR bitfields) moved the LCRR assignment to after relocation
to RAM because of the potential problem with changing the local bus
clock while executing from flash.
This change unfortunately adversely affects the boot time, as running
all code up to cpu_init_r can cause significant slowdown.
E.G. on a 8347 board a bootup time increase of ~600ms has been observed:
0.020 CPU: e300c1, MPC8347_PBGA_EA, Rev: 3.0 at 400 MHz, CSB: 266.667 MHz
0.168 RS: 232
0.172 I2C: ready
0.176 DRAM: 64 MB
1.236 FLASH: 32 MB
Versus:
0.016 CPU: e300c1, MPC8347_PBGA_EA, Rev: 3.0 at 400 MHz, CSB: 266.667 MHz
0.092 RS: 232
0.092 I2C: ready
0.096 DRAM: 64 MB
0.644 FLASH: 32 MB
So far no boards have needed the late LCRR setup, so simply revert it
for now - If it is needed at a later time, those boards can either do
their own final LCRR setup in board code (E.G. in board_early_init_r),
or we can introduce a CONFIG_SYS_LCRR_LATE config option to only do
the setup in cpu_init_r.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
|
|
We are using generic implementation of ffs. This should
be part of Simon's commit 0413cfecea350000eab5e591a0965c3e3ee0ff00
Here is warning message which this patch removes.
In file included from /tmp/u-boot-microblaze/include/common.h:38,
from cmd_mtdparts.c:87:
/tmp/u-boot-microblaze/include/linux/bitops.h:123:1: warning: "ffs" redefined
In file included from /tmp/u-boot-microblaze/include/linux/bitops.h:110,
from /tmp/u-boot-microblaze/include/common.h:38,
from cmd_mtdparts.c:87:
/tmp/u-boot-microblaze/include/asm/bitops.h:269:1:
warning: this is the location of the previous definition
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
A typo caused the stack and malloc regions to overlap, which prevented
mem_malloc_init() from returning. This commit makes the memory layout match
the example described in include/configs/microblaze-generic.h
Signed-off-by: Graeme Smecher <graeme.smecher@mail.mcgill.ca>
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
Previously MAKEALL would always return a value of 0, even if 1 or more
boards did not compile. This change causes MAKEALL to return 0 if all
boards were able to build, otherwise 1.
This change also requires changing the script interpreter from sh to
bash to support bash's PIPESTATUS variable.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
|
|
Recent commits 1a99de2cb4d08eb3bf9fb3f60a9d533150de8c0e and
6a590c5f5fd12cdd27f3153522acfac3854590e7 both fixed the same bug in the
same manner. Unfortunately git was "smart" enough to merge both changes
which resulted in some duplicate code.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Reordered code and comment a bit.
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
commit bd3784df94bfeca43fbf34094df9cb1bd3ecca3b deleted some unused
code in do_i2c_mw(), but missed to also remove the respective
commment. This patch fixes this.
Signed-off-by: Heiko Schocher <hs@denx.de>
|
|
To update the real memory size in the memory node on the
uc101 and mucmc52 boards call fdt_fixup_memory() in
ft_board_setup().
Signed-off-by: Heiko Schocher <hs@denx.de>
|
|
Depending on offset, flash size and the number of bad blocks,
get_len_incl_bad may return a too small value which may lead to:
1) If there are no bad blocks, nand_{read,write}_skip_bad chooses the
bad block aware read/write code. This may hurt performance, but does
not have any adverse effects.
2) If there are bad blocks, the nand_{read,write}_skip_bad may choose
the bad block unaware read/write code (if len_incl_bad == *length)
which leads to corrupted data.
Signed-off-by: Daniel Hobi <daniel.hobi@schmid-telecom.ch>
|
|
- NfsTimeout() does not correctly update the NFS timeout value which
results in NfsTimeout() only being called once in certain situations.
This can result in the 'nfs' command hanging indefinetly. For
example, the command:
nfs 192.168.0.1:/home/user/file
will not exit until ctrl-c is pressed if 192.168.0.1 does not have an
NFS server running.
This issue is resolved by reinitializting the NFS timeout value inside
NfsTimeout() when a timeout occurs.
- Make the 'nfs' command print the 'T' character when a timeout occurs.
Previously there was no indication that timeouts were occuring.
- Mimic the 'tftpboot' command and when a download fails print "Retry
count exceeded; starting again", and restart the download taking the
'netretry' environment variable into account.
Signed-off-by: Evan Samanas <esamanas@xes-inc.com>
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Tested on TQM8xxL.
Tested by: Wolfgang Denk <wd@denx.de>
Tested on MPC8527DS.
Tested by: Ed Swarthout <Ed.Swarthout@freescale.com>
|
|
The help message for the 'bootm' command listed the 'cmdline' and 'bdt'
sub-commands in the wrong order which resulted in the error below when
following the 'help' command's instructions:
"Trying to execute a command out of order"
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
|
|
"nandecc" help output should not reproduce the command name, nor have
a trailing newline.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
|
|
Since commit 736fead8fdbf8a8407048bebc373cd551d01ec98 "Convert SMC911X
Ethernet driver to CONFIG_NET_MULTI API" SMC911X configration options
are called CONFIG_SMC911X rather than CONFIG_DRIVER_SMC911X. Update
README to reflect that change.
Signed-off-by: Mike Rapoport <mike@compulab.co.il>
|
|
Signed-off-by: Mike Rapoport <mike@compulab.co.il>
|
|
An off by one error may cause nfs readlink lookup fail if
nfs_path_buff has non-zero data from a previous use.
Loading: *** ERROR: File lookup fail
Signed-off-by: Ed Swarthout <Ed.Swarthout@freescale.com>
|
|
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
Commit dce3d79710 updated the zlib code to v0.95; this caused
conflicts when building for the "cradle" board, because the (pretty
generic) preprocessor variable "OFF" was used in multiple files.
Make sure to avoid further conflicts by #undef'ing it in zlib.c
before redefining it.
Signed-off-by: Wolfgang Denk <wd@denx.de>
cc: Giuseppe Condorelli <giuseppe.condorelli@st.com>
cc: Angelo Castello <angelo.castello@st.com>
cc: Alessandro Rubini <rubini-list@gnudd.com>
|
|
Signed-off-by: Wolfgang Denk <wd@denx.de>
|
|
The Linux kernel build system changed how it compresses things with LZMA
such that the header no longer contains the filesize (it is instead set to
all F's). So if we get a LZMA image that has -1 for the 64bit field,
let's just assume that the decompressed size is unknown and continue on.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
Two later additions to the Configuration Option section unfortunately
split the description of Show boot progress and the list of its call outs.
Signed-off-by: Detlev Zundel <dzu@denx.de>
|
