From: bri <bri@abrij.org>
To: Antonio Ospite <ao2@ao2.it>
Cc: Frank Praznik <frank.praznik@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
Henrik Rydberg <rydberg@euromail.se>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 001/001] hid-sony.c: add sysfs provisioning
Date: Tue, 18 Nov 2014 19:13:53 -0500 [thread overview]
Message-ID: <20141119001353.GA635@abrij.org> (raw)
In-Reply-To: <20141118234349.7b44949197898390d496f1cd@ao2.it>
On Tue, Nov 18, 2014 at 11:43:49PM +0100, Antonio Ospite wrote:
> On Mon, 17 Nov 2014 21:01:44 -0500
> bri <bri@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 if not _on_ the target.
>
> And if you need help to write the program which uses the HID ioctls
> just ask :)
What, no, that's really super easy for me. I don't prefer to do it that
way, personally so I won't -- I'm going to have to heavily mod things
down through hid-core and up through js to get other behaviors I want,
anyway.
The point of pushing the patch up here, of course, was so that people
who could not do many of the above listed things would have an easy
interface.
Thanks, though.
If I actually end up having the time to get anything working I'll post
a link to a repo so that if anything looks in there looks interesting
someone can ask me for a patch submittal.
next prev parent reply other threads:[~2014-11-19 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 18:18 [PATCH 001/001] hid-sony.c: add sysfs provisioning bri
2014-11-17 12:35 ` Antonio Ospite
2014-11-18 2:01 ` bri
2014-11-18 22:43 ` Antonio Ospite
2014-11-19 0:13 ` bri [this message]
[not found] ` <546A4EF7.903@gmail.com>
[not found] ` <20141118000005.GA32256@abrij.org>
2014-11-18 3:21 ` Frank Praznik
2014-11-18 14:26 ` bri
2014-11-18 22:30 ` Antonio Ospite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141119001353.GA635@abrij.org \
--to=bri@abrij.org \
--cc=ao2@ao2.it \
--cc=frank.praznik@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rydberg@euromail.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).