From: Jeff Dike <jdike@addtoit.com>
To: Joerg Hoh <joerg@devone.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Porting UML to other plattforms
Date: Mon, 08 Dec 2003 15:42:48 -0500 [thread overview]
Message-ID: <200312082042.hB8KgmAv029431@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sat, 06 Dec 2003 23:45:35 +0100." <20031206224535.GF3376@hydra.joerghoh.de>
joerg@devone.org said:
> Can someone tell me, how hard is the job to port UML to other
> plattforms than i386 (how far went the ppc port?).
In principal, it shouldn't be too hard. In practice, the immature arch
abstraction layer inside UML is a problem, but this should be improved once
I get the x86_64 port merged.
More troublesome are are host-specific problems. Every architecture that UML
has run on has exposed toolchain problems of one sort or another. Host kernel
and hardware bugs are also somewhat common. These are what will hold up any
new port, rather than any problems with UML itself.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-08 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 22:45 [uml-devel] Porting UML to other plattforms Joerg Hoh
2003-12-06 23:38 ` Henrik Nordstrom
2003-12-08 20:42 ` Jeff Dike [this message]
2003-12-08 22:14 ` Joerg Hoh
2003-12-08 23:26 ` Jeff Dike
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=200312082042.hB8KgmAv029431@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=joerg@devone.org \
--cc=user-mode-linux-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.