Re: [Council] Council_Update-July_2011
Quote:
Quote:
|
Re: [Council] Council_Update-July_2011
Quote:
And think about North America: Nokia never had a great success in the USA because they never went down to strict agreements with the carriers. DAMN, in the US you have to pay to RECEIVE a message. It's something totally different against the rest of the world. And now it looks like for WP7 there will be huge agreements with carriers for subsidizing. I will never buy a susidized phone for myself. For my business and if it is convenient yes, but not for my private life. Everything is centered on the service, the HW is a surplus. As baron BIC said once, gift them with razors because they will buy blades. Sorry, I want to decide my blades. Again on topic, I think momcilo centered well the matter. We have to fix a path, and then to start following it. About option 1, I discarded it because I don't think it will happen. Let's say if we have any news from the Council, but I sincerely am not hoping anything from Nokia, sorry. I will be glad to be wrong. |
Re: [Council] Council_Update-July_2011
Quote:
Council members: what was the voice of The Creator? |
Re: [Council] Council_Update-July_2011
Quote:
Second problem is size of kernel. Modern kernels dont fit in 2mb. Someone once made uboot for N8x0, maybe someone can do that. |
Re: [Council] Council_Update-July_2011
Quote:
As for patches for omap2, I think that 2.6.35 on ubuntu maverick has omap2 listed. I know this since I was playing with gentoo and beagleboard(omap3). |
Re: [Council] Council_Update-July_2011
Quote:
|
Re: [Council] Council_Update-July_2011
Quote:
Can we find volunteers to get a cpufreq kernel going based on linux-omap? It will help no matter if it is Debian, Ubuntu, MeeGo or whatever |
Re: [Council] Council_Update-July_2011
I'm not sure that there is a cpufreq issue, at least openwrt seemed to scale fine last time I tried it. Their patches on top of vanilla kernel.org are here.
|
Re: [Council] Council_Update-July_2011
I just like to say that for a long time I haven't browsed through 3 pages (in line) of such useful, meritocratic and informative discussion. Really, respect for You guys.
I would also opt for "softer" option 4 - main focus on new way, while providing things for older devices when we can (and it doesn't require months of work). I also think there still be bunch of people developing things for older devices, and there is no problem with "new way" people cooperating with "them", or even being on both "camps" at the same time ;) I mean that if someone provide more openness for legacy devices, our new "foundation" should be open and helpful, but main goal fixed as "new way". Ho ever, since developing first really "our" software/hardware (CordiaTAB, if it will be proved to most independent?), we should try to keep as tight "compatibility" with it (in case of even further devices/system versions), as it's possible. So, literally, we start new things, and people who "follow" us (I mean not only developers - average Joey the (power) user, who buy device), can be sure that his device from "our" legacy won't be left dead after 2 years. Just my 2 cents, from guy much-more-(power)user-than-dev. what do you think about it? |
All times are GMT. The time now is 18:42. |
vBulletin® Version 3.8.8