From: Bernd Petrovitsch <bernd@firmix.at>
To: "Ajay Singh (ajaysi)" <ajaysi@cisco.com>
Cc: Rick Brown <rick.brown.3@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-newbie@vger.kernel.org
Subject: RE: kernel porting query
Date: Fri, 16 Feb 2007 10:32:42 +0100 [thread overview]
Message-ID: <1171618362.23981.10.camel@tara.firmix.at> (raw)
In-Reply-To: <677342AB6AE12D4DB59A9D473F40D74B028E0411@xmb-blr-416.apac.cisco.com>
On Fri, 2007-02-16 at 07:46 +0530, Rick Brown wrote:
Your quoting style sucks. I fixed it by hand.
[...]
> > 1) Can any one please shed some light on precisely and exactly what are
> > differences in different boards for which we need to port linux?
> On Fri, 2007-02-16 at 09:48 +0530, Ajay Singh (ajaysi) wrote:
> The differences depends on the boards ... Mostly if they belong to the
> same family the differences could be mainly in the peripherials ...
> Interrupt mappings... Serial interface ... Memory sizes (if differnet
> boards have different memory sizes) ... Sometimes some devices may be
> moved to some other locations in the memory map (Look at memory map of
> your SoC on your board).
You may have different boot loaders (or none at all).
You also may have different storage media like FlashRAM, IDE,
network, .... for boot loader/kernel/root filesystem. They may have
different sizes and it makes a "little" difference for your requirements
in the toolchain if you have 4MB or 1GB to boot your system from.
All that kind of information can be found in a BSP (board support
package).
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
prev parent reply other threads:[~2007-02-16 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 2:16 Rick Brown
2007-02-16 4:18 ` Ajay Singh (ajaysi)
2007-02-16 9:32 ` Bernd Petrovitsch [this message]
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=1171618362.23981.10.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=ajaysi@cisco.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rick.brown.3@gmail.com \
/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
all inboxes | Powered by JetHome®