Hi Subhajit,

On 08/13/2014 06:04 AM, Subhajit Naha wrote:
> Any documentation on the Goldfish architecture?

Here is the main documentation that I'm aware of.

https://android.googlesource.com/platform/external/qemu.git/+/master/docs/GOLDFISH-VIRTUAL-HARDWARE.TXT

> I find the Goldfish audio and MTD driver codes into the staging driver in the
> up to date kernel.
> is this the emulatir that is used when when we run our Android examples onto
> the eclipse+Android SDK?
> 
> On Wednesday, May 6, 2009 3:05:11 PM UTC+5:30, Piethein Strengholt wrote:
> 
>     Goldfish
> 
>     The Android emulator runs a virtual CPU that Google calls Goldfish.
>     Goldfish executes ARM926T instructions and has hooks for input and
>     output -- such as reading key presses from or displaying video output
>     in the emulator. These interfaces are implemented in files specific to
>     the Goldfish emulator and will not be compiled into a kernel that runs
>     on real devices.
> 
>     On Apr 27, 11:54 am, Chih-Wei <cwhu...@linux.org.tw> wrote:
>     > Hello, I saw the follow branches in kernel git repository:
>     >
>     >   korg/android-2.6.25
>     >   korg/android-2.6.27
>     >   korg/android-2.6.29
>     >   korg/android-goldfish-2.6.27
>     >   korg/android-goldfish-2.6.29
>     >   m/master
>     >
>     > So, what are the differences between goldfish kernel and non-goldfish
>     > kernel?
>     > And what is the master branch?

Regards,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

-- 
-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
--- 
You received this message because you are subscribed to the Google Groups 
"Android Linux Kernel Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-kernel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to