Hi all,
I'm interested in looking at some Bluetooth stuff on my OMAP 4460
Panda ES. Looking at the bug reports I don't see any Jelly Bean
releases that have BT working properly on Panda. Is this correct?
Can you please point me to a release where BT and display/hdmi are
working for Panda? It's OK if it is ICS.
I'm OK starting with binaries but I would much prefer to be able to
build from source and reproduce any known-good bins. I have already
built JB from the latest tip as well as the 13.07 manifest (display is
working fine but BT doesn't work, bugs already filed). I tried the
12.07 Panda LEB (which I think was the last ICS release?) but the
binaries supplied did not have display working even after running the
install-binaries-4.0.4.sh script.
Thanks,
Mike
Hi,
I don’t know I am in right channel to ask this question, if not then please
guide me.
Currently, I am following
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/UsingXdeb for
cross compiling using xdeb. I am using “raring” as a Ubuntu distribution.
So using above link, up to the section “Kick a build of grep and
build-deps”, everything goes perfectly.
But, this shows how to build any single package like grep, libpng, etc..
If I want to build (cross-compile) all the “raring” Ubuntu Distribution
package as one shot, how can I do??
Is there any tools available for cross compiling all packages ?? How can I
setup auto builder machine??
Please guide me as I am stuck in doing single package one by one.
Regards,
Gaurang Shastri
On 1 August 2013 20:46, Jon Medhurst (Tixy) <tixy(a)linaro.org> wrote:
> On Thu, 2013-08-01 at 17:40 +0100, Peter Maydell wrote:
>> On 1 August 2013 09:30, Ryan Harkin <ryan.harkin(a)linaro.org> wrote:
>> > The vexpress defconfig has always been broken.
>>
>> ...maybe we could fix it?
>
> It has been suggested that should be deleted as people can use the
> multiplatform defconfig (though I believe that is missing the regulator
> config for mmc as well).
>
> People have different ideas where various configs should live, boards
> specific defconfig, multiplatform defconfig or in Kconfig; and any
> particular change probably would have people arguing against it. And
> with vexpress we have the added complication thrown into the mix that
> people use it a lot with QEMU ;-)
For the kernel CI, we build all the defconfigs and boot test on
available platforms in LAVA lab.
Since vexpress_defconfig is known broken
(https://bugs.launchpad.net/linaro-ci/+bug/1212893),
what's the next step to move forward?
I'm trying to use flashbench to characterize a Kingston 8 GB data
traveler USB flash drive I have and am getting strange results. Could
someone help me understand how the diff can be negative? It seems that
the drive reads faster when crossing almost all boundaries rather than
slower:
psusi@arafel:/usr/share/doc/flashbench$ sudo flashbench -a
--blocksize=1024 /dev/sdb
align 2147483648 pre 766µs on 737µs post 869µs diff -80712n
align 1073741824 pre 783µs on 740µs post 850µs diff -76424n
align 536870912 pre 745µs on 737µs post 852µs diff -61441n
align 268435456 pre 748µs on 736µs post 846µs diff -61366n
align 134217728 pre 753µs on 739µs post 852µs diff -63074n
align 67108864 pre 747µs on 738µs post 849µs diff -59359n
align 33554432 pre 753µs on 739µs post 850µs diff -61974n
align 16777216 pre 764µs on 757µs post 866µs diff -57423n
align 8388608 pre 763µs on 758µs post 861µs diff -53705n
align 4194304 pre 764µs on 739µs post 847µs diff -66497n
align 2097152 pre 749µs on 740µs post 856µs diff -62748n
align 1048576 pre 811µs on 806µs post 902µs diff -50206n
align 524288 pre 809µs on 803µs post 910µs diff -56065n
align 262144 pre 810µs on 806µs post 909µs diff -53535n
align 131072 pre 809µs on 801µs post 909µs diff -57797n
align 65536 pre 811µs on 807µs post 908µs diff -52651n
align 32768 pre 809µs on 805µs post 907µs diff -53486n
align 16384 pre 808µs on 803µs post 862µs diff -31784n
align 8192 pre 808µs on 800µs post 882µs diff -45365n
align 4096 pre 809µs on 804µs post 803µs diff -1767ns
align 2048 pre 809µs on 808µs post 807µs diff -239ns
psusi@arafel:/usr/share/doc/flashbench$ sudo flashbench -a /dev/sdb
align 2147483648 pre 1.35ms on 1.36ms post 1.36ms diff 3.13µs
align 1073741824 pre 1.36ms on 1.35ms post 1.36ms diff -5105ns
align 536870912 pre 1.35ms on 1.35ms post 1.36ms diff -3044ns
align 268435456 pre 1.36ms on 1.35ms post 1.36ms diff -4602ns
align 134217728 pre 1.36ms on 1.36ms post 1.35ms diff 2.73µs
align 67108864 pre 1.36ms on 1.35ms post 1.36ms diff -4807ns
align 33554432 pre 1.35ms on 1.36ms post 1.36ms diff 1.34µs
align 16777216 pre 1.37ms on 1.36ms post 1.38ms diff -15503n
align 8388608 pre 1.37ms on 1.37ms post 1.37ms diff 1.2µs
align 4194304 pre 1.35ms on 1.35ms post 1.36ms diff -734ns
align 2097152 pre 1.37ms on 1.36ms post 1.35ms diff -1662ns
align 1048576 pre 1.37ms on 1.37ms post 1.37ms diff -2851ns
align 524288 pre 1.37ms on 1.38ms post 1.37ms diff 1.69µs
align 262144 pre 1.37ms on 1.37ms post 1.38ms diff 146ns
align 131072 pre 1.38ms on 1.37ms post 1.37ms diff -3798ns
align 65536 pre 1.38ms on 1.37ms post 1.38ms diff -2426ns
align 32768 pre 1.37ms on 1.37ms post 1.37ms diff -3169ns
On 08/16/2013 03:57 AM, Dai Yan wrote:
> sorry about that I didn't express explicity.
> what I wrote is cp15 c15 regsiter .
> And I found that it cannont be written on my adndale board .
Those would be implementation defined registers which I don't have much
experience with. My only suggestions would be to check for hypervisor traps
and read and re-read the chip-specific and architecture documentation.
Christopher
> 2013/8/16 Dai Yan <kanshuzhi(a)gmail.com <mailto:kanshuzhi@gmail.com>>
>
> Could someone help me with that?
> Previously i always do writing the register from kernel modules but always
> failed.
>
>
>
> 2013/8/16 Dai Yan <kanshuzhi(a)gmail.com <mailto:kanshuzhi@gmail.com>>
>
> it seems that the all of cp15 registers cannot be written,
> I try write it from kernel space(module).
>
> Best Regards
>
>
> 2013/8/15 Christopher Covington <cov(a)codeaurora.org
> <mailto:cov@codeaurora.org>>
>
> Hi Dai,
>
> On 08/15/2013 08:15 AM, Dai Yan wrote:
> > Hello,
> >
> > Maybe it's a stupid question.
> >
> > I want to modify cp15 register.
>
> Which register?
>
> > but I found that the register cannont be written,it can ony be read.
>
> Is this from user space or kernel space?
>
> > Could someone help me with that?
> >
> > distribute version: ubnuntu linaro 13.07 arndale board
> >
> > kernel:3.10.2+
>
> Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
Hello,
Maybe it's a stupid question.
I want to modify cp15 register.
but I found that the register cannont be written,it can ony be read.
Could someone help me with that?
distribute version: ubnuntu linaro 13.07 arndale board
kernel:3.10.2+
Best Regards
The following patches extend accurate time much further back into
the boot process by adding an optional arch_early_time source that
starts counting about 1.75ms after the MMU is enabled.
This exposes currently hidden kernel boot times exceeding 340ms for a 2GByte
dual A9.
Currently only Arm globaltimer is supported as the early time source.
Where the globaltimer is and how to map it is configured by
Device Tree as explained in the second patch.
To get monotonic time in the kernel starting from before the normal time
source can be initialized, the early time source offset is allowed to be
added to scheduler clock time in the first patch.
---
Andy Green (2):
scheduler: time: allow arch-specific time offset function
arm: time: add globaltimer-based arch_early_time
arch/arm/Kconfig | 16 ++++++
arch/arm/Kconfig.debug | 10 ++++
arch/arm/boot/dts/mb8ac0300eb.dts | 10 +++-
arch/arm/configs/fujitsu_defconfig | 2 +
arch/arm/include/asm/memory.h | 8 +++
arch/arm/kernel/devtree.c | 1
arch/arm/kernel/setup.c | 50 ++++++++++++++++++
arch/arm/kernel/time.c | 101 ++++++++++++++++++++++++++++++++++++
arch/arm/mach-mb8ac0300/Kconfig | 3 +
arch/arm/mm/mmu.c | 49 +++++++++++++++++
include/linux/time.h | 7 ++
kernel/sched/clock.c | 12 ++--
mm/Kconfig | 2 -
13 files changed, 263 insertions(+), 8 deletions(-)
--