linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[Linaro-dev] Goals of upcoming Linaro Engineering Summit

by Yuri Bushmelev

Hello! I have some questions regarding upcoming Linaro event. Can anyone explain goals of upcoming summit (19-23 July)? Wiki page[1] contains no goals ATM. Will there be a possibility and any point/sense for 'external' projects (e.g. kexecboot) and people to participate in summit? Is there any possibility to have some sponsor help with travel expenses to come to summit? [1] http://wiki.linaro.org/Events/2010-07-PlatformSprint -- Yuri Bushmelev

14 years, 6 months

[Linaro-dev] git.linaro.org repos structure

by Loïc Minier

Hi folks I'd like to discuss structure of the repositories we create on git.linaro.org for interaction with upstreams using git (e.g. kernel and u-boot). I think we should have two layouts: - /$person/$project/$topic repos for personal repositories, - /$project/$topic repos for canonical repositories, such as team repos For instance, /jcrigby/u-boot/for-upstream.git or /linaro-kernel/linux/arm-next.git. What do you folks think? Thanks! -- Loïc Minier

14 years, 6 months

[Linaro-dev] gcc-linaro bzr branches up

by Loïc Minier

Hi folks I created a gcc-linaro project and a ~gcc-linaro-dev team (Julian, Andrew, and myself right now). I grabbed Vincent's recent imports of FSF gcc 4.4 and 4.5 branches (lp:~vila/gcc/4.4 and lp:~vila/gcc/4.5) and pushed the latest tagged release in each [1]: bzr push -r tag:gcc_4_4_4_release lp:~gcc-linaro-dev/gcc-linaro/4.4 bzr push -r tag:gcc_4_5_0_release lp:~gcc-linaro-dev/gcc-linaro/4.5 Performance of bzr is a bit inconvenient, I think I'll check with the bazaar team to see if there's something we can tune on our side or something they could fix on their side to help this. I've setup gcc-linaro 4.4 and 4.5 series too so that one can checkout lp:gcc-linaro/4.4 and lp:gcc-linaro/4.5. Cheers, [1] and then I discovered I didn't even need the local copies: bzr branch -r tag:gcc_4_4_4_release lp:~vila/gcc/4.4 \ lp:~gcc-linaro-dev/gcc-linaro/4.4 but that doesn't help much since stuff still transits client-side -- Loïc Minier

14 years, 6 months

Re: [Linaro-dev] git.linaro.org repos structure

by Rodrigo Belem

I would like see git.linaro.org using gitorious. Em 11/06/2010 06:23, "Loïc Minier" <loic.minier(a)linaro.org>escreveu: Hi folks I'd like to discuss structure of the repositories we create on git.linaro.org for interaction with upstreams using git (e.g. kernel and u-boot). I think we should have two layouts: - /$person/$project/$topic repos for personal repositories, - /$project/$topic repos for canonical repositories, such as team repos For instance, /jcrigby/u-boot/for-upstream.git or /linaro-kernel/linux/arm-next.git. What do you folks think? Thanks! -- Loïc Minier _______________________________________________ Linaro-dev mailing list Linaro-dev(a)lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev

14 years, 6 months

[Linaro-dev] What about the middleware?

by Shaz

Dear all, No one has yet discussed the middleware. Am I on the wrong list? I have been working on a number of middlewares and dbus is the defacto standard for all. I see a lot of work going on the FreeSmartPhone.Org (FSO) [1] standard's implementation. It is being consumed by Angstrom, debian like and other embedded OSes. FSO is based on the specifications of freedesktop.org [2] therefore I can't see a better middleware technology. Are there any better alternatives? [1] http://www.freesmartphone.org/ [2] http://wiki.freesmartphone.org/index.php/Main_Page -- Shaz

14 years, 6 months

[Linaro-dev] linaro build system (was Re: Availability of hardware for Linaro development?)

by JD Zheng

> > > > Would it not make more sense to simply standardize on a readily > > available toolchain such as CodeSourcery's Lite ARM toolchain? > > Excellent suggestion! :-) > > Hello, I just subscribed to this maillist and am very interested in build system setup for linaro as a long time embedded developer (half of my time on UI system and half on BSP/distribution) and of course most on ARM :-) I certainly suggest CodeSourcery toolchain too! But build system is more than just gcc, binutil and libc and in distributions, it is often bound to package system, and tools to create a clean chroot to install dependencies automatically. Some tools like scratchbox basically "pretend" the cross compiling to be native to avoid/minimize special patches for cross compiling (we can't guarantee code from upstream are always cross compiling friendly). OBS(Opensuse Build System) does native compiling through QEMU and it also can be used similar to scratchbox, i.e., native compiling using cross gcc, native(x86)bash/perl/python to speed up the build. I think Debian/Ubuntu and most other dist are similar to OBS too, while traditional embedded linux doesn't have pkg system and using cross compiling directly. So my question is what will be the default build system, which, I guess, is part of deliveries? Since linaro is not a distribution, will it be dist-agnostic? (Don't get me wrong as I am a Debian/Ubuntu fan :-) ). Thanks. Jiandong Zheng

14 years, 6 months

[Linaro-dev] Introducing kexecboot software

by Yuri Bushmelev

Hello! I wish to introduce kexecboot software here. It would be great to see kexecboot in list of Linaro supported projects. Feel free to contact me about this software by email or on irc.freenode.net, #kexecboot channel. My nickname is Jay7. ---------------- Kexecboot is a C program able to scan the partitions on available devices, offering a graphical framebuffer menu and allowing user to select from which one to boot. Specifically, kexecboot creates the command line for kexec. Typically kexecboot resides together with kexec in a small initramfs, embedded in a custom-tailored kernel compiled with support for initramfs and kexec system call. Both binaries are built static, linked against klibc to optimize size. Flashed on NAND and launched as first kernel by the original bootloader, this solution gives following advantages: * multi machine support: we build for many architectures using OpenEmbedded (tested on arm and x86/x86_64) * zImage and uImage support * easy customization: just add machine-specific workarounds (see Zaurus raw read of bootparams from NAND) * small size: complete linux-kexecboot_2.6.x image (initramfs + kernel) is about 1Mb (less with lzma patches) * easy boot choice: boot from SD/CF/NAND/... even if bootloader doesn't support it * multiple fs detection: we support many filesystems e.g. ext2/3/4, jffs2, reiserfs, vfat and more (ubifs is work in progress) * kernel upgrade: no need to flash the device (kernel is in /boot of removable media) * rapid testing: different distributions can live in separate partitions on the same device Thus, kexecboot is an interesting solution for embedded linux distributions, which can just rely on kexecboot whithout having to consider what the real bootloader can and cannot do. About customization, initially the program has been developed for Sharp Zaurus PDA (armv5te). For the machines of that family there is specific code reading bootparams directly from NAND, circumventing the obsolete bootloader which is incompatible with modern 2.6.x kernels. ---------------- We are sponsored by CELF in this year to do following work: 1.Write user's and developer's guides. 2.Extend architecture and filesystems support. MIPS arch support and UBIFS support will be added. 3.Improve debugging ability. We should allow users to have ability to look for debugging information without special hardware (serial cable e.g.). 4.Implement text-mode UI. We have already patches against one of old releases. This can be used later to use kexecboot UI over serial line or telnet/ssh connection. 5.Improve GUI. Make GUI more clean and eye-candy (fonts and icons). 6.Add ability to use multiple kernels on same partition. Current implementation allows only one kernel per partition. List of accessible hardware: - Sharp Zaurus'es: C860, C1000, C3200, SL-5500, SL-6000; - TouchBook (waiting for order, donated by CELF for this device support work). - Ben NanoNote (waiting for delivery, donated by CELF for MIPS support work); Links: * Current project home (down at this moment, we are looking for hosting): http://projects.linuxtogo.org/projects/kexecboot * Project git tree: http://git.linuxtogo.org/?p=groups/kexecboot/kexecboot.git * OpenEmbedded recipes: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/kexecboot -- Yuri Bushmelev

14 years, 6 months

[Linaro-dev] Test

by David Rusling

All, Please ignore this - I replied to an email this morning but didn't see it on the mailing list, just checking... Dave CTO, Linaro

14 years, 6 months

[Linaro-dev] Availability of hardware for Linaro development?

by Joel Crisp

Hi all Given the intention of Linaro seems to be improved Linux support for new and upcoming hardware, how would an individual dev who might be wanting to contribute acquire suitable hardware? Is there any hardware being targeted which is currently on the market (e.g. BeagleBoard type systems)? Or are emulators the intended development platform? I have previous experience in embedded systems work and was the original author of the SPCA50x driver for Linux USB webcams. I have also worked on vxWorks ports and embedded JVM technology but I currently have a full time job I'm not planning on leaving (Greencard application) and would have to be a hobbyist contributor - it isn't clear if the Linaro project has scope for such due to the hardware issue. This I see as the main differentiation between the Ubuntu development and Linaro. Thoughts? Thanks Joel -- The cyder is strong in this one Lord!

14 years, 6 months

Re: [Linaro-dev] Introducing kexecboot software

by Robert Schwebel

On Fri, Jun 04, 2010 at 02:47:35PM +0400, Yuri Bushmelev wrote: > > What's the checkout address of the git tree? Can you update the gitweb > > to contain that information? > > Ah, sorry. You can checkout it by following command: > git clone git://git.linuxtogo.org/home/groups/kexecboot/kexecboot.git > > Not sure about gitweb. I'm not familiar with it and seems it's property of > LinuxToGo. Hmm, I think all you have to do is adding something like this to /etc/gitweb.conf: @git_base_url_list = ( 'git://git.pengutronix.de/git', 'http://git.pengutronix.de/git', '(developers only) ssh://git.pengutronix.de/git' ); Replace this by your own entries ;) -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |

14 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev