Android Mainlining Project - Revision history

Tim Bird: /* Patch/Feature Status Chart */

2012-10-26T22:09:12Z

‎Patch/Feature Status Chart

Tim Bird: /* Patch/Feature Status Chart */

2012-10-26T22:06:13Z

‎Patch/Feature Status Chart

Tim Bird: /* Patch/Feature Status Chart */

2012-10-26T22:02:06Z

‎Patch/Feature Status Chart

Tim Bird: /* Patch/Feature Status Chart */

2012-10-26T21:58:52Z

‎Patch/Feature Status Chart

Tim Bird: /* Patch/Feature Status Chart */

2012-10-26T21:55:06Z

‎Patch/Feature Status Chart

Const: /* Meetings */ + KS2012: Status of Android upstreaming

2012-10-13T09:43:20Z

‎Meetings: + KS2012: Status of Android upstreaming

Const: + USB, ccg

2012-10-13T09:40:04Z

+ USB, ccg

Tim Bird: /* Patch/Feature Status Chart */

2012-06-18T22:36:43Z

‎Patch/Feature Status Chart

Tim Bird: /* Patch/Feature Status Chart */

2012-05-02T20:57:53Z

‎Patch/Feature Status Chart

Bhairavi: /* Patch/Feature Status Chart */

2012-05-01T15:41:49Z

‎Patch/Feature Status Chart

@@ Line 155: / Line 155: @@
+|
+|
-|Andrzej Pietrasiewicz?  Mike Lockwood of Google seems to be involved.
+|Andrzej Pietrasiewicz?, Kyungmin Park?.  Mike Lockwood of Google seems to be involved.
 |[[#USB|USB]]

@@ Line 98: / Line 98: @@
 |yes
 |Rafael Wysocki
-|Is important due to impact on board support and drivers by 3rd parties.  Last effort was around "autosleep and wakelocks".
+|John Stultz wrote (2012-10-11):
 See http://lwn.net/Articles/479841/ and this thread: http://thread.gmane.org/gmane.linux.kernel/1249726.  This code apparently made it into 3.4, with more code to appear in 3.5?
 |-
@@ Line 127: / Line 135: @@
 |yes
 |no one
-|Generated a fair amount of discussion on last submission. See http://elinux.org/Android_Binder#obstacles_to_mainlining
+|John Stultz wrote (2012-10-11):
 See also this thread: http://lists.linuxfoundation.org/pipermail/ce-android-mainline/2012-January/thread.html#42
 |-

@@ Line 175: / Line 175: @@
 |yes (but system might work without it)
 |Anton Vorontsov
-|See https://lkml.org/lkml/2011/12/18/173 for discussion about these patches
+|Anton said (2012-10-11):
 |-
 |ram console
 |ability to save console output to a reserved ram area for diagnostics on a subsequent boot
-|in drivers/staging/android, in kernel version 3.3 2012.03.19
+|in drivers/staging/android, in kernel version 3.3 2012.03.19 ; new system pstore RAM backend is mainlined
 |no
-|Shuah Khan
+|Anton Vorontsov
 |No lkml submission attempt history found so far. pstore fs interface solves the same problem and is in mainline 3.1.5. fs/pstore  Reference - http://lwn.net/Articles/421297/ After investigating and discussing ram console use cases, it is clear that the proposal to use ram-oops and pstore will not be a complete solution to cover all the cases. Hence, the going forward plan is to pursue ram console inclusion in the mainline. ram console is going through re-write splitting it into twp drivers. Waiting for these changes to get into the 3.3 staging area. For now working with the unofficial patches.

@@ Line 207: / Line 207: @@
 |Jesse Barker
+|
 |}

@@ Line 139: / Line 139: @@
 |Android USB gadget driver
 |Support for Android as gadget device from host
-|unknown
-|? (not sure if needed for basic bringup or not, but would be really painful if missing)
-|no one?
+|Andrzej Pietrasiewicz?  Mike Lockwood of Google seems to be involved.
 |[[#USB|USB]]
 |-
 |timed gpio
@@ Line 173: / Line 185: @@
 Anton Vortontsov moved some functionality from the ram_console into the new "persistent_ram" feature, in fs/pstore/ram_core.c (May 17, 2012 - see commit cddb8751c)
 |-
 |ion graphics memory driver

@@ Line 30: / Line 30: @@
 * Linaro blueprint for project: https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-android-upstreaming
-== Meetings ==
+== Updates ==
 * Meeting: [[Android mainlining interest group meeting 2012]]
 ** Summary: 9:30- 12:00 February 10, 2012 at the Sofitel Hotel in Redwood Shores, California.

@@ Line 89: / Line 89: @@
 |See [[Mainline Android logger project]] for a list of ideas, issues and a project plan for this feature
 Also see [http://lkml.indiana.edu/hypermail/linux/kernel/1112.2/index.html#02419 this LKML discussion thread]
-Some cleanup patches in linux-next, with more extensive changes to be written, tested, reviewed by Tim in Spring 2012.  Tim has some changes to avoid hardcoding the logging channels, but needs to test them before submission to mainline (5/2/2012).
+Some cleanup patches in linux-next, with some changes to avoid hardcoding logging channels (see Linus' tree commit: 10b241991fc)
 |-
 |wakelocks
 |Power management locking mechanism to prevent opportunistic suspend
-|not mainlined, as of 2012.03.19, work in progress
+|parts mainlined, as of 2012.06.18, work in progress
 |yes
 |Rafael Wysocki
 |Is important due to impact on board support and drivers by 3rd parties.  Last effort was around "autosleep and wakelocks".
-See http://lwn.net/Articles/479841/ and this thread: http://thread.gmane.org/gmane.linux.kernel/1249726
+See http://lwn.net/Articles/479841/ and this thread: http://thread.gmane.org/gmane.linux.kernel/1249726.  This code apparently made it into 3.4, with more code to appear in 3.5?
 |-
 |Android alarm timers
@@ Line 111: / Line 112: @@
 |yes
 |John Stultz
-|Working on fadvise volatile alternative implementation that handles part of the ashmem functionality. However, there are additional aspects of ashmem design that need to be addressed(no tmpfs mounts, atomic create/unlink behavior,etc).
+|Working on fadvise volatile alternative implementation that handles part of the ashmem functionality. However, there are additional aspects of ashmem design that need to be addressed (no tmpfs mounts, atomic create/unlink behavior,etc).
 |-
 |network security
@@ Line 169: / Line 170: @@
 |Shuah Khan
 |No lkml submission attempt history found so far. pstore fs interface solves the same problem and is in mainline 3.1.5. fs/pstore  Reference - http://lwn.net/Articles/421297/ After investigating and discussing ram console use cases, it is clear that the proposal to use ram-oops and pstore will not be a complete solution to cover all the cases. Hence, the going forward plan is to pursue ram console inclusion in the mainline. ram console is going through re-write splitting it into twp drivers. Waiting for these changes to get into the 3.3 staging area. For now working with the unofficial patches.
 |-
 |ion graphics memory driver

@@ Line 147: / Line 147: @@
 |no? (is this needed for basic bringup?)
 |Shuah Khan
-|A new transient trigger added to led triggers in Linux 3.4 to address the need for one shot timer activation. This driver could be removed once the legacy libaries are changed to use the new transient trigger. https://lkml.org/lkml/2012/4/30/288
+|A new transient trigger added to led triggers in Linux 3.4 to address the need for one shot timer activation. This driver could be removed once the legacy libraries are changed to use the new transient trigger. https://lkml.org/lkml/2012/4/30/288
 |-
 |timed output
@@ Line 154: / Line 154: @@
 |no? (required by timed_gpio)
 |Shuah Khan
-|A new transient trigger added to led triggers in Linux 3.4 to address the need for one shot timer activation. This driver could be removed once the legacy libaries are changed to use the new transient trigger. https://lkml.org/lkml/2012/4/30/288
+|A new transient trigger added to led triggers in Linux 3.4 to address the need for one shot timer activation. This driver could be removed once the legacy libraries are changed to use the new transient trigger. https://lkml.org/lkml/2012/4/30/288
 |-
 |low memory killer