Nimit , Is it ? CAn you please check and tell me if the driver is ads7846 ? Did the keypad work for you ?
On Fri, Jan 16, 2009 at 3:35 AM, Nimit Manglick <nimitandr...@gmail.com>wrote: > Hi Bhoj, > > I didn't do anything specific with touchscreen. I was having my kernel > ready with > > touchscreen support and my things got up. > > Regards > Nimit > > On Thu, Jan 15, 2009 at 1:35 PM, vishal bhoj <vishalb...@gmail.com> wrote: > >> NIMIT, >> >> how did you get the touch screen working ? >> >> On Thu, Jan 15, 2009 at 2:45 AM, vishal bhoj <vishalb...@gmail.com>wrote: >> >>> NIMIT, >>> >>> >>> remove WAKE_DROPPED from the keys and try, worked for me . with the >>> default mapping are you getting some characters when you press key ? >>> >>> >>> On Thu, Jan 15, 2009 at 1:59 AM, Nimit Manglick >>> <nimitandr...@gmail.com>wrote: >>> >>>> Hi Kapare, >>>> >>>> Thanks for ur reply and sorry for late replying.. >>>> >>>> So my status is :- I tried with ur suggestions but still my MENU key is >>>> not getting >>>> >>>> mapped :( >>>> >>>> Thanks & Regards >>>> Nimit >>>> >>>> On Thu, Jan 15, 2009 at 11:33 AM, vishal bhoj <vishalb...@gmail.com>wrote: >>>> >>>>> Kapare, >>>>> >>>>> >>>>> I have got Android running on omap3evm ,Keypad is working fine. I am >>>>> having problem with the touchscreen. the touch are recognised ans the top >>>>> bar (date and time) slides and goes back . how can i get touchscreen >>>>> running >>>>> on android ? >>>>> >>>>> >>>>> On Fri, Dec 19, 2008 at 1:27 PM, kapare < >>>>> kevyn.alexandre.p...@gmail.com> wrote: >>>>> >>>>>> >>>>>> 1- Go to minicom console and run getevent& >>>>>> >>>>>> >>>>>> 2- Click on keypad buttons of OMAP35xx EVM and you will see something >>>>>> like that: >>>>>> >>>>>> /dev/input/event0: 0001 006a 00000001 >>>>>> /dev/input/event0: 0001 006a 00000000 >>>>>> >>>>>> >>>>>> 3- This mean that the hexadecemal value for the key pressed is 6A. >>>>>> >>>>>> >>>>>> 4- Convert that value to decimal 106. >>>>>> >>>>>> >>>>>> 5- Edit /system/usr/keylayout/qwerty.kl and map with the current >>>>>> OMAP35xx EVM keypad. >>>>>> >>>>>> >>>>>> 6- Here from OMAP35xx EVM keypad from left(next to SD slot) to right >>>>>> (serial port) and from top(screen) to bottom(power connector) Map of >>>>>> OMAP35xx EVM keypad "Hexa(Dec)": >>>>>> >>>>>> 19(25) 18(24) 31(49) 25(37) 24(36) >>>>>> >>>>>> 17(23) 1C(28) 21(33) 12(18) 67(103) >>>>>> >>>>>> 6C(108) 30(48) 1E(30) 6A(106) 69(105) >>>>>> >>>>>> >>>>>> 7- Edit /system/usr/keylayout/qwerty.kl like that: >>>>>> >>>>>> key 25 HOME WAKE_DROPPED >>>>>> >>>>>> key 24 DPAD_UP WAKE_DROPPED >>>>>> >>>>>> key 49 BACK WAKE_DROPPED >>>>>> >>>>>> key 37 MENU WAKE_DROPPED >>>>>> >>>>>> key 36 A WAKE_DROPPED >>>>>> >>>>>> key 23 DPAD_LEFT WAKE_DROPPED >>>>>> >>>>>> key 28 DPAD_CENTER WAKE_DROPPED >>>>>> >>>>>> key 33 DPAD_RIGHT WAKE_DROPPED >>>>>> >>>>>> key 18 VOLUME_UP >>>>>> >>>>>> key 103 B WAKE_DROPPED >>>>>> >>>>>> key 108 CALL WAKE_DROPPED >>>>>> >>>>>> key 48 DPAD_DOWN WAKE_DROPPED >>>>>> >>>>>> key 30 ENDCALL WAKE_DROPPED >>>>>> >>>>>> key 106 VOLUME_DOWN WAKE_DROPPED >>>>>> >>>>>> key 105 C WAKE_DROPPED >>>>>> >>>>>> Regards >>>>>> >>>>>> kap >>>>>> >>>>>> On Dec 19, 12:21 am, "Nimit Manglick" <nimitandr...@gmail.com> wrote: >>>>>> > Hi Anil, >>>>>> > >>>>>> > can you please share the keypad mapping of 3530 EVM >>>>>> > >>>>>> > Regards >>>>>> > Nimit >>>>>> > >>>>>> > On Thu, Dec 18, 2008 at 12:15 PM, Nimit Manglick < >>>>>> nimitandr...@gmail.com>wrote: >>>>>> > >>>>>> > > Hi Rupesh, >>>>>> > >>>>>> > > Its compiling now. In your patch the filename is there. >>>>>> > >>>>>> > > Thanks >>>>>> > >>>>>> > > Nimit >>>>>> > >>>>>> > > On Thu, Dec 18, 2008 at 12:10 PM, Nimit Manglick < >>>>>> nimitandr...@gmail.com>wrote: >>>>>> > >>>>>> > >> Hi Rupesh, >>>>>> > >>>>>> > >> Ya now i am following all the steps. I have applied the patches . >>>>>> > >>>>>> > >> But If you can see the new file added in >>>>>> libc/arch-arm/bionic/ffs.S, there >>>>>> > >> is an empty >>>>>> > >>>>>> > >> #include i.e there is no filename mentioned there. >>>>>> > >>>>>> > >> Can you please verify it and let me know. >>>>>> > >>>>>> > >> Thanks & Regards >>>>>> > >> Nimit >>>>>> > >>>>>> > >> On Thu, Dec 18, 2008 at 12:01 PM, Rupesh Gujare < >>>>>> > >> rupesh.guj...@embinux.com> wrote: >>>>>> > >>>>>> > >>> Nimit, >>>>>> > >>> Did you followed all steps given on :- >>>>>> > >>>http://labs.embinux.org/android-porting-on-beagle.html >>>>>> > >>>>>> > >>> You are required to apply patches to Android build, to make >>>>>> sound work. >>>>>> > >>>>>> > >>> Regards, >>>>>> > >>>>>> > >>> -- >>>>>> > >>> Rupesh Gujarehttp://embinux.com >>>>>> > >>>>>> > >>> Regards, >>>>>> > >>>>>> > >>> Nimit Manglick wrote: >>>>>> > >>>>>> > >>> Hi Anil / Rupesh, >>>>>> > >>>>>> > >>> I am getting the following errors after doing a check out of >>>>>> alsa-lib & >>>>>> > >>> while doing "make" >>>>>> > >>>>>> > >>> in the top source directory. >>>>>> > >>>>>> > >>> >>>>>> out/target/product/generic/obj/STATIC_LIBRARIES/libasound_intermediates/libasound.a(input.o): >>>>>> > >>> In function `snd_input_buffer_scan': >>>>>> > >>> external/alsa-lib/src/input.c:245: undefined reference to >>>>>> `vsscanf' >>>>>> > >>> collect2: ld returned 1 exit status >>>>>> > >>> make: *** >>>>>> > >>> >>>>>> [out/target/product/generic/obj/SHARED_LIBRARIES/libaudio_intermediates/LINKED/libaudio.so] >>>>>> > >>> Error 1 >>>>>> > >>>>>> > >>> Thanks & Regards >>>>>> > >>> Nimit >>>>>> > >>>>>> > >>> On Thu, Dec 18, 2008 at 11:14 AM, Rupesh Gujare < >>>>>> > >>> rupesh.guj...@embinux.com> wrote: >>>>>> > >>>>>> > >>>> Nimit, >>>>>> > >>>> We have already successfully tested sound on beagle >>>>>> (OMAP3530) . >>>>>> > >>>> You can go through following how to for more details:- >>>>>> > >>>>http://labs.embinux.org/android-porting-on-beagle.html >>>>>> > >>>>>> > >>>> Regards, >>>>>> > >>>> Rupesh Gujare >>>>>> > >>>>http://embinux.com >>>>>> > >>>>>> > >>>> Nimit Manglick wrote: >>>>>> > >>>>>> > >>>> Hi Anil, >>>>>> > >>>>>> > >>>> Can you please tell me which all packages shall i need to check >>>>>> out. >>>>>> > >>>>>> > >>>> 1. external/alsa-lib.git >>>>>> > >>>>>> > >>>> 2. hardware/alsa_sound.git >>>>>> > >>>>>> > >>>> Other than this shall I need to check out any other package ? >>>>>> > >>>>>> > >>>> But i didn't found the alsa-utils package ? As i want aplay, >>>>>> amixer >>>>>> > >>>> utilities as well. >>>>>> > >>>>>> > >>>> What else is required to integrate ? >>>>>> > >>>>>> > >>>> I am just doing the "make" in root directory so taht i wwill >>>>>> have my new >>>>>> > >>>> file system with >>>>>> > >>>>>> > >>>> alsa libs. Will mount this new filesystem. >>>>>> > >>>>>> > >>>> Thanks & Regards >>>>>> > >>>> Nimit >>>>>> > >>>>>> > >>>> On Wed, Dec 17, 2008 at 6:54 PM, Anil Sasidharan < >>>>>> anil...@gmail.com>wrote: >>>>>> > >>>>>> > >>>>> Hi, >>>>>> > >>>>>> > >>>>> This has already been done by Windriver and TI. You >>>>>> will be >>>>>> > >>>>> able to get the sources fromhttp:// >>>>>> android.git.kernel.org/(ASLA <http://android.git.kernel.org/%28ASLA>lib >>>>>> > >>>>> and HAL ported by Windriver) or fromhttp://git.omapzoom.org. >>>>>> > >>>>> Integration is pretty straightforward. >>>>>> > >>>>>> > >>>>> Warm Regards, >>>>>> > >>>>> Anil >>>>>> > >>>>>> > >>>>> On Wed, Dec 17, 2008 at 4:35 PM, Nimit Manglick < >>>>>> > >>>>> nimitandr...@gmail.com> wrote: >>>>>> > >>>>> > Hi Anil, >>>>>> > >>>>>> > >>>>> > I am now trying to compile alsa using android tool chain but >>>>>> i am not >>>>>> > >>>>> > getting success. >>>>>> > >>>>>> > >>>>> > Secondly i also tried to compile it using another arm-eabi >>>>>> toolchain >>>>>> > >>>>> but >>>>>> > >>>>> > there also my alsa-utils are not getting compiled. >>>>>> > >>>>>> > >>>>> > Regards >>>>>> > >>>>> > Nimit >>>>>> > >>>>>> > >>>>> > On Wed, Dec 17, 2008 at 11:54 AM, Anil Sasidharan < >>>>>> anil...@gmail.com> >>>>>> > >>>>> wrote: >>>>>> > >>>>>> > >>>>> >> Hi Nimit, >>>>>> > >>>>>> > >>>>> >> Have you integrated the ALSA audio support into >>>>>> Android >>>>>> > >>>>> HAL? >>>>>> > >>>>> >> Or is it another sound support being added there (OSS, ESD, >>>>>> custom)? >>>>>> > >>>>> >> Do you see the media files listed (scanned and enumerated >>>>>> by media >>>>>> > >>>>> >> scanner)? >>>>>> > >>>>>> > >>>>> >> Warm Regards, >>>>>> > >>>>> >> Anil >>>>>> > >>>>>> > >>>>> >> On Wed, Dec 17, 2008 at 11:01 AM, Nimit Manglick < >>>>>> > >>>>> nimitandr...@gmail.com> >>>>>> > >>>>> >> wrote: >>>>>> > >>>>> >> > Hi Anil, >>>>>> > >>>>>> > >>>>> >> > Can you give me some pointers on my previous query on 35x >>>>>> EVM >>>>>> > >>>>>> > >>>>> >> > I have put some media files on SD card (audio + video - >>>>>> mpeg + wmv >>>>>> > >>>>> >> > format + >>>>>> > >>>>> >> > 3gp) >>>>>> > >>>>> >> > Media player is able to play the audio file but i am not >>>>>> able to >>>>>> > >>>>> hear >>>>>> > >>>>> >> > any >>>>>> > >>>>> >> > sound :( >>>>>> > >>>>>> > >>>>> >> > So where i need to change in the hardware so that i will >>>>>> be able >>>>>> > >>>>> to >>>>>> > >>>>> >> > listen >>>>>> > >>>>> >> > music ?? But the media player is not even detecting any >>>>>> of the >>>>>> > >>>>> video >>>>>> > >>>>> >> > files >>>>>> > >>>>> >> > .. >>>>>> > >>>>>> > >>>>> >> > Thanks & Regards >>>>>> > >>>>> >> > Nimit >>>>>> > >>>>>> > >>>>> >> > On Wed, Dec 17, 2008 at 10:46 AM, Anil Sasidharan < >>>>>> > >>>>> anil...@gmail.com> >>>>>> > >>>>> >> > wrote: >>>>>> > >>>>>> > >>>>> >> >> twebb, >>>>>> > >>>>>> > >>>>> >> >> Please see my answers in-lined............. >>>>>> > >>>>>> > >>>>> >> >> > Anil, >>>>>> > >>>>> >> >> > Hope you don't mind me contacting you directly. We >>>>>> actually >>>>>> > >>>>> own a >>>>>> > >>>>> >> >> > Mistral OMAP35x EVM board and I've gotten android >>>>>> running on >>>>>> > >>>>> it. >>>>>> > >>>>> >> >> > However I'm running into an issue or two that maybe >>>>>> you can >>>>>> > >>>>> help >>>>>> > >>>>> >> >> > with. >>>>>> > >>>>>> > >>>>> >> >> > 1. I've only run with a filesystem that was extracted >>>>>> from the >>>>>> > >>>>> >> >> > android emulator, mounted via NFS or YAFFS2. No >>>>>> problems. >>>>>> > >>>>> However, >>>>>> > >>>>> >> >> > I >>>>>> > >>>>> >> >> > now have built the android source and want to run with >>>>>> the >>>>>> > >>>>> "built" >>>>>> > >>>>> >> >> > filesystem, but I'm having problems. On startup, >>>>>> either init >>>>>> > >>>>> >> >> > function >>>>>> > >>>>> >> >> > says it can't find files on /data or /system, or (if I >>>>>> mess >>>>>> > >>>>> around >>>>>> > >>>>> >> >> > alot with permissions/ownership) android will start >>>>>> but several >>>>>> > >>>>> apps >>>>>> > >>>>> >> >> > don't run because of permissions/ownership issues. Is >>>>>> there >>>>>> > >>>>> any >>>>>> > >>>>> >> >> > secret to "preparing" the source built filesystem >>>>>> > >>>>> (../out/target/ >>>>>> > >>>>> >> >> > product/generic/system and ../root and ../data) for >>>>>> use on an >>>>>> > >>>>> actual >>>>>> > >>>>> >> >> > target? (I'd rather not have to "un-yaffs" the >>>>>> system.img and >>>>>> > >>>>> >> >> > data.img files since I won't be using yaffs in the >>>>>> long run.) >>>>>> > >>>>>> > >>>>> >> >> The out/target/product/<board-name> directory contains >>>>>> /system, >>>>>> > >>>>> /data >>>>>> > >>>>> >> >> and /root directories. You don't need to worry about >>>>>> un-yaffs the >>>>>> > >>>>> .img >>>>>> > >>>>> >> >> files. However please make sure that the init.rc under >>>>>> /root >>>>>> > >>>>> directory >>>>>> > >>>>> >> >> is modified according to your setup (especially comment >>>>>> out the >>>>>> > >>>>> >> >> mounting of YAFFS2 partitions). The easy approach would >>>>>> be to >>>>>> > >>>>> make use >>>>>> > >>>>> >> >> of the very same file system you already have on the NFS >>>>>> or SD >>>>>> > >>>>> card >>>>>> > >>>>> >> >> and just replace the system directory alone with the one >>>>>> built >>>>>> > >>>>> out of >>>>>> > >>>>> >> >> sources. >>>>>> > >>>>>> > >>>>> >> >> > 2. I'm also seeing an issue where I'm having an issue >>>>>> where >>>>>> > >>>>> D-pad >>>>>> > >>>>> >> >> > key >>>>>> > >>>>> >> >> > presses (i.e. left/right/up/down) don't seem to cause >>>>>> the >>>>>> > >>>>> >> >> > screen to refresh such that the next icon is >>>>>> highlighted. >>>>>> > >>>>> Based on >>>>>> > >>>>> >> >> > how the code reacts, the icon is actually active (i.e. >>>>>> ENTER >>>>>> > >>>>> causes >>>>>> > >>>>> >> >> > it >>>>>> > >>>>> >> >> > to launch) but just not highlighted. It seems as >>>>>> though every >>>>>> > >>>>> other >>>>>> > >>>>> >> >> > key press results in the screen being refreshed (such >>>>>> that >>>>>> > >>>>> every >>>>>> > >>>>> >> >> > other >>>>>> > >>>>> >> >> > icon is highlighted as the directions keys are used to >>>>>> move >>>>>> > >>>>> around an >>>>>> > >>>>> >> >> > array of icons on the screen). Is this a keyboard >>>>>> driver >>>>>> > >>>>> issue, a >>>>>> > >>>>> >> >> > frame buffer driver issue, or something else? All >>>>>> other key >>>>>> > >>>>> related, >>>>>> > >>>>> >> >> > touchscreen related, and frame buffer related >>>>>> functionality >>>>>> > >>>>> seems >>>>>> > >>>>> >> >> > fine. I've modified omapfb_main.c per the "page >>>>>> flipping frame >>>>>> > >>>>> >> >> > buffer" question onhttp://elinux.org/Android_on_OMAP. >>>>>> Are >>>>>> > >>>>> there >>>>>> > >>>>> >> >> > other mods to frame buffer driver or keypad driver I >>>>>> need to >>>>>> > >>>>> make to >>>>>> > >>>>> >> >> > eliminate this problem? >>>>>> > >>>>>> > >>>>> >> >> This is one of the notorious/infamous issues that I've >>>>>> faced >>>>>> > >>>>> while >>>>>> > >>>>> >> >> bringing up Android on OMAP3EVM. This is an issue with >>>>>> the >>>>>> > >>>>> framebuffer >>>>>> > >>>>> >> >> update. I presume you already have added support for >>>>>> > >>>>> double-buffering >>>>>> > >>>>> >> >> in fb driver (fb_pan). The GO bit needs to be set for >>>>>> the >>>>>> > >>>>> shadowed >>>>>> > >>>>> >> >> registers to take effect in hardware. Once the hardware >>>>>> is ready, >>>>>> > >>>>> the >>>>>> > >>>>> >> >> GO bit will be reset. Per the hardware specifications, >>>>>> we should >>>>>> > >>>>> not >>>>>> > >>>>> >> >> change any display controller registers until the GO bit >>>>>> is >>>>>> > >>>>> >> >> reset.Android desktop icon-navigation problem got >>>>>> resolved after >>>>>> > >>>>> this >>>>>> > >>>>> >> >> change is made in the display controller source. >>>>>> > >>>>> >> >> For you reference the code is added here (extracted from >>>>>> the >>>>>> > >>>>> function >>>>>> > >>>>> >> >> _setup_plane in drivers/video/omap/dispc.c. The source >>>>>> file to be >>>>>> > >>>>> >> >> modified may change depending on the kernel version at >>>>>> you end >>>>>> > >>>>> :-) ): >>>>>> > >>>>>> > >>>>> >> >> MOD_REG_FLD(DISPC_CONTROL, 0x20, 0); /* clears and sets >>>>>> the GOLCD >>>>>> > >>>>> bit >>>>>> > >>>>> >> >> */ >>>>>> > >>>>> >> >> MOD_REG_FLD(DISPC_CONTROL, 0x20, 0x20); >>>>>> > >>>>>> > >>>>> >> >> > Thanks for your time. >>>>>> > >>>>> >> >> > twebb >>>>>> > >>>>>> > >>>>> >> >> Warm Regards, >>>>>> > >>>>> >> >> Anil >>>>>> > >>>>>> > >>>> -- >>>>>> > >>>> Rupesh Gujare >>>>>> > >>>> Engineer- Embedded Software >>>>>> > >>>> Embedded and >>>>>> > >>>>>> > ... >>>>>> > >>>>>> > read more ยป >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> with regards vishal >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> with regards vishal >>> >> >> >> >> -- >> with regards vishal >> >> >> > > > > -- with regards vishal --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
