Well your estimate for the graphics is way low. That's just a framebuffer -- every window has its own buffer (and is actually double-buffered) as well.
The modem is a lot more too. :) Anyway, regardless of exactly what takes what, this is the RAM we end up with on the device. On Thu, Jul 9, 2009 at 6:58 PM, tom <tomisl...@gmail.com> wrote: > > 2MB framebuffer should be enough for a 480*320*16bpp device, (even > considering the virtual 960 width, and double buffer) > for camera, a 3M pixel camera, 6MB might be enough, or the worst 10MB > Modem, RAM for its execution, plus the AP-BP communication, 15M is > enough enough. > other driver's DMA buffer should be all small. > correct me if i am wrong or missed something. > > I can think of at most 20M usage. > there is still a big gap to the "lost" 91MB :-( > > Thanks, > Tom > > On Jul 10, 1:25 am, Dianne Hackborn <hack...@android.com> wrote: > > On Wed, Jul 8, 2009 at 10:33 PM, tom <tomisl...@gmail.com> wrote: > > > yes, kernel need to reserve some for its text, data, mem_map, and > > > other like FB etc. > > > But, 192-101=91MB, does modem need 91MB?! > > > > It also includes DMA buffers, graphics memory, etc. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
