From: Zhaobin Zhu <zzhu@emc.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: General question on how to port linux kernel ?
Date: Thu, 31 Aug 2000 18:11:58 -0400 [thread overview]
Message-ID: <39AED82E.9D9FFA56@emc.com> (raw)
Hello all,
I am a newbie to Linux kernel port.
Just want to ask some general questions regarding porting linux kernel.
1) I have experiences porting pSOS kernel on different custom board.
Usually what I did is to bring the board to a known state and
provide
some required parameters and I/O interfacces, then call an entry
point
of the kernel. That is it.
Is Linux porting similar to this process ? If yes ,
2) Is there a well-defined known state before jumping into linux kernel
?
3) Is linux kernel modulized ? For example, to integrate a different
PCI
bridge controller, which .c and .h files should I change ?
Thanks,
--
Zhaobin Zhu
zzhu@emc.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-08-31 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39AED82E.9D9FFA56@emc.com \
--to=zzhu@emc.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).