of USB_MAX_XFER_BLK from 65535 to 32767 fixed also that "corrupted
load" problem, so from what I experienced 32767 is a much more practical and
"real life" reliable value.
If, as Fabio Estevam suggested, changing USB_MAX_XFER_BLK to 32767 is being
considered, I definitely vo
In data venerdì 15 aprile 2016 12:53:36, Marek Vasut ha scritto:
> On 04/14/2016 03:20 PM, Diego wrote:
> > On 18.02.2016, Schrempf Frieder wrote:
> >> At the moment I have two sticks with the same chip around for which
> >> setting USB_MAX_XFER_BLK from 65535 to 32
Il 27 aprile 2016 04:14:45 CEST, Marek Vasut ha scritto:
>On 04/15/2016 02:13 PM, Diego wrote:
>>
>> Hi Marek,
>>
>> yes, I was getting the following error with the Kingston DTSE9 USB
>2.0:
>> EHCI timed out on TD - token=0x1e008d80
>> EHCI timed out
0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
bNumConfigurations 1
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x
(Bus Powered)
Bests,
Diego
___
on TD - token=0x50008d80
Error reading cluster
** Unable to read file file20.raw **
U-Boot > load usb 0:1 0x10008000 file40.raw
reading file40.raw
EHCI timed out on TD - token=0x1e008d80
EHCI timed out on TD - token=0x1e008d80
EHCI timed out on TD - token=0x1e008d80
Error reading cluster
** Unable
In data martedì 3 maggio 2016 23:01:10, Marek Vasut ha scritto:
> On 04/29/2016 09:58 AM, Diego wrote:
> > In data venerdì 29 aprile 2016 00:49:22, Marek Vasut ha scritto:
> >> Urgh, so you seem to have third revision of this stick. I have two
> >
> >> sticks wh
In data mercoledì 4 maggio 2016 13:45:57, Marek Vasut ha scritto:
> On 05/04/2016 11:13 AM, Diego wrote:
> > In data martedì 3 maggio 2016 23:01:10, Marek Vasut ha scritto:
> >> On 04/29/2016 09:58 AM, Diego wrote:
> >>> For me it fails for files bigger than
In data mercoledì 4 maggio 2016 23:36:46, Marek Vasut ha scritto:
> On 05/04/2016 04:06 PM, Diego wrote:
> > In data mercoledì 4 maggio 2016 13:45:57, Marek Vasut ha scritto:
> >> On 05/04/2016 11:13 AM, Diego wrote:
> >>>
> >>> So I see three option
mdisk? ext3.gz initrd? cpio.gz initramfs?
Thanks for any help!
Bests,
Diego
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
In data domenica 19 marzo 2017 23:14:14 CEST, Diego ha scritto:
> Hi all,
>
> I'm trying to use the multi-file format mentioned in pages 12-13 of "U-Boot
> – Multi image booting scenarios" PDF slides.
>
> I'd like to use FIT format, but I already have u
> On Mon, Jul 10, 2017 at 03:44:17PM +0200, Olliver Schinagl wrote:
> > Ping,
> >
> > any reason this hasn't been merged yet? :)
>
> I don't know. Jagan?
>
> Maxime
It looks like Jagan isn't responding.
A
Currently, the kernel devicetree is setting the DRAM size to ~4G.
Signed-off-by: Diego Sueiro
---
configs/vexpress_aemv8a_semi_defconfig | 2 +-
include/configs/vexpress_aemv8a.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/configs/vexpress_aemv8a_semi_defconfig
- Wifi + BT
- OTG + power supply
Signed-off-by: Diego Rondini
---
arch/arm/dts/Makefile | 3 +-
arch/arm/dts/sun8i-h3-orangepi-zero-plus2.dts | 139 ++
board/sunxi/MAINTAINERS | 5 +
configs/orangepi_zero_plus2_h3_defconfig
a6912f4811)
has been avoided as it breaks U-Boot build.
Signed-off-by: Diego Rondini
---
Changes in v2:
- clarify where the dts comes from
---
arch/arm/dts/Makefile | 3 +-
arch/arm/dts/sun8i-h3-orangepi-zero-plus2.dts | 139 ++
boa
the value of a GPIO in
scripts we introduce the `gpio read` command that sets the variable
`name` to the value of the pin. Return code of the `gpio read` command
can be used to check for CMD_RET_SUCCESS or CMD_RET_FAILURE.
CONFIG_CMD_GPIO_READ is used to enable the `gpio read` command.
Signed-off
e the usb otg, and for a
fraction of second the power is disconnected. I solved it by attaching a
battery (and I have a PSU as a side effect :) ).
Regards,
Diego.
--
Diego Roversi
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Add script for retrieving the kernel via TFTP and mounting the
rootfs via NFS.
Signed-off-by: Diego Dorta
---
include/configs/pico-imx6ul.h | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/include/configs/pico-imx6ul.h b/include/configs/pico
Pico-imx6ul has a KSZ8081 Ethernet PHY.
Add support for it.
Signed-off-by: Diego Dorta
---
board/technexion/pico-imx6ul/pico-imx6ul.c | 84 ++
include/configs/pico-imx6ul.h | 10
2 files changed, 94 insertions(+)
diff --git a/board/technexion/pico
Allow i.MX6Q Sabre SD to load the kernel and dtb via SPL in Falcon mode.
Based on the Falcon mode code for MX6 Gateworks Ventana board.
Signed-off-by: Diego Dorta
---
board/freescale/mx6sabresd/mx6sabresd.c | 12
include/configs/mx6sabresd.h| 12
2 files
Add a README to explain the steps for booting mx6sabresd in different ways:
1. Booting via Normal U-Boot (u-boot.imx)
2. Booting via SPL (SPL and u-boot.img)
3. Booting via Falcon mode (SPL launches the kernel directly)
Signed-off-by: Diego Dorta
---
board/freescale/mx6sabresd
t supported
ERROR: booting os 'Invalid OS' (0) is not supported
ERROR prep subcommand failed!
Subcommand failed
I can't understand this error. Does anybody know how to fix it?
Regards,
Diego
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Ladislay,
>From: Ladislav Michl
>Sent: Wednesday, October 19, 2016 7:50 AM
>To: Diego Dorta
>Cc: u-boot@lists.denx.de; h...@denx.de
>Subject: Re: Help with spl: zImage support in Falcon mode
>
>Hi,
>
>On Tue, Oct 18, 2016 at 04:36:54PM +, Diego Dorta wrote:
&g
Remove unused define constant.
Signed-off-by: Diego Dorta
---
board/freescale/mx6ul_14x14_evk/mx6ul_14x14_evk.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/board/freescale/mx6ul_14x14_evk/mx6ul_14x14_evk.c
b/board/freescale/mx6ul_14x14_evk/mx6ul_14x14_evk.c
index 88d3fbd..160c4c6
now how to solve this?
Regards,
Diego Dorta
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
> From: Stefano Babic
>
>
> Hi Diego,
>
> On 08/08/2016 18:12, Diego Dorta wrote:
> > Hi Stefano,
>>
> > I downloaded the patch about Falcon Mode from:
>>
> > https://www.amazon.com/clouddrive/share/hVlzRXoJv1Jq4DJdgDcVnfmOWjARqR06eCfheWjRcSh
Add support for Falcon mode and explain in the README the steps to
boot the kernel directly without loading the full U-Boot.
Signed-off-by: Diego Dorta
---
board/freescale/mx6sabreauto/README | 62 +
board/freescale/mx6sabreauto/mx6sabreauto.c | 7
is is the equivalent fix from commit 4b6035da482c ("mx6sabresd: Make
> Ethernet functional again").
>
> Reported-by: Miquel RAYNAL
> Signed-off-by: Fabio Estevam
Tested-by: Diego Dorta
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
is is the equivalent fix from commit 4b6035da482c ("mx6sabresd: Make
> Ethernet functional again").
>
> Reported-by: Miquel RAYNAL
> Signed-off-by: Fabio Estevam
Tested-by: Diego Dorta
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
is is the equivalent fix from commit 4b6035da482c ("mx6sabresd: Make
> Ethernet functional again").
>
> Reported-by: Miquel RAYNAL
> Signed-off-by: Fabio Estevam
Tested-by: Diego Dorta
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Add a README file to help users getting started with the board.
Signed-off-by: Diego Dorta
---
board/freescale/mx6ullevk/README | 36
1 file changed, 36 insertions(+)
create mode 100644 board/freescale/mx6ullevk/README
diff --git a/board/freescale
. Pick it up.
>
> The board support is a large patch because of the ddr related code.
> If it is not good, please first review/pick-up other patches if they
> are ok.
>
I applied your patches and I am facing the following errors:
LD u-boot
arch/arm/lib/built-in.o: In function `d
Hi Peng,
2017-11-29 0:42 GMT-02:00 Peng Fan :
> Hi Diego,
>
> On Tue, Nov 28, 2017 at 02:42:20PM -0200, Diego Dorta wrote:
>>Hi Peng Fan,
>>
>>2017-11-28 10:31 GMT-02:00 Peng Fan :
>>> This patchset is to add i.MX8M and i.MX8MQ-EVK support
>>>
>&g
.
Signed-off-by: Diego Dorta
---
include/mmc.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/mmc.h b/include/mmc.h
index 010ebe0..3ddfc2d 100644
--- a/include/mmc.h
+++ b/include/mmc.h
@@ -588,6 +588,7 @@ int board_mmc_init(bd_t *bis);
int cpu_mmc_init(bd_t *bis);
int
file.
Signed-off-by: Diego Dorta
---
Changes since v1:
- Add 'mmc' prefix
- Change function prototype to sys_proto.h
- Update commit log accordingly
arch/arm/include/asm/mach-imx/sys_proto.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/include/asm/mach-imx/sys_proto
When building with W=1 errors like the one below is seen:
board/freescale/mx6sabresd/mx6sabresd.c:546:5: warning:
no previous prototype for ‘overwrite_console’
[-Wmissing-prototypes] int overwrite_console(void)
Fix the build warnings by including .
Signed-off-by: Diego Dorta
---
board
t to HDMI
Display: HDMI (1024x768)
In:serial
Out: serial
Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> https://lists.denx.de/listinfo/u-boot
Thanks,
Diego
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
When compiling with W=1 the following warning is observed:
arch/arm/mach-imx/mx6/soc.c:213:12: warning: no previous prototype for
‘get_board_rev’ [-Wmissing-prototypes] u32 __weak get_board_rev(void)
Fix the build warning by including .
Signed-off-by: Diego Dorta
---
arch/arm/mach-imx/mx6
When compiling with W=1 the following warning is observed:
board/freescale/mx6sabresd/mx6sabresd.c:586:5: warning: no previous prototype
for ‘board_ehci_hcd_init’ [-Wmissing-prototypes] int board_ehci_hcd_init(int
port)
Remove this warning by including .
Signed-off-by: Diego Dorta
---
board
When compiling with W=1 the following warning is observed:
board/freescale/mx6sabresd/mx6sabresd.c:680:5: warning: no previous prototype
for ‘board_spi_cs_gpio’ [-Wmissing-prototypes] int board_spi_cs_gpio(unsigned
bus, unsigned cs)
Remove this warning by including .
Signed-off-by: Diego
file.
Signed-off-by: Diego Dorta
---
include/usb/ehci-ci.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/usb/ehci-ci.h b/include/usb/ehci-ci.h
index cd3eb47..8c9f3cd 100644
--- a/include/usb/ehci-ci.h
+++ b/include/usb/ehci-ci.h
@@ -280,6 +280,7 @@ struct usb_ehci {
int
When compiling with W=1 the following warning is observed:
arch/arm/mach-imx/mx6/soc.c:590:6: warning: no previous prototype for ‘s_init’
[-Wmissing-prototypes] void s_init(void)
Remove this warning by adding the function prototype into include/common.h file.
Signed-off-by: Diego Dorta
function prototype into arch-mx6/clock.h file.
Signed-off-by: Diego Dorta
---
arch/arm/include/asm/arch-mx6/clock.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/include/asm/arch-mx6/clock.h
b/arch/arm/include/asm/arch-mx6/clock.h
index 2d9c45e..26afefb 100644
--- a/arch/arm/include
’ [-Wmissing-prototypes] __weak int
imx6_pcie_toggle_reset(void)
Remove these warnings by adding the functions prototypes on arch-mx6/sys_proto.
Signed-off-by: Diego Dorta
---
arch/arm/include/asm/arch-mx6/sys_proto.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/include/asm/arch
arch/arm/dts/fsl-imx8mq-evk.dts
patching file arch/arm/include/asm/arch-mx8m/ddr.h
patching file arch/arm/mach-imx/mx8m/Kconfig
patching file board/freescale/mx8mq_evk/Kconfig
patching file board/freescale/mx8mq_evk/Makefile
patching file board/freescale/mx8mq_evk/README
patching file board/freescale/mx8mq_
roller memory map
> imx: add i.MX8MQ EVK support
>
> Tom Rini (1):
> arm: imx: Rework i.MX specific commands to be excluded from SPL
Thanks for your V5 patches, this time I had no problem on compiling it.
But, even following your README step by step, the U-Boot hangs
completely on this point:
U-Boot SPL 2018.01-00038-gb464677cc7 (Jan 10 2018 - 09:50:45)
PMIC: PFUZE100 ID=0x10
PMU message timeout
Normal Boot
Trying to boot from MMC2
Do you know how to solve it? If so, please add this information on the
README file.
Thanks,
Diego
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Hi Peng,
2018-01-10 23:16 GMT-02:00 Peng Fan :
> Hi Diego,
>
> On Wed, Jan 10, 2018 at 11:08:54AM -0200, Diego Dorta wrote:
>>Hi Peng,
>>
>>2018-01-10 3:20 GMT-02:00 Peng Fan :
>>> This patchset is to add i.MX8M and i.MX8MQ-EVK support
>>>
>>>
Hi Peng,
2018-01-13 8:55 GMT-02:00 Peng Fan :
> Hi Diego,
> On Thu, Jan 11, 2018 at 10:36:02AM -0200, Diego Dorta wrote:
>>Hi Peng,
>>
>>2018-01-10 23:16 GMT-02:00 Peng Fan :
>>> Hi Diego,
>>>
>>> On Wed, Jan 10, 2018 at 11:08:54AM -0200, Diego
Hi Peng,
2018-01-16 10:25 GMT-02:00 Peng Fan :
>
>
>> -Original Message-----
>> From: Diego Dorta [mailto:diegohdo...@gmail.com]
>> Sent: Tuesday, January 16, 2018 8:15 PM
>> To: Peng Fan
>> Cc: Peng Fan ; Fabio Estevam
>> ; U-Boot-Denx
>>
I talked to Peng offline, and we will work on improving the README file.
Thanks,
Diego
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
i.MX8M support
> mmc: fsl_esdhc: support i.MX8M
> imx: lcdif: include i.MX8M
> gpio: mxc: add i.MX8M support
> net: fec: do not access reserved register for i.MX8M
> imx: imx8mq: add dtsi file
> power: pmic/regulator allow dm be omitted by SPL
> imx: mx8m: add
The main reason for this update is due the currently README has no enough
info to boot the board. Add a few more steps that make the board bootable.
Signed-off-by: Diego Dorta
---
This patch depends on Peng Fan's patch series:
https://patchwork.ozlabs.org/cover/857942/
board/free
The main reason for this update is due the currently README has no enough
info to boot the board. Add a few more steps that make the board bootable.
Signed-off-by: Diego Dorta
---
This patch depends on Peng Fan's patch series:
https://patchwork.ozlabs.org/cover/857942/
board/free
On Tue, Nov 19, 2019 at 2:47 PM Diego Rondini
wrote:
>
> Orangepi Zero Plus 2 is an open-source single-board computer, available
> in two Allwinner SOC variants, H3 and H5. We add support for H3 variant
> here, as the H5 is already supported.
>
> H3 Orangepi Zero Plus 2 has:
&g
ccording to the docs[1] it seems that it's not possible yet to verify
a FIT image signature without also booting the corresponding image. Is
that right?
[1]
https://gitlab.denx.de/u-boot/u-boot/blob/v2019.10/doc/uImage.FIT/signature.txt#L580
Thank you,
Diego Rondini
Hi Lukasz,
On Thu, Dec 5, 2019 at 11:14 PM Lukasz Majewski wrote:
>
> Hi Diego,
>
> > Hi,
> >
> > I would like to ask if it is possible to source a script after
> > verifying its signature.
> >
> > Currently I've been able to source a scrip
as reported also
elsewhere:
http://patchwork.ozlabs.org/project/uboot/patch/caexmxltm9bhx7aaub+mazgbdw2ccsoo3ne6ep7dbm8mmrya...@mail.gmail.com/#1976362
http://linux-sunxi.org/U-Boot/USB_Mass_Storage#Prerequisites
Regards,
Diego Rondini
the value of a GPIO in
scripts we introduce the `gpio read` command that sets the variable
`name` to the value of the pin. Return code of the `gpio read` command
can be used to check for CMD_RET_SUCCESS or CMD_RET_FAILURE.
Signed-off-by: Diego Rondini
---
cmd/gpio.c
Hello,
I want to use the u-boot drivers such as gpio and spi on a standalone
application. What do I need to modify in the Makefile to build and link my code
with the rest of the U-boot code in order to include those drivers in my
application? because when I try to compile my code, it shows som
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Thursday, January 22, 2015 8:59 PM
> To: Pantelis Antoniou
> Cc: Diego Santa Cruz; u-boot@lists.denx.de
> Subject: Re: [U-Boot] [PATCH v4 01/18] mmc: show hardware partition sizes in
> m
> -Original Message-
> From: Pantelis Antoniou [mailto:pa...@antoniou-consulting.com]
> Sent: Friday, January 23, 2015 9:35 AM
> To: Diego Santa Cruz
> Cc: Stephen Warren; u-boot@lists.denx.de
> Subject: Re: [U-Boot] [PATCH v4 01/18] mmc: show hardware partition sizes i
The eMMC spec mandates that the high-capacity group size definitions
should be enabled when the device is partitioned (by setting
ERASE_GROUP_DEF in EXT_CSD). The current test to determine when this is
required misses a few cases. In particular a device may have been
partitioned without setting the
hardware partition support. I
have tested this with Micron eMMC 4.41 parts and it is working as
expected.
I am new to sending patches to the U-Boot mailing list, let alone
working with git, so please excuse any mishaps.
Diego Santa Cruz (18):
mmc: show hardware partition sizes in mmcinfo output
There is currently no command that will provide an overview of the hardware
partitions present on an eMMC device, one has to switch to every partition
via "mmc dev" and run mmcinfo for each to get the partition's capacity.
This commit adds a few lines of output to mmcinfo with the sizes of the
pres
The mmc_startup() function uses the ext_csd data even if reading it
from the mmc device failed. This bug was introduced in commit
bc897b1d4d86597311430dbe7b3e6c807c8c53e5. We now bail out if
reading it fails, this should not be a problem as ext_csd was
introduced in MMC 4.0 and this code is conditi
The eMMC spec numbers general purpose partitions starting at 1, but
the mmcinfo output follows the internal numbering which starts at 0.
Make the mmcinfo command output number partitions as in the eMMC
spec to avoid confusion.
---
common/cmd_mmc.c |2 +-
1 files changed, 1 insertions(+), 1 del
This adds an API to do hardware partitioning on eMMC devices. The
new mmc_hwpart_config() function does the partitioning in one go.
As the different attributes and partitioning options on eMMC may
be interdependent validation has to be done based on the complete
partitioning configuration. The func
The erase_grp_size in struct mmc is to be a size in 512-byte sectors
but the code used to compute it for eMMC when EXT_CSD_ERASE_GROUP_DEF is
enabled computed it as bytes, leading to erase sizes and alignment
much larger than what is actually required by the mmc device.
---
drivers/mmc/mmc.c |
This modification reads the size of the eMMC enhanced user data area
upon initialization of an mmc device, it will be used later by
mmcinfo.
---
drivers/mmc/mmc.c | 15 +++
include/mmc.h |4
2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/drivers/mmc/mmc.
eMMC partitions are defined as of eMMC 4.41, but mmcinfo process
partition info for eMMC >= 4.0, change it to do it for >= 4.41
---
common/cmd_mmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/common/cmd_mmc.c b/common/cmd_mmc.c
index 414fac6..bc02273 100644
--- a/com
This adds output to show the eMMC enhanced user data area size and offset
along with the partition sizes in mmcinfo's output.
---
common/cmd_mmc.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/common/cmd_mmc.c b/common/cmd_mmc.c
index bc02273..aa5ba0e 100644
--
---
drivers/mmc/mmc.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c
index c045f9e..b088fd7 100644
--- a/drivers/mmc/mmc.c
+++ b/drivers/mmc/mmc.c
@@ -1023,6 +1023,7 @@ static int mmc_startup(struct mmc *mmc)
m
Read the eMMC high capacity write protect group size at mmc device
initialization. This is useful to correctly partition an eMMC device,
as partitions need to be aligned to this size.
---
drivers/mmc/mmc.c |6 ++
include/mmc.h |1 +
2 files changed, 7 insertions(+), 0 deletions(-)
This adds the erase group size and high-capacity WP group size to
mmcinfo's output. The erase group size is necessary to properly align
erase requests on eMMC. The high-capacity WP group size is necessary
to properly align partitions on eMMC.
---
common/cmd_mmc.c | 10 ++
1 files changed
Adds the mmc hwpartition sub-command to perform eMMC hardware
partitioning on an mmc device. The number of arguments can be
large for a complex partitioning, but as the partitioning has
to be done in one go it is difficult to make it simpler.
---
common/cmd_mmc.c | 92 +++
This extends the mmcinfo hardware partition info output to show
partitions with write reliability enabled with the "WRREL" string.
If the partition does not have write reliability enabled the "WRREL"
string is omitted; this is analogous to the ehhanced attribute.
Example output:
Device: OMAP SD/M
The eMMC spec says that partitioning is only effective after the
PARTITION_SETTING_COMPLETED is set in EXT_CSD (and a power cycle was done,
but that we cannot know). Thus the partition sizes and attributes should
be ignored when that bit is not set, otherwise the various capacities
are not coherent
This extends the mmcinfo command's output to show which eMMC partitions
have the enhanced attribute set. Note that the eMMC spec says that
if the enhanced attribute is supported then the boot and RPMB
partitions are of the enhanced type.
The output of mmcinfo becomes:
Device: OMAP SD/MMC
Manufactu
This change extends the mmc hwpartition sub-command to change the
per-partition write reliability settings. It also changes the
syntax used for the enhanced user data area slightly to better
accomodate the write reliability option.
---
common/cmd_mmc.c | 116 ++
The eMMC partition write reliability settings are to be set while
partitioning a device, as per the eMMC spec, so changes to these
attributes needs to be done in the hardware partitioning API.
This commit adds such support.
---
common/cmd_mmc.c | 21 +++--
drivers/mmc/mmc.c |
Hi Pantelis,
[resending as message was rejected due to base64 content]
>
> Hi Diego,
>
> This is quite a large patchset, so we'll have to take a close look.
Feedback is appreciated. The number of patches is relatively large, but I have
tried to break them in small chunks
Hi Pantelis,
> Hi Diego,
>
> At first glance it's OK, I'm not the turning of user_enh_start, _size to a
> structure
> has a lot of benefits. It makes the diff longer.
>
I did that so that all the user data area members can be easily reset to zero
when parsing the
Hi,
> -Original Message-
> From: Joakim Tjernlund [mailto:joakim.tjernl...@transmode.se]
> Sent: Friday, November 28, 2014 11:05 AM
> To: Diego Santa Cruz
> Cc: pa...@antoniou-consulting.com; u-boot@lists.denx.de
> Subject: Re: [U-Boot] [PATCH 00/18] Support for eMM
in my git repo so that I can generate a new patch series.
Thanks,
Diego
--
Diego Santa Cruz, PhD
Technology Architect
spinetix.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
send the patch series?
I guess I should resend the whole series to the mailing list for consistency.
Best,
Diego
--
Diego Santa Cruz, PhD
Technology Architect
spinetix.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
-boot.git master of a few minutes ago.
Diego Santa Cruz (18):
mmc: show hardware partition sizes in mmcinfo output
mmc: extend mmcinfo to show enhanced partition attribute
mmc: make eMMC general purpose partition numbering match spec
mmc: skip mmcinfo partition info processing for eMMC
There is currently no command that will provide an overview of the hardware
partitions present on an eMMC device, one has to switch to every partition
via "mmc dev" and run mmcinfo for each to get the partition's capacity.
This commit adds a few lines of output to mmcinfo with the sizes of the
pres
This extends the mmcinfo command's output to show which eMMC partitions
have the enhanced attribute set. Note that the eMMC spec says that
if the enhanced attribute is supported then the boot and RPMB
partitions are of the enhanced type.
The output of mmcinfo becomes:
Device: OMAP SD/MMC
Manufactu
The eMMC spec numbers general purpose partitions starting at 1, but
the mmcinfo output follows the internal numbering which starts at 0.
Make the mmcinfo command output number partitions as in the eMMC
spec to avoid confusion.
---
common/cmd_mmc.c |2 +-
1 files changed, 1 insertions(+), 1 del
eMMC partitions are defined as of eMMC 4.41, but mmcinfo process
partition info for eMMC >= 4.0, change it to do it for >= 4.41
---
common/cmd_mmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/common/cmd_mmc.c b/common/cmd_mmc.c
index 414fac6..bc02273 100644
--- a/com
---
drivers/mmc/mmc.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c
index c045f9e..b088fd7 100644
--- a/drivers/mmc/mmc.c
+++ b/drivers/mmc/mmc.c
@@ -1023,6 +1023,7 @@ static int mmc_startup(struct mmc *mmc)
m
The eMMC spec mandates that the high-capacity group size definitions
should be enabled when the device is partitioned (by setting
ERASE_GROUP_DEF in EXT_CSD). The current test to determine when this is
required misses a few cases. In particular a device may have been
partitioned without setting the
This modification reads the size of the eMMC enhanced user data area
upon initialization of an mmc device, it will be used later by
mmcinfo.
---
drivers/mmc/mmc.c | 15 +++
include/mmc.h |4
2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/drivers/mmc/mmc.
This adds output to show the eMMC enhanced user data area size and offset
along with the partition sizes in mmcinfo's output.
---
common/cmd_mmc.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/common/cmd_mmc.c b/common/cmd_mmc.c
index bc02273..aa5ba0e 100644
--
The erase_grp_size in struct mmc is to be a size in 512-byte sectors
but the code used to compute it for eMMC when EXT_CSD_ERASE_GROUP_DEF is
enabled computed it as bytes, leading to erase sizes and alignment
much larger than what is actually required by the mmc device.
---
drivers/mmc/mmc.c |
The eMMC spec says that partitioning is only effective after the
PARTITION_SETTING_COMPLETED is set in EXT_CSD (and a power cycle was done,
but that we cannot know). Thus the partition sizes and attributes should
be ignored when that bit is not set, otherwise the various capacities
are not coherent
This adds the erase group size and high-capacity WP group size to
mmcinfo's output. The erase group size is necessary to properly align
erase requests on eMMC. The high-capacity WP group size is necessary
to properly align partitions on eMMC.
---
common/cmd_mmc.c | 10 ++
1 files changed
The mmc_startup() function uses the ext_csd data even if reading it
from the mmc device failed. This bug was introduced in commit
bc897b1d4d86597311430dbe7b3e6c807c8c53e5. We now bail out if
reading it fails, this should not be a problem as ext_csd was
introduced in MMC 4.0 and this code is conditi
Read the eMMC high capacity write protect group size at mmc device
initialization. This is useful to correctly partition an eMMC device,
as partitions need to be aligned to this size.
---
drivers/mmc/mmc.c |6 ++
include/mmc.h |1 +
2 files changed, 7 insertions(+), 0 deletions(-)
Adds the mmc hwpartition sub-command to perform eMMC hardware
partitioning on an mmc device. The number of arguments can be
large for a complex partitioning, but as the partitioning has
to be done in one go it is difficult to make it simpler.
---
common/cmd_mmc.c | 93 +++
The eMMC partition write reliability settings are to be set while
partitioning a device, as per the eMMC spec, so changes to these
attributes needs to be done in the hardware partitioning API.
This commit adds such support.
---
drivers/mmc/mmc.c | 39 +++
incl
1 - 100 of 144 matches
Mail list logo
