kernel packaging for android devices
tim.gardner at canonical.com
Mon Apr 22 14:38:48 UTC 2013
On 04/22/2013 08:11 AM, Ricardo Salveti de Araujo wrote:
> On 04/22/2013 10:59 AM, Sergio Schvezov wrote:
>> While doing the work to integrate the packaged kernels into the
>> Android/Phablet builds I noticed that the kernels have distinguishing
>> names such as nexus4 and nexus7 in their package names.
>> Those don't seem to be adequate as they are commercial names and can
>> umbrella different configurations/boards.
>> I suggest using the actual names used for the devices, so nexus7 should
>> be grouper and nexus4 should be mako.
>> In the case of maguro (Galaxy Nexus/Nexus3) we use the tuna kernel which
>> applies to much more devices.
>> Anyways, those are my thoughts and ideas to not get into conflicts later.
> The binary package can probably use the device name itself, as that will
> be specific even if they share the same sources (at least config
> specific, as I don't believe we're near having a single kernel for such
> What we can probably rename is the source tree and source package name,
> to use the umbrella codename, such as tuna for the galaxy nexus family.
> This will probably happen with other vendors as well later on.
I guess we could change the source package name for S, but we're pretty
well stuck for Raring. I'm inclined to leave the git repository name as
it is, e.g., nexus4 and nexus7. I assume we don't have to worry about an
upgrade path from R to S since there has yet to be an automated way of
upgrading kernels ?
Tim Gardner tim.gardner at canonical.com
More information about the kernel-team