Razer Deathadder support

[DanielVoogsgerd]

I noticed that the Razer Deathadder mouse isn't supported. The mouse is quite popular and I have one if you'd like to try some things.

[terricain]

Sure, same info as last time :wink:, Also is it the plain deathadder or the chroma one? (though a link would solve that question ha)

[DanielVoogsgerd]

Razer Deathadder 2012 Edition It has a pulsating logo and mousewheel. Just blue, Chroma wasn't a thing back then unfortunately I couldn't find a link unfortunately VID/PID: 1532:0016

[terricain]

Ok a list of features would be useful.

Output of lsusb -v -d 1532:0016 in pastebin would also help

[DanielVoogsgerd]

https://gist.github.com/DanielVoogsgerd/0912506f1d5fc8dc27ebaedc99d243cc. Not many features, but here we go:

• DPI switch button
• Back button
• Forward button
• Pulsating Logo
• Pulsating scrollwheel

[terricain]

Back and forward buttons should work as normal. Logo and scrollwheel should be dooable. Does it have adjustable DPI? Is it wireless?

[DanielVoogsgerd]

@terrycain No it's not wireless, but it does have adjustable DPI

[terricain]

Ok we should be able to support most of it (there are some DPI settings I need to analyse further like setting up DPI stages but can definitly set current DPI). Do you know if the logo and scroll wheel can be modified seperatly?

[DanielVoogsgerd]

Not that I'm aware of On 24 May 2016 18:20, "Terry Cain" notifications@github.com wrote:

Ok we should be able to support most of it (there are some DPI settings I need to analyse further like setting up DPI stages but can definitly set current DPI). Do you know if the logo and scroll wheel can be modified seperatly?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/126#issuecomment-221325053

[terricain]

Ok, cool though we might be able to control them separately :wink:. I'll get to work on this later in the week, have one last bit of work due for Uni tomorrow.

[nonverbally]

DeathAdder Chroma support would also be great. It is listed as 1532:0043. Here is the lsusb output:

http://pastebin.com/DHV22GkW

This is the product listing: http://www.razerzone.com/store/razer-deathadder-chroma

The features are fairly basic. It is wired and has back and forward buttons and lighting of the logo and mouse wheel.

[terricain]

@nonverbally would you mind creating a new issue, as then I can keep the death adder and death adder chroma separate as will be a fair bit of differences.

[terricain]

@DanielVoogsgerd I'm gonna work on the tartarus, then the deathadder choma (as nonverbally can capture packets) then I should be able to convert the deathadder chroma to a normal deathadder driver

[presianbg]

I poses both - Chroma and the normal death adder. Just say if you need some help with dumps or other things.

[terricain]

Yeah dumps please :smile: If you could create a chroma deathadder issue here and attach some dumps (preferably with a readme saying what was done in each dump) that would be great. If you could start with the chroma, then the normal should be the same without lighting. Look here for info about getting dumps etc... And if I could get screenshots of each page of razer synapse that'll help too as then it'll be easier to see what features the mice have and what options etc...

[presianbg]

@terrycain Ok :) I will do that when have the time.

Meanwhile... are you aware of this project ? I'm using this tool and Michael has reverse engineered most of the drivers for the Razer mouse.

[terricain]

Yeah the difference with that project I believe is that they dont use kernel drivers, they use libusb which is fine I just found during my initial testing kernel drivers work a little nicer + having a kernel module is cooler yeah.

[mirh]

Speaking of kernel drivers, probably dumb question: why isn't this being mainlined?

[terricain]

Short story. Wanted to make big code changes, and use some features of github that you need to be owner for

[mirh]

Well, assuming big code changes are senseful, I don't see why they shouldn't be accepted in the end. And.. development could still proceed here then, you should only need to push stable releases to linux-next every now and then.

[claell]

@terrycain I think that you explained why you continued development of this on your own fork (https://github.com/terrycain/razer-drivers).

As far as I understand @mirh wanted to know, why the drivers aren't included in the Kernel.

[terricain]

As getting drives in the kernel is a mission in its self, especially getting it into the older kernels. The main reason is I'd rather focus on getting it working with as many devices as possible and getting the supporting software working well rather than bothering with linus' whineing when the driver doesnt look as pretty as he wants it.

[mirh]

I don't see why even only getting in newest kernels couldn't still be seen as an accomplishment. And if the bar is set high, then that might not be the first objective, but looking into it anyway.

[terricain]

Yeah I do eventually want it to be in a mainline kernel but I have other things I want to get working first. And if I can get all of the tooling in place working nicely then when the driver does make it into the kernel then it will work out of the box so to speak.

[r0l1]

Hi, you are always welcome to join the OpenRazer project, joining our efforts into a single project :) The kernel code has reached its first stable and clean release and the patches are already send to the linux mailing lists. Hope this is the beginning of a great Razer expierence under Linux.