On 22 March 2011 06:47, Alexander Sack wrote:
> On Mon, Mar 21, 2011 at 7:35 PM, Jeremy Chang wrote:
[...]
>> +dev_mount sdcard /mnt/sdcard 7
>> /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
>
> from what i understand this hardcodes that our sdcard partition is
> partition 7 right?
Yes, it was
On Mon, Mar 21, 2011 at 7:35 PM, Jeremy Chang wrote:
> +###
> +## Regular device mount
> +##
> +## Format: dev_mount
> +## label - Label for the volume
> +## mount_point - Where the volume will be mounted
> +## part - Partition # (1 based), or 'auto' for fir
Last week a new tab was added to the banner of wiki.linaro.org
called "HowTo". This links to a page we have been working on
that is intended to point people to some of our most common
how-to scenarios. In addition it includes a pointer to pages
that are tagged with "CategoryHowTo", just click on th
This is needed for supporting multiple partition layout.
Change-Id: Ic4e1b5f7219cb51f02d9e0d2c14046da9f7b51f1
Signed-off-by: Jeremy Chang
---
DirectVolume.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/DirectVolume.h b/DirectVolume.h
index 4bf14ff..345de09 100644
--
vold.fstab is the vold configuration file to tell what the device to
mount.
Add device.mk, the device-specific product definition file for copy
device-specific drivers, configuration files, settings, etc.
Signed-off-by: Jeremy Chang
---
beagleboard.mk |1 +
device.mk | 16 +++
Create the directories that vold needs to complete the mounting.
vold communicates with MountService which manages Android platform
storage. Let vold do the sdcard partition mounting so sdcard partition
can be the Android external storage.
Signed-off-by: Jeremy Chang
---
init.rc | 15 +++-
On 18 March 2011 23:29, Guilherme Salgado wrote:
> I'm currently working on the PatchTracking[1] spec and, wrt patch
> series, I'm wondering whether you consider the patches that are part of
> a series to be separate or the series to be a single entity?
Depends. By putting a patchset into a serie
Hello Everybody,
The Engineering Resources team weekly report for 2011-3-17 can be
found at:
https://wiki.linaro.org/Resources/Status/WeeklyMeeting/2011-03-17
Highlights below.
Best regards,
Matt
=== Action Items from This Meeting ===
* Improve the Linaro planning structure guides. ie:
* e
On Mon, 21 Mar 2011 14:03:37 +0100
Matthias Klose wrote:
> On 21.03.2011 11:25, Neil Williams wrote:
> > The people who are most likely to be doing this now are Linaro.
> > Emdebian Crush stalled after Lenny (and used ARM not armel), so the
> > version of gcc-4.2 in Lenny should still build with
On 21.03.2011 11:25, Neil Williams wrote:
> The people who are most likely to be doing this now are Linaro.
> Emdebian Crush stalled after Lenny (and used ARM not armel), so the
> version of gcc-4.2 in Lenny should still build with the typical
> "dpkg-buildpackage -aarm". Later versions of gcc prob
> If you don't get any other feedback and Chris is happy with the
I would like to have a look at it, please give me a few days.
--
Pengutronix e.K. | Wolfram Sang|
Industrial Linux Solutions | http://www.pengutronix.de/ |
signature.asc
On Mon, Mar 21, 2011 at 01:39:45PM +0100, Arnd Bergmann wrote:
[...]
>
> Hi Shawn,
>
Hi Arnd,
> The changes you make look very nice, great work there!
>
> I think the split of the series into five patches is not ideal
> because you have more interdependencies than necessary, and it's
> not clea
On Monday 21 March 2011, Shawn Guo wrote:
> This patch set is to take sdhci device driver specific things out
> from sdhci-pltfm.c and make them self registered. Here are the
> differences it makes.
>
> * Get the sdhci device driver follow the Linux trend that driver
>take the registration by
On 18 March 2011 08:43, Patrik Ryd wrote:
> On 18 March 2011 07:06, Jim Huang wrote:
>
>> On 17 March 2011 23:35, Patrik Ryd wrote:
>> > Hi,
>> > I think your patches are good enough (now after the review) to start
>> pushing
>> > them to a toolchain_preview branch. That way people can use
>> >
I had great hopes of doing these status reports once a week; but it
turns out to take more effort to get together that I estimated.
Here's the status of ARM device tree support as of today. As always,
let me know if you have any corrections or additional information.
1 - Latest news
-
On Mon, 21 Mar 2011 09:55:26 +0100
Raphael Hertzog wrote:
(Trimming the CC: feel free to drop patches@l.o if linaro-dev@l.l.o is
more useful. Please keep debian-embedded in CC to reach me.)
> Not knowing much about cross-compilation I had started with a sligthly
> different approach than you, mi
On Mon, Mar 21, 2011 at 11:17:19AM +0100, Linus Walleij wrote:
> Does anyone beside me *ever* try to actually boot a recent kernel
> on this thing?
>
> How do you do it? Do I need patched U-boots etc, or can I just load
> a Z-record image of vmlinux into RAM over the serial console?
>
> Needless
I have this Integrator/AP development board here in my office:
Initialising Boot Monitor System Information Block
boot Monitor > i
ARM bootPROM [Version 1.3] Rebuilt on Jun 26 2001 at 22:04:10
Running on a Integrator Evaluation Board
Board Revision V1.0, ARM920T Processor
Memory Size is 128MBytes,
On Mon, Mar 21, 2011 at 5:23 AM, Sachin Gupta wrote:
>> Hi All,
>>
>> Please find enclosed link to minutes and actions for multimedia wg
>> meeting on 15st March 2011.
>>
>>
>> https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-03-15
>>
>> Summary
>> - Kan created seperate
The sdhci_pltfm.c becomes a file only having common support functions
than a driver with its registeration before. The patch is to update
Makefile and Kconfig to let MMC_SDHCI_PLTFM be selected by specific
SDHCI device drivers.
Signed-off-by: Shawn Guo
---
drivers/mmc/host/Kconfig | 24 +
The patch adds sdhci-tegra its own .probe and .remove which in turn
call into the common functions provided by sdhci-pltfm.c, so that
sdhci-tegra driver registers itself and keep all sdhci-tegra specific
things like sdhci_tegra_pdata away from sdhci-pltfm.c which is common.
As sdhci-tegra is the l
The patch adds sdhci-dove its own .probe and .remove which in turn
call into the common functions provided by sdhci-pltfm.c, so that
sdhci-dove driver registers itself and keep all sdhci-dove specific
things like sdhci_dove_pdata away from sdhci-pltfm.c which is common.
Signed-off-by: Shawn Guo
-
This patch set is to take sdhci device driver specific things out
from sdhci-pltfm.c and make them self registered. Here are the
differences it makes.
* Get the sdhci device driver follow the Linux trend that driver
take the registration by its own
* sdhci-pltfm.c becomes significantly simple
The patch turns the common stuff to in sdhci-pltfm.c into functions,
and add sdhci-esdhc-imx its own .probe and .remove which in turn call
into the common functions, so that sdhci-esdhc-imx driver registers
itself and keep all sdhci-esdhc-imx specific things like
sdhci_esdhc_imx_pdata away from sdh
The patch adds sdhci-cns3xxx its own .probe and .remove which in turn
call into the common functions provided by sdhci-pltfm.c, so that
sdhci-cns3xxx driver registers itself and keep all sdhci-cns3xxx
specific things like sdhci_cns3xxx_pdata away from sdhci-pltfm.c which
is common.
Signed-off-by:
On Mon, Mar 21, 2011 at 12:58 AM, Grant Likely
wrote:
> On Sun, Mar 20, 2011 at 9:42 PM, Shawn Guo wrote:
>> This patch set is to take sdhci device driver specific things out
>> from sdhci-pltfm.c and make them self registered. Here are the
>> difference it makes.
>>
>> * Get the sdhci device dr
On Sun, Mar 20, 2011 at 9:42 PM, Shawn Guo wrote:
> This patch set is to take sdhci device driver specific things out
> from sdhci-pltfm.c and make them self registered. Here are the
> difference it makes.
>
> * Get the sdhci device driver follow the Linux trend that driver
> take the registrat
27 matches
Mail list logo