From: "Sarnath Kannan" <sparc64@rediffmail.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: RE: Re:How to boot linux on sandpoint board ?
Date: 11 Oct 2001 05:35:13 -0000 [thread overview]
Message-ID: <20011011053513.17120.qmail@mailweb19.rediffmail.com> (raw)
Hi every1,
Thanx for quick replies. Was a good introduction.
But I have some more doubts.
> Yes!... Linux has to be changed based on Architecure,
> and the board (chipset). And for additional devices,
> we can put in device drivers as necessary. For
> example, port for PPC is different from
> port for ARM or x86.
Yeah,I can understand that linux for PPC is diff from
linux for x86. But how come linux for PPC is diff
from Linux on a sandpoint. For exp, in an IBM board,
PIC always sits at IO addresses 0x20 and 0xA0. In any
IBM board, whether it is for a PC or for a minimal
board, the basic chipsets and their IO address space
assignments (Which are hardwired, as in case of PIC,
8254) remain the same. So, if we need to run a
desktop OS on a minimal board, the changes involved
would be less. This is my understanding. Correct
me if I am wrong. Coming to point, has sandpoint
board got some additional chipsets ? or has it got
the same chipsets arranged in a diff way, i mean
the address assignments. Can u list some of the
idiosyncracies of the board ? + and -. Meanwhile
I am also browsing archives and hunting info about
PPC peripherals. Any pointers on this topics are most
welcome.
Thank you.
Mark,
Thanx for the suggestions. I m sure it would help me.
Sarnath
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-11 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 5:35 Sarnath Kannan [this message]
2001-10-11 1:05 ` How to boot linux on sandpoint board ? ashish anand
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 13:01 Sarnath Kannan
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=20011011053513.17120.qmail@mailweb19.rediffmail.com \
--to=sparc64@rediffmail.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).