It does not have to be a hypervisor. but having a standard operating environment on EVERY handset would solve all the user experience problems. For example, some of my android devices do not support ICS, so I have two sets of apps, well 3 if you include the tablet.
On Mar 24, 4:29 pm, Tim Mensch <[email protected]> wrote: > On 3/23/2012 9:47 PM, Evan Pyle wrote: > > > 3,4. > > CPU/GPU should not be to hard, google should just say "As of Android > > 5.0 all device must support XYZ instruction set" > > If you've got the highest-level OpenGL GPU, then you're fine on that front. > > But there are at least three distinct numeric coprocessors that I'm > aware of in Android devices. If you're writing native/NDK code that > includes hardware floating point, you may want to support all three. I > don't think a hypervisor could emulate floating point hardware not > actually on the chip. > > I also have no idea why you're talking about using a hypervisor anyway. > The point of a hypervisor is to run several OSs concurrently [1]; most > of the devices we're talking about are RAM-limited enough that if you > tried to even run two at once you'd be in trouble. If all you want is to > be able to multi-boot into various different configurations, you can do > that without a hypervisor and its overhead. It would be far simpler to, > for example, add a hack to an Android image that causes it to read its > resolution from a configuration file and act as if it's a lower > resolution than it would to create a hypervisor layer that translated > every hardware access to different actual hardware. > > Tim > > [1]https://en.wikipedia.org/wiki/Hypervisor -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
