On 26 July 2012 14:46, Dirk Behme wrote:
> ---
> drivers/mmc/card/Kconfig | 27 +++
> drivers/mmc/card/block.c |2 +-
> include/linux/mmc/host.h |7 +++
> 3 files changed, 35 insertions(+), 1 deletion(-)
>
> Index: a/drivers/mmc/card/Kconfig
> ==
On 20.07.2012 13:56, Jassi Brar wrote:
On 20 July 2012 17:00, Dirk Behme wrote:
On 19.07.2012 22:45, Jassi Brar wrote:
This problem can occur on many devices with embedded MMC and removable
SD,
e.g. smart phones. So I think we should find an solution to define MMC
scan
order or device number
On 19.07.2012 15:13, Arnd Bergmann wrote:
On Wednesday 18 July 2012, Dirk Behme wrote:
Any idea how we could influence the initialization order of the mmc
block devices using a DT based kernel? Ensuring that the internal, hard
wired mmc card is always mapped to mmcblk0?
I think the best solut
On 20 July 2012 17:00, Dirk Behme wrote:
> On 19.07.2012 22:45, Jassi Brar wrote:
>>> This problem can occur on many devices with embedded MMC and removable
>>> SD,
>>> e.g. smart phones. So I think we should find an solution to define MMC
>>> scan
>>> order or device number/name in a device tree
On 19.07.2012 22:45, Jassi Brar wrote:
On 18 July 2012 19:41, Knut Wohlrab wrote:
On 07/18/2012 03:47 PM, Jassi Brar wrote:
On 18 July 2012 15:19, Knut Wohlrab wrote:
If a SD card is inserted at boot time, its "mmcblk0", the embedded
MMC (eMMC) device "mmcblk1". This makes it difficult to
On 18 July 2012 19:41, Knut Wohlrab wrote:
> On 07/18/2012 03:47 PM, Jassi Brar wrote:
>>
>> On 18 July 2012 15:19, Knut Wohlrab wrote:
>>
>>> If a SD card is inserted at boot time, its "mmcblk0", the embedded
>>> MMC (eMMC) device "mmcblk1". This makes it difficult to give the kernel
>>> the
>>
El Wed, Jul 18, 2012 at 05:16:49PM +0200 Knut Wohlrab ha dit:
> On 07/18/2012 04:54 PM, Eric Nelson wrote:
> >On 07/18/2012 07:11 AM, Knut Wohlrab wrote:
> >>On 07/18/2012 03:47 PM, Jassi Brar wrote:
> >>>On 18 July 2012 15:19, Knut Wohlrab wrote:
> >>>
> If a SD card is inserted at boot time
On Wednesday 18 July 2012, Dirk Behme wrote:
> Any idea how we could influence the initialization order of the mmc
> block devices using a DT based kernel? Ensuring that the internal, hard
> wired mmc card is always mapped to mmcblk0?
I think the best solution would be to parse the "/aliases" de
Le Wed, 18 Jul 2012 17:16:49 +0200,
Knut Wohlrab a écrit :
> No, because we have to know which will be the name of the root device
> _before_ we start the kernel. In our embedded device we start the kernel
> with a bootloader (U-Boot) and pass the root device with the kernel
> command line par
On 07/18/2012 04:54 PM, Eric Nelson wrote:
On 07/18/2012 07:11 AM, Knut Wohlrab wrote:
On 07/18/2012 03:47 PM, Jassi Brar wrote:
On 18 July 2012 15:19, Knut Wohlrab wrote:
If a SD card is inserted at boot time, its "mmcblk0", the embedded
MMC (eMMC) device "mmcblk1". This makes it difficult
On 07/18/2012 07:11 AM, Knut Wohlrab wrote:
On 07/18/2012 03:47 PM, Jassi Brar wrote:
On 18 July 2012 15:19, Knut Wohlrab wrote:
If a SD card is inserted at boot time, its "mmcblk0", the embedded
MMC (eMMC) device "mmcblk1". This makes it difficult to give the kernel the
correct device for th
On 07/18/2012 03:47 PM, Jassi Brar wrote:
On 18 July 2012 15:19, Knut Wohlrab wrote:
If a SD card is inserted at boot time, its "mmcblk0", the embedded
MMC (eMMC) device "mmcblk1". This makes it difficult to give the kernel the
correct device for the eMMC root file system ("root=/dev/mmcblk?p
On 18 July 2012 15:19, Knut Wohlrab wrote:
> If a SD card is inserted at boot time, its "mmcblk0", the embedded
> MMC (eMMC) device "mmcblk1". This makes it difficult to give the kernel the
> correct device for the eMMC root file system ("root=/dev/mmcblk?p1 ...").
>
How about root=UUID= ?
--
On 07/18/2012 09:23 AM, Jassi Brar wrote:
On 18 July 2012 11:56, Dirk Behme wrote:
Similar to [1] we have a device which has two mmc block devices connected:
One external removable and a second internal hard wired one. Depending on
the availability of the external removable mmc card at boot tim
On 18 July 2012 11:56, Dirk Behme wrote:
>
> Similar to [1] we have a device which has two mmc block devices connected:
> One external removable and a second internal hard wired one. Depending on
> the availability of the external removable mmc card at boot time, the
> internal hard wired device b
Similar to [1] we have a device which has two mmc block devices
connected: One external removable and a second internal hard wired one.
Depending on the availability of the external removable mmc card at boot
time, the internal hard wired device becomes mmcblk1 (external mmc card
available ==
16 matches
Mail list logo
