From: DENX Support System <support@denx.de>
To: u-boot@lists.denx.de
Subject: [DNX#2006040142000777] [U-Boot-Users] Ocotea with 512 megs of ram - ping [...]
Date: Sat, 1 Apr 2006 00:20:34 +0200 [thread overview]
Message-ID: <1143843634.354031.258916155@castor.denx.de> (raw)
Hello list,
inside the automatic U-Boot patch tracking system a new ticket
[DNX#2006040142000777] was created:
<snip>
> Dale,
>
> You've run into a problem where U-Boot maps the 2nd 256MB of physical
> memory into the same logical space as the 1st 256MB. It's a one line/one
> character typo that I've been meaning to post a patch for but I've been
> tied up on other projects. Here's the context diff:
>
> --- ./board/amcc/ocotea/init.S 2005-12-19 18:14:46.000000000 -0800
> +++ ../u-boot-git-ocotea-patch/board/amcc/ocotea/init.S 2005-12-22
> 13:38:38.000000000 -0800
> @@ -92,5 +92,5 @@
> tlbentry( CFG_ISRAM_BASE + 0x1000, SZ_4K, 0x80001000, 0,
> AC_R|AC_W|AC_X )
> tlbentry( CFG_SDRAM_BASE, SZ_256M, 0x00000000, 0,
> AC_R|AC_W|AC_X|SA_G|SA_I )
> - tlbentry( CFG_SDRAM_BASE+0x10000000, SZ_256M, 0x00000000, 0,
> AC_R|AC_W|AC_X|SA_G|SA_I )
> + tlbentry( CFG_SDRAM_BASE+0x10000000, SZ_256M, 0x10000000, 0,
> AC_R|AC_W|AC_X|SA_G|SA_I )
> tlbentry( CFG_PCI_BASE, SZ_256M, 0x00000000, 2, AC_R|AC_W|SA_G|SA_I
> )
> tlbentry( CFG_PCI_MEMBASE, SZ_256M, 0x00000000, 3,
> AC_R|AC_W|SA_G|SA_I )
>
> This should fix your problem.
>
> Marc
>
> > -----Original Message-----
> > From: u-boot-users-admin at lists.sourceforge.net
> > [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf
> > Of Dale Dunlea
> > Sent: Tuesday, February 14, 2006 8:32 AM
> > To: u-boot-users at lists.sourceforge.net
> > Subject: [U-Boot-Users] Ocotea with 512 megs of ram - ping fails
> >
> > Hi,
> >
> > I have an Ocotea (AMCC 440GX) test board which I have been
> > using happily
> > with U-Boot 1.1.4. In it's original configuration, it uses a
> > single 256
> > meg dimm. This works fine and my kernel and initrd images are
> > downloaded
> > happily via tftp. I replaced this dimm with a 512 meg dimm
> > and now the
> > network interface is no longer functional. Has anyone else
> > seen this issue?
> >
> > Regards,
> > Dale
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > through log files
> > for problems? Stop! Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the web.
> > DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&
> > dat=121642
> > _______________________________________________
> > U-Boot-Users mailing list
> > U-Boot-Users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/u-boot-users
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
</snip>
Your U-Boot support team
reply other threads:[~2006-03-31 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143843634.354031.258916155@castor.denx.de \
--to=support@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.