Em 21-05-2012 00:20, Antti Palosaari escreveu: > ma 21.5.2012 5:42 VDR User kirjoitti: >> On Sun, May 20, 2012 at 7:22 PM, Antti Palosaari <cr...@iki.fi> wrote: >>>> So you think that it makes more sense to ignore existing issues rather >>>> than fix them. Isn't fixing issues& flaws the whole point of an >>>> overhaul/redesign? Yes, it is. I do get the point you're trying to >>>> make -- there are bigger fish to fry. But this is not an urgent >>>> project and I disagree with the attitude to just disregard whatever >>>> you deem unimportant. If you're going to do it, do it right. >>> >>> I am not sure what you trying to say. Do you mean I should try to get >>> remote >>> controller totally optional module which can be left out? >> >> I am saying it's a dependency that is currently forced onto every usb >> device whether the device even supports rc or not. This is clearly >> poor design. For that matter, the whole usb handling must be poor >> design if it needs to be overhauled. >> >>> How much memory will be saved if remote can be left out as unloaded? >> >> I don't know. I'm merely pointing out just one of the issues that >> should be resolved if the idea is to fix things that are wrong with >> usb handling. If nobody cares, doesn't think it matters, or simply >> doesn't want to bother, so be it. I guess I'm crazy but when I'm >> facing an overhaul, especially when there's no rush, I compile a list >> of _everything_ that's wrong and make sure the overhaul fixes it all. >> I guess there's quite a difference between my idea of what an overhaul >> should be, and other peoples. >> >> If you really want, there's probably people who deal with embedded >> systems where every wasted byte counts, that would agree cleaning up >> the waste is a good idea. >> >> Since nobody thinks it should be fixed, just pretend I didn't even >> bring it up. Problem solved. > > There is quite few devices that are shipped without remote. I agree that > it could be better and more modular. And it is asked multiple times during > these years. But my main motivation is to fix problems first and then do > enhancements. I will look if I can found some time for that too.
I see two separate issues here: 1) the dvb_usb properties struct needs to point if the device has RC or not. It could be possible to optimize it if the remote code is not enabled, but provided that the structure is properly designed, the only per-device information is the RC keytable. Optimizing it when IR is not compiled will save just a few bytes per card. Not worth, IMHO. 2) Remove the RC dependency from dvb-usb, and making the dvb-usb-remote code as a module. This can bring some savings, as the RC core and IR decoders won't be loaded. I think (2) is valuable to do, but this can be done latter with a likely simple patch, and won't require any changes at the DVB structures. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
