Hi Peter,
It depends on how the device driver create the interface to the userspace.
For example of LED, if you use leds framework in the kernel there will be
sysfs interface that you can open and write directly from java using the
standard file operation.
If it's using character device interfac
>Hi everybody,
>
>I am new to Android.
>I know that application programs can control a device by open / read /
>write device driver file in C code.
>I want to know how to control a device in java code under dalvik
>virtual machine in Android system.
>
>Where could i find information about Android d
Hi everybody,
I am new to Android.
I know that application programs can control a device by open / read /
write device driver file in C code.
I want to know how to control a device in java code under dalvik
virtual machine in Android system.
Where could i find information about Android device dev
I keep getting asked about kernel versions and android releases at
work too.
I keep telling people that the only kernel requirements any version of
Android has are that its a 2.6 kernel (for bionic) and it has a small
set of patches (binder, logger, wakelocks, ashmem, and perhaps a few
others that
Hi all,
I was looking around if anyone installed encfs on android: has it been
done/can be done?
If not, any other experiences with other softwares to encrypt an
entire directory tree?
(possibly on a file per file basis)
thanks
giammy
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
A bit to quick with the enter key.
Assuming you have a reasonable up to date distro on the host pc a quick way to
see if it is your firewall, do a 'iptables --flush' (might need sudo)
this removes all firewall checks
then boot your 2430 system. If it then connects to your NFS server
then you know
assuming you have a reasonable up to date distro on the host pc
iptables --list
On Thu, Aug 5, 2010 at 11:57 AM, sri wrote:
>
>
> Hi,
>
> My bootargs settings are :
> setenv bootcmd 'tftp 0x8000 uImage; bootm 0x8000'
> setenv bootargs console=ttyS0,115200n8 root=172.28.6.33:/dev/nfs rw
Hi,
My bootargs settings are :
setenv bootcmd 'tftp 0x8000 uImage; bootm 0x8000'
setenv bootargs console=ttyS0,115200n8 root=172.28.6.33:/dev/nfs rw
noinitrd ip=172.28.6.34:172.28.6.33::255.255.255.0::eth0:on nfsroot=/
nfsroot/rootfs,nolock mem=32M
With same bootargs, kernel boots up fo
Ok, thnx. That's what I assumed looking into the git repos.
@Akash. Not using the google git kernel directly but more as a
reference point. Using linux omap from git.kernel.org
On Thu, Aug 5, 2010 at 4:23 AM, Mike Lockwood wrote:
> Actually Froyo is 2.6.32. 2.6.35 is being used for post-Froyo
