--- Evgeny F <[EMAIL PROTECTED]> wrote:
> Damjan Jovanovic <[EMAIL PROTECTED]> wrote:
>
> > What "microdriver" are you talking about? Are you
> > working on STI? For STI, there is a convention for
> > Windows 2000 and onwards, something like
> > \\.\USBSCAN\... (check the STI documentation on
Damjan Jovanovic <[EMAIL PROTECTED]> wrote:
> What "microdriver" are you talking about? Are you working on STI? For
> STI, there is a convention for Windows 2000 and onwards, something like
> \\.\USBSCAN\... (check the STI documentation on MSDN).
> If it's STI, I have some code; do you want it?
Y
Damjan Jovanovic <[EMAIL PROTECTED]> wrote:
> What "microdriver" are you talking about? Are you
> working on STI? For STI, there is a convention for
> Windows 2000 and onwards, something like
> \\.\USBSCAN\... (check the STI documentation on MSDN).
>
> If it's STI, I have some code; do you want
--- Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
> Monday, August 29, 2005, 3:13:43 AM, Damjan
> Jovanovic wrote:
> >> It looks like there are multiple projects going
> on
> >> along the same lines here.
> >> Ivan Leo and me working on this too (making
> safedisc
> >> protected games work on
> >>
Monday, August 29, 2005, 3:13:43 AM, Damjan Jovanovic wrote:
>> It looks like there are multiple projects going on
>> along the same lines here.
>> Ivan Leo and me working on this too (making safedisc
>> protected games work on
>> wine).
>>
>> So far we have functional DeviceIoCotrol on a
>> devic
--- Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
>
> Saturday, August 27, 2005, 6:24:21 AM, Evgeny F
> wrote:
> > In message Mon, 28 Mar 2005 02:30:28 -0800, Damjan
> Jovanovic wrote:
> >> I propose adding a driver loading system to Wine
> that
> >> works as follows:
> >> -CreateFile() gets a de
--- Evgeny F <[EMAIL PROTECTED]> wrote:
> In message Mon, 28 Mar 2005 02:30:28 -0800, Damjan
> Jovanovic wrote:
>
>
> > I propose adding a driver loading system to Wine
> that
> > works as follows:
> > -CreateFile() gets a device filename, like (in my
> > case) \\.\MiiScan0
> > -Currently, Win
Saturday, August 27, 2005, 6:24:21 AM, Evgeny F wrote:
> In message Mon, 28 Mar 2005 02:30:28 -0800, Damjan Jovanovic wrote:
>> I propose adding a driver loading system to Wine that
>> works as follows:
>> -CreateFile() gets a device filename, like (in my
>> case) \\.\MiiScan0
>> -Currently, Wine'
In message Mon, 28 Mar 2005 02:30:28 -0800, Damjan Jovanovic wrote:
> I propose adding a driver loading system to Wine that
> works as follows:
> -CreateFile() gets a device filename, like (in my
> case) \\.\MiiScan0
> -Currently, Wine's behaviour for such a filename is to
> try load a VXD.
> -In
On Mon, 4 Apr 2005 10:20, C. Scott Ananian wrote:
> Um, I'm fairly certain that rendezvous via any kernel synchronization
> mechanism (semaphores, condition variables, etc) will do exactly what you
> want. The blocked task goes to sleep and the rest of the time slice is
> preferentially transfere
--- Kuba Ober <[EMAIL PROTECTED]> wrote:
> > > I've been trying to add STI (still image)
> support to
> > > Wine, and I've made some progress. However, I
> see a
> > > deep and unsurmountable need to add (at least
> > > user-space) device drivers to Wine, and I would
> like
> > > some feedback on
--- James Courtier-Dutton <[EMAIL PROTECTED]>
wrote:
> Damjan Jovanovic wrote:
> > Hi
> >
> > I've been trying to add STI (still image) support
> to
> > Wine, and I've made some progress. However, I see
> a
> > deep and unsurmountable need to add (at least
> > user-space) device drivers to Wine,
Hi,
On Sun, Apr 03, 2005 at 08:20:48PM -0400, C. Scott Ananian wrote:
> On Mon, 4 Apr 2005, Troy Rollo wrote:
>
> >run into problems with timing issues. Interrupts pose a particular
> >challenge
> >in that ideally the process handling the device should be activated
> >immediately, and the Linux
Hi,
On Mon, Apr 04, 2005 at 08:58:32AM +1000, Troy Rollo wrote:
> Of course such a mechanism would be much slower than a native driver, and may
> run into problems with timing issues. Interrupts pose a particular challenge
> in that ideally the process handling the device should be activated
>
On Mon, 4 Apr 2005, Troy Rollo wrote:
run into problems with timing issues. Interrupts pose a particular challenge
in that ideally the process handling the device should be activated
immediately, and the Linux kernel currently provides no interface to say
"switch to this task now" - the scheduler c
On Sat, 2 Apr 2005 08:15, Kuba Ober wrote:
> Not really. It just needs some sort of device-class-specific forwarding
> protocol. usbfs and libusb already do that, and you should be able to run
> any windows driver that way without even touching the kernel.
USB (along with SCSI) is a special case
Damjan Jovanovic wrote:
> Hi
>
> I've been trying to add STI (still image) support to
> Wine, and I've made some progress. However, I see a
> deep and unsurmountable need to add (at least
> user-space) device drivers to Wine, and I would like
> some feedback on these ideas.
>
> Basically, many Wi
Le ven 01/04/2005 à 17:06, Kuba Ober a écrit :
[snip]
> All that without touching the kernel in any way. And I mean
> here full support for *any* usb device, rain or shine. Network adapters
> (visible in wine only, but so what?),
Does that mean we'd need a database of USB identifiers?
For netwo
> I am not trying to _load_ a Windows driver (that
> either requires kernel support for the Windows DDK,
> like ndiswrapper has, or emulation of an entire x86,
> like bochs does).
Not really. It just needs some sort of device-class-specific forwarding
protocol. usbfs and libusb already do that, a
> > I've been trying to add STI (still image) support to
> > Wine, and I've made some progress. However, I see a
> > deep and unsurmountable need to add (at least
> > user-space) device drivers to Wine, and I would like
> > some feedback on these ideas.
>
> Drivers belong in the kernel.
Not necess
--- Mike McCormack <[EMAIL PROTECTED]> wrote:
>
> Damjan Jovanovic wrote:
>
> > I've been trying to add STI (still image) support
> to
> > Wine, and I've made some progress. However, I see
> a
> > deep and unsurmountable need to add (at least
> > user-space) device drivers to Wine, and I would
>
On Mon, Mar 28, 2005 at 07:52:48PM +0900, Mike McCormack wrote:
>
> Damjan Jovanovic wrote:
>
> >I've been trying to add STI (still image) support to
> >Wine, and I've made some progress. However, I see a
> >deep and unsurmountable need to add (at least
> >user-space) device drivers to Wine, and
Damjan Jovanovic wrote:
I've been trying to add STI (still image) support to
Wine, and I've made some progress. However, I see a
deep and unsurmountable need to add (at least
user-space) device drivers to Wine, and I would like
some feedback on these ideas.
Drivers belong in the kernel. If there's
Hi
I've been trying to add STI (still image) support to
Wine, and I've made some progress. However, I see a
deep and unsurmountable need to add (at least
user-space) device drivers to Wine, and I would like
some feedback on these ideas.
Basically, many Windows device drivers are really
trivial, b
24 matches
Mail list logo
