Hi,
Maybe I'm wrong but I think they are not shared because applications run in
different processes.
Regards
Le jeudi 19 avril 2012 16:19:03 UTC+2, Pascal Wittmann a écrit :
>
> Hi,
>
> I'm currently working on a security type system that enforces a
> noninterference-like property based on a st
Yeah I agree with Mark. Also, it depends on what kind of drivers you want
to write .
I write some sensor drivers..For that, as long as the driver follows
standard Linux interfaces (on which android relies on)
it should work on an android device (of course, with HW support for that
sensor)
So, I wo
Yes, new lead devices often start with a relatively recent stable kernel,
and older lead devices often stay with the older kernel that they were
first released with and patched as needed. There are exceptions; this is
not a guaranteed rule.
On Wednesday, April 25, 2012 8:16:49 PM UTC-7, dennis
There are no changes you really should need to make between an "gnu/linux"
and "android/linux" driver. Some will say you need to add wake_lock's to
your driver critical sections but, almost every time I see a wake_lock in
the kernel (for the devices I work on) the lock was truly not needed. The
f
Any idea !!!
Which kind of changes i need to make to make it work with Android?
Where can i look for this perticular modifications ?
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
I think it will nt work...some how driver gets change from normal linux
kernel to android kernel...android on handset is nothing but a "embedded
linux"..which are mainly designed with low memory and less resources...
On Thu, Apr 26, 2012 at 9:08 PM, Chirag Shah wrote:
> Hi All,
> I know that lin
Hi All,
I know that linux mainframe kernel and Android linux kernel are
different (i.e. Binder, Ashmem, pmem, power management etc features
are added). These changes are towards generic architecture and
performance improvement.
But, I want to know in respect to device driver development for new
dr
