Where did you find this file? ~/mydroid$ find . -name '*ramebuffer.cpp' ./hardware/msm7k/libgralloc/framebuffer.cpp ./hardware/msm7k/libgralloc-qsd8k/framebuffer.cpp ./hardware/libhardware/modules/gralloc/framebuffer.cpp
On 20 ноя, 01:54, Porting beginner <porting.begin...@gmail.com> wrote: > On Thu, Nov 19, 2009 at 2:45 PM, Alexey Roslyakov < > > > > alexey.roslya...@gmail.com> wrote: > > Michael, our architectures are almost identical (arm920 s3c244x). > >http://www.newsycat.com/android/eclair/eclair_20112009.diff > > > On 20 ноя, 00:22, Michael Trimarchi <trimar...@gandalf.sssup.it> > > wrote: > > > Hi, > > > > Alexey Roslyakov wrote: > > > > I added LOGI just before return from fb_device_open. > > > > > I/gralloc ( 713): fb_device_open res: 0 > > > > > fb device initialized successfully. Problem is not here. > > > > But where? > > > > maybe we have the same architecture. I'm compiling eclair for openmoko > > but > > > the issue that I have is a crash in opencore. I'm trying to find the > > > related problem, > > > can you share with us your configuration for compile on the armv4t > > > architecture? > > > > Michael > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting > > I just put LOG and check again, have ioctl operation on fb, all are > successful and there must not be any issue from fb driver. > > But having issue with dpi value, when it reads from fbDev->xdpi, its -ve > value > thats wrong. What you guying seeing for this ? > > framebuffer/base/libs/ui/Framebuffer.cpp , line 127 > > -- > Thanks -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
