Hi all,
To support the new Linaro roadmap process, the Infrastructure team has
added new reports to status.linaro.org.
You can find the status for the current quarter here and drill down
into the cards targeted for Q4.
http://status.linaro.org/11.11/roadmap-2011Q4.html
There's of course work
As per new conventions Samsung SoC's are named as Exynos.
Cortex-A9 based Soc's are named as exynos4. s5pc2xx is cortex-A9
based, hence renamed to exynos4. This is done as per kernel
naming convetions.
Similerly s5pc210 is now exynos4210. Hence S5PC210/s5pc210
suffix/prefix has been renamed to exy
Hi, All
ICS has changed its default shell to mksh.
and the source of mksh is under ${AOSP}/external/mksh.
In ICS, mksh use /system/etc/mkshrc as the default profile if we log into
android with adb shell or on the serial console.
so if we want to export some environment variable like(PS1), we can c
Dear Chander Kashyap,
On 24 November 2011 19:48, Chander Kashyap wrote:
> As per new conventions Samsung SoC's are named as Exynos.
> Cortex-A9 based Soc's are named as exynos4. s5pc2xx is cortex-A9
> based, hence renamed to exynos4. This is done as per kernel
> naming convetions.
>
> Similerly s
On Fri, Nov 18, 2011 at 02:54:09PM +0530, Ashish Jangam wrote:
> Driver for DA9052 battery charger. This driver depends on DA9052 MFD core
> dirver
> for definitions and methods.
>
> Tested on Samsung SMDK6410 board with DA9052-BC and DA9053-BA evaluation
> boards.
>
> Signed-off-by: David Daju
Riku,
On 24 November 2011 13:32, Riku Voipio wrote:
> Hi,
>
> Just to let you all know, due to the ongoing multiarch work, it is not
> possible to cross-compile
> relatively complex packages in ubuntu. For example, following the
> instructions[1], Firefox.
Out of curiosity and having a few minu
Hi,
* Linus Walleij [24 01:29]:
> On Tue, Nov 22, 2011 at 6:54 PM, Tony Lindgren wrote:
>
> > Note that with device tree things get simpler for muxing as we can
> > get rid of the hardcoded grouping of pins in mux drivers. Instead of
> > hardcoded pingroups, the groups can be created dynami
On 24 November 2011 15:32, Riku Voipio wrote:
> Just to let you all know, due to the ongoing multiarch work, it is not
> possible to cross-compile
And of course I mean "now possible" ..
Riku
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http
Hi,
Just to let you all know, due to the ongoing multiarch work, it is not
possible to cross-compile
relatively complex packages in ubuntu. For example, following the
instructions[1], Firefox. While
building on oneiric, patched packages from the linaro-maintainers
overlay are needed, many of
those
On 24 November 2011 12:38, Shilimkar, Santosh wrote:
> On Wed, Nov 23, 2011 at 6:55 AM, Andy Green wrote:
>> On 11/22/2011 08:57 PM, Somebody in the thread at some point said:
>>>
>>> On Tue, Nov 22, 2011 at 6:02 PM, Mans Rullgard
>>> wrote:
So keep them on by default but allow them to be t
On Wed, Nov 23, 2011 at 6:55 AM, Andy Green wrote:
> On 11/22/2011 08:57 PM, Somebody in the thread at some point said:
>>
>> On Tue, Nov 22, 2011 at 6:02 PM, Mans Rullgard
>> wrote:
>>>
>>> On 22 November 2011 05:14, Shilimkar, Santosh
>>> wrote:
Mans,
On Tue, Nov 22, 2011 a
Hello.
Here is the weekly status report from the Android Platform Team.
Key Points for wider discussion
===
* Android 2.3.7 Platform Release 11.11 complete and tested on all boards.
* Android 4.0 ICS up and running on Snowball.
Team Highlights
==
On Fri, Nov 18, 2011 at 02:49:54PM +0530, Ashish Jangam wrote:
There's still a few issues in here. It'd be very much easier to review
this stuff if you split the patch down into smaller patches, for example
having the ADC, SPI and I2C as separate patches. The bigger each
individual e-mail is the
As per new conventions Samsung SoC's are named as Exynos.
Cortex-A9 based Soc's are named as exynos4. s5pc2xx is cortex-A9
based, hence renamed to exynos4. This is done as per kernel
naming convetions.
Similerly s5pc210 is now exynos4210. Hence S5PC210/s5pc210
suffix/prefix has been renamed to EXY
I just downloaded directfb-1.6.0pre1-2011.11.tar.bz2 from [1] and wonder
what are the build options for this?
I.e. what are the best/tested/recommended configure/compile options for
this? And maybe which compiler to use (if this matters ;) )?
Are there any binary packages available, too?
M
On Wed, Nov 23, 2011 at 1:28 AM, Stephen Warren wrote:
> Describing the HW doesn't necessarily
> mean that each device needs to describe what pinmux pins it uses; one
> could quite easily have the pinmux describe what settings the various
> pins should have and which drivers will use those pins.
On Tue, Nov 22, 2011 at 6:54 PM, Tony Lindgren wrote:
> Note that with device tree things get simpler for muxing as we can
> get rid of the hardcoded grouping of pins in mux drivers. Instead of
> hardcoded pingroups, the groups can be created dynamically based on
> what the driver DT entries have
17 matches
Mail list logo
