init.rc usage example:
mount vfat mmc@blk1p3 /mnt/sdcard2
---
init/builtins.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/init/builtins.c b/init/builtins.c
index e0ccf9f..32d9d7f 100644
--- a/init/builtins.c
+++ b/init/builtins.c
@@ -356,6 +356,16 @@ int
On Wed, Feb 23, 2011, Andy Green wrote:
> Over the longer term I think it could be possible to arrange things that
> - hwpacks as they are
> - initrds, and
> - Qemu requirement for image composition, maybe whole l-m-c
> could in most or all cases be dispensed with. In that situation
> l-m-c its
The following changes since commit 239a14a340ad4a81cfff4075625382d7f78f5258:
(Rebased against git://git.linaro.org/kernel/linux-linaro-2.6.38.git)
Merge commit 'v2.6.38-rc6' into linaro-2.6.38 (2011-02-22 22:26:28 -0500)
are available in the git repository at:
git://git.linaro.org/people/dm
On Wed, Feb 23, 2011 at 10:45 AM, Jim Huang wrote:
> init.rc usage example:
> mount vfat mmc@blk1p3 /mnt/sdcard2
this feels like a weird split of the device name with mmc before and
blk1 after the @. especially if you look how its used with mtd@FSNAME
how about using mmcblkX@FSNAME or even mm
On 23 February 2011 20:58, Alexander Sack wrote:
> On Wed, Feb 23, 2011 at 10:45 AM, Jim Huang wrote:
>> init.rc usage example:
>> mount vfat mmc@blk1p3 /mnt/sdcard2
>
> this feels like a weird split of the device name with mmc before and
> blk1 after the @. especially if you look how its used
On Tue, 22 Feb 2011 22:54:38 +0100, Loïc Minier wrote:
> On Wed, Feb 23, 2011, Michael Hudson-Doyle wrote:
> > I ask mostly from a position of ignorance, but is the information in
> > this database related to the information linaro-media-create keeps about
> > each board? If so, could it be share
Hi,
The notes and actions for this weeks Android Platform Team meeting along
with team activity reports are now available at:
https://wiki.linaro.org/Platform/Android/Meetings/2011-02-23
= Actions Recorded =
* kjnabe to contribute framebuffer support back to jstultz'
git.linaro.org tree
On Wed, Feb 23, 2011, James Westby wrote:
> How would this interact with the proposal for storing some of this
> information in hwpacks?
This came up; basically linaro-image-tools + hwpacks are one of the
many copies of this information which we have around. It will take
some time to share thi
Hi Sascha,
I noticed there were no comments for v3, but you had comments for v2 which
was posted after v3. See below:
>>I see. Maybe we should make this a platform driver then like for example
>>davinci does.
>I had sent out v3 patch before the your last comments.
>I noticed how davinci is doing
On Wed, 23 Feb 2011 15:57:31 +0100, Loïc Minier wrote:
> I'm not sure; for instance consider the case of data which changes with
> the distro over time; let's say linaro-image-tools depends on that data
> and combines the data + 1 hwpack + 1 rootfs to create an image. Then
> the data changes,
On 02/23/2011 10:28 AM, Somebody in the thread at some point said:
Hi -
Any scripting config left from kernel package install could be
batched and deferred until first boot where it runs natively.
Hmm this is a bit too far-looking for me
I mention it because kernel post-install scriptlets
On Wed, Feb 23, 2011, James Westby wrote:
> So longer term we should be thinking of having the hwpack generation
> read some information from the common files corresponding to the
> versions it is building for (e.g. grab the package containing the common
> files and look for the one with a specific
On Tue, Feb 22, 2011 at 10:13:10PM +0800, Shawn Guo wrote:
> Hi Grant,
>
> Thanks for the explanation in details.
>
> One more minor doubt below ...
>
> On Mon, Feb 21, 2011 at 10:10:24AM -0700, Grant Likely wrote:
> > On Mon, Feb 21, 2011 at 2:46 AM, Shawn Guo wrote:
> [...]
> > >> +
On Wed, 23 Feb 2011 18:32:29 +0100, Loïc Minier wrote:
> Did you have something specific in mind?
Nope.
Thanks,
James
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Wed, 2011-02-23 at 11:19 +0800, Eric Miao wrote:
> Just a thought in the other way: will it be useful to to have some
> web crawler to collect those activities as long as we all use linaro
> email addresses? For mails like patch within, there should be some
> thing we can identify.
I don't thin
On Wed, 2011-02-23 at 10:09 +0800, Jammy Zhou wrote:
> Hi All,
>
> For some upstream projects, we don't use git-send-mail to send patch
> for review. Take KDE/Kwin project for example, post-review and the
> reviewboard[1] are used for patch review. How shall we handle such
> kind of cases?
I supp
On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote:
> Maybe Steve Sakoman can suggest some example boards that will be
> difficult to tell apart at runtime, but it matters?
Here's one example: the Seagate DockStar is very similar to the
Marvell Sheevaplug (same Kirkwood SoC), but has a dif
On Tue, 22 Feb 2011, Grant Likely wrote:
> Hi Nicolas,
>
> Here's the branch implementing basic device tree support based on the
> linaro-2.6.38 tree. Should be good to go.
Merged !
Please send any corrections my way as well from now on for inclusion
into the Linaro tree.
Nicolas
_
Good evening,
First post on this list so I apologize in advance if I post on the wrong
list.
I am desperately looking for a working thumb-2 kernel tree. I am
currently using the dirty/arm/omap-thumb2+merged branch from
git://git.linaro.org/people/dmart/linux-2.6-arm.git repo,
since it is the o
On Wed, 23 Feb 2011 15:57:31 +0100, Loïc Minier wrote:
> On Wed, Feb 23, 2011, James Westby wrote:
> > How would this interact with the proposal for storing some of this
> > information in hwpacks?
>
> This came up; basically linaro-image-tools + hwpacks are one of the
> many copies of this in
Hi Markos,
On Wed, Feb 23, 2011 at 10:37:19PM +, markos.chand...@gmail.com wrote:
> First post on this list so I apologize in advance if I post on the wrong
> list.
Welcome to the list!
> I am desperately looking for a working thumb-2 kernel tree. I am
> currently using the dirty/arm/omap-th
On Wed, Feb 23, 2011 at 05:18:42PM -0500, Nicolas Pitre wrote:
> On Tue, 22 Feb 2011, Grant Likely wrote:
>
> > Hi Nicolas,
> >
> > Here's the branch implementing basic device tree support based on the
> > linaro-2.6.38 tree. Should be good to go.
>
> Merged !
>
> Please send any corrections m
On Wed, 2011-02-23 at 07:32 +0900, sola wrote:
> From 7784102e184c134eaa11b5986f31c892748f1604 Mon Sep 17 00:00:00 2001
> From: Masashi YOKOTA
> Date: Sat, 19 Feb 2011 02:40:56 +0900
> Subject: [PATCH 1/2] Add virtual battery driver
>
> This patch adds virtual battery driver.
> This is based on
>
On Wed, Feb 23, 2011 at 02:49:43PM -0800, Steve Langasek wrote:
> > [...]
> > since it is the only one that compiles for me. However, to my
> > understanding, this is not a very 'safe' branch to use on daily basis.
> > Is that true? Is there a more 'stable' git branch which I can compile as
> > thu
For some reason the virtual battery driver code allocates
4k on the stack. This is clearly broken, so keep the length
smaller (256) and cleanup the string management code to use
the bounds checking versions.
CC: Akihiro MAEDA
CC: Masashi YOKOTA
Signed-off-by: John Stultz
---
drivers/power/virt
On Wed, 23 Feb 2011, Markos Chandras wrote:
> On Wed, Feb 23, 2011 at 02:49:43PM -0800, Steve Langasek wrote:
> > > [...]
> > > since it is the only one that compiles for me. However, to my
> > > understanding, this is not a very 'safe' branch to use on daily basis.
> > > Is that true? Is there a
On Thu, Feb 24, 2011, Michael Hudson-Doyle wrote:
> One of the issues here I guess is: do we know what all the data required
> is? My impression (from a step removed, admittedly) is that adding
> support for new boards to l-m-c still tends to require code changes and
> not just data changes. Hope
On Thu, Feb 24, 2011 at 4:46 AM, Guilherme Salgado wrote:
> On Wed, 2011-02-23 at 10:09 +0800, Jammy Zhou wrote:
> > Hi All,
> >
> > For some upstream projects, we don't use git-send-mail to send patch
> > for review. Take KDE/Kwin project for example, post-review and the
> > reviewboard[1] are us
On 02/23/2011 06:21 PM, Somebody in the thread at some point said:
On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote:
Maybe Steve Sakoman can suggest some example boards that will be
difficult to tell apart at runtime, but it matters?
Here's one example: the Seagate DockStar is very s
29 matches
Mail list logo
