Hi,
Le 17/01/2018 à 11:05, Jaehoon Chung a écrit :
Hi Guillaume,
On 01/09/2018 11:37 PM, Guillaume Gardet wrote:
Hi,
Le 17/11/2017 à 10:48, Jaehoon Chung a écrit :
Hi,
On 2017년 11월 16일 21:29, Guillaume Gardet wrote:
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working
Hi Guillaume,
On 01/09/2018 11:37 PM, Guillaume Gardet wrote:
> Hi,
>
>
> Le 17/11/2017 à 10:48, Jaehoon Chung a écrit :
>> Hi,
>>
>> On 2017년 11월 16일 21:29, Guillaume Gardet wrote:
>>> I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working
>>> fine.
>>>
>>> I guess there is a
Hi,
Le 17/11/2017 à 10:48, Jaehoon Chung a écrit :
Hi,
On 2017년 11월 16일 21:29, Guillaume Gardet wrote:
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working fine.
I guess there is a better way to implement the following patch ?
Le 18/11/2017 à 17:33, Guillaume Gardet a écrit :
Le 17/11/2017 à 17:06, Jaehoon Chung a écrit :
On 2017년 11월 17일 18:38, Guillaume Gardet wrote:
Le 17/11/2017 à 10:36, Lukasz Majewski a écrit :
On Thu, 16 Nov 2017 13:29:56 +0100
Guillaume Gardet wrote:
I found a workaround. If I disab
Le 17/11/2017 à 17:06, Jaehoon Chung a écrit :
On 2017년 11월 17일 18:38, Guillaume Gardet wrote:
Le 17/11/2017 à 10:36, Lukasz Majewski a écrit :
On Thu, 16 Nov 2017 13:29:56 +0100
Guillaume Gardet wrote:
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is
working fine.
I gue
On 2017년 11월 17일 18:38, Guillaume Gardet wrote:
>
>
> Le 17/11/2017 à 10:36, Lukasz Majewski a écrit :
>> On Thu, 16 Nov 2017 13:29:56 +0100
>> Guillaume Gardet wrote:
>>
>>> I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is
>>> working fine.
>>>
>>> I guess there is a better wa
Hi,
On 2017년 11월 16일 21:29, Guillaume Gardet wrote:
> I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working fine.
>
> I guess there is a better way to implement the following patch ?
>
> **
> diff --git a/driv
Le 17/11/2017 à 10:36, Lukasz Majewski a écrit :
On Thu, 16 Nov 2017 13:29:56 +0100
Guillaume Gardet wrote:
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is
working fine.
I guess there is a better way to implement the following patch ?
**
On Thu, 16 Nov 2017 13:29:56 +0100
Guillaume Gardet wrote:
> I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is
> working fine.
>
> I guess there is a better way to implement the following patch ?
>
> **
> diff --
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working fine.
I guess there is a better way to implement the following patch ?
**
diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c
index 23f642980b..a6a093
Le 15/11/2017 à 11:22, Guillaume Gardet a écrit :
Forgot to Cc ML. Done now.
Le 15/11/2017 à 11:14, Guillaume Gardet a écrit :
Hello,
I tested U-Boot v2017.09 on a Samsung Snow (Chromebook ARM) and while mmc0
(internal eMMC) is working fine, mmc1 (external SD slot) does not work.
I get the
Forgot to Cc ML. Done now.
Le 15/11/2017 à 11:14, Guillaume Gardet a écrit :
Hello,
I tested U-Boot v2017.09 on a Samsung Snow (Chromebook ARM) and while mmc0
(internal eMMC) is working fine, mmc1 (external SD slot) does not work.
I get the following error for 'mmc dev 1' command:
mmc_ini
12 matches
Mail list logo