linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ±è»ó¹ü <ksb@ns.icu.ac.kr>
To: linuxppc-dev@lists.linuxppc.org
Subject: About linux porting on MPC 750...
Date: Fri, 16 Apr 1999 11:11:01 +0900	[thread overview]
Message-ID: <37169C34.558710D9@icu.ac.kr> (raw)


My team is going to port Linux on Motorola YellowKnife board composing
of a PPC 750 ,  MPC 106 PCI bus, and some other hardware. I want to know

whether my work is possible. If it is possible, how can I do this? Or
where can I find the source?

My team and I are beginners in Linux porting. Please send your comment
to me.
Thank you.


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

                 reply	other threads:[~1999-04-16  2: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=37169C34.558710D9@icu.ac.kr \
    --to=ksb@ns.icu.ac.kr \
    --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).