On Feb 10, 12:01 am, dh wrote:
> Hi,
>
> > I had thought about before too. From the implementation point of view,
> > you need someone to send you either a binder or handler (like
> > invitation) to be able to create a kernel level reference (numbered
> > locally), which you can then use to star
And also check if you lcd is loaded and enabled.
# adb shell cat /sys/devices/omapdss/display0/enabled
connect ddms or screen cast and check if you have any compositions
happening in the frame buffer.
- Preetam
On Thu, Feb 9, 2012 at 11:01 PM, Zoltan Kuscsik wrote:
> Check the framebuffer re
Check the framebuffer resolution in:
# adb shell cat /sys/class/graphics/fb0/virtual_size
Is your LCD display able to work with this resolution, did you tried
to swap the HDMI-/DVI connector?
Here you can check if the display is set to the right resolution/timing:
# adb shell cat /sys/devices/o
Yes, I'd like to know something about the security of the binder
implementation.
Can I just forge an IPC by talking to /dev/binder?
-Earlence
On Feb 9, 2:01 pm, dh wrote:
> Hi,
>
> > I had thought about before too. From the implementation point of view,
> > you need someone to send you either a
Hi,
> I had thought about before too. From the implementation point of view,
> you need someone to send you either a binder or handler (like
> invitation) to be able to create a kernel level reference (numbered
> locally), which you can then use to start transaction with. As the
> reference n
hello everyone
I am using the Blaze board to run Android 4.0 system which have the
Linux kernel 3.0.8.
the u-boot ,x-loader and kernel is downloaded and built by the
[L27.IS.2.P2 OMAP4 Icecream Sandwich Release Notes] which is recorded
in http://omappedia.org/wiki/L27.IS.2.P2_OMAP4_Icecr
