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(-)
--
Hi, Mattia
Sorry, I do not know much about the things you talked about.
Maybe someone else can help to give you the details.
Thanks,
Yongqin Liu
On 10 August 2013 23:26, Mattia Ruggeri <mattia.ruggeri88(a)gmail.com> wrote:
> Hello Mr Liu
>
> I'm Mattia and i'm writing you about Lava Dispatcher (a Linaro project): I
> think this project is perfect and it is the way to solve my issue with
> Huawei G615 (a K3v2 processor device ).
>
> Yesterday Huawei released kernel source code and some of us would love to
> build custom roms.
> Since Huawei blocked bootloader, it's impossible for us to install custom
> roms and kernel. I saw Lava Dispatcher is able to interact with bootloader,
> maybe it can allow us to "bypass" this restriction.
>
> could you help us with this?
>
> thank you
> regards,
>
--
Thanks,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/pipermail/linaro-validation
The following patches introduce a debug feature, accurate timestamps
on all kernel logs during boot.
At the moment until time is set up in the kernel, all logs are timestamped
[0.000000] giving the impression these early boot activities have no duration.
That's far from the case.
These patches give accurate, monotonic timestamps from the very first log
entry allowing insight into where the time is going during the whole of
the boot process.
It's a debug feature like DEBUG_LL, it does not cooperate with
ARCH_MULTIPLATFORM (it works with such a kernel though) but can only be enabled
for a single platform at compile-time.
To use it, you need an ARM SoC with a globaltimer, which is very common now.
Even if the globaltimer is used by the kernel, we can use it in early boot
and stop using it as soon as a normal time source is set up, so there's no
conflict.
There are more details on how to use it and examples of the results
in the second patch.
---
Andy Green (2):
scheduler: time: allow arch-specific time offset function
arm: time: add globaltimer-based arch_early_time
arch/arm/Kconfig | 4 +++
arch/arm/Kconfig.debug | 35 ++++++++++++++++++++++++++
arch/arm/kernel/head.S | 65 ++++++++++++++++++++++++++++++++++++++++++++++++
arch/arm/kernel/time.c | 41 ++++++++++++++++++++++++++++++
include/linux/time.h | 6 ++++
kernel/sched/clock.c | 12 ++++-----
6 files changed, 157 insertions(+), 6 deletions(-)
--
Hi all,
There is currently a thread on LAKML that once again touches on the
issue of automated build/boot testing:
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/257669
There seemed to be some good discussions between the LAVA team and
Kevin at LCE13 and I wanted to make others are aware of this thread
(and possibly of automated testing being a topic at the ARM Summit).
Regards,
Mike