Linaro-android August 2012

linaro-android@lists.linaro.org

40 participants
50 discussions

First (semi-)working Linaro JellyBean build

by Bernhard Rosenkränzer

Hi, I've just committed the code needed to build an initial Linaro JellyBean version (buildable with the Linaro gcc 4.7 compiler): repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro_android_4.1.1 repo sync Currently the build supports only the Galaxy Nexus - didn't want to run into trouble with potentially incompatible binary blobs before knowing the rest of the system is working. Support for our normally supported boards will be added over the next couple of days. Optimizations that currently aren't on the 4.1 branch will also be restored in the next couple of days. There's also 2 problems we need to fix quickly: E/WVMExtractor( 126): Failed to open libwvm.so entries showing up in logcat (a quick grep indicates nothing seems to build libwvm - neither in our tree nor in AOSP) and I/v8 ( 1293): ERROR: Binary compiled with -mfloat-abi=hard but without -DUSE_EABI_HARDFLOAT (we don't actually use hardfloat (yet), so chances are the check for hardfloat goes wrong with gcc 4.7.x) The camera isn't working, but that's not a high priority issue given the Galaxy Nexus is not a device we're supporting officially. Of course our gerrit is always happy to receive patches for these and other issues. ;) ttyl bero

13 years, 7 months

Re: [Omapandroid-discussion] smsc95xx: download ok, upload hangs

by Zach Pfeffer

On 29 June 2012 10:55, Émeric Vigier <emeric.vigier(a)savoirfairelinux.com> wrote: > Hi, > > I am not 100% sure but it seems my smsc95xx is unable to wake up the CPU while it is in WFI. > I have verified that my OMAP4430 constantly enters WFI. Note that sleep states are disabled. > USB mouse and keyboard events wake it up properly. eth0 RX seems to wake it up, but eth0 TX does not... > What could be possibly wrong in my config then? usbnet.c only creates softirq to submit URB. No HW irq. > > How can I make smsc95xx trigger an interrupt (ehci_hcd:usb1) while transferring data? > Do you know? I don't know. Including linaro-android and pandaboard. > Emeric > > ----- Mail original ----- >> De: "Émeric Vigier" <emeric.vigier(a)savoirfairelinux.com> >> À: "Zach Pfeffer" <zach.pfeffer(a)linaro.org> >> Cc: "Vikram Pandita" <vikram.pandita(a)ti.com>, omapandroid-discussion(a)gforge.ti.com >> Envoyé: Jeudi 28 Juin 2012 16:04:31 >> Objet: Re: [Omapandroid-discussion] smsc95xx: download ok, upload hangs >> >> I tried 4AI.1.4-P1 kernel this morning. The panda_defconfig did not >> compiled out of the box: >> arch/arm/mach-omap2/temp_sensor_device.c:38: undefined reference to >> `omap_temp_sensor_idle' >> I disabled CONFIG_OMAP_TEMP_SENSOR and CONFIG_OMAP4_DIE_TEMP_SENSOR. >> It seems that there are not supported on omap4430 anyway... >> But kernel panics short after init, with my Android images. And I am >> not really into investigating this panic. >> >> Compiling my current kernel with gcc-4.6 (provided by google android) >> did not change the behavior. >> >> I made more tests though. My test setup is now as follows: >> On the pandaboard I run: >> # nc -l -p 1032 < /dev/zero & >> On my host computer (connected to the same network), I run: >> # nc 192.168.50.107 1032 > /dev/null >> I can see with nethogs that TX is stalled as I got "nc [...] 0KB/sec" >> >> I tried to change mtu, from 1500 to 512, no real improvement. >> >> here is a list of my usb devices: >> >> # cat /d/usb/devices >> >> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3 >> B: Alloc= 0/800 us ( 0%), #Int= 3, #Iso= 0 >> D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 >> P: Vendor=1d6b ProdID=0002 Rev= 3.00 >> S: Manufacturer=Linux 3.0.8-g2562c68-dirty ehci_hcd >> S: Product=OMAP-EHCI Host Controller >> S: SerialNumber=ehci-omap.0 >> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA >> I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub >> E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms >> >> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 5 >> D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1 >> P: Vendor=0424 ProdID=9514 Rev= 1.00 >> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 2mA >> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=01 Driver=hub >> E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms >> I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub >> E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms >> >> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 >> D: Ver= 2.00 Cls=ff(vend.) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 >> P: Vendor=0424 ProdID=ec00 Rev= 1.00 >> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 2mA >> I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff >> Driver=smsc95xx >> E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms >> E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms >> E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=1ms >> >> T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 4 Spd=1.5 MxCh= 0 >> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >> P: Vendor=04b3 ProdID=3025 Rev= 1.02 >> S: Manufacturer=CHICONY >> S: Product=USB NetVista Full Width Keyboard >> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA >> I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid >> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms >> >> T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#= 6 Spd=12 MxCh= 0 >> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >> P: Vendor=066b ProdID=400b Rev= 1.01 >> S: Manufacturer=LINKSYS Inc >> S: Product=LINKSYS USB Adapter >> S: SerialNumber=9b1fa5 >> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=156mA >> I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=pegasus >> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms >> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms >> E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=1ms >> >> We can see the smsc9514 chipset which is causing me so much pain. >> Also I compiled the pegasus driver to support an external Linksys >> device. This device ethernet behaves just fine as eth1. I noticed >> that MxPS (MaxPacketSizes) and Cls (Class) are different on the two >> ethernet devices. But I don't think this is the cause of my problem. >> >> When I stress the cpu: >> # stress -c 1 >> TX is resumed and speed increases to ~20KBps. >> This is strange, because I remember having tested with "stress -c 2" >> before, without seeing any improvement. My setup is probably >> different now... >> >> Something must be wrong with the wakeonlan capability of the chipset. >> I checked register 0x20, smsc95xx.h defines: >> >> #define PM_CTRL (0x20) >> #define PM_CTL_DEV_RDY_ (0x00000080) >> #define PM_CTL_SUS_MODE_ (0x00000060) >> #define PM_CTL_SUS_MODE_0 (0x00000000) >> #define PM_CTL_SUS_MODE_1 (0x00000020) >> #define PM_CTL_SUS_MODE_2 (0x00000060) >> #define PM_CTL_PHY_RST_ (0x00000010) >> #define PM_CTL_WOL_EN_ (0x00000008) >> #define PM_CTL_ED_EN_ (0x00000004) >> #define PM_CTL_WUPS_ (0x00000003) >> #define PM_CTL_WUPS_NO_ (0x00000000) >> #define PM_CTL_WUPS_ED_ (0x00000001) >> #define PM_CTL_WUPS_WOL_ (0x00000002) >> #define PM_CTL_WUPS_MULTI_ (0x00000003) >> >> # while(true); do ethtool -d eth0 | grep 020: ; sleep 1; done >> 020: 81 00 00 00 00 00 11 01 1f 00 00 1f a0 30 f8 00 >> 020: 81 00 00 00 00 00 11 01 1f 00 00 1f a0 30 f8 00 >> 020: 81 00 00 00 02 00 11 01 1f 00 00 1f a0 30 f8 00 >> 020: 81 00 00 00 00 00 11 01 1f 00 00 1f a0 30 f8 00 >> 020: 81 00 00 00 00 00 11 01 1f 00 00 1f a0 30 f8 00 >> >> The only register changing is 0x24 which is LED_GPIO_CFG, which >> confirms that my register is correct. >> If I decode correctly, register 0x20 has PM_CTL_WUPS_ED_ and >> PM_CTL_WOL_EN_ set. >> Still lacking register description though... >> >> ethtool returns nothing regarding wakeonlan for eth0: >> >> # ethtool eth0 >> Settings for eth0: >> Supported ports: [ TP MII ] >> Supported link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> Advertised auto-negotiation: Yes >> Speed: 100Mb/s >> Duplex: Full >> Port: MII >> PHYAD: 1 >> Transceiver: internal >> Auto-negotiation: on >> Current message level: 0x00000007 (7) >> Link detected: yes >> >> Same ethtool result returned with linaro-11.09, whose ethernet works >> like a charm. >> >> I checked again this linaro-11.09. ifconfig eth0 returns an MTU of >> 1488 Bytes, where my faulty android build makes eth0 return 1500 >> Bytes. I believe this 1500 comes from the fact that I apply "9bbf566 >> [PATCH] net: usb: smsc95xx: fix mtu" to my current kernel. >> Changing linaro build's mtu to 1500 does not impact its good >> performance. >> Decreasing the mtu to 512 on my current (and faulty) build does not >> improve the bad performance :-(. >> >> I am starting to go mad. >> >> Regards, >> Emeric >> >> ----- Mail original ----- >> > De: "Émeric Vigier" <emeric.vigier(a)savoirfairelinux.com> >> > À: "Zach Pfeffer" <zach.pfeffer(a)linaro.org> >> > Cc: "Vikram Pandita" <vikram.pandita(a)ti.com>, >> > omapandroid-discussion(a)gforge.ti.com >> > Envoyé: Mercredi 27 Juin 2012 10:06:10 >> > Objet: Re: [Omapandroid-discussion] smsc95xx: download ok, upload >> > hangs >> > >> > Hi Zach, >> > >> > Following Ti's advice >> > (http://e2e.ti.com/support/omap/f/849/p/196732/704452.aspx#704452), >> > I will try >> > http://omapedia.org/wiki/4AI.1.4-P1_OMAP4_Icecream_Sandwich_Release_Notes >> > today. >> > >> > Also I just found out that my current 3.0.8 kernel is compiled with >> > gcc-4.4.3. I am currently trying with gcc-4.6 but I don't feel >> > confident about that. >> > I will try the one you mentioned right after. >> > >> > Thanks, >> > Emeric >> > >> > ----- Mail original ----- >> > > De: "Zach Pfeffer" <zach.pfeffer(a)linaro.org> >> > > À: "Émeric Vigier" <emeric.vigier(a)savoirfairelinux.com> >> > > Cc: "Vikram Pandita" <vikram.pandita(a)ti.com>, >> > > omapandroid-discussion(a)gforge.ti.com >> > > Envoyé: Jeudi 21 Juin 2012 17:34:15 >> > > Objet: Re: [Omapandroid-discussion] smsc95xx: download ok, upload >> > > hangs >> > > >> > > You may want to checkout our omapzoom focused tree: >> > > >> > > https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-oma… >> > > >> > > On 21 June 2012 15:20, Émeric Vigier >> > > <emeric.vigier(a)savoirfairelinux.com> wrote: >> > > > Hi Vikram, >> > > > >> > > > I made this diff and came up with few patches in smsc95xx.c and >> > > > usbnet.c (listed below). I applied them to my kernel, but issue >> > > > occurred again. >> > > > >> > > > Because linaro-12.05 uses a 3.4 kernel, and mine is only 3.0.8, >> > > > I >> > > > narrowed down the oldest linaro having ethernet working fine. >> > > > It came up to be linaro-11.09 for panda, which uses 3.1 kernel. >> > > > diff between my kernel and theirs is null for smsc95xx.c and >> > > > usbnet.c. >> > > > >> > > > Then something must be wrong with my config. I will make the >> > > > diff >> > > > of my config and theirs. I have to figure out what's the config >> > > > file linaro uses for 11.09. >> > > > My config file is for Android-4.0.4, quite long (and probably >> > > > faulty): >> > > > http://pastebin.com/2VXemSae >> > > > >> > > > Emeric >> > > > >> > > > ----- Mail original ----- >> > > >> De: "Vikram Pandita" <vikram.pandita(a)ti.com> >> > > >> À: "Émeric Vigier" <emeric.vigier(a)savoirfairelinux.com> >> > > >> Cc: omapandroid-discussion(a)gforge.ti.com >> > > >> Envoyé: Jeudi 21 Juin 2012 14:03:07 >> > > >> Objet: Re: [Omapandroid-discussion] smsc95xx: download ok, >> > > >> upload >> > > >> hangs >> > > >> >> > > >> > test linaro-12.05 ICS release and see ethernet behavior - >> > > >> > PASSED >> > > >> >> > > >> What version kernel does this use if its working? >> > > >> Would be worth a try to take a diff of the smsc driver files >> > > >> between >> > > >> AOSP and this. >> > > >> At least says its not a hw issue. >> > > >> >> > > >> >> > > >> On Thu, Jun 21, 2012 at 8:30 AM, Émeric Vigier >> > > >> <emeric.vigier(a)savoirfairelinux.com> wrote: >> > > >> > >> > > >> > Hi, >> > > >> > >> > > >> > I am experiencing ethernet issue with a pandaboard A3 >> > > >> > (OMAP4430 >> > > >> > rev >> > > >> > 2.2) featuring smsc LAN9514-JZX usbnet chipset. >> > > >> > My panda runs android-4.0.4 with linux kernel 3.0.8 >> > > >> > (android-omap-panda-3.0 branch on >> > > >> > https://android.googlesource.com/kernel/omap.git). >> > > >> > >> > > >> > Receiving ethernet frames work fine, but transmitting them >> > > >> > does >> > > >> > not. The driver/chip seems stuck. >> > > >> > Moving the USB mouse (or USB keyboard key pressed) unlocks >> > > >> > this >> > > >> > behavior and transmission gets resumed for a second or two. >> > > >> > Then >> > > >> > ethernet transmission gets stuck again. >> > > >> > >> > > >> > Recently, I cherry-picked dozen of usbnet and smsc95xx >> > > >> > patches, >> > > >> > and >> > > >> > managed to get a watchdog barking (see test 21 below). >> > > >> > >> > > >> > Unfortunately I have no JTAG probe, so I am limited to >> > > >> > driver >> > > >> > tweaks and tryouts... >> > > >> > Here are the tests I have performed so far, along with a >> > > >> > todo >> > > >> > list: >> > > >> > >> > > >> > FAILED means that the issue came up. >> > > >> > PASSED means that the issue has not come up. >> > > >> > DONE, NOT DONE, ONGOING are more related to a todo list than >> > > >> > a >> > > >> > test >> > > >> > report. >> > > >> > >> > > >> > 1. check with constant cpu load (stress -c 2) - FAILED >> > > >> > 2. check if problem occurs on older releases (non ICS) - NOT >> > > >> > DONE >> > > >> > 3. try CONFIG_PL310_ERRATA_769419 patch in cpuidle - FAILED >> > > >> > 4. check without USB hub connected - FAILED >> > > >> > 5. check with usbcore.autosuspend=600 added to cmdline - >> > > >> > FAILED >> > > >> > 6. patch ehci-omap.c to verify clock frequency - NOT DONE >> > > >> > 7. check with CPU1 offlined - FAILED >> > > >> > 8. check ethtool on android - FAILED >> > > >> > Cannot get register dump: Operation not supported on >> > > >> > transport >> > > >> > endpoint >> > > >> > 9. check without USB_EHCI_TT_NEWSCHED - FAILED >> > > >> > >> > > >> > 10. try to unbind, rebind smsc95xx - FAILED >> > > >> > 11. disable turbo_mode and reset the chip - FAILED >> > > >> > 12. test with "CONFIG_NO_HZ is not set" - FAILED >> > > >> > 13. test with another external USB ethernet dongle - NOT >> > > >> > DONE >> > > >> > 14. test linaro-12.05 ICS release and see ethernet behavior >> > > >> > - >> > > >> > PASSED >> > > >> > Ethernet runs fine on release: >> > > >> > . 12.05 tracking - PASSED >> > > >> > . 11.10 tracking - PASSED >> > > >> > . 11.09 release - PASSED >> > > >> > 15. try with "netcfg eth0 dhcp" - FAILED >> > > >> > 16. check datasheet - ONGOING >> > > >> > registers description is missing on 9514.pdf, only eeprom is >> > > >> > described >> > > >> > 17. adapt driver to ethtool - DONE >> > > >> > 18. dump registers and check against linaro 11.09 - ONGOING >> > > >> > 19. ethtool returns heaps of "0", the pattern I added to the >> > > >> > array >> > > >> > is all replaced by "0"... >> > > >> > Actually the eeprom is blank. I found it out since each time >> > > >> > I >> > > >> > unbind/bind the device to smsc95xx driver, I get a random >> > > >> > MAC >> > > >> > address... >> > > >> > >> > > >> > 20. test with 11.09 linaro kernel - NOT DONE >> > > >> > zygote not starting >> > > >> > 21. uploading 24MB file on the web (http://dl.free.fr) - >> > > >> > FAILED >> > > >> > This occurred only with these patches added to my kernel: >> > > >> > From 8a78335 [PATCH] usbnet: consider device busy at each >> > > >> > recieved >> > > >> > packet >> > > >> > From 5d5440a [PATCH] usbnet: don't clear urb->dev in >> > > >> > tx_complete >> > > >> > From 4231d47 [PATCH] net/usbnet: avoid recursive locking in >> > > >> > usbnet_stop() >> > > >> > From 1aa9bc5 [PATCH] usbnet: use netif_tx_wake_queue >> > > >> > instead >> > > >> > of >> > > >> > netif_start_queue >> > > >> > From 7bdd402 [PATCH] net/usbnet: reserve headroom on rx >> > > >> > skbs >> > > >> > From 0956a8c [PATCH] usbnet: increase URB reference count >> > > >> > before >> > > >> > usb_unlink_urb >> > > >> > From 9bbf566 [PATCH] net: usb: smsc95xx: fix mtu >> > > >> > From 720f3d7 [PATCH] usbnet: fix leak of transfer buffer of >> > > >> > dev->interrupt >> > > >> > From a472384 [PATCH] usbnet: fix failure handling in >> > > >> > usbnet_probe >> > > >> > From 5b6e9bc [PATCH] usbnet: fix skb traversing races >> > > >> > during >> > > >> > unlink(v2) >> > > >> > From 07d69d4 [PATCH] smsc95xx: mark link down on startup >> > > >> > and >> > > >> > let >> > > >> > PHY interrupt >> > > >> > a timeout occurred: >> > > >> > http://pastebin.com/KpaTJY3N >> > > >> > >> > > >> > My current kernel is based on: >> > > >> > commit 52f476403350050beb0dff135a55c06c9e7a82a9 >> > > >> > Author: Jean-Baptiste Queru <jbq(a)google.com> >> > > >> > Subject: Revert "gpu: pvr: Revert to 1.8@550175" >> > > >> > >> > > >> > I managed to get a register and PHY dump when upload is >> > > >> > stuck, >> > > >> > thanks to ethtool: >> > > >> > >> > > >> > 000: 01 00 00 ec 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 010: 04 00 00 00 00 14 00 00 00 00 00 00 00 20 00 00 >> > > >> > 020: 81 00 00 00 00 00 11 01 1f 00 00 1f a0 30 f8 00 >> > > >> > 030: 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 >> > > >> > 040: 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 060: 00 00 00 00 00 00 00 00 00 80 00 00 00 20 00 00 >> > > >> > 070: 00 00 00 00 83 0f 83 0f 00 00 00 00 0f 06 0f 06 >> > > >> > 080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 090: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 0f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 100: 0c 20 10 00 f7 6f 00 00 a2 7d 13 dd 00 00 00 40 >> > > >> > 110: 20 00 00 80 40 09 00 00 e1 c1 00 00 00 00 00 00 >> > > >> > 120: 00 81 00 00 ff ff 00 00 00 00 00 00 00 00 00 00 >> > > >> > 130: 00 31 00 00 2d 78 00 00 07 00 00 00 c3 c0 00 00 >> > > >> > 140: e1 0d 00 00 e1 c1 00 00 0b 00 00 00 ff ff 00 00 >> > > >> > 150: ff ff 00 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 >> > > >> > 160: ff ff 00 00 ff ff 00 00 ff ff 00 00 00 00 00 00 >> > > >> > 170: 40 00 00 00 02 00 00 00 e1 00 00 00 ff ff 00 00 >> > > >> > 180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > > >> > 190: ff ff 00 00 ff ff 00 00 00 00 00 00 0a 00 00 00 >> > > >> > 1a0: 00 00 00 00 c8 00 00 00 50 00 00 00 58 10 00 00 >> > > >> > >> > > >> > But the 9514.pdf datasheet I have misses register >> > > >> > description. >> > > >> > Then decoding all this is quite troublesome. >> > > >> > >> > > >> > I saw that Ubuntu release got trouble with this chipset and >> > > >> > acpi. >> > > >> > But there is no acpi on Android AFAIK. >> > > >> > Did anyone else experience this issue? >> > > >> > Does anyone have an idea where it can come from? >> > > >> > >> > > >> > >> > > >> > Thanks a lot for your kind support, >> > > >> > Emeric >> > > >> > _______________________________________________ >> > > >> > Omapandroid-discussion mailing list >> > > >> > Omapandroid-discussion(a)gforge.ti.com >> > > >> > https://gforge.ti.com/mailman/listinfo/omapandroid-discussion >> > > >> >> > > > >> > > > _______________________________________________ >> > > > Omapandroid-discussion mailing list >> > > > Omapandroid-discussion(a)gforge.ti.com >> > > > https://gforge.ti.com/mailman/listinfo/omapandroid-discussion >> > > >> > > >> > > >> > > -- >> > > Zach Pfeffer >> > > Android Platform Team Lead, Linaro Platform Teams >> > > Linaro.org | Open source software for ARM SoCs >> > > Follow Linaro: http://www.facebook.com/pages/Linaro >> > > http://twitter.com/#!/linaroorg - >> > > http://www.linaro.org/linaro-blog >> > > -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

13 years, 11 months

How identify my board

by Sandro Aurelio Feres de Palma

Hello there, how are you today? My name is Sandro Palma and I am very interested to install Linaro on my devices. I will start with the lasiest one (a Chinese table) the brand is Genesis, made by SK Mtek. Model GT-8230. Let me know if need additional info. Please I would really appreciate a support to identify which file I install. Many thanks in advance, Regards, Sandro Palma Project Especialist Note: https://wiki.linaro.org/Platform/Android/ReadAndroidBuildNames [cid:image002.jpg@01CD48A4.30FEE520] ________________________________ Esta mensagem, incluindo seus anexos, tem car?ter confidencial e seu conte?do ? restrito ao destinat?rio da mensagem. Caso voc? tenha recebido esta mensagem por engano, queira por favor retorn?-la ao destinat?rio e apag?-la de seus arquivos. Qualquer uso n?o autorizado, replica??o ou dissemina??o desta mensagem ou parte dela ? expressamente proibido. A Yp? n?o ? respons?vel pelo conte?do ou a veracidade desta informa??o Confidentiality Notice: The information contained in this email message, including any attachment, is confidential and is intended only for the person or entity to which it is addressed. If you are neither the intended recipient nor the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you may not review, retransmit, convert to hard copy, copy, use or distribute this email message or any attachments to it. If you have received this email in error, please contact the sender immediately and delete this message from any computer or other data bank. Thank you.

14 years

MediaScanner issue with JB on panda

by BELLONI Alexandre

Hi, I tried build #46 of panda-jb-gcc47-tilt-stable-blob. There is a small issue with sdcard mounting/mediascanning. Basically, the sdcard is mounted on /mnt/sdcard and MediaScanner is trying to scan /storage/sdcard0. To solve that, I created a symbolic link from /storage/sdcard0 to /mnt/sdcard in the initramfs. I really believe there is a much cleaner solution but that is a good workaround for me for now. Is that something you are willing to fix ? Regards, -- Alexandre Belloni Linux/Android Technical Leader Direct Phone : +33 4 26 49 25 08 Adeneo Embedded Adetel Group 4, ch. du Ruisseau - 69134 Ecully, France - Phone: +33 4 72 18 08 40 www.adeneo-embedded.com

14 years

About the SGX version of AOSP kernel source for panda

by YongQin Liu

Hi, All I just did a try to build the AOSP for panda locally, and found the version of the latest SGX driver binary google provides mismatches with the version in kernel/omap(android-omap-panda-3.0 branch). Below is the detail information for each: version in kernel: shell@android:/ $ cat /proc/pvr/version Version CustomerGoogle_Android_ogles1_ogles2_GPL sgxddk 18 1.8@905891 (release) omap4430_android System Version String: None shell@android:/ $ can also be checked via the file kernel/drivers/gpu/pvr/pvrversion.h The version of the SX binaries google provides: 14:10:01 liuyq:android$ strings vendor/imgtec/panda/proprietary/libGLESv2_POWERVR_SGX540_120.so |grep build OpenGL ES 2.0 build 1.8@785978 OpenGL ES GLSL ES 1.00 build 1.8@785978 14:10:26 liuyq:android$ And this mismatch will cause the the following error: PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4807, drivers/gpu/pvr/bridged_pvr_bridge.c] which will make the monitor not work. Just for your information. -- Thanks, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation(a)lists.linaro.org http://lists.linaro.org/pipermail/linaro-validation

14 years

Help: porting on to Android (shared memory calls)

by Naresh Kamboju

Hi, Here is a file massive_intr.c attached. which use shared memory call like (shm_open shm_close). I would like to port this file to Android. How can i do it? I have seen some links talks about share memory implementation on android, since i am new to Android not sure on the porting. http://www.androidenea.com/2010/03/share-memory-using-ashmem-and-binder-in.… http://www.netmite.com/android/mydroid/frameworks/base/libs/utils/IMemory.c… http://gitorious.org/android-eeepc/base/blobs/6340d73153190021292172e5f7281… do you feel we have to change file from .c to .cpp then only we can use shared memory in Android? please provide me the information on how to port this. Best regards Naresh Kamboju

14 years

Problem with NFS ICS booting on Pandaboard ES.

by K K

I am trying to boot ICS on Pandaboard ES over NFS. By default the linaro-android build is configured to boot images from mmc and as such, commands in 'init.rc' are tailored to mount the mmc card. This clearly needs to be modify in order to boot from NFS. I extracted and modified "uInitrd" image in the boot directory by commenting <mount ext4 /dev/block/mmcblk0p2 /system wait ro> in the "init.partitions.rc" file using following commands dd if=boot/uInitrd of=initrd.cpio.gz bs=1 skip=64 sudo gunzip -c ../initrd.cpio.gz | cpio -i sudo find . | cpio -o -H newc | gzip > ../newinitrd.cpio.gz mkimage -A arm -O linux -T ramdisk -C gzip -a 0 -e 0 -n initramfs -d ./newinitrd.cpio.gz ./uInitrd.new cp uInitrd.new boot/uInitrd Now i copied boot files on to the boot partition of the sd card. I did Server side configuration successfully. As below: 1. Install NFS packages host-PC$ sudo apt-get install nfs-kernel-server nfs-common 2. Add this line to the /etc/exports /tmp/system *(rw,sync,no_subtree_check,no_root_squash) 3. Start the NFS service host-PC$ sudo service nfs-kernel-server restart 4. Update exports for the NFS server host-PC$ sudo exportfs -a 5. Making sure the server is running host-PC$ showmount -e Export list for host-PC: /tmp/system * 6. Copied the contents of the Android system directory into /tmp/system 7. Added a text file with name "On_host_PC.txt" to the *"/tmp/system"* to verify whether the filesystem used during the boot is NFS or not. On the board I used an SD card which has ICS which is booting with out any issues. Then Rebooted the the board and entered into Uboot prompt and entered the following commands on Uboot prompt. setenv serverip 100.100.100.64 setenv ipaddr 100.100.100.50 mmc rescan setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" fatload mmc 0:1 0x80200000 uImage fatload mmc 0:1 0x81600000 uInitrd setenv bootargs "console=ttyO2,115200n8 rootwait ro earlyprintk fixrtc nocompcache vram=48M omapfb.vram=0:24M,1:24M mem=456M@0x80000000 mem=512M@0xA0000000 init=/init androidboot.console=ttyO2 root=/dev/nfs rw nfsroot=100.100.100.64:/tmp/system,nolock,wsize=1024,rsize=1024 ip=100.100.100.50 gw=100.100.100.64 bootserver=100.100.100.64 rootdelay=2" bootm 0x80200000 0x81600000 iam getting the following messages and booting stops. [ 5.412231] iss_register_subdev_group: Unable to register subdev ov5650 [ 5.530548] IP-Config: Guessing netmask 255.0.0.0 [ 5.533172] IP-Config: Complete: [ 5.533172] device=eth0, addr=100.100.100.50, mask=255.0.0.0, gw=255.255.255.255, [ 5.547576] host=100.100.100.50, domain=, nis-domain=(none), [ 5.547576] bootserver=255.255.255.255, rootserver=100.100.100.64, rootpath= [ 5.563232] Freeing init memory: 276K [ 5.573333] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. [ 5.911193] init: cannot open '/initlogo.rle' [ 7.348236] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xC9E1 [ 10.006286] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) [ 10.045043] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null) [ 10.092987] android_usb: already disabled [ 10.097900] adb_bind_config [ 10.298828] init: service 'console' requires console [ 10.304168] init: cannot find '/system/bin/servicemanager', disabling 'servicemanager' [ 10.312652] init: cannot find '/system/bin/vold', disabling 'vold' [ 10.312652] init: cannot find '/system/bin/netd', disabling 'netd' [ 10.325958] init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' [ 10.333526] init: cannot find '/system/bin/rild', disabling 'ril-daemon' [ 10.340698] init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger' [ 10.349151] init: cannot find '/system/bin/app_process', disabling 'zygote' [ 10.356658] init: cannot find '/system/bin/drmserver', disabling 'drm' [ 10.363677] init: cannot find '/system/bin/mediaserver', disabling 'media' [ 10.371063] init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' [ 10.378295] init: cannot find '/system/bin/installd', disabling 'installd' [ 10.385711] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' [ 10.394683] init: cannot find '/system/bin/keystore', disabling 'keystore' [ 10.394744] init: cannot find '/system/bin/gatord', disabling 'gatord' [ 10.394744] init: cannot find '/system/bin/aibd', disabling 'aibd' [ 10.415649] init: cannot find '/system/bin/pvrsrvinit', disabling 'pvrsrvinit' [ 10.423370] init: cannot find '/system/bin/uim', disabling 'uim' [ 10.429718] init: property (null) has no value for writing to /sys/class/android_usb/android0/iManufacturer [ 10.429748] init: property (null) has no value for writing to /sys/class/android_usb/android0/iProduct [ 10.452087] init: service 'console' requires console Can any one help me where I am doing mistake?

14 years

An Android kernel patch appears broken - "Input: evdev - Add ioctl to block suspend while event queue is not empty."

by Jon Medhurst (Tixy)

Hi John An Android patch in the linaro-android-* branches seems to be broken in it's used of spinlocks. The patch is the one titled "Input: evdev - Add ioctl to block suspend while event queue is not empty." This is generating lockdep warning as logged in this bug https://bugs.launchpad.net/linaro-landing-team-arm/+bug/1037565 and my analysis of the problem is in this comment: https://bugs.launchpad.net/linaro-android/+bug/1037565/comments/2 Making the wakeup driver use spin_unlock_irqsave everywhere for events_lock would solve the issue, but seems like the wrong thing. A reimplementation of the evdev patch to avoid the issue might be possible, but not something I really have time for. So my suggestion would be that we should reverted the patch in the linaro-android- branches and let upstream know about the issue. I've tested that reverting doesn't appear to cause problems. This issue has only surfaced now because Jelly Bean calls the new evdev ioctls, but ICS didn't seem to. -- Tixy

14 years

Android builds timing out

by Jon Medhurst (Tixy)

The last two vexpress builds were timed out after 3 hours but I can't see anything particularly wrong in the logs, they seemed to be going fine up to the point they were aborted. Also, one of the recent Panda builds was timed out: https://android-build.linaro.org/builds/~linaro-android/panda-jb-gcc47-tilt… I notice previous successful vexpress builds have taken about 2h45m, but I can't see any recent changes which might have made pushed the builds over 3h. (I doubt newly added pm-qa tests take a significant time.) Perhaps there is some infrastructure slowness? I'm not sure what to do. -- Tixy

14 years

Adding a git to a manifest

by Zach Pfeffer

Hey Rajagopal! Sorry for not sending this mail sooner. After you go through: https://wiki.linaro.org/Platform/Android/Gerrit https://wiki.linaro.org/Platform/Android/UpdateManifestByExample You should have a pretty good idea how to include your git the the Android manifest. A couple of things: 1. We build the tip of your git, so it should always build. If things don't build or the build breaks, please be ready to fix it. 2. We can put your git under Gerrit which will allow you to review changes, etc... we also allow backdoor access for maintainers. 3. Make sure you push the manifest change to all manifests. We have many and we try and keep them aligned. 4. Please make sure everything builds locally after integrating your manifest. Feel free to add me to the review for the manifest -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

14 years

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android August 2012