Khasim from the Rowboat project asked me to post the following request
to the BeagleBoard group instead of the Rowboat group. Request
follows:
Hi Khasim,
I'd like to see the Beagleboard expansion I2C and SPI supported (and
tested) in the Android DevKit.
Thanks,
Jim
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.
{List deleted}
Regards,
Khasim
Syed Mohammed, Khasim
View profile
More options Jul 20, 7:02 am
Local: Tues, Jul 20 2010 7:02 am
called "Android DevKit"
Reply | Reply to author | Forward | Print | Individual message | Show
original | Report this message | Find messages by this author
Jimb,
Can you post this request to Beagle mailing list, we want to focus
more on Android enablement.
If I can get a patch for I2C and SPI support for Beagle, then we can
integrate it on rowboat kernel.
I'm puzzled about this request. The rowboat people are getting payed to work on this and all the patches we use on beagleboard are available from multiple sources, the validation repo being one of them. Khasim is the one that started the validation repo!
So can someone explain why the rowboat people can't take the patches from the beagle repo?
Khasim from the Rowboat project asked me to post the following request
to the BeagleBoard group instead of the Rowboat group. Request
follows:
Hi Khasim,
I'd like to see the Beagleboard expansion I2C and SPI supported (and
tested) in the Android DevKit.
I'm puzzled about this request. The rowboat people are getting payed to work on this
Really ? Very Delighted to get this info from you ...
and all the patches we use on beagleboard are available from multiple sources, the validation > repo being one of them. Khasim is the one that started the validation repo!
So can someone explain why the rowboat people can't take the patches from the beagle
repo?
The requirement for rowboat is not to hunt for board specific kernel
features but to address the android specifics for all TI Devices.
The Kernel specific patches "should" to go linux-omap and it will
automatically get pulled on to rowboat kernel. If some one has any
patch or fix that can impact android activity in kernel like the adb
over USB we discussed on rowboat mailing list yesterday, we will be
very happy to consider such patches directly on rowboat kernel GIT.
It is better we align all kernel level features and fixes on
linux-omap and not on other repos. Other repos are meant to ease the
development flow for users and community members to develop on top of
it.
The patches should not get stocked at multiple repos, it should move
upstream. If we start pulling or accepting kernel patches on rowboat
then it will stock a big chunk in no time.
The reason I directed this question on beagle list is to make us aware
that we have an action item to get I2C and SPI support for expansion
connector in linux mainline. If that happens then all other repos will
get this feature automatically.