tuna and maguro, a quick clarification

[Jean-Baptiste Queru]

"Double fish, what does it mean?"

There've been several questions in this group about tuna vs maguro,
but such questions were buried in the middle on long threads so I'll
try to summarize in a new clean thread.

The Galaxy Nexus family is codenamed "tuna". Using fish names in
relationship to devices isn't quite new, since in the past we've had
goldfish (emulator), trout (G1), mahimahi (Nexus One), herring (Nexus
S) and stingray (Xoom).

There are two actual Galaxy Nexus devices, codenamed maguro and toro.
Maguro is the GSM/HSPA+ variant, and Toro is the CDMA/LTE variant.
Toro is a bit fatter, hence its name.

In the source tree released yesterday, there are two directories
called device/samsung/tuna and device/samsung/maguro. The former
contains all the files that are common to both toro and maguro, while
the latter contains the maguro-specific files. There's no
device/samsung/toro in AOSP yet, that directory will get created when
we release the exact code that actually ships on toro.

device/samsung/tuna contains makefiles as if it was an actual device.
There's no such device in reality, but the abstraction is convenient
for engineering purposes as it allows creating a common system image
that works on both toro and maguro, even though it supports neither
GSM/HSPA+ nor CDMA/LTE. This is only meant for engineering purposes,
and the only real devices are maguro and toro.

Looking a little bit in my crystal ball, we'll be supporting toro in
AOSP along with maguro, with similar downloads for proprietary
binaries, and the whole process is tied to shipping toro. Be aware
that my crystal ball is rarely more accurate than a Magic 8-ball, so
you should take this with a grain of salt.

Personally, I prefer working with maguro, as supporting GSM in AOSP is
easier than CDMA in my experience.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, 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.

[Siva]

Thanks JBQ !! This is exact info i was looking for :) !!

Any idea on when will product package available for herring ( Nexus
S ) or is it left to dev playground to come up with PP :) ??

BR/Siva

[Jean-Baptiste Queru]

Files related to specific retail devices get released in AOSP when the
matching build it on its way to consumers. Since Nexus S isn't getting
ICS right now today as I'm writing this, the matching files also
aren't available right now today as I'm writing this. And that's
really all I can say on that subject.

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en