Grazvydas Ignotas wrote:
> These regulators are not needed to start the kernel and only
> cause "incomplete constraints" warnings from kernel, so don't
> turn them on to save power.
>
> Signed-off-by: Grazvydas Ignotas
Ack-ed
Thanks
Tom
___
U-Boot mai
>>> I don't think so -- the reset vector is fixed at 0xfffc, which
will map to the last word of flash.
ok, understood. thanks again for the help!
Bob
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Bob Winslow wrote:
> Is it possible to change TEXT_BASE and RESET_VECTOR_ADDRESS in such a
> way that I can put the 512kB uboot image at the
> beginning of the 4M flash instead of the end??
I don't think so -- the reset vector is fixed at 0xfffc, which will
map to the last word of flash.
-Sc
Thanks Scott, that helped alot... i think I understand a bit more..
>> I have tried to change the value of TEXT_BASE to (xFFF8_) in the
>> config.mk file(and other
>> entries) but I must not be doing something else right..
> What specifically happened when you tried changing TEXT_BASE?
>
o
I'm having problems with fw_setenv. The reported error is "End of
range reached, aborting".
Looking further into fw_env.c, I see that in flash_write_buf(),
ENVSECTORS is used although the README says that this value is not
used for NOR devices. It appears to be used here. What value is this
sup
Bob Winslow wrote:
> last try, sorry about the multiple posts.
Please don't post the same thing repeatedly. If there is anything new
or changed in this version, it's very hard to spot. Just follow-up with
only the new information.
-Scott
___
U-Boot
Bob Winslow wrote:
> I guess I don't understand TEXT_BASE very well.. and how it relates to
> the boot location:
>
> From the manual:
> 4.4.3.3 Boot ROM Location
> The MPC8568E defines the default boot ROM address range
> to be 8 Mbytes at address 0x0_FF80_
>
last try, sorry about the multiple posts.
I must be doing something stupid, or I just don't understand how the
8567 boots from rom..., law entries, tables, etc...
Our board is using a MPC8567 with a 4 MEGByte boot rom flash (16
bit) It has just 512MB of DDR2 memory(no ram on
the local bus).
Hi all,
MPC8567 u-boot question for the experts out there...
I must be doing something stupid, or I just don't understand how the
8567 boots from rom..., law entries, tables, etc...
Our board is using a MPC8567 with a 4 MEGByte boot rom flash (16
bit) It has just 512MB of DDR2 memory(no r
On Thursday 10 December 2009 21:00:31 Kumar Gala wrote:
> --- a/drivers/bios_emulator/Makefile
> +++ b/drivers/bios_emulator/Makefile
patch summary (subject) really should mention the specific region you're
fixing (bios_emulator) since this isnt a tree-wide issue
-mike
signature.asc
Description
On Thursday 10 December 2009 08:41:07 Daniel Hobi wrote:
> During parallel build, the top Makefile spawns multiple sub-makes
> for targets in cpu/$(CPU). If cpu/$(CPU)/.depend is not present, the
> sub-makes may end up generating this file simultaneously which leads
> to corrupted content.
>
> A t
The following changes since commit 3b887ca8ce72cc12129183538f6e828db13f4867:
Peter Korsgaard (1):
mpc83xx: boot time regression, move LCRR setup back to cpu_init_f
are available in the git repository at:
git://git.denx.de/u-boot-nand-flash.git master
Stefan Roese (1):
nand: Fix
On Wed, Dec 09, 2009 at 09:01:43AM +0100, Stefan Roese wrote:
> 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
> Cc: Scott Wood
> Cc: Wolfgang Denk
> ---
> driver
Hi all,
MPC8567 u-boot question for the experts out there...
I must be doing something stupid, or I just don't understand how the
8567 boots from rom..., law entries, tables, etc...
Our board is using a MPC8567 with a 4 MEGByte boot rom flash (16
bit) It has just 512MB of DDR2 memory(no
I've cross-compiled and am running fw_printenv on an ARM system using
linux-2.6.28. The u-boot environment is kept in SPI-based NOR flash.
The configuration within fw_env.h is...
//#define CONFIG_FILE "/etc/fw_env.config"
//#define HAVE_REDUND /* For systems with 2 env sectors */
#define DEVI
Hi all,
I'm sorry, I sent to the list the debug messages of a older U-Boot
version. Here are the debug messages of the current U-Boot version.
FLASH: flash detect cfi
fwc addr fe00 cmd f0 f0 8bit x 8 bit
fwc addr fe00 cmd ff ff 8bit x 8 bit
fwc addr fe55 cmd 98 98 8bit x 8 bit
is= cmd
Wolfgang Denk a écrit :
> Dear Albert ARIBAUD,
>
> In message <4b1a05a9.4040...@free.fr> you wrote:
>>> No, this is not correct. get_ram_size() is used always on a single
>>> bank of memory only.
>> Do you mean calling get_ram_size() four up to times based on the
>> configured number of banks and
ARDEX EUROPE SAS
TIPOGRAFIA CENTRO STAMPA DIGITALE
Via Walter Tobagi, 6 - Milano 20143 - Tel. 0289123436 - Fax 0289122612
info @ ardexeurope.it
Controllate sul nostro sito tutte le offerte del periodo:
www . ardexeurope . it
Vi presenta le Nostre offerte di stampa di Giugno/Luglio 2009
BIGL
Did you setup the System I/O Configuration Registers SICRL, SICRH?
>I want to configure GPIOs on MPC8315, but I can't set the gpio. Below the
>configuration code and the output.
>
> What is wrong?
___
U-Boot mailing list
U-Boot@lists.denx.de
http://l
Hi all,
We have a MPC5200B custom board and we are evaluating the Numonyx
M29W128 Flash as a second source for the Spansion's S29GL128.
I've checked the top of the tree version of the U-Boot (u-boot.git) CFI
driver and the Numonyx Flash is not detected. This is the U-Boot debug
output:
FLASH: fl
These regulators are not needed to start the kernel and only
cause "incomplete constraints" warnings from kernel, so don't
turn them on to save power.
Signed-off-by: Grazvydas Ignotas
---
this patch depends on "TWL4030: make LEDs selectable for twl4030_led_init()"
http://lists.denx.de/pipermail
Dear Lasse Skov,
In message <4f4169b21905494ebd47a304f02192c92772357...@xch-hq-01.kk.local> you
wrote:
>
> I have a problem with disabling the data cache on my PPC.
Let's go back to the start, please: Which is the original problem you
try to solve by disabling the data cache?
> The target fami
fec_init() will only allocate fec->base_ptr if it is non-NULL. But
the cleanup routine on error will free the pointer without setting
it to NULL. This means that a later call to fec_init() would result
in using an invalid pointer.
The following patch to fix this is against u-boot-2009.11-rc2.
Sig
23 matches
Mail list logo
