From: Ricardo Scop <scop@digitel•com.br>
To: "Atit_Shah" <Atit_Shah@satyam•com>, <linuxppc-embedded@ozlabs•org>
Subject: Re: Impact of change n port size
Date: Tue, 19 Apr 2005 00:14:09 -0300 [thread overview]
Message-ID: <200504190014.09256.scop@digitel.com.br> (raw)
In-Reply-To: <D8595042F3765A4285B848A78A2C2ED1027748@bsdmsg002.corp.satyam.ad>
Hi Atit,
On Monday 18 April 2005 01:31, Atit_Shah wrote:
> Hi All,
>
> =09I have a kernel image which works perfectly for my reference
> board. When I try to port the same image on my board I seem to be facin=
g
> problems.=20
Like what?
> The only difference I see between the reference board and my
> board is the port size and capacity of RAM.
And hw design, board layout, ...
> =09I have taken care of sending the right value for the RAM size
> through BD_INFO. Would there be and where all would the change be, if
> any, in the kernel code OR when I make the kernel image ie through "mak=
e
> menuconfig" / "menu xconfig" required to be made for port size of RAM?
Well, if you're using PPCBoot or U-Boot to boot Linux, what you've done w=
ould=20
be enough.
OTOH, as you have a new hardware design you should check the SDRAM contro=
ller=20
initialization in the bootloader code. It may be sligthly wrong, so the=20
bootloader runs but the OS doesn't, because Linux really stresses out RAM=
=20
operation in burst mode. (BTW, this is a FAQ, if appliable).
> =09Out of curiosity what would be the change required for different
> FLASH port size again on the kernel side.
Look for the MTD parameters in the kernel compilation options.
HTH,
--=20
Ricardo Scop.
\|/
___ -*-
(@ @)/|\
/ V \| R SCOP Consult.
/( )\ Linux-based communications
--^^---^^+------------------------------
rscop@matrix•com.br
+55 51 999-36-777
Porto Alegre, RS - BRazil
next prev parent reply other threads:[~2005-04-19 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 4:31 Impact of change n port size Atit_Shah
2005-04-19 3:14 ` Ricardo Scop [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 6:05 Atit_Shah
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=200504190014.09256.scop@digitel.com.br \
--to=scop@digitel$(echo .)com.br \
--cc=Atit_Shah@satyam$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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