linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

Re: Please review blueprint linaro-n-validation-job-dispatcher

by Paul Larson

On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson <paul.larson(a)linaro.org>wrote: > 2. One queue TOTAL. One queue may seem like a bottleneck, but I don't >>> think it has to be in practice. One process can monitor that queue, then >>> launch a process or thread to handle each new job that comes in. >>> >> I think RabbitMQ message can have the ability to include the board >> information in it to use one queue, and also we can use different queues for >> different types of boards. >> > Right, but my question was, if you are already encoding that information in > the job stream, what is the advantage to having a queue for each board type, > rather than a single queue? > > >> >>> >>> >>> Job description: >>> I'd like to see some more detail here. Can you provide an example of a >>> job file that would illustrate how you see it working? We also need to >>> specify the underlying mechanisms that will handle parsing what's in the job >>> file, and calling [something?] to do those tasks. What we have here feels >>> like it might be a bit cumbersome. >>> >> I added an detailed one on the spec, like: >> >> 1. >> >> [Beagle-1, >> http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/imx51/20110131/0/ima…, >> >> http://snapshots.linaro.org/11.05-daily/linaro-headless/20110131/0/images/t…, >> 900, ["abrek", "LTP", 180], ["none", "echo 100 > abc", 1], ... ] >> 2. >> >> [IMX51-2, 20100131, 900, ["abrek", "LTP", 180], ["none", "echo 100 > >> abc", 1], ... ] >> >> This looks almost like JSON, which is what Zygmunt was originally pushing > for IIRC. If we are already going down that path, seems it would be > sensible to take it a step further and have defined sections. For example: > > Tests:[ > { > name:"LTP", > testsuite:"abrek", > subtest:"ltp", <---- not thrilled about that name "subtest", > but can't think of something better to call it at the moment > timeout:180, > reboot_after:True > }, > { > name:"echo test", > testsuite:"shell", > timeout:20 > reboot_after:False > } > ] > What do you think? Obviously, there would be other sections for things > like defining the host characteristics, the image to deploy, etc. > > >> >>> >>> >> Other questions... >>> What if we have a dependency, how does that get installed on the target >>> image? For example, if I want to do a test that requires bootchart be >>> installed before the system is booted, we should be able to specify that, >>> and have it installed before booting. >>> >>> What about installing necessary test suites? How do we tell it, in >>> advance, what we need to have installed, and how does it get on the image >>> before we boot, or before we start testing? >>> >> I think validation tools, test suites and necessary files are likely to >> install after test image deployment. >> > Yes, clearly they have to be installed after deployment, but we may also > need to consider them installing BEFORE we actually boot the test image. > > Had another thought on this tonight, I didn't hear much back on the previous proposal, but how about something more like this as an example of what a job description might look like. In this scenario, there would be some metadata for the job itself, such as timeout values, etc. Then steps that would define commands with parameters. That would allow us to be more flexible, and add support for more commands without changing the format. Hopefully the mailer doesn't mangle this too badly. :) { "job_name": "foo", "target": "panda01", "timeout": 18000, "steps": [ { "command": "deploy", "parameters": { "rootfs": " http://snapshots.linaro.org/11.05-daily/linaro-developer/20110208/0/images/… " "hwpack": " http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/20110208/0/ima… " } }, { "command": "boot_test_image" }, { "command": "test_abrek", "parameters": { "test_name": "ltp" } }, { "command": "submit_results", "parameters": { "server": "http://dashboard.linaro.org", "stream": "panda01-ltp" } } ] } Thanks, Paul Larson

13 years, 10 months

Re: OMAP DVFS feature for Linaro

by Nicolas Pitre

On Tue, 15 Feb 2011, Vishwanath Sripathy wrote: > Hi Nicolas, > > Pls find attached the patch set for supporting DVFS feature on OMAP. > These patches have been generated against latest Linaro 2.6.37 tree > and tested on OMAP3430 and ZOOM3. > > Note that these patches are already posted to linux omap mailing list > (https://patchwork.kernel.org/patch/495021/) and they are under > discussion. So I have prefixed these patches as WIP. Kindly merge > these patches for 11.05 release. A few notes on those patches: 1) Please CC linaro-dev next time so other people are aware of what you did, what you sent me, etc. I've added it to this reply. This way at least if nothing happens with your patches it's easier to put the blame on me. :-) 2) Your cover message contains this in plain sight in the diffstat part: mode change 100644 => 100755 arch/arm/mach-omap2/voltage.c mode change 100644 => 100755 arch/arm/plat-omap/cpu-omap.c This is clearly wrong to flag .c files as executables, so you should take care to fix that and understand why this happened in the first place. Incidentally this mode change does not appear in any of your patches. 3) All your patches were numbered, except for: V4-OMAP3-PM-Set-clear-T2-bit-for-Smartreflex-on-TWL.patch Since I'm sure you know better than I do where that patch should be applied in the series (if at all) you should rename it appropriately, or at least let me know in which order to apply it (I initially applied it last based on the date recorded in the patch but that didn't work out). 4) This patch is a bit thin on explanation: [PATCH 08/13] [PM WIP OMAP] OMAP3: cpufreq driver changes for DVFS support Changes in the omap cpufreq driver for DVFS support. Signed-off-by: Vishwanath BS <vishwanath.bs(a)ti.com> What are those changes? It is not obvious to me looking at the patch. All the other patches are sufficiently documented. I've applied them to the linaro-2.6.37 branch. Please note that the 11.05 Linaro release will be based on a 2.6.38 branch I'm about to create. Can you tell me what is the likelyhood for those patches to be merged upstream for the next merge window? Nicolas

13 years, 10 months

[PATCH v3 0/3] ARM: IMX5: cpuidle driver

by yong.shen＠linaro.org

change log: addressed some comments in previous cycle.

13 years, 10 months

[linaro-android][PATCH 1/1] Add virtual battery driver

by sola

>From 494eb1f2bb56261815e4230e582d27311f32ae81 Mon Sep 17 00:00:00 2001 From: Akihiro MAEDA <sola.1980.a(a)gmail.com> Date: Thu, 17 Feb 2011 07:16:37 +0900 Subject: [PATCH 1/1] Add virtual battery driver This patch adds virtual battery driver. This is based on git://git.linaro.org/people/jstultz/linux.git dev/linaro.android Signed-off-by: Akihiro MAEDA <sola.1980.a(a)gmail.com> --- drivers/power/Kconfig | 5 + drivers/power/Makefile | 1 + drivers/power/virtual_battery.c | 427 +++++++++++++++++++++++++++++++++++++++ 3 files changed, 433 insertions(+), 0 deletions(-) create mode 100644 drivers/power/virtual_battery.c diff --git a/drivers/power/Kconfig b/drivers/power/Kconfig index 60d83d9..7258bc9 100644 --- a/drivers/power/Kconfig +++ b/drivers/power/Kconfig @@ -185,4 +185,9 @@ config CHARGER_TWL4030 help Say Y here to enable support for TWL4030 Battery Charge Interface. +config BATTERY_VIRTUAL + tristate "Virtual Battery Driver" + help + Say Y to include support for Virtual Battery. + endif # POWER_SUPPLY diff --git a/drivers/power/Makefile b/drivers/power/Makefile index c75772e..71f8b36 100644 --- a/drivers/power/Makefile +++ b/drivers/power/Makefile @@ -32,3 +32,4 @@ obj-$(CONFIG_BATTERY_JZ4740) += jz4740-battery.o obj-$(CONFIG_BATTERY_INTEL_MID) += intel_mid_battery.o obj-$(CONFIG_CHARGER_ISP1704) += isp1704_charger.o obj-$(CONFIG_CHARGER_TWL4030) += twl4030_charger.o +obj-$(CONFIG_BATTERY_VIRTUAL) += virtual_battery.o diff --git a/drivers/power/virtual_battery.c b/drivers/power/virtual_battery.c new file mode 100644 index 0000000..a85baac --- /dev/null +++ b/drivers/power/virtual_battery.c @@ -0,0 +1,427 @@ +/* + * drivers/power/virtual_battery.c + * + * Virtual battery driver + * + * Copyright (C) 2008 Pylone, Inc. + * Author: Masashi YOKOTA <yokota(a)pylone.jp> + * Modified by: Akihiro MAEDA <sola.1980.a(a)gmail.com> + * + * This software is licensed under the terms of the GNU General Public + * License version 2, as published by the Free Software Foundation, and + * may be copied, distributed, and modified under those terms. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/kernel.h> +#include <linux/types.h> +#include <linux/err.h> +#include <linux/string.h> +#include <linux/device.h> +#include <linux/platform_device.h> +#include <linux/power_supply.h> +#include <linux/version.h> + + +/* module parameters */ +static int ac_status = 1; /* online */ +static int battery_status = POWER_SUPPLY_STATUS_CHARGING; +static int battery_health = POWER_SUPPLY_HEALTH_GOOD; +static int battery_present = 1; /* true */ +static int battery_technology = POWER_SUPPLY_TECHNOLOGY_LION; +static int battery_capacity = 50; + + +static struct platform_device *bat_pdev; + +static enum power_supply_property virtual_ac_props[] = { + POWER_SUPPLY_PROP_ONLINE, +}; + +static enum power_supply_property virtual_battery_props[] = { + POWER_SUPPLY_PROP_STATUS, + POWER_SUPPLY_PROP_HEALTH, + POWER_SUPPLY_PROP_PRESENT, + POWER_SUPPLY_PROP_TECHNOLOGY, + POWER_SUPPLY_PROP_CAPACITY, +}; + +static int virtual_ac_get_property(struct power_supply *psy, + enum power_supply_property psp, + union power_supply_propval *val) +{ + int ret = 0; + + dev_dbg(&bat_pdev->dev, "%s: psp=%d\n", __func__, psp); + switch (psp) { + case POWER_SUPPLY_PROP_ONLINE: + val->intval = ac_status; + break; + default: + ret = -EINVAL; + break; + } + return ret; +} + +static int virtual_battery_get_property(struct power_supply *psy, + enum power_supply_property psp, + union power_supply_propval *val) +{ + int ret = 0; + + dev_dbg(&bat_pdev->dev, "%s: psp=%d\n", __func__, psp); + switch (psp) { + case POWER_SUPPLY_PROP_STATUS: + val->intval = battery_status; + break; + case POWER_SUPPLY_PROP_HEALTH: + val->intval = battery_health; + break; + case POWER_SUPPLY_PROP_PRESENT: + val->intval = battery_present; + break; + case POWER_SUPPLY_PROP_TECHNOLOGY: + val->intval = battery_technology; + break; + case POWER_SUPPLY_PROP_CAPACITY: + val->intval = battery_capacity; + break; default: ret = -EINVAL; + break; + } + + return ret; +} + +static struct power_supply power_supply_ac = { + .properties = virtual_ac_props, + .num_properties = ARRAY_SIZE(virtual_ac_props), + .get_property = virtual_ac_get_property, + .name = "ac", + .type = POWER_SUPPLY_TYPE_MAINS, +}; + +static struct power_supply power_supply_bat = { + .properties = virtual_battery_props, + .num_properties = ARRAY_SIZE(virtual_battery_props), + .get_property = virtual_battery_get_property, + .name = "battery", + .type = POWER_SUPPLY_TYPE_BATTERY, +}; + + +struct battery_property_map { + int value; + char const * key; +}; + +static struct battery_property_map map_ac_online[] = { + { 0, "on" }, + { 1, "off" }, + { -1, NULL }, +}; + +static struct battery_property_map map_status[] = { + { POWER_SUPPLY_STATUS_CHARGING, "charging" }, + { POWER_SUPPLY_STATUS_DISCHARGING, "discharging" }, + { POWER_SUPPLY_STATUS_NOT_CHARGING, "not-charging" }, + { POWER_SUPPLY_STATUS_FULL, "full" }, + { -1, NULL }, +}; + +static struct battery_property_map map_health[] = { + { POWER_SUPPLY_HEALTH_GOOD, "good" }, + { POWER_SUPPLY_HEALTH_OVERHEAT, "overheat" }, + { POWER_SUPPLY_HEALTH_DEAD, "dead" }, + { POWER_SUPPLY_HEALTH_OVERVOLTAGE, "overvoltage" }, + { POWER_SUPPLY_HEALTH_UNSPEC_FAILURE, "failure" }, + { -1, NULL }, +}; + +static struct battery_property_map map_present[] = { + { 0, "false" }, + { 1, "true" }, + { -1, NULL }, +}; + +static struct battery_property_map map_technology[] = { + { POWER_SUPPLY_TECHNOLOGY_NiMH, "NiMH" }, + { POWER_SUPPLY_TECHNOLOGY_LION, "LION" }, + { POWER_SUPPLY_TECHNOLOGY_LIPO, "LIPO" }, + { POWER_SUPPLY_TECHNOLOGY_LiFe, "LiFe" }, + { POWER_SUPPLY_TECHNOLOGY_NiCd, "NiCd" }, + { POWER_SUPPLY_TECHNOLOGY_LiMn, "LiMn" }, + { -1, NULL }, +}; + + +static int map_get_value(struct battery_property_map * map, const char * key, int def_val) +{ + char buf[4096]; + int cr; + + strcpy(buf, key); + cr = strlen(buf) - 1; + if (buf[cr] == '\n') + buf[cr] = '\0'; + + while (map->key) { + if (strcasecmp(map->key, buf) == 0) + return map->value; + map++; + } + + return def_val; +} + + +static const char * map_get_key(struct battery_property_map * map, int value, const char * def_key) +{ + while (map->key) { + if (map->value == value) + return map->key; + map++; + } + + return def_key; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_ac_status(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_ac_status(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s\n", __func__, kp->name, key); + ac_status = map_get_value( map_ac_online, key, ac_status); + power_supply_changed(&power_supply_ac); + return 0; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_get_ac_status(char *buffer, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_get_ac_status(char *buffer, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s\n", __func__, kp->name); + strcpy(buffer, map_get_key( map_ac_online, ac_status, "unknown")); + return strlen(buffer); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_battery_status(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_battery_status(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s.\n", __func__, kp->name, key); + battery_status = map_get_value( map_status, key, battery_status); + power_supply_changed(&power_supply_bat); + return 0; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_get_battery_status(char *buffer, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_get_battery_status(char *buffer, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s\n", __func__, kp->name); + strcpy(buffer, map_get_key( map_status, battery_status, "unknown")); + return strlen(buffer); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_battery_health(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_battery_health(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s\n", __func__, kp->name, key); + battery_health = map_get_value( map_health, key, battery_health); + power_supply_changed(&power_supply_bat); + return 0; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_get_battery_health(char *buffer, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_get_battery_health(char *buffer, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s\n", __func__, kp->name); + strcpy(buffer, map_get_key( map_health, battery_health, "unknown")); + return strlen(buffer); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_battery_present(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_battery_present(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s\n", __func__, kp->name, key); + battery_present = map_get_value( map_present, key, battery_present); + power_supply_changed(&power_supply_ac); + return 0; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_get_battery_present(char *buffer, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_get_battery_present(char *buffer, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s\n", __func__, kp->name); + strcpy(buffer, map_get_key( map_present, battery_present, "unknown")); + return strlen(buffer); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_battery_technology(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_battery_technology(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s\n", __func__, kp->name, key); + battery_technology = map_get_value( map_technology, key, battery_technology); + power_supply_changed(&power_supply_bat); + return 0; +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_get_battery_technology(char *buffer, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_get_battery_technology(char *buffer, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + dev_dbg(&bat_pdev->dev, "%s: name=%s\n", __func__, kp->name); + strcpy(buffer, map_get_key( map_technology, battery_technology, "unknown")); + return strlen(buffer); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static int param_set_battery_capacity(const char *key, const struct kernel_param *kp) +#else /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +static int param_set_battery_capacity(const char *key, struct kernel_param *kp) +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ +{ + int tmp; + + dev_dbg(&bat_pdev->dev, "%s: name=%s, key=%s\n", __func__, kp->name, key); + + if (1 != sscanf(key, "%d", &tmp)) + return -EINVAL; + + battery_capacity = tmp; + power_supply_changed(&power_supply_bat); + return 0; +} + +#define param_get_battery_capacity param_get_int + +static int __init virtual_battery_init(void) +{ + int ret; + + bat_pdev = platform_device_register_simple(KBUILD_BASENAME, 0, NULL, 0); + if (IS_ERR(bat_pdev)) + return PTR_ERR(bat_pdev); + + ret = power_supply_register(&bat_pdev->dev, &power_supply_ac); + if (ret) + goto err_battery_failed; + + ret = power_supply_register(&bat_pdev->dev, &power_supply_bat); + if (ret) + goto err_ac_failed; + + printk(KERN_INFO KBUILD_BASENAME": registered \n"); + return 0; + + err_battery_failed: + power_supply_unregister(&power_supply_ac); + err_ac_failed: + return ret; +} + +static void __exit virtual_battery_exit(void) +{ + power_supply_unregister(&power_supply_ac); + power_supply_unregister(&power_supply_bat); + platform_device_unregister(bat_pdev); + printk(KERN_INFO KBUILD_BASENAME": unregistered \n"); +} + +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) +static struct kernel_param_ops param_ops_ac_status = { + .set = param_set_ac_status, + .get = param_get_ac_status, +}; + +static struct kernel_param_ops param_ops_battery_status = { + .set = param_set_battery_status, + .get = param_get_battery_status, +}; + +static struct kernel_param_ops param_ops_battery_present = { + .set = param_set_battery_present, + .get = param_get_battery_present, +}; + +static struct kernel_param_ops param_ops_battery_technology = { + .set = param_set_battery_technology, + .get = param_get_battery_technology, +}; + +static struct kernel_param_ops param_ops_battery_health = { + .set = param_set_battery_health, + .get = param_get_battery_health, +}; + +static struct kernel_param_ops param_ops_battery_capacity = { + .set = param_set_battery_capacity, + .get = param_get_battery_capacity, +}; +#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 36) */ + +module_init(virtual_battery_init); +module_exit(virtual_battery_exit); + +#define param_check_ac_status(name, p) __param_check(name, p, void); +#define param_check_battery_status(name, p) __param_check(name, p, void); +#define param_check_battery_present(name, p) __param_check(name, p, void); +#define param_check_battery_technology(name, p) __param_check(name, p, void); +#define param_check_battery_health(name, p) __param_check(name, p, void); +#define param_check_battery_capacity(name, p) __param_check(name, p, void); + +module_param(ac_status, ac_status, 0644); +MODULE_PARM_DESC(ac_status, "AC charging state <on|off>"); + +module_param(battery_status, battery_status, 0644); +MODULE_PARM_DESC(battery_status, "battery status <charging|discharging|not-charging|full>"); + +module_param(battery_present, battery_present, 0644); +MODULE_PARM_DESC(battery_present, "battery presence state <good|overheat|dead|overvoltage|failure>"); + +module_param(battery_technology, battery_technology, 0644); +MODULE_PARM_DESC(battery_technology, "battery technology <NiMH|LION|LIPO|LiFe|NiCd|LiMn>"); + +module_param(battery_health, battery_health, 0644); +MODULE_PARM_DESC(battery_health, "battery health state <good|overheat|dead|overvoltage|failure>"); + +module_param(battery_capacity, battery_capacity, 0644); +MODULE_PARM_DESC(battery_capacity, "battery capacity (percentage)"); + + +MODULE_AUTHOR("Masashi YOKOTA <yokota(a)pylone.jp>"); +MODULE_LICENSE("GPL"); +MODULE_DESCRIPTION("Virtual battery driver"); +MODULE_ALIAS("platform:"KBUILD_BASENAME); -- 1.7.0.4

13 years, 10 months

GCC ICE compiling glibc with latest linaro gcc 4.5

by Khem Raj

Hi Commit r99457 on linaro 4.5 branch is causing a ICE when compiling the attached file with following options gcc-4_5-branch/build.i686-linux.armeb-oe-linux-gnueabi/gcc/cc1 -O2 -mtune=xscale a.i It only happens when I use -mtune=xscale otherwise it compiles fine It was tested on armeb I have not done a test on LE. I have attached the testcase to this email as well. Thanks -Khem

13 years, 10 months

[PM] 16/02/2011 - Minutes for the Power Management WG weekly call

by Vincent Guittot

Hi All, The minutes of the power management weekly call can be found at : https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2011-02-16 Regards, Vincent

13 years, 10 months

[RFC] agent-based remote validation invocation for LAVA

by Jim Huang

Hello list, Regarding integration of LAVA [1] architecture with Android devices, we would like to reuse the existing infrastructure and framework design. Abrek [2] is a great testsuite framework for running test cases and benchmarks. However, due to the restrictions of unusual Android runtime, we consider to introduce the agent-based remote validation invocation mechanism for LAVA as the extension. Also, the proof-of-concept implementation is attached. ** Why can't we execute LAVA/Abrek directly on Android devices? LAVA/Abrek is written in Python, which implies there must be a solid Python runtime for Android. CPython is verified and well-designed, but it is not well tested on Android. In fact, Android has its own libc implementation, bionic, which is the minimal and special libc originally taken from NetBSD libc. However, bionic libc only supports limited set of POSIX C APIs, and it is almost not feasible to maintain Linaro bionic modifications in early stage just to satisfy CPython. The bionic libc is always changed fast by Google engineers, and we have no idea about their plans. Therefore, we prefer the way not to modify Android runtime. That is, don't execute LAVA/Abrek directly on Android environment. ** Yet another agent? In fact, Android already provide an elegant approach for accessing target environment, adb (Android Debug Bridge)[3], which is a versatile tool allowing users to manage the state of Android-powered device. adb itself is a client-server program that includes three components: (1) A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. (2) A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on the device. (3) A daemon, which runs as a background process on each device instance. The adb protocol can be established through USB (device needs to enable Android USB gadget driver) or TCP/IP. adb is very solid and powerful. For example, if you would like to test Android UI, you can use the command on Host side: $ adb shell monkey -v -p your.package.name 500 The above could be illustrated: Host commands --> adb protocol (USB or TCP/IP) --> Target receives the command --> execute "monkey" Monkey is a program on Android device that runs on your emulator or device and generates pseudo-random streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. In this example, your Android application is launched, and 500 pseudo-random events are sent to it. We call it as "agent-based remote invocation", and it is built-in. ** So, what's agent-based remote validation invocation for LAVA? There are three key items: (a) Agent (b) Remote validation invocation (c) LAVA We keep in mind that we make no technical impact to LAVA architecture, and the "Agent" is just the "helper". Originally, the client-server communication looks like the following: LAVA server <----> LAVA client --> Abrek test suite Since Python runtime is hard to support, the proposed model would be: LAVA server <--> LAVA client --> Abrek test suite || adb extension (host) <--> adb (target) -> execute command For integrating test items and benchmarks for Android, this proposal is running abrek on the host side. By using Android's standard tool, adb to communicate with the adbd (adb daemon) on target, the test case commands can be issued and the output can return back. Besides, the files can be pushed and pull to and from the target by adb as well. Sometimes the results may be stored in certain file on target, and we definitely could couple with the case. Thus, running abrek on host side along with "Agent" should be a workable approach. ** Show me the use case The attached patch is just trivial proof-of concept implementation done by Jeremy Chang that adds a 'monkey' test definition file for abrek. Once TCP/IP or USB is ready, for Android's monkey testing, the procedure is like as following: (1) abrek run monkey (2) abrek dashboard put /anonymous/ monkey1297752359.0 In addition, if we wish to execute certain native application on Android device, abrek could ask adb to send the executable files and related data to target first. Then, execute it as expected. The command looks like: $ adb push <my-executable-file> /system/bin $ adb push <my-data-file> /data $ adb shell /system/bin/<my-executable-file> The above instructions could be refined into "adb extension" as the part of LAVA client framework. That's all. It could be straightforward and transparent. Any suggestion is appreciated. Thank you in advance. Sincerely, Jim Huang (jserv) http://0xlab.org/ [1] https://wiki.linaro.org/Platform/Validation/LAVA/Architecture [2] https://wiki.linaro.org/Platform/Validation/AbrekTestsuites [3] http://developer.android.com/guide/developing/tools/adb.html

13 years, 10 months

ST-Ericsson launches the Igloo open source community

by Lee Jones

http://eetimes.eu/en/st-ericsson-launches-the-igloo-open-source-community.h… =:-D

13 years, 10 months

Announcing the Linaro porting jam

by Steve Langasek

Hello, my fellow ARM aficionados! The Linaro Developer Platform Team is pleased to announce a new initiative to help improve the state of software on ARM: the ARM porting jam. Starting today, February 16th, we will be running a weekly IRC jam on Wednesdays from 1400-1800 UTC to bring developers together to work on all manner of userspace porting bugs, with the aim of fixing portability issues and getting the fixes delivered to our upstreams. An initial porting queue of known issues can be found here: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue Interested in making the software in Ubuntu run better on ARM? Stop on by the #linaro channel on irc.linaro.org today! -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek(a)ubuntu.com vorlon(a)debian.org

13 years, 10 months

Minutes for Mentor team meeting - 2011-2-15

by Matt Waddel

The wiki formatted minutes are at: https://wiki.linaro.org/Mentoring/Status/2011-02-15 Please direct suggestions or comments to Matt or Andy. Cheers, Matt == Team Highlights == * Wiki Additions * https://wiki.linaro.org/Mentoring/Additions-l-m-c * Email setup * https://wiki.linaro.org/Internal/Process/ThunderbirdSetup * https://wiki.linaro.org/Internal/Process/MuttSetup * https://wiki.linaro.org/Internal/Process/CalendarSetup * https://wiki.linaro.org/Mentoring/HowTo/UbuntuDevelopmentProcess * https://wiki.linaro.org/Mentoring/KernelDeploy == Action Items and Minutes == * Training the Trainers checklist - Both * IRC quick reference link - Matt * Xchat tutorial - Ericm's request - Andy * Conference Call System rewrite - Matt * Tailored new staff to-do list - Add to New Staff task? - Both * Recorded new staff checklist - Maybe a google form - Matt * Review survey - individuals and trends * Mumble - Matt * Gobby - Andy * Tech lead feedback email * Break out Angus' email into to-do items - Andy * Mapping between Launchpad projects and Linaro teams - Both * Android information - Andy * Extend category tag usage * Waiting on Trainers - should we suggest people == Risks / Issues == * Risk - Unable to recruit trainers within member organizations - carry over from last week * Mitigation - Perform mentoring tasks from within this team * Mitigation - Break responsibilities into smaller portions and recruit multiple trainers * Information we have developed is not easy to find or accessible == Miscellaneous == * Holidays - Feb 21, 2011 - US President's day

13 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev