I try enabling this
config...
--vb
#ifdef CONFIG_BOOTSTAGE_REPORT
bootstage_report();
@@ -225,12 +232,13 @@ static void boot_prep_linux(bootm_headers_t *images)
}
/* Subcommand: GO */
-static void boot_jump_linux(bootm_headers_t *images)
+static void boot_jump_linux
error reporting mechanism, but we have to do with what we
have to do :-)
cheers,
/vb
On Wed, Jan 14, 2009 at 5:42 PM, vb v...@vsbe.com wrote:
On Wed, Jan 14, 2009 at 7:03 AM, Stefan Roese s...@denx.de wrote:
On Tuesday 13 January 2009, vb wrote:
I have several different targets
I am trying to build a kernel image for the AMCC glacier board, using
the latest denx linux kernel
vv
linux-2.6-denx 128 git show
commit 5a7b6e7d15253c01ee0f0b8846b78e2ca23ef40d
Merge: 2f9f8f1... ae04d14...
Author: Wolfgang Denk w...@denx.de
Date:
On Wed, Jan 14, 2009 at 7:03 AM, Stefan Roese s...@denx.de wrote:
On Tuesday 13 January 2009, vb wrote:
The CONFIG_SYS_PCIE0_XCFGBASE constant (and its counterparts for other
PCIe ports) is defined and used in the code, and gets a TLB entry
assigned, but I can't find a place where
Stefan et al,
I am trying to troubleshoot a weird PCIe problem on a PPC460GT based
target, and it is getting curiouser and curiouser.
There is a tlb overlap I mentioned in an earlier email; on top of that
there are some things happening in cpu/ppc4xx/4xx_pcie.c which I also
find hard to
The Canyonland board's init.s file (board/amcc/canyonlands/init.S)
defines the contents of the TLB table for that target, it has these
two records in the table among others:
tlbentry(CFG_PCI_BASE, SZ_256M, 0x, 0xC, AC_R|AC_W|SA_G|SA_I)
Hello Ben,
I am trying to port u-boot on a system which deploys two different
types of ethernet PHYs, and don't see a good way of doing it with the
current sw structure.
There are concurrent implementations for supporting different PHYs,
and it looks like quite often bringing in a new etherent
that on ppc460 (I am not sure if 440gx is the
same, but it might be) the addresses of the peripherals driven by CSs
have nonzero nibble in four MSBs of the 36 bit address, so phys_addr_t
is 64 bits in size.
good luck.
/vb
any insights welcome.
thanks
I am not sure how much this is related, but it is a known problem that
older tftp servers can't serve files larger than 16Mbytes in size.
hth,
/vb
On Fri, Aug 22, 2008 at 12:57 PM, [EMAIL PROTECTED] wrote:
I have been searching the web, but I have not seen any mention of this kind
of problem
quot;006792";
google_color_text = "00";
//-->
Re: [U-Boot] Changing u-boot relocation scheme
vb
Reply via email to
<!--
google_ad_client = "pub-7266757337600734";
google_alternate_ad_url = "
10 matches
Mail list logo