On Jan 26, 5:05 am, Tim Bird wrote:
> On 01/25/2012 05:41 AM, rong wrote:
>
> > Hi Folks,
>
> > I've just finished a fresh implementation of the android binder
> > driver, would love to see some suggestions or comments on the code as
> > well as the whole binder IPC idea.
>
> This is really inte
On 01/25/2012 05:41 AM, rong wrote:
> Hi Folks,
>
> I've just finished a fresh implementation of the android binder
> driver, would love to see some suggestions or comments on the code as
> well as the whole binder IPC idea.
This is really interesting. I hope this doesn't seem rude, but
why are
Usually when we'r directly working on device, RAM_CONSOLE is better choice.
To setup this we have a ram_console driver at drivers/staging/android path
[enable it] & you just create a
platform device entry in BSP code.
Once you have any crash/hang happening on your device, for next the reboot
try
The ram_console is very interesting, but how should I get it, if it
does not boot? Does it matter if I boot recovery or Android?
On Jan 24, 10:01 pm, jagan <402ja...@gmail.com> wrote:
> Is there a way to save the log somewhere (like /cache or /data), so I
> could check what did not work and get a
Hi Folks,
I've just finished a fresh implementation of the android binder
driver, would love to see some suggestions or comments on the code as
well as the whole binder IPC idea. The driver can be found on Github
at
https://github.com/rong1129/android-binder-ipc
in the module/new directory. The
