In addition to an update to the excellent SC Controller software, it seems there's also work towards getting full Steam Controller support in the Linux Kernel.
Currently, to get proper use out of the Steam Controller you either need the Steam client open, or to use something like SC Controller. However, this could change due to the reverse engineering effort from one hacker. This is actually the second revision to their patches, which cleans it up and implements a few more features.
Part of the problem, is that currently it will show up as multiple different types of devices like a virtual keyboard, a virtual mouse and so on. Here's what the developer of the patch said:
This driver was reverse engineered to provide direct kernel support in case you cannot, or do not want to, use Valve Steam Client. It disables the virtual keyboard and mouse, as they are not so useful when you have a working gamepad.
Working: buttons, axes, pads, wireless connect/disconnect.
TO-DO: Battery, force-feedback, accelerometer/gyro, led, beeper...
They said they are working on a third revision to the patches and there will likely be more work to be done if it is to be accepted. Valve developer Pierre-Loup A. Griffais has been commenting on the mailing list as well to provide some help and ask questions. Part of the issue, is this needs to not break support for the Steam Controller with the Steam Client or other software like SC Controller. Nothing seems set in stone right now in regards to this particular code, so it will be interesting to see what happens.
You can find the information here on the mailing list.
Article taken from GamingOnLinux.com.
Quoting: ArdjeBecause Valve is not expecting you to run the latest and greatest bazinga kernel on your old debian install.
What they did fits perfectly into the confined spaces of a stable desktop environment.
See above, it's not an excuse not to upstream the driver. Proper example: amdgpu.
And regarding the firmware, it should have been open source to begin with, Valve even promised that much. But they never opened it.
Last edited by Shmerl on 1 March 2018 at 3:32 pm UTC
Quoting: Shmerl"Done right" or not, it means removing user's choice.I prioritize "done right and just works" far above "complete freedom of users choice". Time is much to precious for me to spend hours into setting up my environment.
Edit: removed some ranting, it's not worth it.
Last edited by jens on 1 March 2018 at 9:01 pm UTC
slaapliedje Mar 2, 2018
Quoting: ArdjeSee above, it's not an excuse not to upstream the driver. Proper example: amdgpu.So you expect us linux users to wait about 10 years before there is even a proper idea how to incorporate a product into the linux kernel?
Because that's how long it took before amdgpu came to be, or even longer... And amdgpu is about a fully established and fully defined API between applications and the hardware...
There still is no clear path for the steam controller.
You can follow a design path for years and finally reach a product and conclude it was a waste of time because it doesn't work as you have now realised, or you can play with the device, reiterate the way you want to use it, and only after that look at how the kernel should be modified to incorporate support for that.
As I said: look at what valve is doing for steamvr, they are modifying and patching and updating RADV and any other *open* (I think they are now looking at amdvlk too) drivers to what they think how VR should work, and push those patches upstream, even to Kronos to adjust the specs, and the linux kernel to fix how one should look at displays.
They are going full experimental on VR, but there is still 0 working product.
They can actually do that, because they get some idea how things should work using the windows platform.
The steamcontroller was working from day 1, but by keeping the full functionality in the steam client for now, they could keep on experimenting.
Ideas seems to be stable now, and Valve helps or hints in the development of the kernel drivers.
I still wonder how, because you still need a middle layer to convert the controller input to something the application groks. And I wonder how the the force feedback API will look like... Like an alsa PCM device (*that's* how much you control you can do)? Or like a rumble pad (dumb).
Quoting: GuestQuoting: PitBut I'm always told here that Valve is soooo supportive of Linux. Hmmm.I really don't understand what point you were making with your tone in your post.
Instead they keep HW details secret and have someone do reverse engineering to properly support Linux....
Did I say some thing bad?
No, your statement was/is absolutely correct.
My answer wasn't against you, but targeted at those people always claiming how supportive Valve is to Linux. Because the two statements don't really go together well....
Quoting: PitSo it's only black or white for you?Quoting: GuestQuoting: PitBut I'm always told here that Valve is soooo supportive of Linux. Hmmm.I really don't understand what point you were making with your tone in your post.
Instead they keep HW details secret and have someone do reverse engineering to properly support Linux....
Did I say some thing bad?
No, your statement was/is absolutely correct.
My answer wasn't against you, but targeted at those people always claiming how supportive Valve is to Linux. Because the two statements don't really go together well....
Quoting: ArdjeSo you expect us linux users to wait about 10 years before there is even a proper idea how to incorporate a product into the linux kernel?
Because that's how long it took before amdgpu came to be, or even longer...
When the driver is a mess, let it take as long as it should to get upstreamed. amdgu is whole different level of complexity than the Steam controller though. So the later should not take as long.
And experimenting with drivers is not detrimental to keeping them open. So there is simply no excuse.
Last edited by Shmerl on 2 March 2018 at 2:08 pm UTC
Quoting: jensQuoting: PitNo, your statement was/is absolutely correct.So it's only black or white for you?
My answer wasn't against you, but targeted at those people always claiming how supportive Valve is to Linux. Because the two statements don't really go together well....
On the contrary. I never denied Valve is contributing. I'm only pointing out that there are also black spots on their shirt that others seem to ignore/overlook.
Quoting: PitGlad to read that, you initial posting on the subject suggests otherwise.Quoting: jensQuoting: PitNo, your statement was/is absolutely correct.So it's only black or white for you?
My answer wasn't against you, but targeted at those people always claiming how supportive Valve is to Linux. Because the two statements don't really go together well....
On the contrary. I never denied Valve is contributing. I'm only pointing out that there are also black spots on their shirt that others seem to ignore/overlook.
slaapliedje Mar 2, 2018
How does the kernel level driver plan on handling the configuration of the controller? I think these are all things Valve was considering before they just said 'screw it' and slapped it into Steam.
Patreon
PayPal
See more from me