On Wed, 2011-09-21 at 12:45 -0700, Deepak Saxena wrote:
Hi all,
We need to start planning for Linaro Connect/UDS in Orlando. For those that have not attended one of these events before, the way they are run is very different than a traditional conference. We will be running summit sessions which are focused discussions on specific topics with the goal of getting a list of concrete action items, both technical and logistical, towards solving a problem. Unlike prior UDS events, where Linaro was 100% focused on planning, we will split the day with planning summits in the morning and hacking in the afternoon. I'd like to gather a list of topics from everyone so that I can start creating the session blueprints that will be used by the scheduler and the notetaking system. My current list of topics:
...
- Android Upstreaming
I'd break these out into two major items for next cycle: o Wakelock equivalent functionality o Ashmem equivalent functionality
As well as likely items from this cycle that have been back-burnered: o lowmemory killer functionality o alarm enabled timerfd
Although I'm ok covering all of these in one discussion.
Another item that is sort of un-related to previous Linaro work is the 2038 issue with 32 bit time_t and what sort of workarounds folks think are reasonable. Intel is pushing a new arch ABI x32, which is a 32bit architecture, but uses a 64 bit time_t. We may want to look for something similar (introducing a new ABI) so that 32bit applications written today continue to function past 26 years from now. Are there any other ABI cleanups needed that could go along with this? (Or did everything except time_t get sorted during the last ABI cleanup? :) Clearly this isn't super critical, as all other 32 bit arches have the same problem, so it can be deferred, but we should maybe start thinking about it.
thanks -john