From: Alan Nishioka <alan@nishioka.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: FW: Error occured when appended FPGA image in the section of .init.text then bootup
Date: Sat, 31 May 2008 03:23:07 -0700 [thread overview]
Message-ID: <4841270B.9080805@nishioka.com> (raw)
In-Reply-To: <BAY124-W49CC670970046CAE18FB33A8B90@phx.gbl>
朱利达 wrote:
>
>
> The request below give rise to the problem.
> I have some boards equiped with MPC8247 and FPGA without storage
> media which used as a PCI interface. So when the linux bootup
> before initialize the PCI, the code of FPGA will download. I
> append the FPGA code file in the Kernel section '.init.text'. when
> linux bootup firstly it check the board type(different board type
> would download different code), and download fpga code. More board
> types lead to more FPGA code. I append them all in the section of
> '.init.text'. when the total size of the code reach out 2M. The
> error occured. I read the '__log_buf' the kernel access some bad
> area. As the powerpce603 will map 16M address use two bat, how and
> why the problem occured, and how to solved it .
>
Since the error occurs at 2M, I am going to guess it is similar to
problem I had. The default link/load address for booting is 0x200000.
Here is a link:
<http://patchwork.ozlabs.org/linuxppc-embedded/patch?id=14717>
This fix is for the arch/ppc tree. I don't know if the arch/powerpc tree
works the same way.
In the future, you should say what kernel version you are using and what
the error was.
Alan Nishioka
alan@nishioka.com
next prev parent reply other threads:[~2008-05-31 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 8:31 FW: Error occured when appended FPGA image in the section of .init.text then bootup 朱利达
2008-05-31 10:23 ` Alan Nishioka [this message]
2008-05-31 17:07 ` David H. Lynch Jr.
2008-05-31 17:57 ` Josh Boyer
2008-05-31 18:34 ` David H. Lynch Jr.
2008-05-31 19:44 ` Josh Boyer
2008-06-01 5:59 ` 朱利达
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=4841270B.9080805@nishioka.com \
--to=alan@nishioka.com \
--cc=linuxppc-embedded@ozlabs.org \
/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.