the kernel version and rebuild.
This is an example of what to look for and set in the Makefile:
VERSION=3
PATCHLEVEL=0
SUBLEVEL=15
EXTRAVERSION=-962322
- bridgette
From: "arun1...@iiitd.ac.in"
To: android-kernel@googlegroups.com
Sent: Thursday, Ap
I'm not sure why it reboots but try the following to resolve the issue...
### run the following command ###
$ lsusb
Bus 001 Device 016: ID 0bb4:0c87 High Tech Computer Corp. Desire (debug)
### add your device to the following file (you may need to create file) ###
$ sudo vi /etc/udev/rules.d/5
hi bloxtr,
There are a quite a few things with your module that you need to
correct...google the adore lkm and it will lead you to answers for what you are
doing. :)
And you will need to gain root access to the device for accessing /data/data
directory.
Hello Talon
Samsung provides a txt file that details how to build the kernel...once your
environment is set up correctly you should only need to run a script file that
they provide, for example mine is called make_kernel_tass_vtr.sh.
If you take a look at the file it points to a specific
using insmod.
hope that helps,
bridgette
On Jul 26, 5:12 am, noam wrote:
> well, i am new to android, but not to linux
>
> i have been tasked to port our application to android, and now i need
> to compile the low level driver.
>
> where do i get the kernel source code that is r
resolved...I the run the build/envsetup.sh followed by running the mm
command from the directory for the Android.mk.
but if there is other insight please let me know...
Thanks
On May 14, 11:32 am, bridgette wrote:
> I added a new gpio-keys.kl file to the out/target/product/beaglebo
I added a new gpio-keys.kl file to the out/target/product/beagleboard/
system/usr/keylayout directory and modified the Android.mk development/
emulator/keymaps which should create a gpio-keys.kcm file. How do I
build the Android.mk file...is there a parameter that I can set on the
command line whe
Hi Arindam,
I'm using beagleboard rev c3 that has been customized with an
expansion board and an embedded lcd (nl2432hc17) attached to it.
Also, the code that I put in place earlier solved itthe
touchscreen is working.
On May 13, 8:20 pm, Arindam Roy wrote:
> Hello Bridgette,
>
I replaced the board (it looks like the board went bad) and the
touchscreen is recognized...now I will start looking at the getting
Android to recognize the events.
On May 13, 10:15 am, bridgette wrote:
> For a brief period, the touchscreen was being recognized. In the
> tsc2005.c file I
gh
> search results for source code that opens these nodes.
>
> Regards,
> Karthik Poduval
>
>
>
> On Wed, May 12, 2010 at 1:02 PM, bridgette wrote:
> > Thanks...the driver is being registered. What is the middleware
> > process that reads these events and p
t driver version for /dev/input/mice, Not a
typewriter
add device 3: /dev/input/
event0
name: "gpio-keys"
On May 12, 1:02 pm, bridgette wrote:
> Thanks...the driver is being registered. What is the middleware
> process that reads these events and passes them to the Android
failed. There also should be a middle ware process to
> read these events from the input dev and pass them to the Android framework.
> Check if this process is running.
>
> --
> Regards,
> Karthik Poduval
>
> On Wed, May 12, 2010 at 11:12 AM, bridgette wrote:
> > I am us
I am using the tsc2005 driver but it is not being recognized. Any
suggestions on how to test?
I have printk statements throughout that indicate that it is being
initialized but I'd like to test to what happens when I touch the
screen and if it is atleast recognizing it.
Thanks.
--
unsubscribe:
Hello Reed,
After you have successfully built the kernel, the next step would be booting
android. How you do that is unknown to us because you have not provided any
information.
Bridgette
> -Original Message-
> From: composerguy
> Date: Sat, 27 Mar 2010 12:41:24
>
14 matches
Mail list logo
