Hi Michael,
>HI Tom
>
>On Sat, Mar 19, 2022 at 6:51 PM Tom Rini wrote:
>>
>> On Sat, Mar 19, 2022 at 06:49:25PM +0100, Michael Nazzareno Trimarchi wrote:
>> > HI Tom
>> >
>> > On Sat, Mar 19, 2022 at 6:44 PM Tom Rini wrote:
>> > >
>> > > On Sat, Mar 19, 2022 at 06:37:18PM +0100, Michael Nazzaren
Hi Bo,
On 10:46 Wed 24 Apr , Bo Shen wrote:
> From: Roberto Cerati
>
> The device interface is 16 bits wide.
> All the available packets are read from the incoming fifo.
>
> Signed-off-by: Roberto Cerati
> Signed-off-by: Raffaele Recalcati
> [voice.s...@atmel.co
On Wed, Jun 1, 2011 at 3:09 PM, Raffaele Recalcati
wrote:
> Thanks to:
>
> commit c3330e9d6a11b6ead4a2346001338ce884b5832b
> Author: Heiko Schocher
> Date: Fri Sep 17 13:10:30 2010 +0200
>
> ARM (ARM926ejs): add data cache support, tested on magnesium and tx25 board
Thanks to:
commit c3330e9d6a11b6ead4a2346001338ce884b5832b
Author: Heiko Schocher
Date: Fri Sep 17 13:10:30 2010 +0200
ARM (ARM926ejs): add data cache support, tested on magnesium and tx25 board
My 'Basi' board, based on DaVinci dm365, can read the uImage (1.5MB)
in 0.7 sec (with ext2loa
Hi Andy,
On Wed, Apr 13, 2011 at 1:24 PM, Andy Fleming wrote:
> On Fri, Mar 11, 2011 at 6:01 AM, Raffaele Recalcati
> wrote:
>> From: Raffaele Recalcati
>>
>> The first SEND_OP_COND (CMD1) command added is used to ask card capabilities.
>> After it an AND
Hi Andy,
On Sun, Apr 3, 2011 at 4:49 PM, Minkyu Kang wrote:
> Dear Raffaele Recalcati,
>
> On 3 April 2011 13:39, Raffaele Recalcati wrote:
>> Hi Minkyu,
>>
>> I have sent some patches about mmc and reviewed one, can you please
>> tell me what to do mainline t
Hi Minkyu,
On Thu, Mar 24, 2011 at 3:46 AM, Minkyu Kang wrote:
> Dear Chander Kashyap,
>
> On 22 March 2011 20:40, Chander Kashyap wrote:
>> Blocksize was hardcoded to 512 bytes. But the blocksize varies
>> depeding on various mmc subsystem commands (between 8 and 512).
>> This hardcoding was re
clean and send it.
We really want to mainline it.
Regards,
Raffaele Recalcati
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Terry,
> So I guess:
> mmc_init calls mmc_send_op_cond that set high_capacity,
> than it calls mmc_startup, that, with MMC_CMD_SEND_CSD command, set
> the capacity, using values in CSD register.
> So I guess that mmc_change_freq should not recalculate high_capacity.
>
> It seems better, isn'
Hi Terry,
On Mon, Mar 21, 2011 at 7:03 AM, Terry Lv wrote:
> MMC driver may wrongly regconize some 2GB eMMC as high capacity card.
>
> This patch is based on the patch picked from community.
>
> fc8a0985c2846292312556cba10b8a4182f55967
> From: Hanumath Prasad
> Date: Tue, 10 Aug 2010 18:01:45 -0
From: Roberto Cerati
The device interface is 16 bits wide.
All the available packets are read from the incoming fifo.
Signed-off-by: Roberto Cerati
---
This driver has been adapted to u-boot starting from ks8851_mll linux driver.
The smsc911x u-boot has been used as reference.
TODO: smsc911x r
From: Raffaele Recalcati
Defining CONFIG_MMC_TRACE in the include board file it is possible to activate
a tracing support.
This code helps in case of eMMC hw failure or to investigate possible eMMC
initialization issues.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 57
From: Raffaele Recalcati
The first SEND_OP_COND (CMD1) command added is used to ask card capabilities.
After it an AND operation is done between card capabilities and host
capabilities (at the moment only for the voltage field).
Finally the correct value is sent to the MMC, waiting that the card
From: Raffaele Recalcati
It is recommended to check card status after these kind of commands.
This is done using CMD13 (SEND_STATUS) JEDEC command until
the card is ready.
In case of error the card status field is displayed.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 60
series on basi board, based on
Davinci dm365, that contains an eMMC device.
Raffaele Recalcati (3):
mmc: checking status after commands with R1b response
mmc: SEND_OP_COND considers card capabilities (voltage)
mmc: trace added
drivers/mmc/mmc.c | 136
Hi Gururaja,
On Fri, Mar 11, 2011 at 9:57 AM, Hebbar, Gururaja
wrote:
> Hi,
>
> On Fri, Mar 11, 2011 at 14:08:14, Raffaele Recalcati wrote:
>> From: Raffaele Recalcati
>>
> [...]
> [...]
it means the lines are ok?
>> @@ -48,6 +48,36 @@ int mmc_send_cmd(str
From: Raffaele Recalcati
Defining CONFIG_MMC_TRACE in the include board file it is possible to activate
a tracing support.
This code helps in case of eMMC hw failure or to investigate possible eMMC
initialization issues.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 71
From: Raffaele Recalcati
The first SEND_OP_COND (CMD1) is used only to ask card capabilities, waiting
that the card is not busy.
After it, an AND operation is done between card capabilities and host
capabilities, (at the moment only for the voltage field).
Finally the correct value is sent to
From: Raffaele Recalcati
It is a recommended to check card status after these kind of commands.
This is done using CMD13 (SEND_STATUS) JEDEC command.
In case of error the card status field is displayed.
Signed-off-by: Raffaele Recalcati
---
It is not clear what should nice to do in case of
series on basi board, based on
Davinci dm365, that contains an eMMC device.
Raffaele Recalcati (3):
mmc: checking status after commands with R1b response
mmc: SEND_OP_COND considers card capabilities (voltage)
mmc: trace added
drivers/mmc/mmc.c | 146
On Fri, Mar 11, 2011 at 4:14 AM, Lei Wen wrote:
> On Fri, Mar 11, 2011 at 12:59 AM, Raffaele Recalcati
> wrote:
>> On Thu, Mar 10, 2011 at 5:29 PM, Lei Wen wrote:
>>> Hi Raffaele,
>>>
>>> On Thu, Mar 10, 2011 at 11:43 PM, Raffaele Recalcati
&g
On Thu, Mar 10, 2011 at 5:29 PM, Lei Wen wrote:
> Hi Raffaele,
>
> On Thu, Mar 10, 2011 at 11:43 PM, Raffaele Recalcati
> wrote:
>> From: Raffaele Recalcati
>>
>> The first SEND_OP_COND (CMD1) is used only to ask card capabilities, waiting
>> that the c
From: Raffaele Recalcati
Defining CONFIG_MMC_TRACE in the include board file it is possible to activate
a tracing support.
This code helps in case of eMMC hw failure or to investigate possible eMMC
initialization issues.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 71
From: Raffaele Recalcati
The first SEND_OP_COND (CMD1) is used only to ask card capabilities, waiting
that the card is not busy.
After it, an AND operation is done between card capabilities and host
capabilities, (at the moment only for the voltage field).
Finally the correct value is sent to
From: Raffaele Recalcati
It is a recommended to check card status after these kind of commands.
This is done using CMD13 (SEND_STATUS) JEDEC command.
In case of error the card status field is displayed.
Signed-off-by: Raffaele Recalcati
---
It is not clear what should nice to do in case of
series on basi board, based on
Davinci dm365, that contains an eMMC device.
Raffaele Recalcati (3):
mmc: checking status after commands with R1b response
mmc: SEND_OP_COND considers card capabilities (voltage)
mmc: trace added
drivers/mmc/mmc.c | 148
Hi Lei,
> I apply your patch and test on my board and find this patch mess my sd card...
Can't you trace the behaviour using the latest patch and send the
results to me ?
> Why you need to keep send the stop command (Also the other command in
> this patch)
> if mmc_send_status fail? As my unders
From: Raffaele Recalcati
Defining CONFIG_MMC_TRACE in the include board file it is possible to activate
a tracing support.
This code helps in case of eMMC hw failure or to investigate possible eMMC
initialization issues.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 71
From: Raffaele Recalcati
The first SEND_OP_COND (CMD1) is used only to ask card capabilities, waiting
that the card is not busy.
After it, an AND operation is done between card capabilities and host
capabilities, (at the moment only for the voltage field).
Finally the correct value is sent to
From: Raffaele Recalcati
It is a recommended to check card status after these kind of commands.
This is done using CMD13 (SEND_STATUS) JEDEC command.
In case of error the previous command is issued again.
Signed-off-by: Raffaele Recalcati
---
drivers/mmc/mmc.c | 106
series on basi board, based on
Davinci dm365, that contains an eMMC device.
Raffaele Recalcati (3):
mmc: checking status after commands with R1b response
mmc: SEND_OP_COND considers card capabilities (voltage)
mmc: trace added
drivers/mmc/mmc.c | 198
2009/10/26 Mike Frysinger :
> On Monday 26 October 2009 07:35:14 Raffaele Recalcati wrote:
>> I've customized the commit f67066b6b0740b826ed862615c5ab022aaf4779a
>> for my pxa255/smx911x (lan9118) board.
>> tftp works nice, also through a switch, but only if I
I've customized the commit f67066b6b0740b826ed862615c5ab022aaf4779a
for my pxa255/smx911x (lan9118) board.
tftp works nice, also through a switch, but only if I'm not connected
to the LAN.
=> tftp a200 uImage
smc911x: detected LAN9118 controller
smc911x: phy initialized .. BSR=0x782D
smc911x:
33 matches
Mail list logo
