> On Oct 5, 2016, at 13:35, Simon Wood <simon@xxxxxxxxxxxxx> wrote: > > On Wed, October 5, 2016 10:54 am, Frank Praznik wrote: >> The best answer I can give is "not to my knowledge”. Rumble and LEDs >> have standard kernel interfaces but obviously we can’t guarantee 100% that >> nobody is using hidraw directly. Commercial games and engines aren't >> running as root and thus can’t use hidraw so I think we can safely say >> that no major commercial software will be broken by this. > > There are a couple of projects I know of, but I am unable to say whether > they are still active or whether proposed changes will affect them... > https://thp.io/2010/psmove/ > http://moveonpc.blogspot.ca/ > https://github.com/chrippa/ds4drv > > Audio output is one area of the DS4 which is not supported in kernel, > maybe some renewed interest can get this working. > > I agree with Frank that we should move forward, if something gets broken > we can work a better solution. > Simon. > > acked-by: Simon Wood <simon@xxxxxxxxxxxxx> > > > This change only affects sending rumble/LED output reports to the DS4, so hidraw input reports and sending/receiving feature reports will be unchanged as will anything not in the DS4 codepath (ie. Move controllers). It looks like ds4drv has both a hidraw backend and one which uses raw Bluetooth sockets. The raw socket backend should be unaffected, but the hidraw backend will probably have issues. It should be trivial to patch it to append the CRC to the raw data packet like the kernel module does though. It also looks like hidraw isn’t the default Bluetooth backend which reduces the odds that it will be an issue even further. I’m definitely in favor of moving toward more correct behavior as long as the ds4drv project is given a warning to start sending CRC-ed output reports. acked-by: Frank Praznik <frank.praznik@xxxxxxxxx>-- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
