For anything out of the ordinary (like what you're proposing), the
process is "ask android-contrib". So far, so good :)
On the subject of creating the external/ project, besides getting an
approval on the principle of this change, we'll need to know where the
upstream code lives, how it's licensed, and the plan to handle both
the upstream copy and the Android copy.
#1 starts by updating the Android copy of the relevant linux kernel
header(s) in external/kernel-headers. You'll want to reference the
exact commit SHA-1 from which you copied those files from the kernel
tree. Once that's approved, the stripped variant used in bionic can be
re-generated.
#2 will involve some backporting indeed. Let's start with grouper
(Nexus 7, the newest device) and work backward from there. I'm not
sure that we'll strictly need this in goldfish 2.6.29, especially as
there's some work going on to move goldfish to 3.4. Uploads go through
the AOSP Gerrit as well.
#3 is very similar to #2, it's indeed just a case of uploading the
matching contributions.
JBQ
> --
>
>
>
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.