linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Rolf Liu" <rolfl@sc.mcel.mot.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: the porting of Linux
Date: Mon, 27 Nov 2000 09:37:49 +0800	[thread overview]
Message-ID: <019a01c05812$a69879c0$bf0102c8@sc.mcel.mot.com> (raw)


Hi, all,
These days I am looking through the Linux ppc source code.
I am just wondering how much effort or what should be done
 if I want to port such code to a different platform, such as arm, or other
so specific one.
I know the arch-specific codes are located at linux/arch/... .
But I just want to know if there is exact interface specification
about the interfaces that the linux/arch/... must provide for the
arch-independent kernel codes.

Any suggestions and discussion is appreciated!
thanks a lot!

BRs
Rolf Liu


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2000-11-27  1:37 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='019a01c05812$a69879c0$bf0102c8@sc.mcel.mot.com' \
    --to=rolfl@sc.mcel.mot.com \
    --cc=linuxppc-dev@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).