On Tue, Nov 18, 2014 at 11:43:49PM +0100, Antonio Ospite wrote:
> On Mon, 17 Nov 2014 21:01:44 -0500
> bri wrote:
> If you can upload a shell script to the target system you may as well
> upload a static binary; and if you can use a modified kernel you can
> compile _for_ the target even if not
On Mon, 17 Nov 2014 21:01:44 -0500
bri wrote:
> On Mon, Nov 17, 2014 at 01:35:18PM +0100, Antonio Ospite wrote:
> > I had tried doing something similar in the past (the parsing was just a
> > sscanf): http://thread.gmane.org/gmane.linux.bluez.kernel/5261 but then
> > we deliberately decided
On Tue, 18 Nov 2014 09:26:29 -0500
bri wrote:
> On Mon, Nov 17, 2014 at 10:21:53PM -0500, Frank Praznik wrote:
> > Hi Brian,
> >
> > On 11/17/2014 19:00, bri wrote:
> > >
> > >>Yeah, the device ID in the driver is only for tracking devices internally
> > >>and setting sane default LED values.
On Mon, Nov 17, 2014 at 10:21:53PM -0500, Frank Praznik wrote:
> Hi Brian,
>
> On 11/17/2014 19:00, bri wrote:
> >
> >>Yeah, the device ID in the driver is only for tracking devices internally
> >>and setting sane default LED values. It has no meaning outside of the
> >>module. Like Antonio
On Tue, 18 Nov 2014 09:26:29 -0500
bri b...@abrij.org wrote:
On Mon, Nov 17, 2014 at 10:21:53PM -0500, Frank Praznik wrote:
Hi Brian,
On 11/17/2014 19:00, bri wrote:
Yeah, the device ID in the driver is only for tracking devices internally
and setting sane default LED values. It
On Mon, 17 Nov 2014 21:01:44 -0500
bri b...@abrij.org wrote:
On Mon, Nov 17, 2014 at 01:35:18PM +0100, Antonio Ospite wrote:
I had tried doing something similar in the past (the parsing was just a
sscanf): http://thread.gmane.org/gmane.linux.bluez.kernel/5261 but then
we deliberately
On Tue, Nov 18, 2014 at 11:43:49PM +0100, Antonio Ospite wrote:
On Mon, 17 Nov 2014 21:01:44 -0500
bri b...@abrij.org wrote:
If you can upload a shell script to the target system you may as well
upload a static binary; and if you can use a modified kernel you can
compile _for_ the target even
On Mon, Nov 17, 2014 at 10:21:53PM -0500, Frank Praznik wrote:
Hi Brian,
On 11/17/2014 19:00, bri wrote:
Yeah, the device ID in the driver is only for tracking devices internally
and setting sane default LED values. It has no meaning outside of the
module. Like Antonio said, if you want
Hi Brian,
On 11/17/2014 19:00, bri wrote:
Yeah, the device ID in the driver is only for tracking devices internally
and setting sane default LED values. It has no meaning outside of the
module. Like Antonio said, if you want the system number for a controller
you are better off just getting
On Mon, Nov 17, 2014 at 01:35:18PM +0100, Antonio Ospite wrote:
> I had tried doing something similar in the past (the parsing was just a
> sscanf): http://thread.gmane.org/gmane.linux.bluez.kernel/5261 but then
> we deliberately decided against exposing specific sysfs interfaces for
>
On Sun, 16 Nov 2014 13:18:46 -0500
bri wrote:
Hi Brian,
> Add some sysfs interfaces to cover some corner use cases when provisioning:
>
> 1) Allow read access to the IDA index through device/gamepad_number. The
> IDA index is used to identify the device to the user as the "controller
>
On Sun, 16 Nov 2014 13:18:46 -0500
bri b...@abrij.org wrote:
Hi Brian,
Add some sysfs interfaces to cover some corner use cases when provisioning:
1) Allow read access to the IDA index through device/gamepad_number. The
IDA index is used to identify the device to the user as the controller
On Mon, Nov 17, 2014 at 01:35:18PM +0100, Antonio Ospite wrote:
I had tried doing something similar in the past (the parsing was just a
sscanf): http://thread.gmane.org/gmane.linux.bluez.kernel/5261 but then
we deliberately decided against exposing specific sysfs interfaces for
Hi Brian,
On 11/17/2014 19:00, bri wrote:
Yeah, the device ID in the driver is only for tracking devices internally
and setting sane default LED values. It has no meaning outside of the
module. Like Antonio said, if you want the system number for a controller
you are better off just getting
Add some sysfs interfaces to cover some corner use cases when provisioning:
1) Allow read access to the IDA index through device/gamepad_number. The
IDA index is used to identify the device to the user as the "controller number"
and is reflected via the initial LED states when plugged in. This
Add some sysfs interfaces to cover some corner use cases when provisioning:
1) Allow read access to the IDA index through device/gamepad_number. The
IDA index is used to identify the device to the user as the controller number
and is reflected via the initial LED states when plugged in. This
16 matches
Mail list logo
