From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mips port
Date: Mon, 08 Oct 2012 20:48:56 -0400 [thread overview]
Message-ID: <50737478.4040106@gmail.com> (raw)
In-Reply-To: <CAOUdcc-LNNJxLwrKGmmiR=H_3jv-BRsNKey-2TXzAtVMv=tqFw@mail.gmail.com>
On 10/06/2012 09:11 PM, Dmytro Milinevskyy wrote:
> Hi,
> I'm new to uboot mips port and first decided to try it with qemu.
Welcome. :-)
> I've encountered some problems with UART, but I guess that's more qemu
> issue(lsr reg is not updated when the line is available).
>
> Another issue I faced was code execution after the relocation is done. The
> address of board_init_r is not computed correctly(it was relative to boot
> ROM address space/bfc00000).
> Is it specific to qemu(I don't see the reference here though) or is it a
> generic mips port issue? Attached patch allows me to proceed with the boot
> in qemu.
>
> And last - why do we need relocation at all with u-boot? Performance
> constraints?
Generally, yes. Flash is very often slower than RAM (often 8 bits width
vs. 32 bits or more, generally doesn't support bursting, the processor
cache may not work with it, etc.).
A side benefit of running out of RAM is that it makes it much easier to
write to flash... you don't have to worry about writing to the chip you
are executing out of (when you erase/write flash, the chip returns a
"programming in progress" status until it is done - that will crash your
program if you are running out of that chip).
> Thanks,
> -- dmytro
Best regards,
gvb
next prev parent reply other threads:[~2012-10-09 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 1:11 [U-Boot] mips port Dmytro Milinevskyy
2012-10-09 0:48 ` Jerry Van Baren [this message]
2012-10-28 17:36 ` Dmytro Milinevskyy
-- strict thread matches above, loose matches on Subject: below --
2012-09-29 10:07 Dmytro Milinevskyy
2012-09-30 23:02 ` Dmytro Milinevskyy
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=50737478.4040106@gmail.com \
--to=gvb.uboot@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox