├── .gitignore ├── LICENSE ├── Makefile ├── README.md ├── hid-vader3 ├── Makefile ├── dkms.conf.in ├── dkms.post_install ├── dkms.post_remove ├── etc-modprobe.d │ └── vader3.conf ├── etc-udev-rules.d │ ├── 50-vader3-fixup-steamlink.rules │ └── 60-vader3.rules └── src │ ├── Makefile │ ├── hid-vader3.c │ └── vader3.h ├── install.sh ├── lib ├── installer.sh └── verbose.sh └── uninstall.sh /.gitignore: -------------------------------------------------------------------------------- 1 | *~ 2 | hid-vader3/dkms.conf 3 | hid-vader3/src/*.ko* 4 | hid-vader3/**/*.mod* 5 | hid-vader3/**/*.o* 6 | hid-vader3/src/*.symvers* 7 | hid-vader3/src/vader3.c 8 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | obj-m := flydigi_vader3.o 2 | flydigi_vader3-objs := hid-flydigi-vader3.o 3 | 4 | KDIR := /lib/modules/$(shell uname -r)/build 5 | PWD := $(shell pwd) 6 | 7 | all: 8 | $(MAKE) -C $(KDIR) M=$(PWD) modules 9 | 10 | clean: 11 | $(MAKE) -C $(KDIR) M=$(PWD) clean 12 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Flydigi Vader 3 Bluetooth driver for GNU/Linux 2 | 3 | Adds support for the 4 back buttons/paddles, C/Z buttons, and 4 | circle/home buttons, while connected in D-Input mode under a 5 | Bluetooth connection. 6 | 7 | # Installation (you have to compile it) 8 | 9 | ``` 10 | make -C hid-vader3 11 | sudo ./uninstall.sh 12 | sudo ./install.sh 13 | sudo modprobe hid-vader3 14 | ``` 15 | 16 | You can confirm it loaded/bound to your controller by checking dmesg 17 | (you should see a similar output): 18 | 19 | ``` 20 | [45188.559255] loaded hid-vader3 0.0.1-1-g6c50ff3-dirty 21 | [45188.559400] input: Flydigi VADER3P as /devices/virtual/misc/uhid/0005:D7D7:0041.0023/input/input526 22 | [45188.559483] vader3 0005:D7D7:0041.0023: input,hidraw0: BLUETOOTH HID v1.01 Gamepad [Flydigi VADER3P] on 14:85:7f:e2:41:03 23 | ``` 24 | 25 | # Toggling Flydigi Vader 3 Input Modes 26 | 27 | Swap the slider on the back to the center position. 28 | 29 | If the status light is white, you're in X-Input mode, just hold the 30 | circle button (left-center under the joysticks) and the A button for 31 | around 3 seconds - you'll see the device power off, then reboot with 32 | the status light blue. 33 | 34 | To revert to X-Input mode, repeat the process, but hold X instead of A. 35 | 36 | X-Input mode does not support the custom buttons as native hardware 37 | events, they will replay the bindings mapped in the Flydigi 38 | SpaceStation app (which unfortunately can't do keyboard binds under 39 | GNU/Linux, or multi-button key-presses). 40 | 41 | # Force Feedback (FF)/ Rumble Support 42 | 43 | Due to hardware limitations, there is none - this is unfortunately not 44 | something I can change at a driver level. 45 | 46 | You can use the 2.4ghz dongle on dongle mode + X-Input (dongle 47 | default, and changed the same way as Bluetooth mode is) if you want 48 | rumble support on GNU/Linux (the USB hid-generic driver handles it 49 | correctly), but this means that you will miss out on the ability to 50 | map native button presses using Qjoypad or AntiMicroX (I enjoy having 51 | 8 additional buttons myself). 52 | 53 | Update: I added support for the 8 extra buttons to "xpad" official 54 | driver via a PR here: 55 | 56 | https://github.com/paroj/xpad/pull/268 57 | 58 | This is very featureful - all extra buttons + rumble (x-input), but 59 | requires the dongle, so is slightly less convenient than bluetooth. 60 | 61 | # Testing 62 | 63 | I've tested the following with good results: 64 | 65 | - Final Fantasy XIV (via Lutris/wine) 66 | - Diablo IV (via Lutris/wine) 67 | - qjoypad (re-mapping software) 68 | 69 | and the following with OK results: 70 | 71 | - Steam controller config (It shows the controller as if it was a 72 | Playstation layout, not an Xbox one. It will will allow you to 73 | assign/remap the main face buttons to the special buttons, but the 74 | special buttons do not show up as distinct input items - so you 75 | could use qjoypad or antimicrox in tandem with Steam there perhaps) 76 | 77 | # Copyright 78 | 79 | Matthew Carter 80 | 81 | Some of the supplemental files (the build scripts (.sh files) and Makefiles, which lack 82 | copyright headers in the source repo (xpadneo - no association to this 83 | project)) are copyright their original authors. 84 | 85 | That project's copyright header/information is as follows: 86 | ``` 87 | /* 88 | * Force feedback support for XBOX ONE S and X gamepads via Bluetooth 89 | * 90 | * This driver was developed for a student project at fortiss GmbH in Munich. 91 | * Copyright (c) 2017 Florian Dollinger 92 | * 93 | * Additional features and code redesign 94 | * Copyright (c) 2020 Kai Krakow 95 | */ 96 | ``` 97 | Please do NOT contact them for support for this project. 98 | 99 | # License 100 | 101 | GPLv3 or later (see: LICENSE) 102 | 103 | ## Disclaimer and Limitation of Liability 104 | 105 | This is the standard GPLv3 verbiage (see LICENSE), but bears 106 | repeating - I haven't had any issues with this on my machine or 107 | controller, but this is the first driver I've written - peer review by 108 | experts, and feedback from users is always appreciated. 109 | 110 | ``` 111 | 15. Disclaimer of Warranty. 112 | 113 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 114 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 115 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 116 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 117 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 118 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 119 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 120 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 121 | 122 | 16. Limitation of Liability. 123 | 124 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 125 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 126 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 127 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 128 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 129 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 130 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 131 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 132 | SUCH DAMAGES. 133 | 134 | ``` 135 | -------------------------------------------------------------------------------- /hid-vader3/Makefile: -------------------------------------------------------------------------------- 1 | KERNEL_SOURCE_DIR ?= /lib/modules/$(shell uname -r)/build 2 | LD := ld.bfd 3 | 4 | all: modules 5 | 6 | .INTERMEDIATE: ../VERSION 7 | 8 | ../VERSION: 9 | git describe --tags --dirty >$@ 10 | 11 | clean modules modules_install: ../VERSION 12 | $(MAKE) -C $(KERNEL_SOURCE_DIR) INSTALL_MOD_DIR="kernel/drivers/hid" LD=$(LD) M=$(shell pwd)/src VERSION="$(shell cat ../VERSION)" $@ 13 | 14 | reinstall: modules 15 | sudo make modules_install 16 | sudo rmmod hid-vader3 || true 17 | sudo modprobe hid-vader3 $(MOD_PARAMS) 18 | -------------------------------------------------------------------------------- /hid-vader3/dkms.conf.in: -------------------------------------------------------------------------------- 1 | PACKAGE_NAME="hid-vader3" 2 | PACKAGE_VERSION="@DO_NOT_CHANGE@" 3 | BUILT_MODULE_NAME[0]="hid-vader3" 4 | BUILT_MODULE_LOCATION[0]="src" 5 | DEST_MODULE_LOCATION[0]="/kernel/drivers/hid" 6 | MAKE[0]="make -C $kernel_source_dir M=$dkms_tree/$PACKAGE_NAME/$PACKAGE_VERSION/build/src VERSION=$PACKAGE_VERSION modules" 7 | AUTOINSTALL="yes" 8 | POST_INSTALL="dkms.post_install" 9 | POST_REMOVE="dkms.post_remove" 10 | -------------------------------------------------------------------------------- /hid-vader3/dkms.post_install: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | #TODO Remove ERTM after kernel patch is deployed in the wild 4 | ERTM_OVERRIDE="/etc/modprobe.d/99-vader3-bluetooth.conf" 5 | DISABLE_ERTM="/sys/module/bluetooth/parameters/disable_ertm" 6 | 7 | if [ `uname -r | awk -F. '{ printf "%03d%03d",$1,$2 }'` -ge 005012 ]; then 8 | echo "Not disabling ERTM, kernel version doesn't require it..." 9 | elif [ "$(readlink "${ERTM_OVERRIDE}" 2>/dev/null)" = "/dev/null" ]; then 10 | echo "Not disabling ERTM, local override in place..." 11 | elif [ -L "${ERTM_OVERRIDE}" ]; then 12 | echo >&2 "WARNING: '${ERTM_OVERRIDE}' is an arbitrary symlink, this is not supported." 13 | echo >&2 "Skipping ERTM fixup, you're expected to manage the options on your own..." 14 | else 15 | echo "Disabling ERTM permanently (requires reboot)..." 16 | echo "options bluetooth disable_ertm=y" >"${ERTM_OVERRIDE}" 17 | echo "HINT: If you want to prevent this in the future, run 'ln -snf /dev/null ${ERTM_OVERRIDE}'." 18 | 19 | if [ -w "${DISABLE_ERTM}" ]; then 20 | echo "Disabling ERTM instantly..." 21 | echo "Y" >"${DISABLE_ERTM}" 22 | fi 23 | fi 24 | 25 | echo "Installing modalias database..." 26 | install -D -m 0644 -t /etc/modprobe.d etc-modprobe.d/vader3.conf 27 | 28 | echo "Installing udev rules..." 29 | install -D -m 0644 -t /etc/udev/rules.d etc-udev-rules.d/50-vader3-fixup-steamlink.rules 30 | install -D -m 0644 -t /etc/udev/rules.d etc-udev-rules.d/60-vader3.rules 31 | 32 | echo "Reloading udev..." 33 | udevadm control --reload 34 | -------------------------------------------------------------------------------- /hid-vader3/dkms.post_remove: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | #TODO Remove ERTM after kernel patch is deployed in the wild 4 | ERTM_OVERRIDE="/etc/modprobe.d/99-vader3-bluetooth.conf" 5 | 6 | [ -L "${ERTM_OVERRIDE}" ] || { echo "Uninstalling ERTM override..."; rm -f "${ERTM_OVERRIDE}"; } 7 | 8 | echo "Uninstalling modalias database..." 9 | rm -f /etc/modprobe.d/vader3.conf 10 | 11 | echo "Uninstalling udev rules..." 12 | rm -f /etc/udev/rules.d/60-vader3.rules 13 | rm -f /etc/udev/rules.d/50-vader3-fixup-steamlink.rules 14 | 15 | echo "Reloading udev..." 16 | udevadm control --reload 17 | -------------------------------------------------------------------------------- /hid-vader3/etc-modprobe.d/vader3.conf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ahungry/vader3/81df136a15f19d2f124c0245a76f2d710fea2098/hid-vader3/etc-modprobe.d/vader3.conf -------------------------------------------------------------------------------- /hid-vader3/etc-udev-rules.d/50-vader3-fixup-steamlink.rules: -------------------------------------------------------------------------------- 1 | ACTION=="add|change", DRIVERS=="vader3", SUBSYSTEM=="hidraw", MODE:="0000" 2 | -------------------------------------------------------------------------------- /hid-vader3/etc-udev-rules.d/60-vader3.rules: -------------------------------------------------------------------------------- 1 | # Rebind driver to vader3 2 | ACTION=="bind", SUBSYSTEM=="hid", DRIVER!="vader3", KERNEL=="0005:D7D7:*", KERNEL=="*:0041.*", ATTR{driver/unbind}="%k", ATTR{[drivers/hid:vader3]bind}="%k" 3 | 4 | # Tag vader3 devices for access in the user session 5 | ACTION=="add|change", DRIVERS=="vader3", SUBSYSTEM=="input", TAG+="uaccess" 6 | -------------------------------------------------------------------------------- /hid-vader3/src/Makefile: -------------------------------------------------------------------------------- 1 | # 2 | # Makefile for the HID driver 3 | # 4 | ccflags-y += -DVERSION=$(VERSION) 5 | obj-m += hid-vader3.o 6 | 7 | #FIXME(kakra) Work-around, cleanup after source code split 8 | hid-vader3-y += vader3.o 9 | $(obj)/vader3.c: $(src)/hid-vader3.c 10 | cp $< $@ 11 | 12 | # hid-vader3-y += vader3/core.o vader3/consumer.o vader3/keyboard.o 13 | -------------------------------------------------------------------------------- /hid-vader3/src/hid-vader3.c: -------------------------------------------------------------------------------- 1 | /* 2 | * Support for Flydigi Vader 3 via Bluetooth (hardware doesn't support FF in that mode). 3 | * 4 | * Learning References (tutorials/blogs): 5 | * https://www.nirenjan.com/2020/linux-hid-driver/ 6 | * 7 | * Project References: 8 | * https://github.com/atar-axis/xpadneo 9 | * 10 | * See also: 11 | * https://github.com/atar-axis/xpadneo/pull/451 if 12 | */ 13 | 14 | #include 15 | #include 16 | #include 17 | 18 | #include "vader3.h" 19 | 20 | MODULE_LICENSE("GPL"); 21 | MODULE_AUTHOR("Matthew Carter "); 22 | MODULE_DESCRIPTION("Linux kernel driver for Flydigi Vader 3 via Bluetooth"); 23 | MODULE_VERSION(VADER3_VERSION); 24 | 25 | #define VENDOR_FLYDIGI 0xD7D7 26 | #define DEV_VADER3 0x0041 27 | 28 | static int vader3_input_mapping(struct hid_device *dev, 29 | struct hid_input *input, 30 | struct hid_field *field, 31 | struct hid_usage *usage, 32 | unsigned long **bit, 33 | int *max) 34 | { 35 | /* 36 | * We are reporting the events in vader3_raw_event. 37 | * Skip the hid-input processing. 38 | */ 39 | // return -1; 40 | 41 | // This uses the AUTO / underlying driver defaults - xpadneo has 42 | // an area where they use STATIC and redefine their own map of codes 43 | // to generated values - I wonder which is most appropriate to map at? 44 | // We can do it here, against codes (which could collide with a name brand controller), 45 | // or we can fiddle bits in the raw area and let them bubble up, or we can 46 | // remap them in the event handler (this seems easiest to get the hid-generic values out of) 47 | return 0; 48 | } 49 | 50 | static int vader3_input_configured(struct hid_device *dev, 51 | struct hid_input *input) 52 | { 53 | struct input_dev * input_dev = input->input; 54 | int i; 55 | int max_btn = 16; 56 | int abs_min = -128; 57 | int abs_max = 127; 58 | int deadzone = 25; // Just hardcode to the same approximated value 59 | 60 | hid_set_drvdata(dev, input_dev); 61 | 62 | // Define features 63 | set_bit(EV_KEY, input_dev->evbit); 64 | set_bit(EV_ABS, input_dev->evbit); 65 | 66 | // If we want to initialize buttons under the first 16, we can, but it 67 | // would violate the Xbox spec, and xpadneo devs recommend we stick to trigger happy range. 68 | // set_bit(BTN_C, input_dev->keybit); 69 | 70 | // So, we'll just initialize the trigger happy range 71 | for (i = 0; i < max_btn; i++) { 72 | set_bit(BTN_TRIGGER_HAPPY1 + i, input_dev->keybit); 73 | } 74 | 75 | // Define stick capabilities 76 | set_bit(ABS_X, input_dev->absbit); 77 | set_bit(ABS_Y, input_dev->absbit); 78 | set_bit(ABS_Z, input_dev->absbit); 79 | set_bit(ABS_RZ, input_dev->absbit); 80 | 81 | // d-pad 82 | set_bit(ABS_HAT0Y, input_dev->keybit); 83 | set_bit(ABS_HAT0X, input_dev->keybit); 84 | 85 | // Define stick ranges 86 | input_set_abs_params(input_dev, ABS_X, abs_min, abs_max, 32, deadzone); 87 | input_set_abs_params(input_dev, ABS_Y, abs_min, abs_max, 32, deadzone); 88 | input_set_abs_params(input_dev, ABS_Z, abs_min, abs_max, 32, deadzone); 89 | input_set_abs_params(input_dev, ABS_RZ, abs_min, abs_max, 32, deadzone); 90 | 91 | // d-pad 92 | /* input_set_abs_params(input_dev, ABS_HAT0Y, -1, 1, 32, 0); */ 93 | /* input_set_abs_params(input_dev, ABS_HAT0X, -1, 1, 32, 0); */ 94 | 95 | return 0; 96 | } 97 | 98 | // I guess we can log/report on exact raw events if we want, but if we don't 99 | // act on it, I think it passes through to the event function. 100 | static int vader3_raw_event(struct hid_device *dev, 101 | struct hid_report *report, u8 *data, int len) 102 | { 103 | /* struct input_dev *input_dev = hid_get_drvdata(dev); */ 104 | /* hid_info(input_dev, "raw_event data 0: %d\n", data[0]); */ 105 | /* hid_info(input_dev, "raw_event data 1: %d\n", data[1]); */ 106 | /* hid_info(input_dev, "raw_event data 2: %d\n", data[2]); */ 107 | /* hid_info(input_dev, "raw_event data 3: %d\n", data[3]); */ 108 | /* hid_info(input_dev, "raw_event data 4: %d\n", data[4]); */ 109 | /* hid_info(input_dev, "raw_event data 5: %d\n", data[5]); */ 110 | /* hid_info(input_dev, "raw_event data 6: %d\n", data[6]); */ 111 | /* hid_info(input_dev, "raw_event data 7: %d\n", data[7]); */ 112 | /* hid_info(input_dev, "raw_event data 8: %d\n", data[8]); */ 113 | /* hid_info(input_dev, "raw_event data 9: %d\n", data[9]); */ 114 | /* hid_info(input_dev, "raw_event data 10: %d\n", data[10]); */ 115 | /* hid_info(input_dev, "raw_event data 11: %d\n", data[11]); */ 116 | /* hid_info(input_dev, "raw_event data 12: %d\n", data[12]); */ 117 | /* hid_info(input_dev, "raw_event data 13: %d\n", data[13]); */ 118 | /* hid_info(input_dev, "raw_event data 14: %d\n", data[14]); */ 119 | /* hid_info(input_dev, "raw_event data 15: %d\n", data[15]); */ 120 | /* hid_info(input_dev, "raw_event data 16: %d\n", data[16]); */ 121 | 122 | // Fix the rightmost back button, the others are 8/16/32, and 64 makes it recognized 123 | // If we don't do this, it actually won't be detected by qjoypad 124 | // The C/Z are 1/2 - no idea why 4 is problematic 125 | if (len > 11 && data[11] & 4) 126 | { 127 | data[11] |= 64; 128 | data[11] &= ~4; 129 | } 130 | 131 | // C-button reports as BTN_0 132 | /* if (data[11] == 1) */ 133 | /* { */ 134 | /* input_report_key(input_dev, BTN_C, 1); */ 135 | /* } */ 136 | 137 | // Z-button reports as Return 138 | /* if (data[11] == 2) */ 139 | /* { */ 140 | /* data[11] = 0; */ 141 | /* data[12] = 1; */ 142 | /* } */ 143 | 144 | /* input_sync(input_dev); */ 145 | 146 | return 0; 147 | 148 | // Sample from the tutorial, auto-mapping a bunch of stuff 149 | 150 | /* struct input_dev *input_dev = hid_get_drvdata(dev); */ 151 | /* int ret = 0; */ 152 | /* int btn; */ 153 | /* int idx; */ 154 | /* int num_buttons = 16; */ 155 | 156 | /* // Samples of how we can overwrite this to anything we want. */ 157 | /* input_report_abs(input_dev, ABS_Z, data[4]); */ 158 | /* input_report_abs(input_dev, ABS_RX, data[5]); */ 159 | /* input_report_abs(input_dev, ABS_RY, data[6]); */ 160 | /* input_report_abs(input_dev, ABS_MISC, data[7]); */ 161 | 162 | /* /\* ... *\/ */ 163 | /* for (int i = 0; i < num_buttons; i++) */ 164 | /* { */ 165 | /* idx = 8 + (i / BITS_PER_BYTE); */ 166 | /* btn = !!(data[idx] & (1 << (i % BITS_PER_BYTE))); */ 167 | /* input_report_key(input_dev, BTN_TRIGGER_HAPPY + i, btn); */ 168 | /* } */ 169 | 170 | /* input_sync(input_dev); */ 171 | /* return ret; */ 172 | } 173 | 174 | static int vader3_event(struct hid_device *dev, struct hid_field *field, 175 | struct hid_usage *usage, __s32 value) 176 | { 177 | struct input_dev *input_dev = hid_get_drvdata(dev); 178 | 179 | // hid_info(input_dev, "type: %d\n", usage->type); 180 | 181 | // d-pad is all messed up 182 | // up/down: 183 | // type 3 (EV_ABS), code 17 (ABS_HAT0Y), value -1 (up), 1 (down), and 0 unpressed 184 | // left/right: 185 | // type 3 (EV_ABS), code 16 (ABS_HAT0X), value -1 (left), 1 (right), and 0 unpressed 186 | // Some users complain about multiple directions inputs registering at once, I bet 187 | // we could track that state here and ensure it's not possible to press left and right 188 | // at the same time 189 | 190 | if (usage->type == EV_ABS) 191 | { 192 | switch (usage->code) 193 | { 194 | case ABS_HAT0X: // all d-pad comes through as this 195 | switch (value) 196 | { 197 | case 1: // up 198 | input_report_abs(input_dev, ABS_HAT0Y, -1); 199 | break; 200 | 201 | case 5: // down 202 | input_report_abs(input_dev, ABS_HAT0Y, 1); 203 | break; 204 | 205 | case 7: // left 206 | input_report_abs(input_dev, ABS_HAT0X, -1); 207 | break; 208 | 209 | case 3: // right 210 | input_report_abs(input_dev, ABS_HAT0X, 1); 211 | break; 212 | 213 | case 2: // up-right 214 | input_report_abs(input_dev, ABS_HAT0Y, -1); 215 | input_report_abs(input_dev, ABS_HAT0X, 1); 216 | break; 217 | 218 | case 4: // bottom-right 219 | input_report_abs(input_dev, ABS_HAT0Y, 1); 220 | input_report_abs(input_dev, ABS_HAT0X, 1); 221 | break; 222 | 223 | case 6: // bottom-left 224 | input_report_abs(input_dev, ABS_HAT0Y, 1); 225 | input_report_abs(input_dev, ABS_HAT0X, -1); 226 | break; 227 | 228 | case 8: // up-left 229 | input_report_abs(input_dev, ABS_HAT0Y, -1); 230 | input_report_abs(input_dev, ABS_HAT0X, -1); 231 | break; 232 | 233 | case 0: // no direction 234 | input_report_abs(input_dev, ABS_HAT0X, 0); 235 | input_report_abs(input_dev, ABS_HAT0Y, 0); 236 | break; 237 | 238 | default: 239 | hid_info(input_dev, "Unknown d-pad direction: %d\n", value); 240 | // input_report_abs(input_dev, usage->code, value); 241 | break; 242 | 243 | } 244 | break; 245 | 246 | default: 247 | // If we want Linux Gamepad Specification, we can multiply the value here to 32k 248 | // It seems to show up as that in jstest already? 249 | input_report_abs(input_dev, usage->code, value); 250 | break; 251 | } 252 | return 1; 253 | } 254 | 255 | if (usage->type == EV_KEY) 256 | { 257 | // Special remapping to make it work correctly and not show weird events out of joy range 258 | switch (usage->code) 259 | { 260 | case BTN_0: // C-Button 261 | input_report_key(input_dev, BTN_TRIGGER_HAPPY1, value); 262 | // input_report_key(input_dev, BTN_C, value); 263 | break; 264 | case KEY_ENTER: // Z-Button 265 | input_report_key(input_dev, BTN_TRIGGER_HAPPY2, value); 266 | break; 267 | case KEY_CHANNELUP: // Leftmost back button 268 | input_report_key(input_dev, BTN_TRIGGER_HAPPY3, value); 269 | break; 270 | case KEY_TV: // Second leftmost back button 271 | input_report_key(input_dev, BTN_TRIGGER_HAPPY4, value); 272 | break; 273 | case KEY_CHANNELDOWN: // Second rightmost back button 274 | input_report_key(input_dev, BTN_TRIGGER_HAPPY5, value); 275 | break; 276 | case KEY_PROGRAM: // Rightmost back button 277 | case KEY_EJECTCD: // Original without our raw re-map - that shows up in evtest but NOT qjoypad 278 | input_report_key(input_dev, BTN_TRIGGER_HAPPY6, value); 279 | break; 280 | case KEY_CAMERA: // Circle button under joysticks 281 | input_report_key(input_dev, BTN_TRIGGER_HAPPY7, value); 282 | break; 283 | case KEY_RED: // Home button under joysticks 284 | input_report_key(input_dev, BTN_TRIGGER_HAPPY8, value); 285 | break; 286 | default: // Anything else, just pass through (why do their usage codes work?) 287 | input_report_key(input_dev, usage->code, value); 288 | break; 289 | } 290 | 291 | return 1; 292 | } 293 | 294 | return 0; 295 | } 296 | 297 | static const struct hid_device_id vader3_devices[] = { 298 | { HID_BLUETOOTH_DEVICE(VENDOR_FLYDIGI, DEV_VADER3) }, 299 | {} 300 | }; 301 | 302 | MODULE_DEVICE_TABLE(hid, vader3_devices); 303 | 304 | static struct hid_driver vader3_driver = { 305 | .name = "vader3", 306 | .id_table = vader3_devices, 307 | .input_mapping = vader3_input_mapping, 308 | .input_configured = vader3_input_configured, 309 | .raw_event = vader3_raw_event, 310 | .event = vader3_event, 311 | }; 312 | 313 | // module_hid_driver(vader3_driver); 314 | static int __init vader3_init(void) 315 | { 316 | pr_info("loaded hid-vader3 %s\n", VADER3_VERSION); 317 | dbg_hid("vader3:%s\n", __func__); 318 | 319 | int ret = hid_register_driver(&vader3_driver); 320 | 321 | return ret; 322 | } 323 | 324 | static void __exit vader3_exit(void) 325 | { 326 | dbg_hid("vader3:%s\n", __func__); 327 | hid_unregister_driver(&vader3_driver); 328 | } 329 | 330 | module_init(vader3_init); 331 | module_exit(vader3_exit); 332 | -------------------------------------------------------------------------------- /hid-vader3/src/vader3.h: -------------------------------------------------------------------------------- 1 | /* 2 | * Support for Flydigi Vader 3 via Bluetooth (hardware doesn't support FF in that mode). 3 | * 4 | * Learning References (tutorials/blogs): 5 | * https://www.nirenjan.com/2020/linux-hid-driver/ 6 | * 7 | * Project References: 8 | * https://github.com/atar-axis/vader3 9 | */ 10 | 11 | #ifndef VADER3_H_FILE 12 | #define VADER3_H_FILE 13 | 14 | #include 15 | #include 16 | 17 | #ifndef VERSION 18 | #error "vader3 version not defined" 19 | #endif 20 | 21 | #define VADER3_VERSION __stringify(VERSION) 22 | 23 | #endif 24 | -------------------------------------------------------------------------------- /install.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash -e 2 | 3 | cd "$(dirname "$0")" || exit 1 4 | source "lib/verbose.sh" 5 | source "lib/installer.sh" 6 | 7 | if [[ ! -d /sys/devices/virtual/misc/uhid ]]; then 8 | 9 | >&2 echo "WARNING: kernel uhid module not found, controller firmware 5.x will not be supported" 10 | 11 | fi 12 | 13 | if [[ -z "${INSTALLED[*]}" ]]; then 14 | 15 | set -e 16 | 17 | echo "* creating dkms.conf" 18 | sed 's/"@DO_NOT_CHANGE@"/"'"${VERSION}"'"/g' hid-vader3/dkms.conf 19 | 20 | # TODO: Works around https://github.com/dell/dkms/issues/177 for DKMS 3 21 | echo "* adding hid-vader3-${VERSION} folder to /usr/src" 22 | mkdir -p "/usr/src/hid-vader3-${VERSION}" 23 | cp --recursive "${V[@]}" hid-vader3/. "/usr/src/hid-vader3-${VERSION}/." 24 | 25 | echo "* installing module (using DKMS)" 26 | dkms install "${V[*]}" "hid-vader3/${VERSION}" --force || cat_dkms_make_log 27 | 28 | else 29 | 30 | echo "already installed!" 31 | 32 | fi 33 | -------------------------------------------------------------------------------- /lib/installer.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | if [ ${EUID} -ne 0 ]; then 4 | echo >&2 "ERROR: You most probably need superuser privileges to use this script, please run me via sudo!" 5 | exit 3 6 | fi 7 | 8 | # shellcheck disable=SC2034 9 | GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || true) 10 | 11 | __version() { 12 | git describe --tags --dirty 2>/dev/null || sed -re's/v?(.*)/v\1/' "$(dirname "${BASH_SOURCE[0]}")/../VERSION" || { 13 | echo >&2 "ERROR: If you install from a git repository, you may need to run" 14 | echo >&2 "ERROR: sudo git config --global --add safe.directory \$PWD" 15 | echo >&2 "ERROR: to trust this git checkout for the root user." 16 | exit 3 17 | } 18 | } 19 | 20 | __version_lte() { 21 | [ "$1" = "$(echo -e "$1\n${2/-/.9999-}" | sort -V | head -n1)" ] 22 | } 23 | 24 | # shellcheck disable=SC2034 25 | VERSION=$(__version) 26 | 27 | DKMS_BIN=$(type -p dkms) 28 | 29 | # shellcheck disable=SC2086 30 | : ${DKMS_BIN:?Please install dkms to continue} 31 | 32 | get_dkms_versions_installed() { 33 | ${DKMS_BIN} status | tr -s ':,/ ' ' ' | awk -- '$1 == "hid-vader3" { print $2 }' | sort -nu 34 | } 35 | 36 | get_upstream_version_latest() { 37 | curl -sI "https://github.com/ahungry/vader3/releases/latest" | \ 38 | awk -- 'BEGIN{IGNORECASE=1} /^location:/ { n = split($2, v, /\//); print v[n]; exit }' | \ 39 | tr -d '[:space:]' 40 | } 41 | 42 | cat_dkms_make_log() { 43 | local last_error=$? 44 | if [ -n "${V[*]}" ]; then 45 | cat "/var/lib/dkms/hid-vader3/${VERSION}/build/make.log" || true 46 | fi 47 | exit ${last_error} 48 | } 49 | 50 | # shellcheck disable=SC2034 51 | INSTALLED=( 52 | $(get_dkms_versions_installed) 53 | ) 54 | -------------------------------------------------------------------------------- /lib/verbose.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | case "$1" in 4 | --verbose) 5 | echo "* verbose mode enabled" 6 | # shellcheck disable=SC2034 7 | V=("$1") 8 | set -x 9 | ;; 10 | "") 11 | ;; 12 | *) 13 | echo "usage: $0 [--verbose]" 14 | exit 1 15 | esac 16 | -------------------------------------------------------------------------------- /uninstall.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | cd "$(dirname "$0")" || exit 1 4 | source "lib/verbose.sh" 5 | source "lib/installer.sh" 6 | 7 | echo "* unloading current driver module" 8 | modprobe -r hid_vader3 || true 9 | 10 | echo "* looking for registered instances" 11 | echo "found ${#INSTALLED[@]} registered instance(s) on your system" 12 | 13 | for instance in "${INSTALLED[@]}" 14 | do 15 | echo "* $instance" 16 | 17 | set -e 18 | 19 | echo " * uninstalling and removing $instance from DKMS" 20 | dkms remove "${V[*]}" "hid-vader3/${instance}" --all 21 | 22 | echo " * removing $instance folder from /usr/src" 23 | rm --recursive "${V[@]}" "/usr/src/hid-vader3-$instance/" 24 | done 25 | --------------------------------------------------------------------------------