On Wed, Dec 10, 2008 at 4:36 PM, Stefan Schmidt <[EMAIL PROTECTED]> wrote: > If OpenEZX would like to come out of the toys-for-developer corner we need to > offer the user something. Most of them do not care about having a 2.6 kernel. > They ask what else we can offer. And if we like to be a solid base for stuff > like Qt Extended, Android or FSO, we need to make compromises from time to > time.
Well, most people cant even use boot_usb, so it doesnt really matter if the suspend/resume support is on the bootloader or on the kernel. Anybody that provides a .shx file gets the users, no matter if it is 2.6, 2.4, android, qtopia, openmoko, bootloader or no bootloader.... People cant use anything that isnt is as easy as "Next, Next, Finish". Im not really interested in this kind of users at the moment. Right now we need users that can discover things by themselves, are not afraid of some C code, and wish to learn more than to have a new environment on their phones. When OpenEZX is stable enough, and I start focusing the mass of users (noobs), you can expect a real easy "Next, Next, Finish" windows application that will do everything.. No need to worry about bootloaders, kernels, etc.. > Back to the topic that shows me that you are not interested in having such a > patch. I'm well aware that you are the driving force in OpenEZX for a long > time > while myself is getting in-active more and more. > > That leaves me two options a) let the issue open or b) kick my ass and prepare > such a patch myself. I think you would not have a problem with such a patch as > long as it lifes in his own branch which ezx/current has no default dep on? Of course i would not have a problem with this.. But note that this is not the right way to go, you know that you have less and less time to maintain openezx (same with me), and thats why you should focus the "no patches out of mainline" approach. My goal is to let users download the ezx kernel source code from www.kernel.org, not from git.openezx.org :) -- Daniel Ribeiro
