linaro-dev October 2010

linaro-dev@lists.linaro.org

68 participants
90 discussions

by Tom Gall

On Wed, Oct 6, 2010 at 10:11 AM, Alexander Sack <asac(a)linaro.org> wrote: > On Wed, Oct 6, 2010 at 4:43 PM, Tom Gall <tom.gall(a)linaro.org> wrote: >> I haven't tested without hwpacks. I'm not sure that's a valid test >> anymore with the removal of flavors and so on from the builds. Outside >> of using an old linaro image, is it valid anymore to call >> linaro-media-create without passing hwpacks? > > I think its still useful in general to have this feature in l-m-c; > someone might run their own builds with kernel included for > convenience. But you are right. as discussed in UP meeting we should > at least spit out a warning or even do a fast-fail check if there is a > kernel in /boot/. Ok. I'll test that variation, adjust the rsync call and unless something else comes up submit a merge proposal. Regards, Tom

14 years

Weekly Linaro image testing

by Jamie Bennett

Hi, We have only 43 (or 42 depending on your timezone) days until the Linaro final release [1] and as we get closer, the need for more structured testing is essential. An idea that has been incubating for some time is to have a weekly 'test day' where individuals can spend a couple of hours downloading, installing and testing a Linaro image on their hardware. Which image(s) you can test will obviously depend on the hardware available but currently we produce: * OMAP3 Headless * OMAP3 ALIP * OMAP3 Plasma Handset * OMAP3 EFL Netbook * Versatile Express Headless * UX500 Headless and in conjunction with a hardware pack from: http://jameswestby.net:8080/ * OMAP4 Headless * iMX51 Headless * OMAP3 X11 Base Starting this Thursday (30th) I propose that each and every Thursday leading up to the final release is a 'Linaro Image Test Day'. If you have any of this hardware available, please spend a little time testing and reporting bugs. As an experiment, we will be setting up the Linaro qatracker each Thursday morning, UTC, with the information for that days images. If you find it useful, please report your testing results at: http://qatracker.linaro.org/ For information on how to install the images on your hardware please take a look at: http://wiki.linaro.org/Source/ImageInstallation Regards, Jamie. -- Linaro Release Manager [1] http://wiki.linaro.org/Releases/1011/Schedule

14 years

Maverick packages patched to build with xdeb

by Peter Pearse

Are available from https://launchpad.net/~peter-pearse/+archive/cross-source deb http://ppa.launchpad.net/peter-pearse/cross-source/ubuntu maverick main deb-src http://ppa.launchpad.net/peter-pearse/cross-source/ubuntu maverick main [Any binaries produced will be amd64/i686 proving the host build is unbroken] Only tested to build with gcc-4.5-arm-linux-gnueabi && > xdeb -a armel --apt-source Resulting armel binaries not tested Please report any problems to me Patches for other packages, reports of other packages which fail to cross-build, etc. welcome....... More will be added later, however most packages cross build without patching Regards Peter Pearse

14 years

Kernel WG calls moved to new line

by Loïc Minier

Hey folks In case someone missed this in the last call, or missed the udpated invite, this is a quick reminder that the Kernel WG calls were moved to line 26344 17169#. Talk to you there! Cheers, -- Loïc Minier

14 years

CFF linaro-alip daily snapshots

by Tom Gall

Hi All, The daily linaro-alip snapshots which can be found at : http://snapshots.linaro.org/10.11-daily/linaro-alip/ are now to a reasonable point where I'd be most appreciative of any and all feedback to improve the image in ways that would be useful to you or anticipated users of the linaro-alip when 10.11 is released. Feel free to either copy the list or email me directly (tom.gall(a)linaro.org) or grab me on irc, tgall_foo or Dr_Who. At this point I believe the next steps are mostly along the lines of slimming down the image size, removing things that just aren't needed. The image as is currently 460Megs of gz'd tarball is a bit hefty. Regards, Tom Linaro User Platforms "We want great men who, when fortune frowns will not be discouraged." - Colonel Henry Knox w) tom.gall att linaro.org w) tom_gall att vnet.ibm.com h) tom_gall att mac.com

14 years

Armel cross compilers for lucid

by Marcin Juszkiewicz

Hi I finally built armel cross compiler packages for Ubuntu 10.04 'Lucid' LTS. They are available in unsigned APT repository: deb http://people.canonical.com/~hrw/ubuntu-lucid-armel-cross-compilers/ ./ They are built from Maverick packages: - binutils-source - eglibc-source - gcc-4.4-source - gcc-4.5-source - linux-source-2.6.35 - armel-cross-toolchain-base - gcc-4.4-armel-cross - gcc-4.5-armel-cross So they do not give exactly same versions as compilers used in 10.04 - please remember about it while doing cross builds. Regards, -- JID: hrw(a)jabber.org Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

14 years

Linaro Infrastructure Team Weekly Report (2010-09-24 to 2010-09-30)

by Ian Smith

All, The weekly report for the Linaro Infrastructure team may be found at: Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-09-30 Burndown chart:http://people.canonical.com/~pitti/workitems/maverick/linaro-infrastr… The burndown chart shows that a number of work items were completed this week, and a number of new work items added. Some work items will need deferring to the next cycle, and some should be completed following reviews being completed by external teams. Of the work items being deferred, some are associated with the additional work from the new Infrastructure Stakeholder process, and the hardware pack development, planning QA resources, interviewing, as well as some items being more complex than originally anticipated. * released Launch Control 0.1.1 to fix a configuration issue * linaro-media-create was refactored to better integrate with hwpack-install * Infrastructure team stakeholder meeting held, and outlines of proposals were drafted * Hardware pack scripts packaged and included in the tools PPA. * arm-m-image-building-console: Three branches landed * Some code was added to make abrek give more output during test execution, with an option to mute this Please let me know if you have any comments or questions. Kind Regards, Ian

14 years

[PATCH 0/2] OMAP3 PM: sleep code clean up

by Vishwanath BS

This patch series has some clean up in OMAP3 sleep code. Patches have been rebased to latest kevin's pm branch. Vishwanath BS (2): OMAP3 PM: move omap3 sleep to ddr OMAP3 PM: sleep code clean up arch/arm/mach-omap2/pm34xx.c | 9 +- arch/arm/mach-omap2/sleep34xx.S | 377 ++++++++++++++--------------- arch/arm/plat-omap/include/plat/control.h | 2 + 3 files changed, 190 insertions(+), 198 deletions(-)

14 years

bzr-pipeline patches for 0.2 release

by Zygmunt Krynicki

Hello. I was trying to improve my work flow and I finally used bzr-pipeline for change management. I have prepared a rather big pipeline with 13 different patches that collectively add some of 0.2 features, some minor enhancements, bug fixes etc. I did not know what to expect of pipeline plug-in so the patches I produces directly reflect my old development style (hack until glad with result) rather than some carefully planned design. I'd like to ask you for advice on how to propose all of this for merging. I used bzr sync-pipeline to publish all of the pipeline components on launchpad (as lp:~zkrynicki/launch-control/stable.pipe). Should I just mark each one as ready for review? I could also export the whole pipeline as a series of patches (I like that but it's somewhat against our nice review system on lp.net). I have no experience with this yet, so if anyone knows of a better way feel free to point me out to it. Best regards Zygmunt Krynicki PS: IMHO pipeline is a really good tool and I hope we can continue using it.

14 years

[Maverick][PATCH] UBUNTU : SAUCE - ARM: Support for vbus, overcurrent and LEDs on IGEPv2

by Mathieu Poirier

>From 210c9482650eb6cb24488303e50e3c49babb3d3a Mon Sep 17 00:00:00 2001 From: Enric Balletbo i Serra <eballetbo(a)gmail.com> Date: Fri, 1 Oct 2010 15:23:31 -0600 Subject: [PATCH] Support for vbus, overcurrent and LEDs on IGEPv2 This patch adds support for the VBUS and over current GPIOs along with the four LEDs present on the IGEPv2 board. Initialisation of the LEDs is done with the LED class if CONFIG_LEDS_GPIO is selected or the General Purpose Input/Output (GPIO) interface if CONFIG_LEDS_GPIO is not selected. https://bugs.launchpad.net/bugs/651589 Signed-off-by: <eballetbo(a)gmail.com> Signed-off-by: <mathieu.poirier(a)canonical.com> --- arch/arm/mach-omap2/board-igep0020.c | 170 ++++++++++++++++++++-------------- 1 files changed, 101 insertions(+), 69 deletions(-) diff --git a/arch/arm/mach-omap2/board-igep0020.c b/arch/arm/mach-omap2/board-igep0020.c index d55c57b..21bb77f 100644 --- a/arch/arm/mach-omap2/board-igep0020.c +++ b/arch/arm/mach-omap2/board-igep0020.c @@ -261,6 +261,77 @@ static struct omap2_hsmmc_info mmc[] = { {} /* Terminator */ }; +#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE) +#include <linux/leds.h> + +static struct gpio_led igep2_gpio_leds[] = { + [0] = { + .name = "gpio-led:red:d0", + .gpio = IGEP2_GPIO_LED0_RED, + .default_trigger = "default-off" + }, + [1] = { + .name = "gpio-led:green:d0", + .gpio = IGEP2_GPIO_LED0_GREEN, + .default_trigger = "default-off", + }, + [2] = { + .name = "gpio-led:red:d1", + .gpio = IGEP2_GPIO_LED1_RED, + .default_trigger = "default-off", + }, + [3] = { + .name = "gpio-led:green:d1", + .default_trigger = "heartbeat", + .gpio = -EINVAL, /* gets replaced */ + }, +}; + +static struct gpio_led_platform_data igep2_led_pdata = { + .leds = igep2_gpio_leds, + .num_leds = ARRAY_SIZE(igep2_gpio_leds), +}; + +static struct platform_device igep2_led_device = { + .name = "leds-gpio", + .id = -1, + .dev = { + .platform_data = &igep2_led_pdata, + }, +}; + +static void __init igep2_leds_init(void) +{ + platform_device_register(&igep2_led_device); +} + +#else +static inline void igep2_leds_init(void) +{ + if ((gpio_request(IGEP2_GPIO_LED0_RED, "gpio-led:red:d0") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED0_RED, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED0_RED, 0); + gpio_set_value(IGEP2_GPIO_LED0_RED, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_RED\n"); + + if ((gpio_request(IGEP2_GPIO_LED0_GREEN, "gpio-led:green:d0") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED0_GREEN, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED0_GREEN, 0); + gpio_set_value(IGEP2_GPIO_LED0_GREEN, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_GREEN\n"); + + if ((gpio_request(IGEP2_GPIO_LED1_RED, "gpio-led:red:d1") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED1_RED, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED1_RED, 0); + gpio_set_value(IGEP2_GPIO_LED1_RED, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_RED\n"); + +} +#endif + static int igep2_twl_gpio_setup(struct device *dev, unsigned gpio, unsigned ngpio) { @@ -274,14 +345,40 @@ static int igep2_twl_gpio_setup(struct device *dev, igep2_vmmc1_supply.dev = mmc[0].dev; igep2_vmmc2_supply.dev = mmc[1].dev; + /* + * REVISIT: need ehci-omap hooks for external VBUS + * power switch and overcurrent detect + */ + gpio_request(gpio + 1, "GPIO_EHCI_NOC"); + gpio_direction_input(gpio + 1); + + /* + * TWL4030_GPIO_MAX + 0 == ledA, GPIO_USBH_CPEN + * (out, active low) + */ + gpio_request(gpio + TWL4030_GPIO_MAX, 0); + gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0); + + /* TWL4030_GPIO_MAX + 1 == ledB (out, active low LED) */ +#if !defined(CONFIG_LEDS_GPIO) && !defined(CONFIG_LEDS_GPIO_MODULE) + if ((gpio_request(gpio+TWL4030_GPIO_MAX+1, "gpio-led:green:d1") == 0) + && (gpio_direction_output(gpio + TWL4030_GPIO_MAX + 1, 1) == 0)) { + gpio_export(gpio + TWL4030_GPIO_MAX + 1, 0); + gpio_set_value(gpio + TWL4030_GPIO_MAX + 1, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_GREEN\n"); +#else + igep2_gpio_leds[3].gpio = gpio + TWL4030_GPIO_MAX + 1; +#endif + return 0; }; -static struct twl4030_gpio_platform_data igep2_gpio_data = { +static struct twl4030_gpio_platform_data igep2_twl4030_gpio_pdata = { .gpio_base = OMAP_MAX_GPIO_LINES, .irq_base = TWL4030_GPIO_IRQ_BASE, .irq_end = TWL4030_GPIO_IRQ_END, - .use_leds = false, + .use_leds = true, .setup = igep2_twl_gpio_setup, }; @@ -355,47 +452,6 @@ static void __init igep2_display_init(void) pr_err("IGEP v2: Could not obtain gpio GPIO_DVI_PUP\n"); } -#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE) -#include <linux/leds.h> - -static struct gpio_led igep2_gpio_leds[] = { - { - .name = "led0:red", - .gpio = IGEP2_GPIO_LED0_RED, - }, - { - .name = "led0:green", - .default_trigger = "heartbeat", - .gpio = IGEP2_GPIO_LED0_GREEN, - }, - { - .name = "led1:red", - .gpio = IGEP2_GPIO_LED1_RED, - }, -}; - -static struct gpio_led_platform_data igep2_led_pdata = { - .leds = igep2_gpio_leds, - .num_leds = ARRAY_SIZE(igep2_gpio_leds), -}; - -static struct platform_device igep2_led_device = { - .name = "leds-gpio", - .id = -1, - .dev = { - .platform_data = &igep2_led_pdata, - }, -}; - -static void __init igep2_init_led(void) -{ - platform_device_register(&igep2_led_device); -} - -#else -static inline void igep2_init_led(void) {} -#endif - static struct platform_device *igep2_devices[] __initdata = { &igep2_dss_device, }; @@ -425,7 +481,7 @@ static struct twl4030_platform_data igep2_twldata = { /* platform_data for children goes here */ .usb = &igep2_usb_data, .codec = &igep2_codec_data, - .gpio = &igep2_gpio_data, + .gpio = &igep2_twl4030_gpio_pdata, .vmmc1 = &igep2_vmmc1, .vmmc2 = &igep2_vmmc2, .vpll2 = &igep2_vpll2, @@ -486,34 +542,10 @@ static void __init igep2_init(void) usb_ehci_init(&ehci_pdata); igep2_flash_init(); - igep2_init_led(); + igep2_leds_init(); igep2_display_init(); igep2_init_smsc911x(); - /* GPIO userspace leds */ -#if !defined(CONFIG_LEDS_GPIO) && !defined(CONFIG_LEDS_GPIO_MODULE) - if ((gpio_request(IGEP2_GPIO_LED0_RED, "led0:red") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED0_RED, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED0_RED, 0); - gpio_set_value(IGEP2_GPIO_LED0_RED, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_RED\n"); - - if ((gpio_request(IGEP2_GPIO_LED0_GREEN, "led0:green") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED0_GREEN, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED0_GREEN, 0); - gpio_set_value(IGEP2_GPIO_LED0_GREEN, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_GREEN\n"); - - if ((gpio_request(IGEP2_GPIO_LED1_RED, "led1:red") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED1_RED, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED1_RED, 0); - gpio_set_value(IGEP2_GPIO_LED1_RED, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_RED\n"); -#endif - /* GPIO W-LAN + Bluetooth combo module */ if ((gpio_request(IGEP2_GPIO_WIFI_NPD, "GPIO_WIFI_NPD") == 0) && (gpio_direction_output(IGEP2_GPIO_WIFI_NPD, 1) == 0)) { -- 1.7.0.4

14 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev October 2010