| Age | Commit message (Collapse) | Author |
|---|
|
New board has faster oscillator and a different Flash chip. This affects:
- CFG_MPC5XXX_CLKIN
- SDRAM timings
- Flash CS configuration (timings)
- Flash sector size, and thus MTD partition layout
- malloc() arena size (due to bigger Flash sectors)
- smaller memory test range (due to bigger malloc() arena)
This patch also enables more extensive memory testing via "mtest".
Signed-off-by: Bartlomiej Sieka <[email protected]>
|
|
Signed-off-by: Stefan Roese <[email protected]>
|
|
|
|
PHYSADDR is for physical address, KSEG1ADDR is for uncached.
Signed-off-by: Vlad Lungu <[email protected]>
Signed-off-by: Shinya Kuribayashi <[email protected]>
|
|
|
|
|
|
On the MPC85xx CDS we have two issues:
1. The device tree fixup code did not check to see if the property we are
trying to update is actually found. Its possible that it would update
random memory starting at 0.
2. Newer Linux kernel's have moved the location of the PCI nodes to be
sibilings of the soc node and not children. The explicit PATH to the PCI
node would not be found for these device trees. Add the ability to handle
both paths. In the future we shouldn't handle such fixups by explicit path.
Signed-off-by: Kumar Gala <[email protected]>
|
|
On the MPC8568 MDS we use ttyS0, UART0, etc. as the standard configured
console. Make it so we match that config what we tell Linux as the early
STDOUT console.
Signed-off-by: Kumar Gala <[email protected]>
|
|
Signed-off-by: Ed Swarthout <[email protected]>
Signed-off-by: Mahesh Jade <[email protected]>
Signed-off-by: Jason Jin <[email protected]>
Signed-off-by: Jon Loeliger <[email protected]>
|
|
Signed-off-by: Runet Torgersen <[email protected]>
|
|
The BCSR status bit for the 66MHz PCI operation was correctly
addressed (MSB/LSB problem). Now the correct currently setup
PCI frequency is displayed upon bootup.
This patch also fixes this problem on Rainier & Yellowstone, since these
boards use the same souce code as Sequoia & Yosemite do.
Signed-off-by: Stefan Roese <[email protected]>
|
|
Adjust flash map to support the new S29GLxxN (N-Type) Flashes with
doubled sector size.
Signed-off-by: Martin Krause <[email protected]>
|
|
At 133 MHz the current SDRAM refresh rate is too fast
(measured 4 * 1.17 us).
CFG_MAMR_PTA changes from 39 to 97. This result
in a refresh rate of 4 * 7.8 us at the default clock
50 MHz. At 133 MHz the value will be then 4 * 2.9 us.
This is a compromise until a new method is found to
adjust the refresh rate.
Signed-off-by: Martin Krause <[email protected]>
|
|
Adjust flash map to support the new S29GLxxN (N-Type) Flashes with
doubled sector size.
Signed-off-by: Martin Krause <[email protected]>
|
|
and remove code violation
|
|
|
|
|
|
|
|
Signed-off-by: Wolfgang Denk <[email protected]>
|
|
|
|
Signed-off-by: Wolfgang Denk <[email protected]>
|
|
|
|
|
|
|
|
Signed-off-by: Grzegorz Bernacki <[email protected]>
|
|
Signed-off-by: Marian Balakowicz <[email protected]>
|
|
|
|
CFG_MEMTEST_START uses weird magic involving gd, which fails to
compile. Use hardcoded values instead (we actually know how much RAM
we have on board.)
Signed-off-by: Haavard Skinnemoen <[email protected]>
|
|
|
|
Signed-off-by: Stefan Roese <[email protected]>
|
|
|
|
Signed-off-by: Stefan Roese <[email protected]>
|
|
|
|
because changing of command handling brings
compilation problems
|
|
Both codes are written by myself without any
support from CTU
|
|
because PowerPC 405 can use UartLite as console
|
|
|
|
|
|
Signed-off-by: Nobuhiro Iwamatsu <[email protected]>
|
|
Signed-off-by: Nobuhiro Iwamatsu <[email protected]>
|
|
Signed-off-by: Nobuhiro Iwamatsu <[email protected]>
|
|
Signed-off-by: Nobuhiro Iwamatsu <[email protected]>
|
|
Conflicts:
CREDITS
|
|
/bin/bash and /bin/dash (which /bin/sh is linked to on ubuntu) handle embedded
nulls in a string differently. For example, the following statement:
echo "this is a string\0" > afile
Will produce the following with /bin/bash:
"this is a string\0"
But with /bin/dash, will produce:
"this is a string
Bug fixed by moving the embedded null out of the makefile and into the
config header. Also renamed the macro to avoid usage colision with the same
macro used by other board ports.
Signed-off-by: Grant Likely <[email protected]>
|
|
Improve indentation in drivers/at45.c
|
|
|
|
Updates to atstk1002 U-Boot header file:
- Changed bootargs:
* Set the bootargs for at1002 to point to the SD-card partition instead
* ... of the boot flash.
* Removing the rootfstype since that argument are not needed.
Signed-off-by: Eirik Aanonsen <[email protected]>
Signed-off-by: Haavard Skinnemoen <[email protected]>
|
|
This patch applies some clarifying comments to how the different
clocks are setup according to atstk1002.h Some of the previous
comments where stating wrongful information.
Signed-off-by: Haavard Skinnemoen <[email protected]>
|
|
[PATCH 3/3] OneNAND support (take #2)
OneNAND support at U-Boot
Signed-off-by: Kyungmin Park <[email protected]>
|
|
With recent toolchains, the environment sectors were no longer aligned to
sector boundaries. The reason was a combination of two bugs:
1) common/environment.c assumed that CONFIG_TQM8xxL would be defined
for all TQM8xxL and TQM8xxM boards. But "include/common.h", where
this gets defined, is not included here (and cannot be included
without causing lots of problems).
Added a new #define CFG_USE_PPCENV for all boards which really
want to put the environment is a ".ppcenv" section.
2) The linker scripts just include environment.o, silently assuming
that the objects in that file are really in the order in which
they are coded in the C file, i. e. "environment" first, then
"redundand_environment", and "env_size" last. However, current
toolchains (GCC-4.x) reorder the objects, causing the environment
data not to start on a flash sector boundary:
Instead of: we got:
40008000 T environment 40008000 T env_size
4000c000 T redundand_environment 40008004 T redundand_environment
40010000 T env_size 4000c004 T environment
Note: this patch fixes just the first part, and cures the alignment
problem by making sure that "env_size" gets placed correctly. However,
we still have a potential issue because primary and redundant
environment sectors are actually swapped, i. e. we have now:
40008000 T redundand_environment
4000c000 T environment
40010000 T env_size
This shall be fixed in the next version.
Signed-off-by: Wolfgang Denk <[email protected]>
|
