the pandaboard aosp kernel repository is here
https://android.googlesource.com/kernel/omap
don't know the specific branch for ICS though
On Mon, Jun 10, 2013 at 4:45 PM, MJ embd wrote:
> This might be a trivial question but I dont know the answer to it. Looking
> for android gurus. My task is
if you use "make menuconfig ARCH=arm" you should be able to find, do not
recommend to edit the config file using an editor.
On Thu, Aug 1, 2013 at 2:09 PM, Jeremy Reeve wrote:
>
> Hi there,
>
> I'm trying to get the boot logo enabled and visible on HDMI for a
> Pandaboard running ICS Kernel:
>
>
which file system did you had in mind. Be aware that android used the linux
filesystem security mechanism so you would most likely need either ext2,
ext3 or ext4 to run it.
regarding partitioning that might depend a bit on the type of board you are
using
On Wed, Sep 25, 2013 at 9:30 AM, mohammad
Gents, try to get yourself a beagleboard or pandaboard development board.
These are not that expansive and allow you to play around with
the kernel. Using QEMU (android vm) will not help since it does not support
dvb devices as far as I know.
There were already some attempts to get DVB running on
Have a look at this http://omappedia.org/wiki/Bootloader_Project this shows
how the boot process takes place on a TI OMAP SoC
Should provide the understanding you're looking for.
On Mon, Nov 4, 2013 at 9:03 PM, Kanchan Joshi wrote:
> Hi All,
>
> I am trying to develop an understanding on the an
a userspace appliaction can not catch an hardware interrupt directly. you
need a driver to handle this or alternatively use user space io.
On Wed, Nov 13, 2013 at 11:25 AM, Oana Medvesan wrote:
>
> Hello
>
> I use a Qualcomm Device (apq8074Dragonboard) with this kernel:
> msm-AU_LINUX_ANDROID_JB
not sure about the ip addresses but both uevent and binder IPC use sockets.
On Tue, Nov 12, 2013 at 7:26 PM, Rui Gonçalo wrote:
> Hi Yves!
>
> Do you still have that code?
>
> On Friday, October 29, 2010 8:24:03 PM UTC+1, Yves wrote:
>>
>> Hi,
>>
>> I've written a kernel module that logs all soc
Not sure why you would need to disassemble the bootloader to learn android
development, since the bootloader has no relation to android
and is only used to start the booting and calling the kernel which
eventually calls android.
Anyway ..
Booting from a TI based system involves 4 elements:
x-loa
the way for communicating between user space applications (thus also
android) and the kernel is still using ioctl calls.
On Tue, Nov 12, 2013 at 7:38 PM, Rui Gonçalo wrote:
> Hi!
>
> What's the best mechanism to communicate between kernel and Android
> Applications?
>
> Unix domain sockets?
>
>