linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

Fwd: [lca-announce] linux.conf.au 2013: Call For Proposals (closes July 6)

by Deepak Saxena

FYI... ---------- Forwarded message ---------- From: linux.conf.au Announcements <lca-announce(a)lists.linux.org.au> Date: 7 June 2012 07:50 Subject: [lca-announce] linux.conf.au 2013: Call For Proposals (closes July 6) To: lca-announce(a)lists.linux.org.au === linux.conf.au Call For Proposals === We are pleased to announce that the Call for Proposals for linux.conf.au 2013 is now open! The conference will showcase the best of open source and community-driven software and hardware. It will be held in Canberra at the Australian National University from Monday 28 January to Saturday 2 February, 2013, and provides a great opportunity for open source developers, users, hackers, and makers to share their ideas and further improve their projects. === Important Dates === * Call for proposals opens: 1 June 2012 * Call for proposals closes: 6 July 2012 * Email notifications from papers committee: 28 August 2012 * Early Bird registrations open: 1 October 2012 * Conference dates: Monday 28 January to Saturday 2 February 2013 === Information on Proposals === The linux.conf.au 2013 papers committee is looking for a broad range of proposals, and will consider submissions on anything from programming and software, to desktop, userspace, community, government, and education. There is only one rule: _Your proposal must be related to open source_ This year, the papers committee is going to be focused on deep technical content, and things we think are going to really matter in the future -- that might range from freedom and privacy to open source cloud systems or to energy efficient server farms of the future. However, the conference is to a large extent what the speakers make it -- if we receive many excellent submissions on a topic, then it’s sure to be represented at the conference. Here’s a few ideas to get you started: * Kernel and core systems: file systems, embedded devices * Networking: peer to peer networking, or tuning a TCP/IP stack * Desktop: office and productivity applications, peripherals, support * Mobile: kernel, applications, programming, challenges * Servers: clusters and supercomputers, databases and cloud computing * Embedded systems: constraints in storage/memory, real-time aspects, open hardware * Virtualisation: benefits, challenges, management, kernel and application support * Systems administration: maintaining large numbers of machines, disaster recovery * Security: application security, network security, cryptography, malware, viruses * Programming: programming languages, software engineering practices, testing, continuous integration/deployment, different development methodologies * Modern web technologies: Open source web browsers, HTML5, CSS3, JavaScript, web apps, accessibility * Audio and video: video editing, VoIP, WebRTC, video player development * Free software and free culture: licensing and Free and Open approaches outside software * Free software use: home, IT, education, manufacturing, research, government applications LCA is known for presentations and tutorials that are strongly technical in nature, but proposals for presentations on other aspects of free software and open culture, such as educational and cultural applications of open source, are welcome. === Code of Conduct === linux.conf.au welcomes first-time and seasoned speakers from all free and open communities - people of all ages, genders, nationalities, ethnicities, backgrounds, religions, abilities, and walks of life. We respect and encourage diversity at our conference. By agreeing to present at or attend the conference, you are agreeing to abide by the terms and conditions (http://lca2013.linux.org.au/cor/terms_and_conditions). We expect all speakers and delegates to have read and understood our Code of Conduct (http://lca2013.linux.org.au/cor/code_of_conduct). === Format === This year, there are three different ways that you can present your content: * Presentations * Tutorials * Miniconferences _Presentations_ Presentations are 40 minute slots that are generally presented in lecture format. These form the bulk of the available conference slots. _Tutorials_ Tutorials are 90 minutes that are generally presented in a classroom format. They should be interactive or hands-on in nature. Tutorials are expected to have a specific learning outcome for attendees. _Miniconferences_ Miniconfs are day-long sessions on a specific topic. A separate CFP process will be used to propose and select miniconfs, and will be announced publicly soon. For more information on miniconfs, see: http://lca2013.linux.org.au/miniconf-cfp === Speaker Information === In recognition of the value that speakers bring to our conference, once a proposal is accepted a speaker is entitled to: * Free registration, which holds all of the benefits of a Professional Delegate Ticket * Exclusive tickets to the Speakers' Dinner for the speaker and their immediate family * One free family ticket to the Partners' Programme If your proposal includes more than one speaker, these additional speakers are not entitled to free registration or to any extra benefits. linux.conf.au does not and will not pay speakers to present at the conference. linux.conf.au is able to provide limited financial assistance for some speakers, for instance, where the cost of flights or accommodation might prohibit a speaker from attending. Please note, however, that there is a limited budget for travel assistance and that asking for assistance could affect your chances of acceptance. === Recording and Licensing === To increase the number of people that can view your presentation, linux.conf.au might record your talk and make it publicly available after the event. When submitting your proposal you will be asked to release materials relating to your presentation under a Creative Commons ShareAlike License. Additionally, if you are discussing software in your presentation, you must ensure the software has an appropriate open licence. For more information, see: http://lca2013.linux.org.au/cfp === About Linux Australia === Linux Australia is the peak body for open source communities around Australia, and as such represents approximately 3500 Free and Open Source users and developers. Linux Australia supports the organisation of this international Free Software conference in a different Australasian city each year. For more information about Linux Australia see: http://www.linux.org.au/ === Papers Enquiries === linux.conf.au 2013 Papers Committee Email: papers-chair at lca2013.linux.org.au _______________________________________________ lca-announce mailing list lca-announce(a)lists.linux.org.au http://lists.linux.org.au/listinfo/lca-announce

13 years, 2 months

[PATCH 0/11] Merge ramoops and persistent_ram, generic pstore RAM backend

by Anton Vorontsov

Hi all, There are currently two competing debug facilities to store kernel messages in a persistent storage: a generic pstore and Google's persistent_ram. Not so long ago (https://lkml.org/lkml/2012/3/8/252), it was decided that we should fix this situation. Recently ramoops has switched to pstore, which basically means that it became a RAM backend for the pstore framework. persistent_ram+ram_console and ramoops+pstore have almost the same features, except: 1. Ramoops doesn't support ECC. Having ECC is useful when a hardware reset was used to bring the machine back to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat corrupt, but usually it is restorable. 2. Pstore doesn't support logging kernel messages in run-time, it only dumps dmesg when kernel oopses/panics. This makes pstore useless for debugging hangs caused by HW issues or improper use of HW (e.g. weird device inserted -> driver tried to write a reserved bits -> SoC hanged. In that case we don't get any messages in the pstore. These patches solve the first issue, plus move things to their proper places. Patches that will fix the second issue are pending. Thanks, --- drivers/char/Kconfig | 9 - drivers/char/Makefile | 1 - drivers/char/ramoops.c | 362 -------------------- drivers/staging/android/Kconfig | 10 +- drivers/staging/android/persistent_ram.c | 473 -------------------------- drivers/staging/android/persistent_ram.h | 78 ----- drivers/staging/android/ram_console.c | 2 +- fs/pstore/Kconfig | 12 + fs/pstore/Makefile | 1 + fs/pstore/ram.c | 384 ++++++++++++++++++++++ fs/pstore/ram_core.c | 530 ++++++++++++++++++++++++++++++ include/linux/pstore_ram.h | 99 ++++++ include/linux/ramoops.h | 17 - 13 files changed, 1028 insertions(+), 950 deletions(-) -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 2 months

[ACTIVITY] (Anton Vorontsov) 2012-05-21 - 2012-06-01

by Anton Vorontsov

== Highlights == * Sent v5 of pstore/console patch set, so far it didn't receive any objections. Perhaps need to ping Greg, as the merge window is now closed; * Finished and sent out pstore/ftrace support; it got a preliminary thumbs up from Steven. Will need to merge the support to the generic function tracer, turning persistent storage into a flag. * Discussed various approaches to make continuous console logging in pstore. And as a part of it tried to make linux_banner printing somewhat more consistent. But folks did not like it, so in the end we'll have just one console log buffer, as it was with ram_console; * Restarted work on vmevents, but got unflattering comments from KOSAKI, plus Minchan started to doubt about the notifiers in general. There is some blowing hot and cold started again. == Plans == * Repost pstore/ftrace support with Steven Rostedt comments fixed. * Move pstore registration earlier, so that we can record early oopses. Suggested by Colin Cross. * Make pstore ecc settings configurable, i.e. address Arve Hjønnevåg's "nice to have" comment on pstore; * I plan to finish all the major pstore items this week, and thus will have to pick a new task; * See how vmevents discussion turns out. -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 2 months

omap2plus kernel CI hwpacks fails to boot

by Deepti Kalakeri

Hello, Its been close to a month now that the kernel CI hwpacks built on ci.linaro.org with default omap2plus defconfigs (available in the linux-arm-soc, linux-next, linux-linaro, linux) are failing to boot on the boards. Here is an example hwpack built using the linux-linaro tree with omap2plus defconfig on ci.linaro.org which is failing to boot, in case you want to try to test it. http://snapshots.linaro.org/kernel-h wpack/linux-linaro-tracking/linux-linaro-tracking_panda-omap2plus/hwpack_linaro-lt-panda_20120509-0641_b64_armel_supported.tar.gz<http://snapshots.linaro.org/kernel-hwpack/linux-linaro-tracking/linux-linar…> I was able to fix the above boot problem of the CI kernel hwpacks built with omap2plus defconfig by adding the options similar to the ones available in (linux-linaro tree) default omap4 defconfig on top of the default omap2plus defconfig options. Here is the list of the config options which I added http://paste.ubuntu.com/977642/ along with the omap2plus defconfig to make it work. Can someone help me with the basic omap2plus defconfig options that will be required to boot the hwpack on the board. Does anyone care of kernel builds for linux-arm-soc, linux-next, linux-linaro, linux tree using omap2plus defconfigs ? Apart from this, there are build failures with the linux-next trees failing since last 20 days. https://ci.linaro.org/jenkins/view/Linux%20%28next%29/ lists such failing build jobs. For example the following job fails https://ci.linaro.org/jenkins/view/Linux%20%28next%29/job/linux-next_panda-… . Can someone look at these linux-next build failures ? -- Thanks and Regards, Deepti Infrastructure Team Member, 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, 3 months

Still travelling...

by Deepak Saxena

This is in the leaves calendar but thought I'd let folks know that I'm off Monday (which is mostly over for me) and tomorrow while I explore Beijing and then off to Linuxcon Japan tue-friday. I'm taking a few days off and will be back home next Tuesday evening PST, back to work sometime on Wed. I'll be checking email the whole time between now and next wed. If you need me for something urgent, email me and then txt me (+15039578596) so I get to my email ASAP. Thanks, ~Deepak

13 years, 3 months

about unuseful information in each message

by Wang wenbing

Hi sir/mrs, why there is unuseful information like attachment in every message?It will disturb us to read whole message. Thanks

13 years, 3 months

[ACTIVITY] (John Stultz) May 29 - June 1

by John Stultz

=== Highlights === * Reworked the fallocate volatile code per feedback and sent out two iterations. * Remotely presented Android Upstreaming status at Connect. * Fixed a leapsecond bug that was reported and sent it in for 3.5 * Spent some time getting my timekeeping queue for 3.6 in order * Sent out the Android Upstreaming biweekly team email === Plans === * Continue fallocate volatile discussion and code iterations. * Hopefully get a fix for the panda HDMI issue that's blocking my testing of upstreamed Android work that landed in 3.5 * Dig in on some of the items LinusW suggested I look at during the Connect session. === Issues === NA

13 years, 3 months

Send linaro-kernel mailing list submissions

by Wang wenbing

Send linaro-kernel mailing list submissions

13 years, 3 months

[PATCH v3 0/9] Fixes for common mistakes w/ for_each_process and task->mm

by Anton Vorontsov

Hi all, This is another resend of several task->mm fixes, the bugs I found during LMK code audit. Architectures were traverse the tasklist in an unsafe manner, plus there are a few cases of unsafe access to task->mm in general. There were no objections on the previous resend, and the final words were somewhere along "the patches are fine" line. In v3: - Dropped a controversal 'Make find_lock_task_mm() sparse-aware' patch; - Reword arm and sh commit messages, per Oleg Nesterov's suggestions; - Added an optimization trick in clear_tasks_mm_cpumask(): take only the rcu read lock, no need for the whole tasklist_lock. Suggested by Peter Zijlstra. In v2: - introduced a small helper in cpu.c: most arches duplicate the same [buggy] code snippet, so it's better to fix it and move the logic into a common function. Thanks, -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 3 months

[kernel boot] - Failed to boot the kernel building by myself. Could you please help on it?

by Tim Jiang

Hi Experts, I am a newbie in Linaro development. The kernel built by myself can't boot up. Could you please help on it? Thanks a lot in advance. # Proglem: There was no any response after following logs: Starting kernel ... Uncompressing Linux... done, booting the kernel. *Followings are details:* # My setting: Development board - i.Mx53 QSB Host PC - Ubuntu 10.04 x64 GCC for build linaro kernel - version is 4.6.2 Create a micro-SD card with linaro Nano 12.02. I used, mx53loco-nano.img.gz<http://releases.linaro.org/12.02/ubuntu/oneiric-images/nano/mx53loco-nano.i…>, to create the disc and it can work well and I can run my program in this Nano linaro. # What I want: I wanted to build a kernel to replace the kernel installed with linaro Naro 12.02. # My steps: 1) Download the kernel source code: I downloaded the code under the linaro 12.02 download page( http://www.linaro.org/downloads/1202), linux-linaro-lt-freescale<http://launchpad.net/linaro-landing-team-freescale>(supplied by landing team). 2) Build the kernel: I copied the configuration file from micor-SD card, /media/rootfs/config-3.1.0-1002-linaro-It-mx5, and rename it to .config. $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules 3) Install kernel to micro-SD card: $ cp arch/arm/boot/uImage /media/boot $ make ARCH=arm INSTALL_MOD_PATH=/media/rootfs modules_install $ sudo umount /media/* 4) Boot with my own kernel: Install the micro-SD card and press power button. # Result: There was no any response after following logs: Starting kernel ... Uncompressing Linux... done, booting the kernel. I have tried several other version kernel code and even update u-boot, but failed to fix it. Could somebody show me suggestion on it? Best Regards, Tim

13 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel