On Monday 04 February 2008 18:29:00 Greg KH wrote:
> On Mon, Feb 04, 2008 at 06:08:51PM +0100, Michael Buesch wrote:
> > On Monday 04 February 2008 18:01:31 Greg KH wrote:
> > > > Firmware upload -> Not sure. Do we already have some generic device
> > > > firmware
> > > >update
On Mon, Feb 04, 2008 at 06:08:51PM +0100, Michael Buesch wrote:
> On Monday 04 February 2008 18:01:31 Greg KH wrote:
> > > Firmware upload -> Not sure. Do we already have some generic device
> > > firmware
> > >update API/subsystem?
> >
> > Yes, we already have a firmware inte
On Monday 04 February 2008 18:01:31 Greg KH wrote:
> > LEDs -> These should conveniently be accessed in a standard way
> > through the LED triggers. So you could map some crazy functions
> > to the LEDs. Like your HDD LED, or your mail notification.
> > I really like that. :
On Mon, Feb 04, 2008 at 05:03:37PM +0100, Michael Buesch wrote:
> On Sunday 03 February 2008 01:09:44 Michael Buesch wrote:
> > However, having a razer specific kernel API seems not too good either.
> > Maybe we can do some generic API? But I have no idea how other mice's
> > features look like...
On Sunday 03 February 2008 01:09:44 Michael Buesch wrote:
> However, having a razer specific kernel API seems not too good either.
> Maybe we can do some generic API? But I have no idea how other mice's
> features look like...
Ok, well. I thought more about the approach to create a generic
"advanc
On Sunday 03 February 2008 00:39:26 Jiri Kosina wrote:
> On Sun, 3 Feb 2008, Michael Buesch wrote:
>
> > Here's the current userspace implementation of the HAL:
> > http://bu3sch.de/gitweb?p=razer.git;a=blob;f=librazer/hw_deathadder.c;h=e76d9347552eb5ea33b524a82e33ba869f3e0b3f;hb=HEAD
> > The comm
On Sun, 3 Feb 2008, Michael Buesch wrote:
> Here's the current userspace implementation of the HAL:
> http://bu3sch.de/gitweb?p=razer.git;a=blob;f=librazer/hw_deathadder.c;h=e76d9347552eb5ea33b524a82e33ba869f3e0b3f;hb=HEAD
> The commands changed slightly in latest firmware version and there's
> a
On Saturday 02 February 2008 23:46:29 Greg KH wrote:
> On Sat, Feb 02, 2008 at 11:31:02PM +0100, Michael Buesch wrote:
> > Hi,
> >
> > I am implementing a driver for Razer USB mice. These
> > mice are standard HID input devices with additional features
> > accessible through USB control commands.
On Sunday 03 February 2008 00:05:21 Jiri Kosina wrote:
> On Sat, 2 Feb 2008, Michael Buesch wrote:
>
> > I am implementing a driver for Razer USB mice. These mice are standard
> > HID input devices with additional features accessible through USB
> > control commands.
>
> Hi Michael,
>
> what d
On Sat, 2 Feb 2008, Michael Buesch wrote:
> I am implementing a driver for Razer USB mice. These mice are standard
> HID input devices with additional features accessible through USB
> control commands.
Hi Michael,
what do the control commands look like? (or is there the source code of
your d
On Sat, Feb 02, 2008 at 11:31:02PM +0100, Michael Buesch wrote:
> Hi,
>
> I am implementing a driver for Razer USB mice. These
> mice are standard HID input devices with additional features
> accessible through USB control commands.
>
> My current prototype driver does this access in userspace
>
Hi,
I am implementing a driver for Razer USB mice. These
mice are standard HID input devices with additional features
accessible through USB control commands.
My current prototype driver does this access in userspace
via libusb, but this brings all kinds of issues while the
kernel driver and othe
12 matches
Mail list logo
