On Sun, Dec 18, 2005, Darren Salt wrote: > I demand that Oliver Endriss may or may not have written... > > Johannes Stezenbach wrote: > >> It would be better to use Gerd Knorr's ir-common (for av7110, too), so > >> keymaps could be manipulated using the standard EVIOCSKEYCODE ioctl, e.g. > >> by using input-kbd from Gerd Knorr's input-utils package. > > > Agreed. > > > How should we handle control data > > - RC5/RCMM selection > > - inversion setting > > if we drop /proc/av7110_ir? As an afterthought, in case ir-common and/or EVIOCSKEYCODE doesn't fly, we still shouldn't copy av7110_ir stuff for budget, but create some common code which would work for all similar cards. > > Should we add module parameters or keep /proc/av7110_ir just for that? > > Wouldn't this really need to be per-device? If so, these should be extra > parameters in the relevant input device directory in sysfs. (If the driver is > still meant to be 2.4-compatible, the existing method should be retained for > that at least.) Good point. Johannes
