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 -- 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
