linaro-dev March 2013

linaro-dev@lists.linaro.org

51 participants
53 discussions

arm64 Debian/Ubuntu port image available

by Wookey

State of the Debian/Ubuntu arm64 port ===================================== *** Arm64 lives! *** Executive summary ----------------- * There is now a bootable (raring) image to download and run * Everything has been rebuilt against glibc 2.17 so it works * A bit more work is needed to make the rootfs useable as a native buildd * Multiarch crossbuilding and the build-profile mechanism is mature enough to cross-build a port from scratch (this is a big deal IMHO) * All packages, sources and tools are in a public repo and this work should be reproducible. * This image is fully multiarched so co-installing armhf for a 64/32 mix should work nicely, as should multiarch crossbuilding to legacy x86 architectures. :-) (but I haven't tried that yet...) * Linaro wants 'the distros' to take this work forward from here so people interested in Debian and Ubuntu on 64-bit arm hardware need to step up and help out. Bootable images --------------- A milestone was reached this week: Enough packages were built for arm64 to debootstrap an image which booted to a prompt! After a bit of fettling (and switching to multistrap) I got an image with all the packages configured which boots with upstart to a login prompt (I admit, I did get quite excited about this, as it represents the coming together of nearly 3 years work on multiarch, crossbuilding, bootstrapping, cyclic dependencies and arm64 :-) The images are available for download: http://wiki.debian.org/Arm64Port#Pre-built_Rootfs And there are destructions there for making your own. All these packages were cross-built on raring, untangling cyclic dependencies with build profiles (see wiki.debian.org/DebianBootstrap for how that works), making this the first (non x86) self-bootstrapped debian port ever (so far as I know). All (?) previous ports have been done using something else like OpenEmbedded (armel, armhf), RedHat/HardHat (arm, alpha, mips), something IBMy (s390) to get an initial linux rootfs on which debian packages are built. The new bootstrap process is (almost) just a list of sbuild commands. In practice there are still a few rough edges around cross- build-dependencies so of the 140 packages needed for the bootstrap, 9 had to be built manually with 'dpkg-buildpackage -aarm64 -d' (to skip build-dep checks) instead of 'sbuild --host arm64 <package>'. The current bootstrap packageset status is here: http://people.linaro.org/~wookey/buildd/raring-arm64/status-bootstrap.html There is no armv8 (arm64/aarch64) hardware available yet, so this image can currently only be run in a model. ARM provide a free-beer prorietary 'Foundation model' so we do have someting to test with. It's sluggish but perfectly useable. Booting the images takes a couple of minutes on my fairly average machine. The images are using the Linaro OE release kernels which seem to work fine for this purpose. Thanks to Marcin for modified bootloader lines in .axf files. Image status ------------ I was impressed that things basically 'just worked' on first boot. There is of course plenty of breakage, I'm sure, and I haven't looked very hard yet, but it's a lot better than I expected after months of just building stuff and testing nothing. (Things that are poorly: nano can't parse it's own syntax-coluring files for example, and multiarch perl has the wrong @INC path compiled in; I'm sure there is more). Consider this alpha-grade until it's been used a bit more. Things that are not yet built which would make the images a lot more useful are apt and a dhcp client. apt needs gnupg needs curl needs nss. The nss cross-build needs fixing to unbung that. A debian chroot without apt turns out to be disappointing quite quickly :-) Expect an updated image with more packages very soon. Multiarch crossbuilding ----------------------- It's really nice to have building and crossbuilding using exactly the same mechanisms and tools, with all files having one canonical location, and dependency mechanisms that are reliable. The more I've used this, the more I've been impressed by it. There is still work to do to expand the set of cross-buildable stuff, but it's a solid base to work from. Getting this port working has been 'interesting' because it's attempting 4 new things all at once: multiarch (file layouts and dependencies), crossbuilding (tools and packaging support in a distro that historically was always natively built), arm64 (aarch64) support in packages that need it, and build-profiles to linearise the build-order. The arm64 part of this is a relatively small part as the heavy lifting has been done upstream (gcc, (e)glibc, binutils, kernel, libffi, autotools and a lot of minor fixes in various packages). Thanks are due to doko (Matthias Klose) for sterling work getting all that integrated into the debian and ubuntu toolchain packages, and infinity (Adam Conrad) for merging various eglibc branches. There were also hordes of very boring patches of the form 'update config.sub and guess before building'. Most of the work has been in making things cross-build (exactly the same fixes needed for armel/hf too so I've had plenty of help there from canonical types who want cross-building for arm to work nicely), and particular thinks to Neil Williams for taking on the perl cross-build challenge and creating the debian-perl-cross package to manage the cross-configury, whilst also working with upstream to make the whole thing a bit less 1996. Multiarchifying has been going on nicely in libraries and -dev packages, but things like perl and python needed significant work, along with a lot of boring bugs saying 'mark this package MA: foreign' and 'build-dep on python:any or perl-base:any'. Thanks are due to doko for the python multiarching and Niko Tyni for the perl multiarchification. Getting all 3 'aspects' of multiarch perl, cross-built perl and arm64 perl config to work at the same time was quite hard work, and there are still bugs there. Wider usage of multiarched perl would no doubt sort this out reasonably quickly. I started a wiki page to track the status of multiarched cross-buildable perl: http://wiki.debian.org/Multiarch/Perl . Help would be welcome. The build-profile work is described on the http://wiki.debian.org/DebianBootstrap page. Progress has been greatly helped by GSOC projects last year, with good work on the tools (crossbuild-essential packages, build-profile support) from P.J McDermott and an impressive contribution from Johannes Schauer on dependency analysis tools around libdose, and apt build-profile support. All of this apart from multiarch perl, crossbuildable perl and build-profile stuff (and a few pending patches) is already in raring. Building stuff yourself ----------------------- Setting up an arm64 build environment is very simple. Use sbuild-createchroot or mk-sbuild and point at the bootstrap repo, with a bit of config and some updated tools packages from the repo (amd64 only supplied). Details are given on https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/arm64bootstrap Once you've created a tarball chroot builds are simply done with sbuild -c quantal-amd64-sbuild -d quantal --host=arm64 <package.dsc> or sbuild -c quantal-amd64-sbuild -d quantal --host=arm64 <package>_<version> (I'd love it if sbuild got smart enough to work out the version itself when given a distro - Roger says he's working on it) To deal with the chore of 'find version, run sbuild, sign result, upload to repo, import to repo, deal with reprepro bitching if you re-upload the same version of something' for every package build, I wrote 'dimstrap' which is a simple-minded tool to wrap that up and either do one-off builds or run through a list. It is part of the xbuilder package here: https://launchpad.net/~linaro-foundations/+archive/cross-build-tools/ It also includes the logfile-parsing script ('generate html') which generates the nice status pages: http://people.linaro.org/~wookey/buildd/raring-arm64/status-bootstrap.html Image building -------------- The config and instructions provided (in http://wiki.debian.org/Arm64Port#Building_your_own_rootfs_image ) is for multistrap. Debootstrap sort-of produces working images too but takes a lot longer to unpack/configure, and misses out various vital packages (like libperl5.14). I'm sure it could be kicked into submission. In theory multistrap (apt really) should have got all the arch all packages from the main repo, but in practice it refused to do that so I had to rebuild them or copy them over anyway (grumble). Any package that installs replaced conffiles seems to generate invalid dpkg status entries (ifupdown did this to me). I've not got to the bottom of that yet. Deleting the offending line gets you an image that works. Issues ------ General: The build-profile patches for dpkg and apt need to be pushed into the distro to make that feature permanent. A thread on debian-devel is working on that (http://debian.2.n7.nabble.com/Bootstrappable-Debian-proposal-of-needed-chan…). The main issue is what syntax to use '<>' or '[]' and how to deal with multiple overlapping profiles. The patches to debian control cannot go in until at least the syntax is agreed and the tools will parse them without barfing. Johannes ands I will send an updated spec soonish. The missing piece of bootstrapping with regard to build-deps is packages that build-dep on gcc-4.6 or binutils. When cross-building this should be satisfied by <triplet>-gcc-4.6 or <triplet>-binutils. Nothing makes that happen currently. A scheme has been mooted but nothing is implemented yet. There is debate about whether cross-toolchains should build against multiarch libraries (libgcc, libstdc++) like everything else, or have their own internal copies. Doko and I disagree on this matter. That will need to be worked out at some point. We won't get that much further with fixing cross- object-introspection, which is a non-trivial job. Image-related: The images do essentially work but very little has been tested so far. Multiarch perl still needs work. nss needs cross-building in order to get apt cross-built I've not got networking working yet. Info is here: https://fedoraproject.org/wiki/Architectures/ARM/AArch64/FoundationModel_Ne… lack of a dhcp client in the image hasn't helped there. More info --------- The canonical arm64 port info page is: http://wiki.debian.org/Arm64Port Full arm64 cross-build status (i.e everything that has been tried) is here: http://people.linaro.org/~wookey/buildd/raring-arm64/status.html All the patches generated so far are here: http://people.debian.org/~wookey/bootstrap/patches/ (most that can, have been filed as bugs - there is a backlog of stuff filed in Launchpad but not yet forwarded to the Debian BTS - yes I am a bad boy - blame the fact that you can't use reportbug or bts from inside ARM due to their idiotic email policies). Future work ----------- Firstly we should say thank you to Linaro for sponsoring this work in various ways over the last 3 years. We wouldn't be at this point now if it wasn't for that. However Linaro has a lot of things to do and is trying hard not to do distro's work for them, concentrating on upstream things. This makes sense for commercially-backed distros like Red Hat and Ubuntu, but rather less for Debian where we _are_ the distro just as much as anyone else is, and ultimately someone has to spend the time to get stuff working. Anyway, I was supposed to stop work on this some time back, but have largely failed to do so (cross-building is so moreish - there is always one more build to try before bedtime!) and appreciate being given enough slack to get this to a point of actual utility. However I expect to have much less time to spend on this from now on, except insofar as it still co-oncides with things Linaro wants doing. I'd love to hear from people who actually want to use this, to get more packages built, the Debian cross-toolchains sorted, build-profiles finalised, and a whole pile of stuff fixed once Wheezy is released. I'm pretty sure there are quite a lot of people who want multiarch Debian or Ubuntu on their arm64 machines (or models). I hear rumours that actual hardware may appear sometime around the middle of the year with some bagsied for Debian. Setting up the ports infrastructure for that would be good. I don't know if anyone is interested in building slowly on models in the meantime, or if we should just carry on crossing and see how far we get. This table shows that 471 packages in raring can be expected to cross-build already: http://people.canonical.com/~cjwatson/cross/armhf/raring/ Todo: Fix up multiarch/cross perl Fix nss Build missing packages for apt Build missing packages for build-essential Build Debian cross-toolchain Get all this working in unstable as well as raring Setup buildds Build all the other packages Set up automated bootstraping runs (eventually) Current setup ------------- Builds have all been run locally using the sbuild/chroot setup described above and on the Arm64Port page, which should be easy for anyone to reproduce. The main irritation is keeping up with raring: out of sync libraries are not MA-installable. Logs are uploaded to people.linaro.org (rsync). The reprepro repo is on people.debian.org (dupload). This stuff should probably move to ports.debian.org and ports.ubuntu.com, but neither of those are set up for cross-building so I'm not quite sure how this will work. I could go on at great length about the machinery of profiled bootstrap builds, and interactions between tools, but it's not very exciting, so will resist. Suffice it to say that whilst it's all pretty slick I'd still like better buildd tools. Build-profile changes --------------------- The build-profile patches are not yet upstreamable so are collecting in the repo. The patch set so far is here: http://people.debian.org/~wookey/bootstrap/patches/profiles/packages/ Other thanks: Other people who have helped make this happen in various ways but not got a mention above: Colin Watson, Dmitry Ledkovs, Steve Langasek, Harry Leibel, Thibaut Girka, Roger Leigh, Marcus Shawcroft, James Morrisey, Jonathan Austin, Steve McIntyre, Peter Pearse, Aurelien Jarno, and whoever does sysadmin at people.{linaro,debian}.org I hope I didn't forget anyone, or any important information. Feedback from anyone attempting to get this working outside my computer is very welcome. I have almost certainly forgotten to write down some things, and upload correct versions of some other things. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

11 years, 9 months

problem about the boot panda images

by YongQin Liu

Hi, All I want to use the panda-linaro build from here: https://android-build.linaro.org/builds/~linaro-android-member-ti/panda-lin… but with the sdcard create by linaro-android-media-create, I can't boot the panda board. Anyone has met the same problem? attached linaro-android-media-create.log is the output of the linaro-android-media-create Following is the output of minicom: Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 10:05:24. Port /dev/ttyUSB0 Press CTRL-A Z for help on special keys U-Boot SPL 2013.01.-rc1 (Mar 12 2013 - 01:42:53) OMAP4460 ES1.1 OMAP SD/MMC: 0 ** Partition 1 not valid on device 0 ** spl: fat register err - -1 ### ERROR ### Please RESET the board ### U-Boot SPL 2013.01.-rc1 (Mar 12 2013 - 01:42:53) OMAP4460 ES1.1 OMAP SD/MMC: 0 ** Partition 1 not valid on device 0 ** spl: fat register err - -1 ### ERROR ### Please RESET the board ### U-Boot SPL 2013.01.-rc1 (Mar 12 2013 - 01:42:53) OMAP4460 ES1.1 OMAP SD/MMC: 0 ** Partition 1 not valid on device 0 ** spl: fat register err - -1 ### ERROR ### Please RESET the board ### U-Boot SPL 2013.01.-rc1 (Mar 12 2013 - 01:42:53) OMAP4460 ES1.1 OMAP SD/MMC: 0 ** Partition 1 not valid on device 0 ** spl: fat register err - -1 ### ERROR ### Please RESET the board ### -- Thanks, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/pipermail/linaro-validation

11 years, 9 months

Failure to generate beagle_sd.img using linaro-media-create on Ubuntu 12.04 (64-bit)

by Rajkiran Mulugu

Hi all, Below is the link for the bug-id (Bug #1135454 ) created for the issue "failure to generate beagle_sd.img using linario-media-create on ubuntu 12.04 on 64bit OS". https://bugs.launchpad.net/linaro-image-tools/+bug/1135454 Thanks & Regards RAJ KIRAN ________________________________________ From: Rajkiran Mulugu Sent: Thursday, February 28, 2013 11:57 To: Fathi Boudra Cc: James Tunnicliffe; Amar Shankar; Prasad Raju; linaro-dev(a)lists.linaro.org Subject: RE: Unable to install svn on Ubuntu 12.04 (64-bit) Hi Fathi Boudra, We tried with below commands but we are getting error as follows : 1.)Getting from the Ubuntu package: sudo add-apt-repository ppa:linaro-maintainers/tools sudo apt-get update sudo apt-get install linaro-image-tools 2.)Creating the u-boot + Linux Linaro image: mkdir $(WORKROOT)/beagle_image && cd $(WORKROOT)/beagle_image wget http://releases.linaro.org/platform/linaro-m/hwpacks/final/hwpack_linaro-om… wget http://releases.linaro.org/platform/linaro-m/headless/release-candidate/lin… sudo linaro-media-create --image_file beagle_sd.img --dev beagle --binary linaro-m-headless-tar-20101101-0.tar.gz --hwpack hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz ------------------------------------------------------------ Installing (linaro-hwpack-install) hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz in target rootfs. Unpacking hardware pack ...Done Updating apt package lists ... Ign file: ./ Release.gpg Ign file:/tmp/tmp.6XUobqnK3P/unpacked/pkgs/ ./ Translation-en Ign file: ./ Release Ign file: ./ Packages Get:1 http://ppa.launchpad.net maverick Release.gpg [316B] Ign http://ppa.launchpad.net/linaro-maintainers/overlay/ubuntu/ maverick/main Translation-en Ign http://ports.ubuntu.com maverick Release.gpg Ign http://ports.ubuntu.com/ maverick/main Translation-en Ign http://ports.ubuntu.com/ maverick/universe Translation-en Ign http://ports.ubuntu.com maverick-security Release.gpg Ign http://ports.ubuntu.com/ maverick-security/main Translation-en Ign http://ports.ubuntu.com/ maverick-security/universe Translation-en Ign http://ports.ubuntu.com maverick-updates Release.gpg Ign http://ports.ubuntu.com/ maverick-updates/main Translation-en Ign http://ports.ubuntu.com/ maverick-updates/universe Translation-en Ign http://ports.ubuntu.com maverick-proposed Release.gpg Get:2 http://ppa.launchpad.net maverick Release [9762B] Ign http://ports.ubuntu.com/ maverick-proposed/main Translation-en Ign http://ports.ubuntu.com/ maverick-proposed/universe Translation-en Ign http://ports.ubuntu.com maverick Release Ign http://ports.ubuntu.com maverick-security Release Ign http://ports.ubuntu.com maverick-updates Release Ign http://ports.ubuntu.com maverick-proposed Release Ign http://ports.ubuntu.com maverick/main armel Packages/DiffIndex Get:3 http://ppa.launchpad.net maverick/main armel Packages [11.7kB] Ign http://ports.ubuntu.com maverick/universe armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-security/main armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-security/universe armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-updates/main armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-updates/universe armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-proposed/main armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick-proposed/universe armel Packages/DiffIndex Ign http://ports.ubuntu.com maverick/main armel Packages Ign http://ports.ubuntu.com maverick/universe armel Packages Ign http://ports.ubuntu.com maverick-security/main armel Packages Ign http://ports.ubuntu.com maverick-security/universe armel Packages Ign http://ports.ubuntu.com maverick-updates/main armel Packages Ign http://ports.ubuntu.com maverick-updates/universe armel Packages Ign http://ports.ubuntu.com maverick-proposed/main armel Packages Ign http://ports.ubuntu.com maverick-proposed/universe armel Packages Err http://ports.ubuntu.com maverick/main armel Packages 404 Not Found Err http://ports.ubuntu.com maverick/universe armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-security/main armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-security/universe armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-updates/main armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-updates/universe armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-proposed/main armel Packages 404 Not Found Err http://ports.ubuntu.com maverick-proposed/universe armel Packages 404 Not Found Fetched 21.8kB in 3s (6379B/s) W: Failed to fetch http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… 404 Not Found E: Some index files failed to download, they have been ignored, or old ones used instead. Cleaning up ...W: Failed to fetch http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… 404 Not Found W: Failed to fetch http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… 404 Not Found E: Some index files failed to download, they have been ignored, or old ones used instead. proc has been unmounted Traceback (most recent call last): File "/usr/bin/linaro-media-create", line 175, in <module> verified_files, *hwpacks) File "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", line 79, in install_hwpacks install_hwpack(chroot_dir, hwpack_file, hwpack_force_yes or hwpack_verified) File "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", line 100, in install_hwpack cmd_runner.run(args, as_root=True, chroot=chroot_dir).wait() File "/usr/lib/python2.7/dist-packages/linaro_image_tools/cmd_runner.py", line 100, in wait raise SubcommandNonZeroReturnValue(self._my_args, returncode) linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process "['chroot', '/tmp/tmpHZWJB3/binary', 'linaro-hwpack-install', '/hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz']" returned a non-zero value: 100 Could you please let us know which are the tar files to be used with linaro-media-create tool inorder to generate beagle_sd.img. It seems that the below files are old versions and referring to 2010 Ubuntu releases. linaro-m-headless-tar-20101101-0.tar.gz hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz Regards, Rajkiran _____________________________________ From: Fathi Boudra [fathi.boudra(a)linaro.org] Sent: 28 February, 2013 11:30 To: Rajkiran Mulugu Cc: James Tunnicliffe; Amar Shankar; Prasad Raju; linaro-dev(a)lists.linaro.org Subject: Re: Unable to install svn on Ubuntu 12.04 (64-bit) On 28 February 2013 07:54, Rajkiran Mulugu <Rajkiran.Mulugu(a)infotech-enterprises.com> wrote: > Hi James, > We tried the link you sent for Latest Release of linaro-media-create as > below: > > But we are facing below error (shown in RED COLOUR). > > raj@Rajkiran:~/uefi$ sudo add-apt-repository > ppa:https://launchpad.net/~linaro-maintainers/+archive/tools the command should be: sudo add-apt-repository ppa:linaro-maintainers/tools > Cannot access PPA (https://launchpad.net/api/1.0/~https/+archive/ppa) to get > PPA information, please check your internet connection. > > Thanks & Regards, > RAJ KIRAN > ________________________________________ > From: James Tunnicliffe [james.tunnicliffe(a)linaro.org] > Sent: Thursday, February 28, 2013 0:08 > To: Amar Shankar > Cc: Dave Pigott; Prasad Raju; Rajkiran Mulugu; linaro-dev(a)lists.linaro.org > Subject: Re: Unable to install svn on Ubuntu 12.04 (64-bit) > > > To get the latest release of linaro-media-create please add the > following PPA and update: > https://launchpad.net/~linaro-maintainers/+archive/tools > > We released a new version of linaro-media-create yesterday that should > resolve this issue. > > Thanks, > > James > > On 27 February 2013 06:40, Amar Shankar > <Amar.Shankar(a)infotech-enterprises.com> wrote: >> >> Hi Dave, >> >> We have installed latest Ubuntu 12.04 (Precise Pangolin) 64-bit from net >> and >> tried to execute the steps to build UEFI image as in link below:- >> >> >> http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=BeagleBoard… >> >> However on executing below command to create beagle_sd.img, we are getting >> the error as below (shown in red). >> >> raj@Rajkiran:~/uefi/beagle_image$ sudo linaro-media-create --image_file >> beagle_sd.img --dev beagle --binary >> linaro-m-headless-tar-20101101-0.tar.gz >> --hwpack >> >> hwpack_linaro-omap3_20101109-1_armel_supported.tar.gzraj@Rajkiran:~/uefi/beagle_image$ >> sudo linaro-media-create --image_file beagle_sd.img --dev beagle --binary >> linaro-m-headless-tar-20101101-0.tar.gz --hwpack >> hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz >> ------------------------------------------------------------ >> Installing (linaro-hwpack-install) >> hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz in target rootfs. >> Unpacking hardware pack ...Done >> Updating apt package lists ... >> Ign file: ./ Release.gpg >> Ign filetmp/tmp.TAq3ZPdSgS/unpacked/pkgs/ ./ Translation-en >> Ign file: ./ Release >> Ign file: ./ Packages >> Ign http://ports.ubuntu.com maverick Release.gpg >> Ign http://ports.ubuntu.com/ maverick/main Translation-en >> Get:1 http://ppa.launchpad.net maverick Release.gpg [316B] >> Ign http://ports.ubuntu.com/ maverick/universe Translation-en >> Ign http://ports.ubuntu.com maverick-security Release.gpg >> Ign http://ports.ubuntu.com/ maverick-security/main Translation-en >> Ign http://ports.ubuntu.com/ maverick-security/universe Translation-en >> Ign http://ports.ubuntu.com maverick-updates Release.gpg >> Ign http://ports.ubuntu.com/ maverick-updates/main Translation-en >> Ign http://ports.ubuntu.com/ maverick-updates/universe Translation-en >> Ign http://ports.ubuntu.com maverick-proposed Release.gpg >> Ign http://ports.ubuntu.com/ maverick-proposed/main Translation-en >> Ign http://ppa.launchpad.net/linaro-maintainers/overlay/ubuntu/ >> maverick/main Translation-en >> Get:2 http://ppa.launchpad.net maverick Release [9762B] >> Ign http://ports.ubuntu.com/ maverick-proposed/universe Translation-en >> Ign http://ports.ubuntu.com maverick Release >> Ign http://ports.ubuntu.com maverick-security Release >> Ign http://ports.ubuntu.com maverick-updates Release >> Ign http://ports.ubuntu.com maverick-proposed Release >> Ign http://ports.ubuntu.com maverick/main armel Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick/universe armel Packages/DiffIndex >> Get:3 http://ppa.launchpad.net maverick/main armel Packages [11.7kB] >> Ign http://ports.ubuntu.com maverick-security/main armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-security/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-updates/main armel Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-updates/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-proposed/main armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-proposed/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick/main armel Packages >> Ign http://ports.ubuntu.com maverick/universe armel Packages >> Ign http://ports.ubuntu.com maverick-security/main armel Packages >> Ign http://ports.ubuntu.com maverick-security/universe armel Packages >> Ign http://ports.ubuntu.com maverick-updates/main armel Packages >> Ign http://ports.ubuntu.com maverick-updates/universe armel Packages >> Ign http://ports.ubuntu.com maverick-proposed/main armel Packages >> Ign http://ports.ubuntu.com maverick-proposed/universe armel Packages >> Err http://ports.ubuntu.com maverick/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-security/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-security/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-updates/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-updates/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-proposed/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-proposed/universe armel Packages >> 404 Not Found >> Fetched 21.8kB in 3s (5576B/s) >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 >> Not >> Found >> >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz >> 404 >> Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… >> 404 Not Found >> >> E: Some index files failed to download, they have been ignored, or old >> ones >> used instead. >> Cleaning up ...W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 >> Not >> Found >> >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz >> 404 >> Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… >> 404 Not Found >> >> E: Some index files failed to download, they have been ignored, or old >> ones >> used instead. >> proc has been unmounted >> Traceback (most recent call last): >> File "/usr/bin/linaro-media-create", line 175, in <module> >> verified_files, *hwpacks) >> File >> >> "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", >> line 79, in install_hwpacks >> install_hwpack(chroot_dir, hwpack_file, hwpack_force_yes or >> hwpack_verified) >> File >> >> "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", >> line 100, in install_hwpack >> cmd_runner.run(args, as_root=True, chroot=chroot_dir).wait() >> File "/usr/lib/python2.7/dist-packages/linaro_image_tools/cmd_runner.py", >> line 100, in wait >> raise SubcommandNonZeroReturnValue(self._my_args, returncode) >> linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process >> "['chroot', '/tmp/tmp1gZKWU/binary', 'linaro-hwpack-install', >> '/hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz']" returned a >> non-zero value: 100 >> ------------------------------------------------------------ >> Installing (linaro-hwpack-install) >> hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz in target rootfs. >> Unpacking hardware pack ...Done >> Updating apt package lists ... >> Ign file: ./ Release.gpg >> Ign filetmp/tmp.TAq3ZPdSgS/unpacked/pkgs/ ./ Translation-en >> Ign file: ./ Release >> Ign file: ./ Packages >> Ign http://ports.ubuntu.com maverick Release.gpg >> Ign http://ports.ubuntu.com/ maverick/main Translation-en >> Get:1 http://ppa.launchpad.net maverick Release.gpg [316B] >> Ign http://ports.ubuntu.com/ maverick/universe Translation-en >> Ign http://ports.ubuntu.com maverick-security Release.gpg >> Ign http://ports.ubuntu.com/ maverick-security/main Translation-en >> Ign http://ports.ubuntu.com/ maverick-security/universe Translation-en >> Ign http://ports.ubuntu.com maverick-updates Release.gpg >> Ign http://ports.ubuntu.com/ maverick-updates/main Translation-en >> Ign http://ports.ubuntu.com/ maverick-updates/universe Translation-en >> Ign http://ports.ubuntu.com maverick-proposed Release.gpg >> Ign http://ports.ubuntu.com/ maverick-proposed/main Translation-en >> Ign http://ppa.launchpad.net/linaro-maintainers/overlay/ubuntu/ >> maverick/main Translation-en >> Get:2 http://ppa.launchpad.net maverick Release [9762B] >> Ign http://ports.ubuntu.com/ maverick-proposed/universe Translation-en >> Ign http://ports.ubuntu.com maverick Release >> Ign http://ports.ubuntu.com maverick-security Release >> Ign http://ports.ubuntu.com maverick-updates Release >> Ign http://ports.ubuntu.com maverick-proposed Release >> Ign http://ports.ubuntu.com maverick/main armel Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick/universe armel Packages/DiffIndex >> Get:3 http://ppa.launchpad.net maverick/main armel Packages [11.7kB] >> Ign http://ports.ubuntu.com maverick-security/main armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-security/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-updates/main armel Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-updates/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-proposed/main armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick-proposed/universe armel >> Packages/DiffIndex >> Ign http://ports.ubuntu.com maverick/main armel Packages >> Ign http://ports.ubuntu.com maverick/universe armel Packages >> Ign http://ports.ubuntu.com maverick-security/main armel Packages >> Ign http://ports.ubuntu.com maverick-security/universe armel Packages >> Ign http://ports.ubuntu.com maverick-updates/main armel Packages >> Ign http://ports.ubuntu.com maverick-updates/universe armel Packages >> Ign http://ports.ubuntu.com maverick-proposed/main armel Packages >> Ign http://ports.ubuntu.com maverick-proposed/universe armel Packages >> Err http://ports.ubuntu.com maverick/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-security/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-security/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-updates/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-updates/universe armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-proposed/main armel Packages >> 404 Not Found >> Err http://ports.ubuntu.com maverick-proposed/universe armel Packages >> 404 Not Found >> Fetched 21.8kB in 3s (5576B/s) >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 >> Not >> Found >> >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz >> 404 >> Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… >> 404 Not Found >> >> E: Some index files failed to download, they have been ignored, or old >> ones >> used instead. >> Cleaning up ...W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/main/binary-armel/Packages.gz 404 >> Not >> Found >> >> W: Failed to fetch >> http://ports.ubuntu.com/dists/maverick/universe/binary-armel/Packages.gz >> 404 >> Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-security/universe/binary-armel/Packa… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/main/binary-armel/Packages.gz >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-updates/universe/binary-armel/Packag… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/main/binary-armel/Packages.… >> 404 Not Found >> >> W: Failed to fetch >> >> http://ports.ubuntu.com/dists/maverick-proposed/universe/binary-armel/Packa… >> 404 Not Found >> >> E: Some index files failed to download, they have been ignored, or old >> ones >> used instead. >> proc has been unmounted >> Traceback (most recent call last): >> File "/usr/bin/linaro-media-create", line 175, in <module> >> verified_files, *hwpacks) >> File >> >> "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", >> line 79, in install_hwpacks >> install_hwpack(chroot_dir, hwpack_file, hwpack_force_yes or >> hwpack_verified) >> File >> >> "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/chroot_utils.py", >> line 100, in install_hwpack >> cmd_runner.run(args, as_root=True, chroot=chroot_dir).wait() >> File "/usr/lib/python2.7/dist-packages/linaro_image_tools/cmd_runner.py", >> line 100, in wait >> raise SubcommandNonZeroReturnValue(self._my_args, returncode) >> linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process >> "['chroot', '/tmp/tmp1gZKWU/binary', 'linaro-hwpack-install', >> '/hwpack_linaro-omap3_20101109-1_armel_supported.tar.gz']" returned a >> non-zero value: 100 >> >> Request your help here to resolve the issue. >> >> Thanks & Regards, >> Amar Shankar >> ________________________________ >> From: linaro-dev-bounces(a)lists.linaro.org >> [linaro-dev-bounces(a)lists.linaro.org] on behalf of Amar Shankar >> Sent: 21 February, 2013 12:29 PM >> To: Dave Pigott >> Cc: Prasad Raju; Rajkiran Mulugu; linaro-dev(a)lists.linaro.org >> Subject: Unable to install svn on Ubuntu 12.04 (64-bit) >> >> >> Hi, >> >> We have installed Ubuntu 12.04 (Precise Pangolin) 64-bit. >> But unable to install svn. >> >> rajkiran@rajkiran-OptiPlex-780:~$ sudo apt-get install subversion >> Reading package lists... Error! >> W: Duplicate sources.list entry cdrom://Ubuntu 12.04.1 LTS _Precise >> Pangolin_ - Release amd64 (20120823.1)/ precise/main i386 Packages >> >> (/var/lib/apt/lists/Ubuntu%2012.04.1%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120823.1)_dists_precise_main_binary-i386_Packages) >> W: Duplicate sources.list entry cdrom://Ubuntu 12.04.1 LTS _Precise >> Pangolin_ - Release amd64 (20120823.1)/ precise/restricted i386 Packages >> >> (/var/lib/apt/lists/Ubuntu%2012.04.1%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120823.1)_dists_precise_restricted_binary-i386_Packages) >> E: Encountered a section with no Package: header >> E: Problem with MergeList >> >> /var/lib/apt/lists/extras.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages >> E: The package lists or status file could not be parsed or opened. >> >> Could you please help us resolve the issue? >> >> Regards, >> Amar >> ________________________________ >> From: Dave Pigott [dave.pigott(a)linaro.org] >> Sent: 19 February, 2013 4:59 PM >> To: Amar Shankar >> Cc: linaro-dev(a)lists.linaro.org; Prasad Raju; Rajkiran Mulugu >> Subject: Re: Failure to generate beagle_sd.img using linaro-media-create >> >> As James said, Anything from the LTS (12.04 - Precise) onwards. >> >> Dave >> >> On 19 Feb 2013, at 10:02, Amar Shankar >> <Amar.Shankar(a)infotech-enterprises.com> wrote: >> >> No >> >> >> >> ________________________________ >> >> DISCLAIMER: >> >> This email may contain confidential information and is intended only for >> the >> use of the specific individual(s) to which it is addressed. If you are not >> the intended recipient of this email, you are hereby notified that any >> unauthorized use, dissemination or copying of this email or the >> information >> contained in it or attached to it is strictly prohibited. If you received >> this message in error, please immediately notify the sender at Infotech >> and >> delete the original message. >> >> ________________________________ >> >> To preserve the environment, please don't print this e-mail unless you >> really need to. >> >> _______________________________________________ >> linaro-dev mailing list >> linaro-dev(a)lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-dev > > _______________________________________________ > linaro-dev mailing list > linaro-dev(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev

11 years, 9 months

Corrupt git archive?

by Tim Northover

Hi, I'm trying to build the OpenEmbedded AArch64 system again, and it looks like the file: http://snapshots.linaro.org/openembedded/sources/git2_git.linaro.org.kernel… linaro-tracking.git.tar.gz is corrupt. gzip thinks it ends unexpectedly. Shall I file some kind of ticket for this or is it something that's fixed out-of-line? Cheers. Tim. -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

11 years, 9 months

Xen Hackathon May 16-17 in Dublin

by Russ Pavlicek

I don't want to spam the list, but as there are likely some people who might want to attend for the benefit of the Linaro effort, I'd like to announce that there is a Xen Hackathon coming on May 16-17 in Dublin Ireland. Details can be found here: http://blog.xen.org/index.php/2013/03/07/google-hosted-xen-hackathon-may-16… Thanks, Russell Pavlicek Xen Evangelist

11 years, 9 months

Black screen error trying to virtualize android-linaro with qemu-linaro on the pandaboard ES and on the arm chromebook

by Mario

Hello to everybody. I'm trying to virtualize Linaro-Android 4 with qemu-linaro on two different kind of machines : 1) Pandaboard ES running Ubuntu with this kernel : Linux arm 3.7.2-x6 #1 SMP Sat Jan 12 07:16:37 UTC 2013 armv7l armv7l armv7l GNU/Linux 2) Samsung XE303C12-A01US Chromebook running CHR Ubuntu with this kernel : Linux localhost.localdomain 3.4.0-5-chromebook #5-Ubuntu SMP Fri Feb 8 14:54:53 UTC 2013 armv7l armv7l armv7l GNU/Linux To accomplish the goal I made the experiments with two versions of qemu-linaro : 1) qemu-linaro-1.3.0-2012.12 2) qemu-linaro 1.4 from the GIT rep In both cases I configured qemu-linaro with these parameters : --disable-kvm --disable-tcg-interpreter --enable-curses --enable-sdl --enable-vnc --disable-debug-tcg --enable-vhost-net I tried to follow two different kind of tutorials : 1) http://www.linuxforu.com/2011/06/qemu-for-embedded-systems-development-part… 2) https://wiki.linaro.org/KenWerner/Sandbox/AndroidQEMU?highlight=%28QEMU%29|… On the TUTORIAL n. 1: 1) Created a small test program, test.c, with the basic “Hello world”: #include<stdio.h> int main(){ printf("Welcome to Open World\n"); } # gcc test.c -o test 2) Built the Linux kernel for ARM # tar -jxvf linux-2.6.37.tar.bz2 (but I tried with a lot of other kernel versions) # cd linux-2.6.37 # make menuconfig ARCH=arm # make ARCH=arm uImage -s # qemu-system-arm -M versatilepb -m 128M -kernel /home/user/Desktop/linux-2.6.37/arch/arm/boot/uImage RESULT = black screen inside the qemu-linaro window without error messages 3) Developed a dummy filesystem (hello.c) for testing #include<stdio.h> int main(){ while(1){ printf("Hello Open World\n"); getchar(); } } # gcc hello.c -static -o hello 4) Created a root filesystem # echo hello | cpio -o --format=newc > rootfs 5) Testing : qemu-system-arm -M versatilepb -m 128M -kernel /home/user/Desktop/ linux-2.6.37/arch/arm/boot/uImage -initrd rootfs -append "root=/dev/ram rdinit=/hello" RESULT = black screen inside the qemu-linaro window without error messages On the TUTORIAL n. 2 : 1) Patched : qemu-linaro-1.3.0-2012.12 with : sed -i "s/#define INITRD_LOAD_ADDR 0x00d00000/#define INITRD_LOAD_ADDR 0x01d00000/" qemu-linaro-1.3.0-2012.12/hw/arm_boot.c and also qemu-linaro 1.4 from the GIT rep with the same patch: sed -i "s/#define INITRD_LOAD_ADDR 0x00d00000/#define INITRD_LOAD_ADDR 0x01d00000/" qemu-linaro/hw/arm_boot.c 2) wget http://releases.linaro.org/12.05/android/images/vexpress-ics-gcc47-armlt-tr… gunzip vexpress-ics-gcc47-armlt-tracking-open.img.gz sudo kpartx -a vexpress-ics-gcc47-armlt-tracking-open.img sudo mount /dev/mapper/loop0p1 /mnt -o loop,ro cp /mnt/uImage /mnt/uInitrd . sudo umount /mnt sudo kpartx -d /dev/mapper/loop0p* dd if=uImage of=vmlinuz skip=64 bs=1 dd if=uInitrd of=initrd.gz skip=64 bs=1 3) Tried to boot Linaro Android 12.05 using qemu-linaro-1.3.0-2012.12 and also qemu-linaro 1.4 from the GIT rep on the Pandaboard ES with this : qemu-system-arm -M vexpress-a9 -m 1024 -smp 1 -snapshot -serial stdio -no-reboot -kernel vmlinuz -initrd initrd.gz -drive file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback --append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0" and on the Samsung XE303C12-A01US Chromebook with this : qemu-system-arm -M vexpress-a15 -cpu-cortex-a15 -m 1024 -smp 1 -snapshot -serial stdio -no-reboot -kernel vmlinuz -initrd initrd.gz -drive file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback --append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0" I've also tried wth : qemu-system-arm -M vexpress-a15 -cpu cortex-a15 -m 1024 -smp 1 -snapshot -serial stdio -no-reboot -kernel uImage -initrd uInitrd -drive file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback --append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0" Also tried with different kind of combinations,like : -M versatilepb ; -M vexpress-a9 ; -cpu cortex-a9 ; -m 512 ; but the RESULT is still the smae = black screen inside the qemu-linaro window without error messages. Any help ? Instead,debian_lenny_armel_desktop is virtualized very well with qemu-linaro following this procedure : a) wget vmlinuz-2.6.32-5-versatile,initrd.img-2.6.32-5-versatile and debian_lenny_armel_desktop from here : http://people.debian.org/~aurel32/qemu/armel/ b) tried to virtualize debian_lenny_armel_desktop with : qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.32-5-versatile -initrd initrd.img-2.6.32-5-versatile -hda debian_lenny_armel_desktop.qcow2 -append "root=/dev/sda1" and it works.... -- Mario.

11 years, 9 months

[ANNOUNCE] linux-linaro kernel schedule for 13.03

by Andrey Konovalov

Greetings, The current 13.03 schedule has been published on wiki: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule llct rebuild is planned later today. The 13.03 release would be v3.9-rc3 based (tentative). Please make sure that requests to add new topics (with the git branch to pull from) have been sent to me, or will be sent as soon as the topic is ready. I would appreciate a "heads up" like information on the new topics which are more complex than a couple patches on top of mainline. For the moment I am aware of the kvm topic only. Anything else? Thanks, Andrey

11 years, 9 months

ubi mount issue

by Malati C

Hi All, I am not sure whether this is the right forum to ask about my issue. Let me know. However this is really blocking for me and I do not have anyone at my work to help me out. Hence asking help - I am encountering a problem on my target board. Any help is hightly appreciated. On my target board which is SOM based on Marvel PXA series, ubiattach fails. The rootfs is ubi and comes up. I am trying to mount another partition to put all my configuration data. Here is the log - [root]#ubiformat /dev/mtd6 -s 2048 -f ./config.img ubiformat: mtd6 (nand), size 152305664 bytes (145.2 MiB), 1162 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes libscan: scanning eraseblock 1161 -- 100 % complete ubiformat: 1162 eraseblocks have valid erase counter, mean value is 0 ubiformat: flashing eraseblock 47 -- 100 % complete ubiformat: formatting eraseblock 1161 -- 100 % complete [root]#ubiattach /dev/ubi_ctrl -m 6 UBI: attaching mtd6 to ubi1 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 126976 bytes UBI: smallest flash I/O unit: 2048 UBI: VID header offset: 2048 (aligned 2048) UBI: data offset: 4096 UBI error: vtbl_check: volume table check failed: record 0, error 9 ubiattach: error!: cannot attach mtd6 error 22 (Invalid argument) [root]# Let me know if you need any other information. Thanks Mchavva

11 years, 9 months

big.LITTLE MP status Mar 4, 2013

by David Zinman

https://wiki.linaro.org/projects/big.LITTLE.MP Work Items for functional completion: https://wiki.linaro.org/projects/big.LITTLE.MP/WorkItems Roadmap Cards: Improving HMP Linux scheduling - http://cards.linaro.org/browse/CARD-190 Blueprints and bugs are all now in a single Launchpad project for big.LITTLE: https://launchpad.net/linaro-big-little-system 2013.03 release for Virtual Express ========================================= https://releases.linaro.org/13.02/android/images/vexpress-linaro-mp Development ============= - Work out how to combine a single holistic ARM/Linaro solution - Feedback received - Upstream work, submitted this month, no schedule estimate - Provide basic scale invariant load contribution : cpupower*(currfreq/maxfreq)*load - work in progress - Ramping up benchmarking efforts on MP Blueprints ----------------- https://blueprints.launchpad.net/linaro-big-little-system/+spec/cpuidle-add… https://blueprints.launchpad.net/linaro-power-kernel/+spec/multi-cluster-cp… https://blueprints.launchpad.net/linaro-big-little-system/+spec/big.little.… https://blueprints.launchpad.net/linaro-big-little-system/+spec/sched-coope… https://blueprints.launchpad.net/linaro-power-kernel/+spec/sched-adaptive-n… https://blueprints.launchpad.net/linaro-big-little-system/+spec/timer-workq… https://blueprints.launchpad.net/linaro-power-kernel/+spec/scheduler-optimi… https://blueprints.launchpad.net/linaro-big-little-system/+spec/power-aware… QA === big.LITTLE MP LAVA Dashboard http://validation.linaro.org/lava-server/dashboard/image-reports/linaro-and… Testing: See attached spreadsheet http://lists.linaro.org/pipermail/linaro-dev/2013-February/015521.html https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ai9ggMs8bsGJdER3a… Bugs: https://bugs.launchpad.net/linaro-big-little-system/+bugs?field.tag=bl-mp -- David Zinman, Project Manager Linaro.org | Open source software for ARM SoCs

11 years, 10 months

[PATCH V2] arm64: add support for 8250/16550 earlyprintk

by Anup Patel

This patch adds support for using earlyprintk with 8250/16550 UART ports. The 8250/16550 UART can either have 8-bit or 32-bit aligned registers which is HW vendor dependent. Kernel args for 8-bit aligned regs: earlyprintk=uart8250-8bit,<phys_address> Kernel args for 32-bit aligned regs: earlyprintk=uart8250-32bit,<phys_address> Signed-off-by: Anup Patel <anup.patel(a)linaro.org> --- arch/arm64/kernel/early_printk.c | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/arch/arm64/kernel/early_printk.c b/arch/arm64/kernel/early_printk.c index 7e320a2..c39e90b 100644 --- a/arch/arm64/kernel/early_printk.c +++ b/arch/arm64/kernel/early_printk.c @@ -24,11 +24,32 @@ #include <linux/io.h> #include <linux/amba/serial.h> +#include <linux/serial_reg.h> static void __iomem *early_base; static void (*printch)(char ch); /* + * 8250/16550 (8-bit aligned registers) single character TX. + */ +static void uart8250_8bit_printch(char ch) +{ + while (!(readb_relaxed(early_base + UART_LSR) & UART_LSR_THRE)) + ; + writeb_relaxed(ch, early_base + UART_TX); +} + +/* + * 8250/16550 (32-bit aligned registers) single character TX. + */ +static void uart8250_32bit_printch(char ch) +{ + while (!(readl_relaxed(early_base + (UART_LSR << 2)) & UART_LSR_THRE)) + ; + writel_relaxed(ch, early_base + (UART_TX << 2)); +} + +/* * PL011 single character TX. */ static void pl011_printch(char ch) @@ -47,6 +68,8 @@ struct earlycon_match { static const struct earlycon_match earlycon_match[] __initconst = { { .name = "pl011", .printch = pl011_printch, }, + { .name = "uart8250-8bit", .printch = uart8250_8bit_printch, }, + { .name = "uart8250-32bit", .printch = uart8250_32bit_printch, }, {} }; -- 1.7.9.5

11 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev March 2013