I know there is some discussion of what should be put in the kernel
module, so I am asking for advice on what to implement... ie. just
handles, everything wineserver does, etc.
The first question is:
Why do you want to do that and what specifically do
you want to achieve?
A smal
On Wed, Aug 08, 2007 at 01:10:08PM -0400, Kuba Ober wrote:
> > > I know there is some discussion of what should be put in the kernel
> > > module, so I am asking for advice on what to implement... ie. just
> > > handles, everything wineserver does, etc.
> >
> > The first question is:
> > Why do
> > I know there is some discussion of what should be put in the kernel
> > module, so I am asking for advice on what to implement... ie. just
> > handles, everything wineserver does, etc.
>
> The first question is:
> Why do you want to do that and what specifically do
> you want to ach
keane wrote:
> I am not sure if this is the direction that some people want to take,
> because I am sure this modification of the IDT would be considered
> improper by kernel types but come on, I mean i386 has something like
> 200 software interrupts and linux uses only one.
Do not anger the kerne
On Wed, Aug 08, 2007 at 02:09:46AM -0400, James Keane wrote:
> I have been working on something that might be useful for kernel
> integration. It is a way for wine to create its own interrupt, so
> that a wine server/kernel/handle/whatever function could be called
> from userspace with a simple IN