Hi Vince, In this module build description that you gave, in the line segment:
make -C /android/kernel/directory where is "directory" from the root of the source tree that is downloaded? I was expecting a directory with the kernel headers under <android-tree-root>/kernel, but don't see one. What should "directory" be in your description? thanks, John On Fri, Jul 16, 2010 at 5:39 AM, sws-vinpa <vincepascu...@gmail.com> wrote: > Building a module for Android is trivial (if you've done it before for > Linux). > > From the directory from which your module source is: > > # CROSS_COMPILE=arm-eabi- ARCH=arm make -C /android/kernel/directory M= > $PWD modules > > Note that the CROSS_COMPILE will only work as above if your Android > toolchain is in your system path. > > As for interfacing at the application level as a sensor, well, I have > not done that yet, but it seems like a cool idea. Like yenchengwang > mentioned, I would take a look at sensor_qemu.c to get an idea of how > it was done. I would imagine that some knowledge in JNI will be > required, though. > > Let me know how it goes! > > > Cheers, > > sws-vinpa. > > On Jul 9, 3:58 am, yenchengwang <yenchengw...@gmail.com> wrote: > > hi, > > I think what the nature lover want is a sensor hardware module~just > like > > the sensors_qemu.c in the > > development/emulator/sensors ~~ > > or u can get the htc_sensors.c on the android's git server. > > > > 2010/7/9 tungsys <tung...@gmail.com> > > > > > > > > > Hi, > > > > > I have a bit confuse about what you are doing : port an i2c driver to > > > Android platform ? > > > Android kernel is based on Linux kernel, so there is nothing > > > difference with the driver layer . > > > I thought you need do the driver for Linux kernel first and then apply > > > the Android patch to your kernel . > > > > > Tung > > > > > On Jul 9, 1:27 am, nature lover <ejko...@gmail.com> wrote: > > > > Hi, > > > > > > I am attempting to port an existing Linux device driver for an i2c > > > > device (which I wrote), > > > > to the Android platform. The intent is to eventually be able to > access > > > > the device via the > > > > Android sensor interface at the application level. > > > > > > I have not been able to find documentation on how to do the above > > > > port, or a description > > > > of the hooks needed for the sensor interface, in any of the Android > > > > sites, or in a general > > > > search of the web. I probably haven't been looking in the right > > > > places. Where would I be > > > > able to find detailed information on this process? > > > > > > Thanks in advance. > > > > > -- > > > unsubscribe: > > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com> > > > > > website:http://groups.google.com/group/android-porting > > > > -- > > Regards > > Y-C Wang > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
