From: Elladan <elladan@eskimo.com>
To: Hell.Surfers@cwctv.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: wine emulation integration.
Date: Tue, 16 Jul 2002 01:02:19 -0700 [thread overview]
Message-ID: <20020716080219.GA26331@eskimo.com> (raw)
In-Reply-To: <004540925061072DTVMAIL7@smtp.cwctv.net>
Wine is collection of application-level libraries and a special runtime
execution system. Integrating it into the kernel isn't sensible, since
applications do not run in the kernel.
However, it is possible for Linux to support special system calls to aid
the implementation of Wine (chiefly for performance reasons). This was
proposed at some point in the past, but I'm not sure what ever became of
it. The basic idea was to provide some special locking primitives for
Win32 applications, as I recall...
What I think you're actually trying to propose is adding an
abstraction/support layer for windows driver binaries in the Linux
kernel. This is actually an interesting idea in some respects, but it's
not really all that closely related to Wine. Kernel development is
at a different level.
It's also probably not worth the trouble at all. Implementing it would
be very difficult, and the number of devices it would enable would be
very small. It would also be very unstable, since besides the bugs in
the windows drivers themselves, debugging the support layer around them
would be really hard. Generally speaking, it would almost always be
easier to just write a native Linux driver for the hardware.
-J
On Tue, Jul 16, 2002 at 07:25:25AM +0100, Hell.Surfers@cwctv.net wrote:
> Could the integration of wine into the kernel, be a good idea to take?
> Its adding could be added to create a hybrid system that with extra
> dev could allow modem cards to work under Linux that wouldnt otherwise
> saving time and effort.
prev parent reply other threads:[~2002-07-16 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 6:25 wine emulation integration Hell.Surfers
2002-07-16 8:02 ` Elladan [this message]
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=20020716080219.GA26331@eskimo.com \
--to=elladan@eskimo.com \
--cc=Hell.Surfers@cwctv.net \
--cc=linux-kernel@vger.kernel.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