Stable Snapshot Android release of rowboat called "Android DevKit"

GoogleGroups
1

Hi all,

Looking at multiple requests for a stable and tested snapshot of our
rowboat components, we are planning to provide a periodic release
called Android DevKit for the users of OMAP35x, AM35x and AM37x EVM
and Beagle platforms.

Our first Android DevKit 1.0 release is planned for July 30th 2010,
below are some of the components or requirements we have captured so
far.

NOTE: The DSP software components is not considered so far in this release.

Let us know if you need any additional features or support to be added
to this list and what kind of validation you expect or products you
want us to include. Please don't hesitate to help us in packaging
these :slight_smile:

Contents of Android DevKit 1.0

    * Android Kernel and device drivers
          o Linux Kernel 2.6.32 with Android patches
          o u-boot
          o x-loader

    * Tools
          o ARM Toolchain pre-built
          o Pin muxing utility
          o Flashing utility
          o SignGP
          o SD Card Image creator

    * SGX DevKit for Android
          o Release binaries of user space libraries for platforms
having SGX core
          o Source for Graphics Kernel Modules. Contains kernel
dependent code, changes depending on Linux kernel used
          o Demos, Training courses, PVR Tools, classes and header
files. Used for building new applications.

    * Root file system binary image
          o Android regular apps like browser, media player, calendar,
clock, etc
          o SGX tests / demos (Vase, evilskull, etc)
          o Benchmarking utilities / scripts
          o adb support over Ethernet and USB (still over ethernet protocol)

    * Documentation
          o Android CTS (compatibility test suite) validation report
          o User guide
          o EVM and Beagleboard setup
          o Using pre-built Images to boot Android on EVM
          o Procedure to download sources
          o Instructions to rebuild Android rootfs, Kernel and
Bootloader images using sources.
          o Procedure to configure and run default apps (Browser,
Media Player, etc)
          o Running validation test cases and bench marking utilities
          o Using ADB to download .apk and executing the same
          o Procedure to use Flashing utility and Pin mux
          o Release notes

Regards,
Khasim

2

Hi,

  It would be really nice to have DSP software components (AV and
Image codec and OMX wrappers) included in this package. Any specific reason
for not considering the DSP components?

Warm Regards,
Anil

3

Working and tested SPI would be nice, It seems
to be something that is very nebulous and confusing
with muxing in a couple places and the work is
mostly done and in the wiki?

Regards

cww

Syed Mohammed, Khasim wrote:

4

We are working on this, you can keep getting latest updates on rowboat
mailing list. There are few issues we noticed. As soon as we clear
them out we should start putting them in our stable snapshot.

Many thanks for the input.

Regards,
Khasim

5

Isn't android 1.0 a bit old? It seems to be at 2.2 nowadays.

regards,

Koen

6

i'm assuming that the "1.0" versioning is for the dev kit and
doesn't represent the version of android itself. otherwise, yes, it's
way too old to have much value.

rday

7

The announcement didn't say so I assume the version numbers are the same.

regards,

Koen

8

Hi all,

Looking at multiple requests for a stable and tested snapshot of our
rowboat components, we are planning to provide a periodic release
called Android DevKit for the users of OMAP35x, AM35x and AM37x EVM
and Beagle platforms.

Our first Android DevKit 1.0 release is planned for July 30th 2010,
below are some of the components or requirements we have captured so
far.

Isn't android 1.0 a bit old? It seems to be at 2.2 nowadays.

i'm assuming that the "1.0" versioning is for the dev kit and
doesn't represent the version of android itself. otherwise, yes, it's
way too old to have much value.

The announcement didn't say so I assume the version numbers are the same.

As Robert mentioned it is the version of DevKit and not the Android
release itself. DevKit 1.0 will be on Android 2.1 (eclair) for this
time and will be moving to FroYo soon.

But I like your comment, do you think we should number them as DevKit
2.1.0, then for Froyo move to DevKit 2.2.0 , 2.2.1, 2.2.3, etc... the
last digit will be some thing like a rowboat release number and first
two corresponds to Android itself.

Regards,
Khasim

9

Using the android version in the devkit release number would help a lot :slight_smile: