Hi guys,
i tried cpuhotplug on pandaboard for both
Pandroid_Froyo_L27.8.2_release_pkg and Linaro 11.11. It has failed to
work stably.
On Pandroid_Froyo_L27.8.2_release_pkg, unplugging cpu1 works well:
# echo 0 > /sys/devices/system/cpu/cpu1/online
CPU1: shutdown
if i enable the cpu1 again by "echo
2011/12/21 Russell King - ARM Linux :
> On Wed, Dec 21, 2011 at 05:23:48PM +0800, Barry Song wrote:
>> Hi guys,
>> i tried cpuhotplug on pandaboard for both
>> Pandroid_Froyo_L27.8.2_release_pkg and Linaro 11.11. It has failed to
>> work stably.
>> On Pandroid_Froy
Hi guys,
I compile a native gdb using linaro 2011.10 by “./configure
--host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi”, and
the gdb runs on arm target boards directly.
# gdb
GNU gdb (Linaro GDB) 7.3-2011.10
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL versi
Hi Ulrich,
2012/2/3 Ulrich Weigand :
> Barry Song <21cn...@gmail.com> wrote:
>
>> So my questions are:
>>
>> 1. Should I compile the native gdb using android toolchain and android
>> bionic/libthread libraries?
>> 2. Why can’t the current gdb cap
2012/2/3 Thiago Jung Bauermann :
> Hi Barry,
>
> On Thu, 2012-02-02 at 10:23 +0800, Barry Song wrote:
>> 2. Why can’t the current gdb capture multithreads for android
>> processes? This question is actually about the theory for gdb to know
>> multi-threads. In my op
Ulrich,
thanks a lot!
2012/2/4 Ulrich Weigand :
> Barry Song <21cn...@gmail.com> wrote.
>> 2012/2/3 Ulrich Weigand :
>> > However, from looking at the gdbserver sources provided with Android,
>> > it seems there are some differences; in particular, there&#x
hi yang,
在 2012年3月10日 下午10:37，yang gqyang 写道：
> Thanks for your comment.
> Finally, i find out that i made a mistake. The uart(8250) have not been
> restore after resume, instead, it use the configuration got from boot. The
> uart have not been restored correctly, so that "ls" can not output
2011/6/14 Linus Walleij :
> From: Linus Walleij
>
> This adds a driver for the U300 pinmux portions of the system
> controller "SYSCON". It also serves as an example of how to use
> the pinmux subsystem. This driver also houses the platform data
> for the only supported platform.
>
> Signed-off-by
Hi Linus,
>> diff --git a/Documentation/ABI/testing/sysfs-class-pinmux
>> b/Documentation/ABI/testing/sysfs-class-pinmux
>> new file mode 100644
>> index 000..c2ea843
>> --- /dev/null
>> +++ b/Documentation/ABI/testing/sysfs-class-pinmux
>> @@ -0,0 +1,11 @@
>> +What: /sys/class/pinmu
Hi Linus,
Looks pretty good. just some minors.
2011/8/19 Linus Walleij :
> From: Linus Walleij
>
> This adds a driver for the U300 pinmux portions of the system
> controller "SYSCON". It also serves as an example of how to use
> the pinmux subsystem. This driver also houses the platform data
> fo
> - Rewrite the interaction with the GPIO subsystem - the pin
> controller descriptor now handles this by defining an offset
> into the GPIO numberspace for its handled pin range. This is
> used to look up the apropriate pin controller for a GPIO pin.
> Then that specific GPIO range is matched
> +
> +Pinmux board/machine configuration
> +==
> +
> +Boards and machines define how a certain complete running system is put
> +together, including how GPIOs and devices are muxed, how regulators are
> +constrained and how the clock tree looks. Of course pinmux set
Hi Linus,
This patch can't compile
> +
> +/**
> + * @dev: a pointer back to containing device
> + * @virtbase: the offset to the controller in virtual memory
> + */
> +struct u300_pmx {
> + struct device *dev;
> + struct pinmux_dev *pmx;
no this structure in head file, now it is pi
> +int foo_list(struct pinmux_dev *pmxdev, unsigned selector)
pinctrl_dev?
> +{
> + if (selector >= ARRAY_SIZE(myfuncs))
> + return -EINVAL;
> + return 0;
> +}
> +
> +const char *foo_get_fname(struct pinmux_dev *pmxdev, unsigned selector)
pinctrl_dev?
> +{
> + if
> +/**
> + * @dev: a pointer back to containing device
> + * @virtbase: the offset to the controller in virtual memory
> + */
> +struct u300_pmx {
> + struct device *dev;
> + struct pinmux_dev *pmx;
pinctrl_dev?
> +static int u300_pmx_enable(struct pinmux_dev *pmxdev, unsigned select
2011/8/22 Linus Walleij :
> On Sun, Aug 21, 2011 at 4:42 PM, Barry Song <21cn...@gmail.com> wrote:
>
>> it seems there is not an actual example that gpio requests pin from
>> pinctrl yet. i might give one on SiRFprimaII.
>
> No good example yet, no.
>
> The re
es
> Cc: Russell King
> Signed-off-by: Linus Walleij
Tested-by: Barry Song
even there are still many discussions about data model and
device/function mapping, it is basically usable to CSR SiRFprimaII.
Then i moved the old prima2 pinmux to this framework and made some
basic tests.
Basi
> +Interaction with the GPIO subsystem
> +===
> +
> +The GPIO drivers may want to perform operations of various types on the
> same
> +physical pins that are also registered as GPIO pins.
> +
> +Since the pin controller subsystem have its pinspace local to the pin
>
2011/9/13 Linus Walleij :
> On Fri, Sep 2, 2011 at 6:04 PM, Stephen Warren wrote:
>> Linus Walleij wrote at Friday, September 02, 2011 2:12 AM:
>>> On Thu, Sep 1, 2011 at 11:33 PM, Stephen Warren wrote:
>>>
>>> >> +static const struct u300_pmx_func u300_pmx_functions[] = {
>>> >> + {
>>> >> +
> +static int __init u300_pmx_probe(struct platform_device *pdev)
> +{
> + int ret;
> + struct u300_pmx *upmx;
> + struct resource *res;
> +
> + /* Create state holders etc for this driver */
> + upmx = devm_kzalloc(&pdev->dev, sizeof(struct u300_pmx), GFP_KERNEL);
an
> +static void __init u300_pmx_dumpregs(struct u300_pmx *upmx)
> +{
> + u16 regval;
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(u300_pmx_registers); i++) {
> + regval = readw(upmx->virtbase + u300_pmx_registers[i]);
> + dev_info(upmx->dev, "PMX%u: 0x%
2011/10/10 Linus Walleij :
> On Sat, Oct 8, 2011 at 11:09 AM, Barry Song <21cn...@gmail.com> wrote:
>>> +static void __init u300_pmx_dumpregs(struct u300_pmx *upmx)
>>> +{
>>> + u16 regval;
>>> + int i;
>>> +
>>
ups and corresponding functions. The idea
> is to use this driver as a a reference for other
> implementation so it needs to be as complete and verbose
> as possible.
>
> Signed-off-by: Linus Walleij
Reviewed-by: Barry Song <21cn...@gmail.com>
> ---
> ChangeLog v9 -> v
2011/10/20 Shawn Guo :
>> #ifdef CONFIG_DEBUG_FS
>>
>> static int pinctrl_pins_show(struct seq_file *s, void *what)
>> diff --git a/include/linux/pinctrl/pinctrl.h
>> b/include/linux/pinctrl/pinctrl.h
>> index 4f8d208..189c047 100644
>> --- a/include/linux/pinctrl/pinctrl.h
>> +++ b/include/linu
2011/10/20 Stephen Warren :
> A pin controller's pin definitions are used both during pinctrl_register()
> and pinctrl_unregister(). The latter happens outside of __init/__devinit
> time, and hence it is unsafe to mark the pin array as __refdata.
Thanks.
Acked-by: Barry Song
mi
change to make it work:
powertop: fix segment fault for single cpu env
Signed-off-by: Barry Song
diff --git a/cpu/cpu.cpp b/cpu/cpu.cpp
index 29fc72c..c56c746 100644
--- a/cpu/cpu.cpp
+++ b/cpu/cpu.cpp
@@ -302,6 +302,9 @@ void enumerate_cpus(void)
model
g have i missed?
>
> Thanks,
> Amit Daniel
>
>
> On 12 December 2011 15:55, Barry Song <21cn...@gmail.com> wrote:
>> Hi Tony/Amit,
>> anybody has tried to use powertop from linaro on a single core ARM
>> SoC? What i am using is
>> git://android
ok now. the reason is the powertop depends on
CONFIG_EVENT_POWER_TRACING_DEPRECATED, after selecting it, powertop
gets to work on SiRFprimaII.
Thanks
barry
2011/12/14 Barry Song <21cn...@gmail.com>:
> Hi Amit,
>
> Thanks!
>
> 2011/12/12 Amit Kachhap :
>> Hi Barry,
>&
Hi All,
I am a freshman to linaro. I found people sent some patches to
linaro-dev@lists.linaro.org. Here I have 2 questions:
1. Whether will linaro send those patches based on newest tree to
Linus' mainline or not? Or developers need to send those patches to
mainline by themselves?
Is there any do
ree. If they are not going upstream, then the
> chances are they won't be accepted into the Linaro tree either.
>
> [1] http://vger.kernel.org/vger-lists.html
>
> Kind regards,
> Lee
>
--
Barry Song, Linux Kernel Developer
http://21cnbao.blog.51cto.com
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Thanks. Amit.
2011/3/8 Amit Kucheria :
> On Tue, Mar 8, 2011 at 10:34 AM, Barry Song <21cn...@gmail.com> wrote:
>> Hi Lee,
>> Great! Thanks a lot. It looks like the communication between linaro
>> and mainline is that linaro can backport some bug fixes and features
>
Thanks. Amit.
2011/3/9 Lee Jones :
> On 09/03/11 02:44, Barry Song wrote:
>> Thanks. Amit.
>>
>> 2011/3/8 Amit Kucheria :
>>> On Tue, Mar 8, 2011 at 10:34 AM, Barry Song <21cn...@gmail.com> wrote:
>>>> Hi Lee,
>>>> Great! Thanks a
n last week, and my
> email backlog is incredibly large. I'm going through it with generous
> usage of the delete key so it is possible that I might have missed
> something.
>
> On Fri, 11 Mar 2011, Barry Song wrote:
>
>> 2011/3/9 Lee Jones :
>> > On 09/03/11
Hi all,
it is easy to get toolchain/uboot/kernel/android source codes. but i
have been really searching all over the website but still fail to get
source codes of pm(expect powerdebug last updated 6 weeks ago),
multimedia, graphics. so i am really difficult to find delivery of pm,
multimedia, graph
Hi Amit,
Thanks very much for your reply.
2011/5/20 Amit Kucheria :
> On 11 May 19, Barry Song wrote:
>> Hi all,
>> it is easy to get toolchain/uboot/kernel/android source codes. but i
>> have been really searching all over the website but still fail to get
>> source co
Hi all,
i am using linaro uboot(u-boot-linaro-stable.git). i have let our
prima2 board support device tree with some workaround in uboot. two
problems i have meet:
1. device tree without ramdisk
now uboot used commands like
"bootm kernel_address ramdisk_address dtb_address"
to start linux kernel
hi Shawn,
thanks a lot.
-barry
2011/5/27 Shawn Guo :
> On Fri, May 27, 2011 at 04:52:38PM +0800, Barry Song wrote:
>> Hi all,
>> i am using linaro uboot(u-boot-linaro-stable.git). i have let our
>> prima2 board support device tree with some workaround in uboot. two
>>
Dear Jim,
After changing TARGET_TOOLS_PREFIX in
build/core/combo/TARGET_linux-arm.mk to
android-toolchain-eabi-4.5-2011.05, then source build/envsetup.sh. go
to dalvik/vm dir by:
cd dalvik/vm
compile dalvik in this dir:
mm -B
we will find many compiling error like: "break strict-aliasing rules",
"u
38 matches
Mail list logo
