On 03/29/2012 11:25 PM, John Stultz wrote:
On 03/28/2012 09:37 PM, Tushar Behera wrote:
On 03/28/2012 10:17 PM, John Stultz wrote:
On 03/28/2012 05:24 AM, Tushar Behera wrote:
On 03/27/2012 12:50 AM, John Stultz wrote:
So after talking about it at the last Linaro Connect, I've
finally
(2012年03月22日 15:45), Shawn Guo wrote:
+};
+
+regulator-1p1@110 {
+compatible = fsl,anatop-regulator;
+regulator-name = vdd1p1;
+
Any update on this patch?
On Tue, 2012-03-13 at 17:58 +0530, Ashish Jangam wrote:
Any update on below patch?
On Mon, 2012-02-06 at 18:16 +0530, Ashish Jangam wrote:
DA9052/53 PMIC has capability to supply power for upto 3 banks of 6
white serial LEDS. It can also control intensity of
Any update on this patch?
On Tue, 2012-03-13 at 17:57 +0530, Ashish Jangam wrote:
Any update on below patch?
On Mon, 2012-02-06 at 18:18 +0530, Ashish Jangam wrote:
This driver adds support for the watchdog functionality provided by the
Dialog Semiconductor DA9052/53 PMIC chip.
This
HI ALL:
My device run the android4.0.3，and the show toucher in developer options
is default active,
how can i disable it when config my OS ? in the build.prop or other files to
modify?
pelease help!
2012-03-30
Peter Lai/ SmartFire
Hi Ashish,
Some comments / suggestions .
On Friday 30 March 2012 03:02 PM, Ashish Jangam wrote:
Any update on this patch?
On Tue, 2012-03-13 at 17:57 +0530, Ashish Jangam wrote:
Any update on below patch?
On Mon, 2012-02-06 at 18:18 +0530, Ashish Jangam wrote:
This driver adds support for
The usual cpuidle initialization routines are to register the
driver, then register a cpuidle device per cpu.
With the device's state count default initialization with the
driver's state count, the code initialization remains mostly the
same in the different drivers.
We can then add a new
Friday is the day to come fix ARM bugs.
Apparently we still have some!
(110 in total, 90 FTBFS):
http://people.linaro.org/~rsalveti/arm-porting-queue/arm-porting-queue-report.html
And all this work is showing results: the sun came out in Debian armhf
(meaning that 99% of the archive is
On Fri, Mar 30, 2012 at 11:49:17AM +0100, Wookey wrote:
Friday is the day to come fix ARM bugs.
Apparently we still have some!
(110 in total, 90 FTBFS):
http://people.linaro.org/~rsalveti/arm-porting-queue/arm-porting-queue-report.html
And all this work is showing results: the sun came out in
On 03/30/2012 01:25 PM, Srivatsa S. Bhat wrote:
On 03/30/2012 04:18 PM, Daniel Lezcano wrote:
The usual cpuidle initialization routines are to register the
driver, then register a cpuidle device per cpu.
With the device's state count default initialization with the
driver's state count, the
On 03/30/2012 04:18 PM, Daniel Lezcano wrote:
The usual cpuidle initialization routines are to register the
driver, then register a cpuidle device per cpu.
With the device's state count default initialization with the
driver's state count, the code initialization remains mostly the
same in
From: Ying-Chun Liu (PaulLiu) paul@linaro.org
Add anatop regulators to imx6q.dtsi for all imx6q platforms.
Signed-off-by: Ying-Chun Liu (PaulLiu) paul@linaro.org
Signed-off-by: Richard Zhao richard.z...@linaro.org
Cc: Shawn Guo shawn@linaro.org
---
arch/arm/boot/dts/imx6q.dtsi |
'domain_destroy with devices attached' case isn't yet handled, instead
code assumes that the device was already detached.
If the domain is destroyed the hardware still has access to invalid
pointers to its page table and internal iommu object. In order to
detach the users we need to track devices
Hi,
If you have the hwpack, I found the config available in the
linux-image*.deb in the boot directory.
-Ash
On Thu, Mar 22, 2012 at 11:49 PM, AKS aungk...@gmail.com wrote:
Hi
I would like to request a working .config file for Gumstix
Overo Tide COM board to cross compile a custom kernel
'domain_destroy with devices attached' case isn't yet handled, instead
code assumes that the device was already detached.
If the domain is destroyed the hardware still has access to invalid
pointers to its page table and internal iommu object. In order to
detach the users we need to track devices
On 03/30/2012 01:59 PM, Srivatsa S. Bhat wrote:
On 03/30/2012 05:15 PM, Daniel Lezcano wrote:
On 03/30/2012 01:25 PM, Srivatsa S. Bhat wrote:
On 03/30/2012 04:18 PM, Daniel Lezcano wrote:
The usual cpuidle initialization routines are to register the
driver, then register a cpuidle device
On 03/29/2012 09:57 PM, Tushar Behera wrote:
The new log messages are because of this config entry.
CONFIG_PROVE_LOCKING=y
But the information is useful, hence better it stays that way.
Yea. The lockdep output is super useful for catching really hard to
trigger bugs. Take those warnings
On 03/30/2012 01:19 AM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-03-29 at 11:00 -0700, John Stultz wrote:
On 03/29/2012 02:22 AM, Jon Medhurst (Tixy) wrote:
John, I've attached a config fragment for Versatile Express.
Great! I've merged that in! There's a few warnings though:
Value requested
On Fri, 2012-03-30 at 09:33 -0700, John Stultz wrote:
On 03/30/2012 01:19 AM, Jon Medhurst (Tixy) wrote:
To do that the vexpress config fragment will need to be a topic branch
on the ARM Landing Teams git, and every topic which changes a config
needs to be stacked on top of that. Is that
On 03/30/2012 10:07 AM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-03-30 at 09:33 -0700, John Stultz wrote:
On 03/30/2012 01:19 AM, Jon Medhurst (Tixy) wrote:
To do that the vexpress config fragment will need to be a topic branch
on the ARM Landing Teams git, and every topic which changes a
On 03/30/2012 12:00 AM, Tushar Behera wrote:
Right, some of the config options should better move to the feature
branches. I have cleaned up origen.conf so that we can now boot
linux-linaro-tracking kernel till the console. Code dropped at [1].
With the help of a couple of patches[2], I was
21 matches
Mail list logo
