linaro-dev January 2011

linaro-dev@lists.linaro.org

81 participants
84 discussions

how to get hardware accelerated video and OpenGL ES for OMAP3530 (IGEPv2 board)? (noob alert)

by Jörg Hohensohn

Hello, This is my first post, I'm a complete noop to Linaro, discovered it yesterday. Needing to run OpenGL ES applications and media playback, I was excited to find e.g. this one: http://www.youtube.com/watch?v=yhglD0mJiLk (under Linaro, GStreamer playing a video by DSP in fullscreen) and this one, admittedly not Linaro but Debian: http://www.youtube.com/watch?v=Qaypv-JhEVI (Quake3 using hardware OpenGL ES) During first and promising own experiments, I was surprised to find that OpenGL acceleration and A/V decoding by hardware don't seem to be part of the Linaro hardware package. Does anybody have that integrated, or how would I do about that? Interestingly, TI has just released those supporting components in a fresh version: http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-dm37x.html But they come with an older kernel. To my understanding, the TI code would have to be recompiled with the Linaro kernel? Thanks for answers, Jörg

12 years, 10 months

Notes & Actions: Linaro Developer Platform Weekly Status Meeting 1/19

by Tom Gall

Enclosed you'll find a link to the agenda, notes and actions from the Linaro Developer Platforms Weekly Status meeting held on January 19th in #linaro-meeting on irc.freenode.net at 15:00 UTC. https://wiki.linaro.org/Platform/Foundations/2011-01-19 Regards, Tom (tgall_foo) Developer Platforms Team "We want great men who, when fortune frowns will not be discouraged." - Colonel Henry Knox w) tom.gall att linaro.org w) tom_gall att vnet.ibm.com h) tom_gall att mac.com

12 years, 10 months

Linaro PPAs and backports / release cycles

by Loïc Minier

Hey As a followup to IRC conversations around backports, releases and QA today, I'd like to hear what others think of our Linaro PPAs. I'll start with some history and proposals: We created a fairly ad hoc PPA layout for the 10.11 cycle, with ppa:linaro-maintainers/tools ppa:linaro-maintainers/override ppa:linaro-maintainers/kernel and nowadays we also have this PPA for toolchain backports: ppa:linaro-maintainers/toolchain and misc other PPAs which I don't really know much about: ppa:linaro-maintainers/user-platforms ppa:linaro-toolchain-dev/ppa ppa:linaro-infrastructure/launch-control ppa:linaro-infrastructure/launch-control-snapshots (and probably many more) There are multiple problems with our current approach: * ~linaro-maintainers membership is poorly defined * it's not clear which software should go in which PPA * it's not clear when we can update which PPAs, e.g. can we update them after 6-monthly releases? how do we QA/validate updates? In general, it's good to avoid PPA proliferation, both for sanity and for the confort of our end users, but I think a consistent set of PPAs is more important than trying to optimize the number of PPAs to the smallest subset possible. Some ideas on addressing this: * have software ownership split by team; ~toolchain owns gcc-linaro and qemu-linaro, ~infrastructure owns * have each team decide between either: - a single PPA for all their outputs (e.g. ~infrastructure/ppa for linaro-image-tools and gcc-log-analyzer) - or multiple PPAs, one per software (e.g. ~toolchain/gcc-linaro PPA for gcc-linaro, ~toolchain/qemu-linaro PPA for qemu-linaro) * optionally, additional PPAs for dailies * optionally, additional PPAs for RC releases [ this is inspired from the set of PPAs for bzr: http://wiki.bazaar.canonical.com/DistroDownloads#Ubuntu%20and%20derivatives ] In addition, we'd have a single overlay PPA which would be used for rootfs builds. We could keep the existing one below ~linaro-maintainers. Open questions: - list of ~linaro-teams - do we upload latest release of e.g. gcc-linaro to the natty toolchain PPA if it already gets uploaded to natty proper? Thanks, -- Loïc Minier

12 years, 10 months

btrfs-tools for arm

by Per Forlin

Hi, I am using the linaro-m-headless-rootfs and tools for btrfs are missing. I want to put btrfs on the onboard MMC and therefore I would like to run btrfs-tools on target. Does any one have arm version of the btrfs-tools? BR Per

12 years, 10 months

Linaro Instructions for Overo(Gumstix)

by Andy Doan

FYI: I've just created a page describing how to get a Linaro image running on the Overo Gumstix board: https://wiki.linaro.org/Boards/Overo/Setup -andy

12 years, 10 months

Hardware Packs v2

by Loïc Minier

Hey there As a result of a series of bugs around linaro-image-tools and daily images, it seemed a sensible approach to solve this class of issues would be to move more data into hardware packs rather than hardcoding stuff in linaro-image-tools. Guilherme, Steve Langasek, and Michael Hudson were all interested in the idea, so Michael convinced me to start a wiki page with some notes: https://wiki.linaro.org/Platform/Specs/11.05/HardwarePacksV2 I'm sending this for others to get the chance to raise issues with hwpacks since we don't want to change the format too frequently. Cheers, -- Loïc Minier

12 years, 10 months

linaro-image-tools 0.4(.1)

by Loïc Minier

Hey I've just uploaded linaro-image-tools 0.4(.1) to natty; thanks to the hard work of Michael Hudson, Guilherme Salgado, James Westby, Martin Ohlsson and many others, we have an awesomely nicer tool to write our Linaro images. For developers: please note that the branch location just moved from: lp:~linaro-maintainers/linaro-image-tools/linaro-image-tools to: lp:~linaro-maintainers/linaro-image-tools/trunk (lp:linaro-image-tools will do the right thing) This doesn't affect existing merge requests, but it might affect your checkouts; use "bzr pull --remember lp:linaro-image-tools" (or push) the next time your pull (or push). Packaging will also be split out into lp:~linaro-maintainers/linaro-image-tools/ubuntu Once this gets out of NEW and enters natty, I should prepare lucid and maverick backports into the Tools PPA (ppa:linaro-maintainers/tools, https://launchpad.net/~linaro-maintainers/+archive/tools/+packages) in the mean time, it's in my PPA: https://launchpad.net/~lool/+archive/ppa/+sourcepub/1448382/+listing-archiv… Cheers, -- Loïc Minier

12 years, 10 months

[PATCH v2] ARM: iMX51 BBG: add clock debug informatio

by yong.shen＠linaro.org

change log: Add more description in commit.

12 years, 10 months

fibcp tool for copying images to SD cards

by Dave Martin

Hi all, I had a go at hacking up a tool to copy sparse images to cards less wastefully (and hopefully faster) by only coping to the important data: See the src/fibcp.c here: git://git.linaro.org/people/dmart/tools.git It's used like this: # fibcp image.bin /dev/<sdcard> There are some caveats, most notably: * You have to be root, since the tool relies on the FIBMAP ioctl. * The filesystem the image file is generated on must not "optmise" explicit writing of blocks of zeros by generating a sparse file. ext[2-4] should work; not sure about btrfs. * The image must be freshly generated via a loop mount (e.g., linaro-media-create --image_file ... copied, tar'd or gzip'd images won't work). It works well enough that e2fsck passes after a writing an image to a card which was previously full of random data. Anyway, it's there if anyone wants to play with it -- comments welcome. Cheers ---Dave

12 years, 10 months

[PM] 19/01/2011 - Minutes for the Power Management WG weekly call

by Amit Kucheria

Hello Everyone, The action packed minutes of the weekly call can be found at: https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2011-01-19 Attendees: Full house! Regards, Amit

12 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev January 2011