RE: brltty and libusb package ?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

RE: brltty and libusb package ?

Dave Korn
Corinna Vinschen wrote:
> On Nov  2 10:11, Dave Korn wrote:

>>   It also involves a kernel-mode device driver.  Is that suitable for
>> cygwin, or should cygwin remain an entirely user-space set of apps?  Is
>> there any policy/precedent?
>
> As long as the driver builds with Cygwin, it seems fine to me.  We have
> already the ioperm package which brings its own driver, too.
>


  <installs source>  Oh, cool, so it does!  I've wanted to know how to build
kmdd's with gcc/cygwin for a while now!  <browse browse browse...>



/* workaround for bug 666316 and bug 671964 */
#undef IoGetCurrentIrpStackLocation
#define IoGetCurrentIrpStackLocation(irp) (*(struct
_IO_STACK_LOCATION**)((char*)(irp) + 96))



    >>>***AAAAAAAAUUUUUGGGGGGHHHHHHSCREAM***<<<


  That's about the most terrifying thing I've ever seen in a kernel-mode
driver.

[  It's also been removed in upstream for about two years now.....  ]


    cheers,
      DaveK
--
Can't think of a witty .sigline today....

Reply | Threaded
Open this post in threaded view
|

Re: brltty and libusb package ?

Corinna Vinschen-2
On Nov  2 14:20, Dave Korn wrote:

> /* workaround for bug 666316 and bug 671964 */
> #undef IoGetCurrentIrpStackLocation
> #define IoGetCurrentIrpStackLocation(irp) (*(struct
> _IO_STACK_LOCATION**)((char*)(irp) + 96))
>
>
>
>     >>>***AAAAAAAAUUUUUGGGGGGHHHHHHSCREAM***<<<
>
>
>   That's about the most terrifying thing I've ever seen in a kernel-mode
> driver.
>
> [  It's also been removed in upstream for about two years now.....  ]

So, maybe you want move this to cygwin-apps so that Marcel gets this too?


Corinna