linaro-dev September 2011

linaro-dev@lists.linaro.org

149 participants
200 discussions

linaro-image-tools_2011.08-1_amd64.changes REJECTED

by Debian FTP Masters

Reject Reasons: linaro-image-tools_2011.08-1.dsc refers to linaro-image-tools_2011.08.orig.tar.gz, but I can't find it in the queue or in the pool. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

13 years, 3 months

Processing of linaro-image-tools_2011.08-1_amd64.changes

by Debian FTP Masters

linaro-image-tools_2011.08-1_amd64.changes uploaded successfully to localhost along with the files: linaro-image-tools_2011.08-1.dsc linaro-image-tools_2011.08-1.debian.tar.gz linaro-image-tools_2011.08-1_all.deb python-linaro-image-tools_2011.08-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)

13 years, 3 months

[ACTIVITY] Android Platform Team 2011-09-12 to 2011-09-19

by Tony Mansson

Key Points for wider discussion =============================== * The 11.09 release and built and tested with the 11.09 toolchain. * OMAP 4460 build bringup started. Team Highlights =============================== * Busybox, powertop, libnl and ncurses gits moved in to Android/Gerrit. * LAVA integration scripts, reviews are ongoing. * Busybox source code has been integrated to Linaro Android platform for all boards. * Effort to integrate Igloo Android for Snowball started. * Audio enabling on Panda ongoing. Miscellaneous =============================== * Frans will be on vacation 2011-09-26 to 2011-10-07. * Bernhard will be moving, may have connectivity problems initially. * Vishal is travelling on 22nd and 23rd (VISA) * Abishek is travelling on 22nd and 23rd (VISA) Bugs fixed =============================== * #845793, #811657 #803634. Reminders =============================== * Release watch schedule: * 26th 0 - 8.5 UTC Botao 8 - 16.5 UTC Bero 16 - 0.5 UTC Mathieu * 27th 0 - 8.5 UTC Vishal 8 - 16.5 UTC Bero, Botao 16 - 0.5 UTC Zach * 28th 0 - 8.5 UTC Botao 8 - 16.5 UTC Patrik 16 - 0.5 UTC Zach

13 years, 3 months

[PATCH v3 0/3] mmc: rectify boot param option for fault injection

by Per Forlin

Akinobu Mita reported that the boot option for mmc fault injection is never compiled in due to a fauly "ifdef KERNEL" that is never set. A correct ifdef would be "ifndef MODULE". This patch set adds a module_param_cb() and thereby no ifndef MODULE is needed. Using a module_param makes it possible to pass default fault attributes for external modules too. This patch set is for 3.2 Change log: v2 - use module_param_cb() to set default fault attributes - fix spelling of documentation in patch #3 v3 - remove unused variable and return error if invalid boot param. Per Forlin (3): fault-inject: export setup_fault_attr() mmc: add module param to set fault injection attributes fault-injection: update documentation with the mmc module param Documentation/fault-injection/fault-injection.txt | 2 +- drivers/mmc/core/debugfs.c | 38 +++++++++++---------- lib/fault-inject.c | 3 +- 3 files changed, 23 insertions(+), 20 deletions(-) -- 1.7.4.1

13 years, 3 months

[PATCH 0/2] mmc: clarifications on host.post_req()

by Per Forlin

Fixes for 3.1. This patchset doesn't fix any bugs in 3.1 but it improves the documentation in order to prevent new bugs. Per Forlin (2): mmc: core: clarify how to use post_req in case of errors mmc: mmci: simplify err check in mmci_post_request drivers/mmc/core/core.c | 6 ++++++ drivers/mmc/host/mmci.c | 2 +- include/linux/mmc/host.h | 3 +++ 3 files changed, 10 insertions(+), 1 deletions(-) -- 1.7.4.1

13 years, 3 months

New roadmap home on the wiki

by Joey Stanford

Hi Gang, FYI Today I moved the draft Roadmap process that Kiko has been toiling over to a new and more official home: https://wiki.linaro.org/Process/Roadmap Joey

13 years, 3 months

IRC change: private #pm to freenode #linaro-pm

by Joey Stanford

Hi Gang, FYI Effective immediately #pm on the private IRC server is deprecated. Please move over to #linaro-pm on Freenode. We were using the private #pm to talk about operational items and potentially some confidential landing team items. For the last few months all of the discussion has not contained any material which contractually needs to remain private so in the interest of transparency I'm forcing the channel over to Freenode. As with all public channels, everyone is welcome to join and participate. Joey

13 years, 3 months

[PATCH] ARM: EXYNOS4: Add header file protection macros

by Sachin Kamat

This patch adds header file protection macros to prevent duplication. Signed-off-by: Sachin Kamat <sachin.kamat(a)linaro.org> --- arch/arm/mach-exynos4/include/mach/pm-core.h | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-exynos4/include/mach/pm-core.h b/arch/arm/mach-exynos4/include/mach/pm-core.h index 1df3b81..4c3406b 100644 --- a/arch/arm/mach-exynos4/include/mach/pm-core.h +++ b/arch/arm/mach-exynos4/include/mach/pm-core.h @@ -14,6 +14,10 @@ * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. */ + +#ifndef __ASM_ARCH_PM_CORE_H +#define __ASM_ARCH_PM_CORE_H __FILE__ + #include <mach/regs-pmu.h> static inline void s3c_pm_debug_init_uart(void) @@ -57,3 +61,5 @@ static inline void s3c_pm_saved_gpios(void) { /* nothing here yet */ } + +#endif /* __ASM_ARCH_PM_CORE_H */ -- 1.7.4.1

13 years, 3 months

[PATCH 0/2] pin controller subsystem v7

by Linus Walleij

From: Linus Walleij <linus.walleij(a)linaro.org> This is the sixth iteration of the controller subsystem, most changes are described in the individual patches, mainly we are now doing away with the patch to the AMBA bus to acquire pinmuxes, instead this is done from the U300 machine core. This way the impacts on the existing drivers and buses are kept to a minimum for the time being. Further I squashed the patch removing the old pinmux driver from the U300 machine into the patch adding the new driver, because it was not really possible to do a clean cut anyway. ChangeLog v6->v7: - Make it possible to have several map entries matching the same device, pin controller and function, but using a different group, and alter the semantics so that pinmux_get() will pick all matching map entries, and store the associated groups in a list. The list will then be iterated over at pinmux_enable()/pinmux_disable() and corresponding driver functions called for each defined group. Notice that you're only allowed to map multiple *groups* to the same { device, pin controller, function } triplet, attempts to map the same device to multiple pin controllers will for example fail. This is hopefully the crucial feature requested by Stephen Warren. - Add a pinmux hogging field to the pinmux mapping entries, and enable the pinmux core to hog pinmux map entries. This currently only works for pinmuxes without assigned devices as it looks now, but with device trees we can look up the corresponding struct device * entries when we register the pinmux driver, and have it hog each pinmux map in turn, for a simple approach to non-dynamic pin muxing. This addresses an issue from Grant Likely that the machine should take care of as much of the pinmux setup as possible, not the devices. By supplying a list of hogs, it can now instruct the core to take care of any static mappings. - Switch pinmux group retrieveal function to grab an array of strings representing the groups rather than an array of unsigned and rewrite accordingly. - Alter debugfs to show the grouplist handled by each pinmux. Also add a list of hogs. - Dynamically allocate a struct pinmux at pinmux_get() and free it at pinmux_put(), then add these to the global list of pinmuxes active as we go along. - Go over the list of pinmux maps at pinmux_get() time and repeatedly apply matches. - Retrieve applicable groups per function from the driver as a string array rather than a unsigned array, then lookup the enumerators. - Make the device to pinmux map a singleton - only allow the mapping table to be registered once and even tag the registration function with __init so it surely won't be abused. - Create a separate debugfs file to view the pinmux map at runtime. - Introduce a spin lock to the pin descriptor struct, lock it when modifying pin status entries. Reported by Stijn Devriendt. - Fix up the documentation after review from Stephen Warren. - Let the GPIO ranges give names as const char * instead of some fixed-length string. - add a function to unregister GPIO ranges to mirror the registration function. - Privatized the struct pinctrl_device and removed it from the <linux/pinctrl/pinctrl.h> API, the drivers do not need to know the members of this struct. It is now in the local header "core.h". - Rename the concept of "anonymous" mux maps to "system" muxes and add convenience macros and documentation. U300 driver: - Adjust the driver to return the group list as an array of strings instead of a unsigned * array. - Add support for the EMIF0 and EMIF1 pin groups. - Acquire all muxmaps using pinmux hogs from the core using a subsystem_initcall(). This way we need not change any drivers or buses. We have the correct struct device * pointers anyway so why not do it from there, and it illustrates pretty well what the pinmux core will be able to do once it can access the device tree. - Use new convenience macros for system mappings. - Unregister the GPIO range at removal. Linus Walleij (2): drivers: create a pin control subsystem v7 pinmux: add a driver for the U300 pinmux Documentation/ABI/testing/sysfs-class-pinmux | 11 + Documentation/pinctrl.txt | 951 +++++++++++++++++++++ MAINTAINERS | 5 + arch/arm/mach-u300/Kconfig | 2 + arch/arm/mach-u300/Makefile | 2 +- arch/arm/mach-u300/core.c | 84 ++- arch/arm/mach-u300/include/mach/syscon.h | 136 --- arch/arm/mach-u300/mmc.c | 16 - arch/arm/mach-u300/padmux.c | 367 -------- arch/arm/mach-u300/padmux.h | 39 - arch/arm/mach-u300/spi.c | 20 - drivers/Kconfig | 4 + drivers/Makefile | 2 + drivers/pinctrl/Kconfig | 36 + drivers/pinctrl/Makefile | 7 + drivers/pinctrl/core.c | 632 ++++++++++++++ drivers/pinctrl/core.h | 73 ++ drivers/pinctrl/pinmux-u300.c | 1008 ++++++++++++++++++++++ drivers/pinctrl/pinmux-u300.h | 141 +++ drivers/pinctrl/pinmux.c | 1178 ++++++++++++++++++++++++++ drivers/pinctrl/pinmux.h | 47 + include/linux/pinctrl/machine.h | 107 +++ include/linux/pinctrl/pinctrl.h | 133 +++ include/linux/pinctrl/pinmux.h | 124 +++ 24 files changed, 4544 insertions(+), 581 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-pinmux create mode 100644 Documentation/pinctrl.txt delete mode 100644 arch/arm/mach-u300/padmux.c delete mode 100644 arch/arm/mach-u300/padmux.h create mode 100644 drivers/pinctrl/Kconfig create mode 100644 drivers/pinctrl/Makefile create mode 100644 drivers/pinctrl/core.c create mode 100644 drivers/pinctrl/core.h create mode 100644 drivers/pinctrl/pinmux-u300.c create mode 100644 drivers/pinctrl/pinmux-u300.h create mode 100644 drivers/pinctrl/pinmux.c create mode 100644 drivers/pinctrl/pinmux.h create mode 100644 include/linux/pinctrl/machine.h create mode 100644 include/linux/pinctrl/pinctrl.h create mode 100644 include/linux/pinctrl/pinmux.h -- 1.7.3.2

13 years, 3 months

Re: Hi guys, could you help me to test busybox on your board?

by Botao Sun

Hi Yongqin, Just test it can be run or not. Run some basic commands, such like busybox top, busybox vi, busybox ps | busybox grep XXX..., something like that. I don't have test cases at my side. And this is the first time I integrated the entire busybox source code to our Android platform. I would like to be ensure it works on every board first. Thanks. On Wed, Sep 21, 2011 at 5:33 PM, Fathi Boudra <fathi.boudra(a)linaro.org>wrote: > Foward to Botao as Yongqin replied to me only. > > ---------- Forwarded message ---------- > From: yong qin <yongqin.liu(a)linaro.org> > Date: 21 September 2011 12:29 > Subject: Re: Hi guys, could you help me to test busybox on your board? > To: Fathi Boudra <fathi.boudra(a)linaro.org> > > > Hi, Botao > What test would you like to do? > Or do you have any test cases or test programs? > Thanks > Yongqin Liu > On 21 September 2011 16:44, Fathi Boudra <fathi.boudra(a)linaro.org> wrote: > > > > ---------- Forwarded message ---------- > > From: Botao Sun <botao.sun(a)linaro.org> > > Date: 21 September 2011 11:42 > > Subject: Hi guys, could you help me to test busybox on your board? > > > > Hi, > > > > The busybox source code has been integrated to Linaro Android platform > > for all boards, so I'd like to ask help from you to test it. I have > > tested it on my Origen board, and it works well. > > > > Thank you! > > > > > > BR > > Botao Sun > > > > _______________________________________________ > > linaro-dev mailing list > > linaro-dev(a)lists.linaro.org > > http://lists.linaro.org/mailman/listinfo/linaro-dev > > > > > -- > Fathi Boudra > Linaro Release Manager | Validation Project Manager > Linaro.org | Open source software for ARM SoCs >

13 years, 3 months

← Newer
1
...
5
6
7
8
9
10
11
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev September 2011