Greetings,
Enclosed you'll find a link to the agenda, notes and actions from the
Linaro User Platforms Weekly Status meeting dated December 1st held in
#linaro-meeting on irc.freenode.net at 13:00 UTC.
https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-12-01
Status Summary:
* spandex benchmark suite packaged up and test definition for abrek created
* new spec created for autocolorspace convertor selection and playbin2
new property in gstreamer
* Implementation of GLProxy library begun
* Packaging of meegotouch compositor and companion packages begun
* All live-helper.configs updated for natty alpha1
* VP8 design document,Infrastructure related-Host Pc,Tools, ffmpeg etc
Regards,
Tom (tgall_foo)
User 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
in case any of the multimedia/middleware folks interested in camerabin2
didn't notice this email from gst-devel list:
---------- Forwarded message ----------
From: Thiago Sousa Santos <thiago.sousa.santos(a)collabora.co.uk>
Date: Fri, Dec 3, 2010 at 11:30 PM
Subject: Re: [gst-devel] Camerabin2 Prototype and IRC Meeting
To: Discussion of the development of GStreamer <
gstreamer-devel(a)lists.sourceforge.net>
On Thu, 2010-12-02 at 12:07 -0300, Thiago Sousa Santos wrote:
> Hello,
>
> As mentioned some time ago, we started planning camerabin2.
>
> The good news is that a small prototype is ready at
> http://gitorious.org/gstreamer-camerabin2/gst-plugins-bad
>
> It is as simple as it gets, being able to take pictures, record videos
> and showing a viewfinder. Feedback, code review, patches, tests are
> welcome. I'm currently trying to get the code in shape to push it as an
> experimental plugin into -bad module.
>
> I'd like arrange meeting with people interested in camerabin2 to discuss
> desired features and problems with this new design. I'm already poking
> some people that mentioned interest to set up a date and time. We'd like
> to do this soon, so expect it to be early next week (Monday or Tuesday).
Based on the feedback I got from the interested people and their
timezones:
http://www.timeanddate.com/worldclock/meetingtime.html?day=7&month=12&year=…
I guess 14PM UTC, Tuesday is a nice option. We'd meet on IRC on
#camerabin2.
Any major problems with this?
>
> Details on camerabin2 design are on the wiki:
> http://www.gstreamer.net/wiki/CameraBin
>
> --
> Thiago
>
>
>
>
------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Avik,
Your debuild looks good. I have never seen this error.
Is there a reason you need a packaged kernel? In general dealing with
packaged kernels is more difficult than just doing a simple
crosscompile.
The instructions of PackageYourOwnKernel are for those who need a
packaged kernel for inclusion in for example hwpacks. If you are
adding some new functionality to the linaro kernel then just use
Nicolas' current kernel which right now is
git://git.linaro.org/kernel/linux-linaro-2.6.36.git. Once you have
the new functionality working then send patches or a pull request to
Nicolas. He will pull them into his tree. Then I will pull them into
the packaged natty kernel tree.
John
On Fri, Dec 3, 2010 at 11:48 AM, Nicolas Pitre <nicolas.pitre(a)linaro.org> wrote:
> On Fri, 3 Dec 2010, Avik Sil wrote:
>
>> I tried to build with the fix using debuild. It seems it now compiles the
>> kernel correctly but fails at later stage when debuild performs some
>> post-build checks. The build output can be found here:
>> http://pastebin.com/kB5kpTMS
>>
>> I use 'debuild -eCROSS_COMPILE=arm-linux-gnueabi- -b -aarmel' command
>> for building.
>>
>> Nicolas, can you please tell me the reason for this error? I consulted the
>> steps given in https://wiki.linaro.org/PackageYourOwnKernel
>
> Sorry, I've never used debuild myself.
>
> Do you get the same issue without the lttng patches merged, i.e. when
> using the standard linaro-2.6.36 tree?
>
>
> Nicolas
>
Hey folks
I'd like to mirror and test the latest build of
http://snapshots.linaro.org/10.11-daily/linaro-headless/
but I have two issues with this:
* having some kind of direct link to the latest image so that I don't
need to parse the HTML to get the latest build; something like
/latest/ or /current/ would help here
* having a constant name for the data as to be rsync friendly; that is,
if the image is named linaro-m-headless-tar-20100923-0.tar.gz and
linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to
convince rsync that the data file from the 24th can be mostly
inferred from the contents of the 23th; if it was named
linaro-m-headless-tar.tar.gz, I would have no problem
Where should I be filing bugs to track these requests, and who should I
harass to get these resolved? :-)
Thanks!
--
Loïc Minier
Hello,
I am proud to announce a Debian sprint on embedded and ARM [0] which
will be discussing and working on embedded tools support, ARM for hard
float (armhf) support, multiarch support within Debian environment.
I thought you might be interested and you are welcome to come along.
If it is interesting to you, feel free to contact sprint organizers.
[0] http://wiki.debian.org/Sprints/2011/EmdebianSprint
Best regards,
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
As discussed below here's a page for listing your PPA for others to use.
https://wiki.linaro.org/DevelopersPPAs
Regards
Peter Pearse
---------- Forwarded message ----------
From: Alexandros Frantzis <alexandros.frantzis(a)linaro.org>
Date: Thu, Dec 2, 2010 at 11:17 AM
Subject: Re: Fwd: Tracking linaro PPAs
To: Peter Pearse <peter.pearse(a)linaro.org>
On Thu, Dec 02, 2010 at 09:58:50AM +0000, Peter Pearse wrote:
> Alexandros - did anything come of this?
>
> If not I'd be glad to start a wiki page to list usefule PPAs......
>
> Peter
>
>
Hi Peter,
although we (User Platforms) have created a team PPA, I am not sure if:
a. other teams have a similar policy
b. team members actually post everything in that PPA
So, I think the wiki page would be useful. I imagine such a page would
also assist in giving us a better overview of what is going on and
therefore help us to organize the PPAs better :)
Thanks,
Alexandros
All,
The weekly report for the Linaro Infrastructure team may be found at:-
Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-12-02
Burndown chart: This link is awaiting the production of new burndown charts.
The Infrastructure related blueprints from the maverick cycle, of which currently there are 4 active ones (4 from the last report), are showing that there are 8 work items in progress (8 last report), and 11 work items to undertake (11 last report). These are to be moved into the natty cycle if still required.
* arm-m-validation-dashboard; 0 work items completed since last report; 3 in progress; 7 to do
* arm-m-image-building-console; 0 work items completed since last report; 3 in progress; 3 to do
* arm-m-automated-testing-framework; no change in status from last report; 1 in progress; 0 to do
* arm-m-testsuites-and-profilers; no change in status from last report; 1 in progress; 1 to do
In the natty cycle, the following lists the current active Blueprints, or Blueprints planned and not started. Currently there are 4 active Blueprints (4 from the last report), which are showing that there are 8 work items in progress (7 last report), 41 work items to undertake (46 last report), 2 work items postponed (0 last report) and 8 work items added (all items added last report).
* other-linaro-n-improve-linaro-media-create: 2 work items completed; 3 work items in progress; 8 work items to do; 2 work items added.
* other-linaro-n-test-result-display-in-launch-control: 8 work item completed; 1 work item in progress; 10 work items to do; 4 work items added
* other-linaro-n-patch-tracking: 0 work item completed; 2 work items in progress; 9 work items to do
* other-linaro-n-image-building: 2 work items in progress; 5 work items to do; 2 work items postponed; 2 work items added
* other-linaro-n-continuous-integration: Not started - awaiting a Hudson build server (RT#42278).
* other-linaro-n-package-development-tools: Not Started; 9 work items to do
Specifics accomplished this week include:-
* Offspring (which used to be known as LexBuilder) has now been open sourced.
* other-linaro-n-image-building: progress being made on hwpacks
* ImproveLinaroMediaCreate: the ports of "ensure_command" and "unpack_binary_tarball" to Python have been completed.
Please let me know if you have any comments or questions.
Kind Regards,
Ian
Here's what the toolchain group has been doing:
* Atomic memory operations are finishing up. Preparing a coverage
report of operations vs data type for GCC and llvm
* IFUNC support is almost complete
* Discussed how to be a good community member. Will start reviewing
patches, sending test results, participating on the mailing list, and
look at making the tree more readily available
* Discussed QEMU Users Conference. Decided to participate but not
present due to no compelling topics
* Discussed bugs, blueprints and visibility. Group will start
properly updating bug status, and will at least weekly update
blueprint status
* Would like to acquire Snapdragon based development boards to
monitor how well our A9 focused work works on Qualcomm parts
Weekly meeting minutes are at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-11-29
Standup minutes are at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-12-01
Audio is here:
http://tc.seabright.co.nz/toolchainwg/
-- Michael
I've written up my notes on network booting the sevenx OMAP3
StageCoach board here:
https://wiki.linaro.org/MichaelHope/Sandbox/StagecoachBringup
I'm not currently using the Linaro kernel as either need a kernel with
USB Ethernet and NFS root built in, or a way of combining uImage and
uInitrd into one. Perhaps next week...
-- Michael