From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Philip Langdale <philipl@overt.org>,
linux-input@vger.kernel.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: INPUT_COMPAT_TEST
Date: Wed, 7 Sep 2011 11:54:16 -0700 [thread overview]
Message-ID: <20110907185416.GC2874@core.coreip.homeip.net> (raw)
In-Reply-To: <4E67BAAE.9060605@zytor.com>
On Wed, Sep 07, 2011 at 11:40:46AM -0700, H. Peter Anvin wrote:
> On 09/07/2011 11:37 AM, Dmitry Torokhov wrote:
> >>
> >>I thought there were pointers, (or longs) there too.
> >>
> >>In fact, we might have had the worst of both worlds here...
> >
> >The pointers are in ioctl paths (upload of force-feedback effects with
> >custom waveforms - noone actually uses them in real life).
> >
>
> Ah... we might have lucked out then!
>
> The proc/sysfs issue is still HUGE, however, because that affects
> all the read/write paths *indirectly*.
>
Yeah, we are stuck with these unfortunately... Unless we want to say
that x32 applications will be presented with bitmaps encoded with 64-bit
segments instead of 32-bit ones. This would mostly matter to startup
scripts... X and the others use ioctls, not proc/sysfs.
--
Dmitry
prev parent reply other threads:[~2011-09-07 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 18:45 INPUT_COMPAT_TEST H. Peter Anvin
2011-07-08 20:46 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-08 22:22 ` INPUT_COMPAT_TEST H. Peter Anvin
2011-07-08 22:37 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-08 22:44 ` INPUT_COMPAT_TEST Thadeu Lima de Souza Cascardo
2011-07-08 23:18 ` INPUT_COMPAT_TEST H. Peter Anvin
2011-07-09 0:35 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-09 8:04 ` INPUT_COMPAT_TEST H. Peter Anvin
2011-09-07 18:16 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-09-07 18:22 ` INPUT_COMPAT_TEST H. Peter Anvin
2011-09-07 18:37 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-09-07 18:40 ` INPUT_COMPAT_TEST H. Peter Anvin
2011-09-07 18:54 ` Dmitry Torokhov [this message]
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=20110907185416.GC2874@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-input@vger.kernel.org \
--cc=philipl@overt.org \
/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).