From: aq <aquynh@gmail.com>
To: "Carl Holtje ,021,vcsg6," <cwh0803@cs.rit.edu>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Porting Xen...
Date: Wed, 5 Jan 2005 23:18:44 +0900 [thread overview]
Message-ID: <9cde8bff050105061846b52768@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0501041233540.18356@moxie.cs.rit.edu>
On Tue, 4 Jan 2005 12:35:52 -0500 (EST), Carl Holtje ;021;vcsg6;
<cwh0803@cs.rit.edu> wrote:
> All-
>
> I'm wondering if there is a guide or a general Getting Started for porting
> Xen to different architectures. I'm interested in supporting the arm
> platform.
as far as I know, there is no such document (the Xen developers too
lazy ;-)). but you can find some hints from the Developer manual.
besides, i have seen this page, and the experience of the author might
be useful for you: http://www.o3one.org/xen.html
regards,
AQ
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-05 14:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 17:35 Porting Xen Carl Holtje ;021;vcsg6;
2005-01-05 14:18 ` aq [this message]
2005-01-05 14:25 ` Mark Williamson
2005-01-05 16:25 ` Dan Magenheimer
-- strict thread matches above, loose matches on Subject: below --
2004-12-22 5:01 Ian Pratt
2004-12-22 11:39 ` Dave Feustel
2004-12-22 11:43 ` Keir Fraser
2004-12-22 21:49 ` David Hopwood
2004-12-22 11:45 ` Dave Feustel
2004-12-22 13:13 ` Keir Fraser
2004-12-22 2:38 Ian Pratt
2004-12-22 3:50 ` Kip Macy
2004-12-22 23:31 ` David Rhodus
2004-12-22 23:55 ` Kip Macy
2004-12-22 4:36 ` David Hopwood
2004-12-22 5:10 ` Adam Sulmicki
2004-12-21 16:03 Dave Feustel
2004-12-21 19:19 ` Kip Macy
2004-12-21 19:32 ` Luciano Miguel Ferreira Rocha
2004-12-21 19:59 ` Dave Feustel
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=9cde8bff050105061846b52768@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=cwh0803@cs.rit.edu \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.