linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

Emdebian sprint - flash-kernel discussion

by Loïc Minier

Hi there flash-kernel is this place where we add support for a lot of weird boards of various architectures. "flash-kernel" because it used to just write a kernel to Flash memory, but that's not always true anymore. Because it's integrated in d-i and with initramfs-tools / linux packages, it is the easiest way to add support for one new board. But flash-kernel isn't in the happiest state right now, as new boards were added by copy-pasting the installation logic of other boards over and over. Also, Ubuntu added more and more boards and features to its flash-kernel package, and the delta is really big now (I will take part of the blame for allowing this to happen). In the light of this situation, and because I think Debian and derivatives will support more and more boards via flash-kernel in the future (for instance modern ARM boards in the armel/armhf ports), I'm interested in improving flash-kernel's code, architecture and scalability (in fact, I started working on it [1]). I'm at the Emdebian sprint in Cambridge this week and I wanted to pursue work on flash-kernel this week, but a lot of people here would like to have a discussion on this work, and other people seem to be interested in solving the same problems in flash-kernel. So in the interest of avoiding work duplication and in the hope to come up with a good roadmap and target architecture for flash-kernel, I'll be hosting a discussion on flash-kernel development tomorrow morning at 11am UK time. (Sorry for the late notice!) If you're interested in flash-kernel, if you have ideas, patches, etc. consider dialing in! Of course, email works too. I'll work on a wiki page summarizing tomorrow's discussion and the plans around flash-kernel. Dial-in details: Access code: 52386 86884# UK Local +44 207 630 2405 UK Freephone 0800 026 0166 US Local +1 781 761 9450 US Toll Free 1 866 352 2709 Brazil 0800 881 0038 Canada 1 866 352 2710 Finland 800 523 103 France 0 805 980 044 Germany 800 589 0993 New Zealand 800 452 290 Taiwan 0800 265 855 China (North) 10 800 152 1873 China (South) 10 800 852 1873 India 000 800 100 7944 Poland 800 331 1398 Anybody is welcome to dial-in. I'd welcome if you would notify me of your presence so that we can expect you on the call. We'll be using #emdebian as back-channel. Cheers, [1] branch at http://git.debian.org/?p=users/lool/d-i/flash-kernel.git * adds a testsuite * consolidates code into functions * moves board support data into a database (currently inline for convenience of testing, but will be split out in its own file) -- Loïc Minier

13 years, 10 months

Thumb-2 kernel tree

by markos.chandras＠gmail.com

Good evening, First post on this list so I apologize in advance if I post on the wrong list. I am desperately looking for a working thumb-2 kernel tree. I am currently using the dirty/arm/omap-thumb2+merged branch from git://git.linaro.org/people/dmart/linux-2.6-arm.git repo, since it is the only one that compiles for me. However, to my understanding, this is not a very 'safe' branch to use on daily basis. Is that true? Is there a more 'stable' git branch which I can compile as thumb-2 and use it for my projects. I keep searching online for kernel+thumb2 references and most of them point to this linaro git tree. Regards, -- Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

13 years, 10 months

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

by Amit Kucheria

Hi All, The minutes of the power management weekly call can be found at : https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2011-02-23 Highlights: Creation of a feature matrix to easily allow outsiders to tell what we've been upto (It is still being populated after testing with hwpacks) Regards, Amit

13 years, 10 months

[REMINDER] Weekly Release Meeting 2011-02-24

by Jamie Bennett

Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC today. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-02-24 and previous action items were: * JamieBennett to email LT to test s5pv310 * lool to ping Marex to enquire about support for Efika netbook support in uboot for this cycle * slangasek to file rt for syncing nano image to snapshots and stop headless syncing * slangasek to raise the issue with debian-policy on whether or not we need e2fsprogs as Essential If you have points to raise or bugs that need to be discussed please add them to the wiki page above. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager

13 years, 10 months

Re: cc'ing patches@linaro.org

by Dave Martin

On Tue, Feb 22, 2011 at 4:38 PM, Amit Kucheria <amit.kucheria(a)linaro.org> wrote: > Hi, > > We're required to cc patches(a)linaro.org for all patches that we send > upstream. bzr/launchpad users are already covered or will be shortly. > > For those using git-send-email to send patches (and you really should > be), it might make sense to use the following command so you don't > forget > > $ git config --global --add sendemail.bcc "patches(a)linaro.org" > > Check $HOME/.gitconfig to make sure you see "bcc = patches(a)linaro.org" > under the [sendemail] section. > WARNING - this will bcc patches(a)linaro.org on all patches from that > machine sent using git-send-email. > > If you want more control, and your linaro work happens in a single git > tree, you could do the following: > > $ cd <your linaro git tree> > $ git config --add sendemail.bcc "patches(a)linaro.org" > > Check <your linaro git tree>/.git/config for the bcc entry as above. > Now patches send from that tree will be bcc'ed to patches@linaro. > > /Amit > p.s. There is also a sendemail.cc instead of sendemail.bcc in case you > want to use that. > Do we need a policy on whether or not to use Bcc here? One argument for using Bcc is that it avoids replies from subscribers to the destination mailing lists from also being CC'd to patches(a)linaro.org. Can your analysis cope with patches(a)linaro.org receiving a whole thread, or do we need to be careful about this? Cheers ---Dave

13 years, 10 months

[PATCH] power: Fixup stack usage in vritual battery driver

by John Stultz

For some reason the virtual battery driver code allocates 4k on the stack. This is clearly broken, so keep the length smaller (256) and cleanup the string management code to use the bounds checking versions. CC: Akihiro MAEDA <sola.1980.a(a)gmail.com> CC: Masashi YOKOTA <yokota(a)pylone.jp> Signed-off-by: John Stultz <john.stultz(a)linaro.org> --- drivers/power/virtual_battery.c | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/power/virtual_battery.c b/drivers/power/virtual_battery.c index ed686ef..30c91b4 100644 --- a/drivers/power/virtual_battery.c +++ b/drivers/power/virtual_battery.c @@ -115,6 +115,7 @@ static struct power_supply power_supply_bat = { }; +#define MAX_KEYLENGTH 256 struct battery_property_map { int value; char const * key; @@ -162,16 +163,18 @@ static struct battery_property_map map_technology[] = { static int map_get_value(struct battery_property_map * map, const char * key, int def_val) { - char buf[4096]; + char buf[MAX_KEYLENGTH]; int cr; - strcpy(buf, key); - cr = strlen(buf) - 1; + strncpy(buf, key, MAX_KEYLENGTH); + buf[MAX_KEYLENGTH-1] = '\0'; + + cr = strnlen(buf, MAX_KEYLENGTH) - 1; if (buf[cr] == '\n') buf[cr] = '\0'; while (map->key) { - if (strcasecmp(map->key, buf) == 0) + if (strncasecmp(map->key, buf, MAX_KEYLENGTH) == 0) return map->value; map++; } -- 1.7.3.2.146.gca209

13 years, 10 months

[git pull] Basic device tree support for ARM

by Grant Likely

Hi Nicolas, Here's the branch implementing basic device tree support based on the linaro-2.6.38 tree. Should be good to go. g. The following changes since commit f60e8ccbfce6b40a112bddef5b4926b7416b4f92: ARM: fix build failure (2011-02-22 15:49:23 -0500) are available in the git repository at: git://git.secretlab.ca/git/linux-2.6 devicetree/arm-linaro-2.6.38 Grant Likely (5): arm/dt: Make __vet_atags also accept a dtb image arm/dt: consolidate atags setup into setup_machine_atags arm/dt: probe for platforms via the device tree arm/dt: Basic versatile devicetree support arm/dt: Basic tegra devicetree support Jeremy Kerr (1): arm/dt: Allow CONFIG_OF on ARM arch/arm/Kconfig | 7 ++ arch/arm/include/asm/mach/arch.h | 9 ++ arch/arm/include/asm/prom.h | 37 ++++++++ arch/arm/include/asm/setup.h | 5 + arch/arm/kernel/Makefile | 1 + arch/arm/kernel/devtree.c | 147 ++++++++++++++++++++++++++++++++ arch/arm/kernel/head-common.S | 24 ++++-- arch/arm/kernel/head.S | 8 +- arch/arm/kernel/setup.c | 90 ++++++++++++-------- arch/arm/mach-tegra/board-harmony.c | 6 ++ arch/arm/mach-versatile/versatile_ab.c | 6 ++ arch/arm/mach-versatile/versatile_pb.c | 6 ++ arch/arm/mm/init.c | 11 +++ 13 files changed, 312 insertions(+), 45 deletions(-) create mode 100644 arch/arm/include/asm/prom.h create mode 100644 arch/arm/kernel/devtree.c -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.

13 years, 10 months

[PATCH v2 0/2] ARM: IMX5: cpuidle driver

by yong.shen＠linaro.org

change log: 1. move code to arch/arm/mach-mx5/, since it is cpu-type specific 2. provide a interface for various board to register board-specific params.

13 years, 10 months

[NOTES] Android Platform Team meeting 2011-02-23

by Jamie Bennett

Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-02-23 = Actions Recorded = * kjnabe to contribute framebuffer support back to jstultz' git.linaro.org tree * kjnabe to contribute beagle defconfig to jstultz git.linaro.org tree * JamieBennett to prod people for framebuffer and defconfig changes to go to jstultz' tree * jserv-- and jeremychang to test John's tree for battery support and report back * JamieBennett to investigate certificates on android-build.linaro.org * jeremychang to confirm https://android-build.linaro.org/job/android-panda/ tarballs work and fix if necessary * patrikryd to confirm https://android-build.linaro.org/job/android-u8500href/ tarballs work and fix if necessary * jserv-- to confirm https://android-build.linaro.org/job/android-beagle/ tarballs work and fix if necessary * jserv-- jeremychang and patrikryd to improve their weekly report before JamieBennett submits a team report to linaro-dev tomorrow * asac to produce a better standing agenda for the meetings Regards, Jamie. -- Linaro Release Manager | Platform Project Manager

13 years, 10 months

[PATCH android/system/core] init: support mmc device mount (by partition)

by Jim Huang

init.rc usage example: mount vfat mmc@blk1p3 /mnt/sdcard2 --- init/builtins.c | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/init/builtins.c b/init/builtins.c index e0ccf9f..32d9d7f 100644 --- a/init/builtins.c +++ b/init/builtins.c @@ -356,6 +356,16 @@ int do_mount(int nargs, char **args) close(fd); ERROR("out of loopback devices"); return -1; + } else if (!strncmp(source, "mmc@blk", 7)) { + sprintf(tmp, "/dev/block/mmcblk%s", source + 7); + + if (wait) + wait_for_file(tmp, COMMAND_RETRY_TIMEOUT); + if (mount(tmp, target, system, flags, options) < 0) { + return -1; + } + + return 0; } else { if (wait) wait_for_file(source, COMMAND_RETRY_TIMEOUT); -- 1.7.2.3

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