Hi Jeremy,
This is latest one for review. I add some minor changes in.
Cheers
Yong
>From efe7fa8bea67f9bf532c0074a92d938e6d6f4c5d Mon Sep 17 00:00:00 2001
From: Yong Shen
Date: Thu, 18 Nov 2010 14:54:49 +0800
Subject: [PATCH] export clock debug information to user space
create a tree-like dire
On Fri, Dec 3, 2010 at 1:30 PM, Yong Shen wrote
> Hi Jeremy,
>
> This is latest one for review. I add some minor changes in.
>
> Cheers
> Yong
Yong,
It helps reviewers if you version your patches (PATCHv1, PATCHv2,
etc.) and you list the changes made in each version in the changelog.
See http:/
Hi, Kernel WG,
Can recent kernel handle NEON registers in corefiles?
Seems we've had plan for this in "Ensure full NEON debug support" in
https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Specs/BSPInvestigations
Any progress on this piece of work? We want to handle NEON registers in
core
Hi Amit,
That's a good reminding. About version number, I am using it in all my
code reviews in different mail list now. About this patch, I planed to
send out a 'v2', however it had been a while since last review, so I
expect a new start.
But I do need to mention the changes.
Changes from last ro
Hi,
notes and actions from our Monday graphics cross-vendor call are
available on the wiki:
+ https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2010-11-22
+ https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2010-11-29
Details about when and where of this meeting can
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,
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
Date: Thu, Dec 2, 2010 at 11:17 AM
Subject: Re: Fwd: Tracking linaro PPAs
To: Peter Pearse
O
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
On Fri, Dec 3, 2010 at 9:06 AM, Yao Qi wrote:
> Hi, Kernel WG,
> Can recent kernel handle NEON registers in corefiles?
>
> Seems we've had plan for this in "Ensure full NEON debug support" in
> https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Specs/BSPInvestigations
> Any progress on this
Hi all,
I'd be interested in people's views on the following idea-- feel free
to ignore if it doesn't interest you.
For power-management purposes, it's useful to be able to turn off
functional blocks on the SoC.
For on-SoC peripherals, this can be managed through the driver
framework in the ker
Recapping on an old discussion here...
On Fri, Sep 24, 2010 at 6:49 PM, Loïc Minier wrote:
> 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
Dave,
For the case of NEON and its use in graphics libraries, we are certainly
pushing explicitly for runtime detection. However, this tends to be done by
detecting the presence of NEON at initialization time, rather than at each
path invocation (to avoid rescanning /proc/self/auxv). Are you say
On Fri, Dec 03, 2010, Dave Martin wrote:
> Having "latest" or "current" aliases can cause traceability problems
> if having mirrored the files, you can't determine which actual
> build/release it was.
We can include a build id in the image itself to help with this; we can
also keep a map of MD5S
Hi,
On Fri, Dec 3, 2010 at 4:51 PM, Russell King - ARM Linux
wrote:
> On Fri, Dec 03, 2010 at 04:28:27PM +, Dave Martin wrote:
>> For on-SoC peripherals, this can be managed through the driver
>> framework in the kernel, but for functional blocks of the CPU itself
>> which are used by instruc
Hi,
On Fri, Dec 3, 2010 at 4:51 PM, Loïc Minier wrote:
> On Fri, Dec 03, 2010, Dave Martin wrote:
>> Having "latest" or "current" aliases can cause traceability problems
>> if having mirrored the files, you can't determine which actual
>> build/release it was.
>
> We can include a build id in th
On Fri, Dec 03, 2010 at 04:28:27PM +, Dave Martin wrote:
> For on-SoC peripherals, this can be managed through the driver
> framework in the kernel, but for functional blocks of the CPU itself
> which are used by instruction set extensions, such as NEON or other
> media accelerators, it would b
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 inc
On Fri, 3 Dec 2010, Dave Martin wrote:
> On Fri, Dec 3, 2010 at 9:06 AM, Yao Qi wrote:
> > Hi, Kernel WG,
> > Can recent kernel handle NEON registers in corefiles?
> >
> > Seems we've had plan for this in "Ensure full NEON debug support" in
> > https://wiki.linaro.org/WorkingGroups/KernelConsolid
The following changes since commit 61cb9ff7af265a28043724678b4d3b0482c2e525:
LINARO: Linaro-2.6.35.1008.13 (2010-10-22 07:02:42 -0600)
are available in the git repository at:
git://git.linaro.org/ubuntu/linux-meta-linaro.git master
John Rigby (1):
LINARO: Linaro-2.6.35.1010.14
meta-s
19 matches
Mail list logo
