From: "Tom Cranbrook" <tcranbrook@australia.edu>
To: "Mark A. Williamson" <mark.williamson@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net, david.hopwood@blueyonder.co.uk
Subject: Re: win4lin-like porting of win98 to xen?
Date: Mon, 11 Oct 2004 07:33:21 -0400 [thread overview]
Message-ID: <416b4a3f.8cc.0@australia.edu> (raw)
>
>For win9x under Xen I think that getting Win4Lin running under XenLinux
would
>be the most straightforward way of doing things. Is the kernel patch GPL?
>If so, the commercial bit must be the userland software and the device
>drivers, right? Given that, the quickest way to a free Win4Lin would be
to
>reuse their kernel patch and rewrite the tools / drivers... Still a
>nontrivial piece of work.
I have looked moderately closely at the win4lin patch and Xen. For the
most part, they look like they can be merged. There is one area that is
probably the deal braker. Win4Lin modifies the layout of the Generl
Descriptor Table at the CPU memory segment level, as does Xen, and there is
an area of overlap. This may be fixable, but not at my skill levels.
Check out the patch on segment.h in the Win4Lin patch.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-11 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 11:33 Tom Cranbrook [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 16:17 win4lin-like porting of win98 to xen? Mikhail Ramendik
2004-10-10 16:32 ` M.A. Williamson
2004-10-10 19:39 ` Mikhail Ramendik
2004-10-10 22:41 ` Mark A. Williamson
2004-10-11 0:05 ` David Hopwood
2004-10-11 0:33 ` Brian Wolfe
2004-10-11 0:38 ` Mark A. Williamson
2004-10-11 1:03 ` Avery Pennarun
2004-10-11 9:05 ` Mikhail Ramendik
2004-10-11 9:21 ` Steven Hand
2004-10-11 1:52 ` David Hopwood
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=416b4a3f.8cc.0@australia.edu \
--to=tcranbrook@australia.edu \
--cc=david.hopwood@blueyonder.co.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--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.