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
RAG:
Red:
Amber:
Green:
Milestones:
| Planned| Estimate | Actual |
finish virtio-system | 2010-08-27 | postponed ||
get valgrind into linaro PPA | 2010-09-15 | 2010-09-28 | 2010-09-28 |
complete a qemu-maemo update | 2010-09-24 | 2010-09-
== This week ==
* Looked at a generic bug in GAS's handling of ifuncs. Sent a patch upstream:
http://sourceware.org/ml/binutils/2010-11/msg00495.html
Alan quite reasonably wanted me to test on a variety of targets. For want
of anything better, I wrote a script to test Alan's list of 11
* Benchmarking of simple package builds with various string routine
versions; not finding enough difference in the noise to make any large
conclusions
* Looking at the string routine behaviour with perf to see where the time
is going
- getting hit by the Linaro kernels on silverbell missin
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
Hi,
* got llvm+clang working on ARM:
https://wiki.linaro.org/KenWerner/Sandbox/HowToBuildToolchainComponents#llvm+clang
* checked whether llvm inlines the __sync_* builtins on ARM or not:
https://wiki.linaro.org/WorkingGroups/ToolChain/AtomicMemoryOperations#LLVM
* developed a patch for
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
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
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
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,
On Thu, Dec 2, 2010 at 9:49 PM, Michael Hope wrote:
> Hi there. Currently you can't use NEON instructions in inline
> assembly if the compiler is set to -mfpu=vfp such as Ubuntu's
> -mfpu=vfpv3-d16. Trying code like this:
>
> int main()
> {
> asm("veor d1, d2, d3");
> return 0;
> }
>
>
On Fri, 2010-12-03 at 10:49 +1300, Michael Hope wrote:
> Hi there. Currently you can't use NEON instructions in inline
> assembly if the compiler is set to -mfpu=vfp such as Ubuntu's
> -mfpu=vfpv3-d16. Trying code like this:
>
> int main()
> {
>asm("veor d1, d2, d3");
>return 0;
> }
>
>
12 matches
Mail list logo
