Hello Jagan,
Jagan Teki writes:
> Any update on this.
The Wandboard Quad is working well for my purposes and much easier to
work with (schematics and very extensive data sheets available, mainline
support in both U-Boot and Linux). As a result, I'm focusing my limited
resources on the Wandboard
Jagannadha Sutradharudu Teki
writes:
> Added W25* parts are which are avilable in spi_flash_probe_legacy.c.
>
> Updated the sector_size attributes as per the flash parts.
> Looks fine for with this sector_size for computing the size
> of flash.
This breaks sector-sized (i.e. 4KiB) erases on W25
Hi Jagannadha,
Jagannadha Sutradharudu Teki
writes:
> SECT_4K, SECT_32K and SECT_64K opeartions are performed to
> to specific flash by adding a SECT* flag on respective
> spi_flash_params.flag param.
[...]
[drivers/mtd/spi/spi_flash_ops.c]
> @@ -153,17 +153,13 @@ int spi_flash_cmd_erase(struct
Hi Jagannadha,
Jagannadha Sutradharudu Teki
writes:
> Added new spi_flash_probe support, currently added N25Q*
> flash part attributes support.
[...]
I've given your series another try on Cubox. It looks better this time
(e.g. the probe issue is gone), but there are still a couple of
issues. I'
Avoid a recently introduced unused variable warning for boards that
use mvgbe but not phylib.
Signed-off-by: Sascha Silbe
---
v5->v6: Split out from CuBox support patch series.
drivers/net/mvgbe.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/mvgbe.
Many recent hard disks are larger than 2TiB. They still use a logical
sector size of 512, so 32-bit sector numbers are insufficient (and
even with 4K logical sector size we'd exceed the limit once there are
16TiB drives).
Signed-off-by: Sascha Silbe
---
arch/arm/include/asm/arch-kir
Hi Albert,
Albert ARIBAUD writes:
> On Mon, 15 Jul 2013 08:19:57 -0400, Tom Rini wrote:
>> On Mon, Jul 15, 2013 at 11:23:54AM +0200, Sascha Silbe wrote:
>>> With v2013.07-rc3, we are now at 376344B (~ 96% of 384KiB) for
>>> openrd_ultimate when built on Debian W
Hello Jagan,
Jagan Teki writes:
> Please find the test branch for this patch series, here.
> http://git.denx.de/?p=u-boot/u-boot-spi.git;a=shortlog;h=refs/heads/master-test
>
> Request to test these changes on your boards.
> Let me know for any issues.
Thanks for setting up a branch for easier
The purpose of CONFIG_BOARD_SIZE_LIMIT is to make sure that U-Boot
fits into the space reserved for it in some permanent storage. This
includes any overhead incurred by native boot image formats, so check
the final image against the size limit, too.
Signed-off-by: Sascha Silbe
---
Makefile | 3
CONFIG_BOARD_SIZE_LIMIT was introduced by f3a14d37 [Makefile: allow
boards to check file size limits] and is in use by several boards, but
never got documented.
Signed-off-by: Sascha Silbe
---
README | 5 +
1 file changed, 5 insertions(+)
diff --git a/README b/README
index a5c3e8d..760c417
Set CONFIG_BOARD_SIZE_LIMIT so we'll notice at build time if U-Boot
has grown so large that it would overlap with the environment area in
flash, rather than bricking the device at run-time on first saveenv.
Signed-off-by: Sascha Silbe
---
include/configs/openrd.h | 5 +
1 file chang
. Here we go.
Sascha Silbe (3):
README: document CONFIG_BOARD_SIZE_LIMIT
Makefile: check native boot image sizes against
CONFIG_BOARD_SIZE_LIMIT
openrd: fail build if U-Boot would overlap with environment in flash
Makefile | 3 +++
README | 5 +
inc
h.
Reviewed-By: Sascha Silbe
No test done as my current test set-up is 100Base-T only.
Sascha
pgpK771OQifMU.pgp
Description: PGP signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Albert ARIBAUD writes:
> Although, with recent proposals like the TPL one:
>
> http://permalink.gmane.org/gmane.comp.boot-loaders.u-boot/164432
>
> ... I am toying with the idea of a more generic build mechanism which
> would allow a target to specify as many binaries as it needs, each with
> its
ssfully on Wandboard
Quad.
Sascha
-- >8 --
From: Sascha Silbe
Date: Fri, 19 Jul 2013 11:37:54 +0200
Subject: [PATCH] phy: fix 10/100Mbps operation on 1Gbps-capable links
de1d786 [add support for Xilinx 1000BASE-X phy (GTX)] introduced a
check for the extended status register in order to su
Sascha Silbe writes:
> I've started a git bisect run (booting via USB OTG), but it's going to
> take a while as git bisect is throwing lots of commits without Wandboard
> Quad support at me and seems to be only narrowing down the commits one
> by one rather than on a lo
Hello,
ethernet support for Wandboard Quad seems to be broken on current master
(576aacdb):
U-Boot 2013.07-rc3-00021-g576aacd (Jul 18 2013 - 08:34:32)
Albert ARIBAUD writes:
>> The situation has gotten better recently and U-Boot fits into the
>> previous partition size of 384KiB again. So it isn't broken on OpenRD
>> anymore and the above would seem like a good approach.
> How well does it fit again, and do you have any idea what caused the
> i
Dear Wolfgang Denk,
Wolfgang Denk writes:
>> -#define rdl(off)readl(MVUSB0_BASE + (off))
>> -#define wrl(off, val) writel((val), MVUSB0_BASE + (off))
>> +#define rdl(base, off) readl((base) + (off))
>> +#define wrl(base, off, val) writel((val), (base) + (off))
>
> Instead
Use structs instead of computing offsets for accessing individual
registers. The base address of the USB controller is still an offset
defined in SoC headers as it can differ between SoCs.
Signed-off-by: Sascha Silbe
---
Tested on CuBox Pro only.
drivers/usb/host/ehci-marvell.c | 48
Avoid a recently introduced unused variable warning for boards that
use mvgbe but not phylib.
Signed-off-by: Sascha Silbe
---
v4->v5: Most of the original patch ("NET: mvgbe: add phylib support")
was merged to master, only this clean-up remains.
drivers/net/mvgbe.c | 5
Dove SoC also uses mvsata, therefore add a SoC specific include to
allow to reuse the mvsata ide driver.
Signed-off-by: Sascha Silbe
Acked-by: Prafulla Wadaskar
---
v4->v5: no changes
drivers/block/mvsata_ide.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/block/mvsata_id
x27;t
matter. Having a single image that works on both hardware variants
is quite convenient during recovery.
Signed-off-by: Sascha Silbe
---
v4->v5:
- dropped MAINTAINERS entry on Sebastian Hesselbarth's request
- some adjustments to account for GPIO and SPI driver changes
board/
This adds a driver for the sdhci controller found on Dove SoCs.
Signed-off-by: Sascha Silbe
---
v4->v5: no changes
arch/arm/include/asm/arch-dove/mmc.h | 27 ++
drivers/mmc/Makefile | 1 +
drivers/mmc/dove_sdhci.c |
From: Sascha Silbe
Marvell 88AP510 (Armada 510, dove) has two separate USB
controllers. Use the index parameter that already gets passed in to
calculate the base address of the controller.
Signed-off-by: Sascha Silbe
---
v4->v5: no changes
drivers/usb/host/ehci-marvell.c |
The GPIO support of Dove is very similar to that on Kirkwood (and
possibly orion5x as well). Instead of duplicating the code, we tweak
the Kirkwood driver so it works for Dove, too.
Signed-off-by: Sascha Silbe
---
v4->v5: Modify Kirkwood driver rather than duplicating it.
The pa
The SPI support on Dove is very similar to that on Kirkwood (and
possibly orion5x as well). Instead of duplicating the code, we tweak
the Kirkwood driver so it works for Dove, too.
Signed-off-by: Sascha Silbe
---
v4->v5: Modify Kirkwood driver rather than duplicating it.
The patch descript
een tested (lightly) on CuBox Pro, not on
OpenRD (Kirkwood). The latter box is in production use, so I'd like to
know whether the current approach is acceptable before I spend
considerable time on testing.
Sascha Silbe (8):
ARM: dove: add support for Marvell Dove SoC
usb: ehci-marvell: add sup
Frederic Leroy writes:
[...]
> disk/part_efi.c| 4 ++--
While testing the CuBox patches using buildman, I noticed a warning in
disk/part_iso.c. The following patch should fix it:
diff --git a/disk/part_iso.c b/disk/part_iso.c
index cc323b0..e15e1b9 100644
--- a/disk/part_iso.c
+++ b/di
Sebastian Hesselbarth writes:
[...]
> I was under the impression that you resent the patches because you have
> a CuBox you want to get supported.
Exactly. I'd like to see support for CuBox enter mainline
U-Boot. However, there's also a limit to the amount of time I can afford
to spend on it (bo
Hello Jagan,
Jagan Teki writes:
> Looks ok to me as per coding style after a quick look.
Thanks for the review.
[...]
> Done use the below tag code instead go for spi_alloc_slave()
> see the sample code on "drivers/spi/exynos_spi.c"
>
> --- TAG+
>> + slave = malloc(s
Sebastian Hesselbarth writes:
> Either orion_spi as it was named originally, or mv_spi as Prafulla
> suggested. Then move mpp (pinctrl) from kirkwood_spi to corresponding
> boards, switch to orion_/mv_spi, and remove kirkwood_spi.
>
> I suggest orion_spi, but Prafulla had his word so it should be
Hello Albert, hello Tom,
Albert ARIBAUD writes:
[Move environment to account for increase in U-Boot size]
> This patch is for 2013.10, not 2013.07, but I prefer raising the issue
> as early as possible.
>
> If there is no way to make things smoother, then I think the 2013.10
> release notes shou
TA hard disk attached to a CuBox Pro
works fine now.
Tested-by: Sascha Silbe
You'll probably have to add your Signed-off-by before your patch can be
merged.
A minor nitpick: The limit is at 2TiB (2^41 Bytes), which is roughly
2.2TB (2.2 * 10^12 Bytes).
Sascha
Frédéric Leroy writes:
> Le 22/06/2013 17:31, Albert ARIBAUD a écrit :
>> > However, the patch issues no warning at compile time and fixes the ide
>> > block layer.
>>
>> OK -- anyone has any idea why Sasha's patch fixes reading from "far"
>> blocks but does not fix ex2ls? Frankly, I'd prefer it
all block drivers as the signature of block_read(),
block_write() and block_erase() in block_dev_desc_t changed.
Signed-off-by: Sascha Silbe
---
Functionality tested on CuBox Pro with a Western Digital WD30EFRX hard
disk (3TB). Build tested for all arm boards and sandbox.
Testing on other boards
Frédéric Leroy writes:
> I will convert every ide block number to 64 bit for disk and partitions.
> I guess CONFIG_LBA48 is also broken in common/cmd_ide.c :
FWIW, I have a patch pending for this already. But it's necessarily
pretty invasive and I'm not even sure yet that I've found all places
Dear Jagan,
Jagan Teki writes:
>> I'd appreciate a review of the latest patch [1,2]. [...]
>> [1] mid:1369593423-19763-6-git-send-email-t-ub...@infra-silbe.de
>> [2] http://patchwork.ozlabs.org/patch/246468/
>
> Thank you, means this v4 is the latest one?
> http://patchwork.ozlabs.org/patch/2464
Dear Jagan,
Jagan Teki writes:
> Does this tested on hw, please re-base the tree and send the next version
> patch.
> Let me know if it ok to review under current tree.
I'd appreciate a review of the latest patch [1,2]. There have been no
changes in master to the files touched by the patch sin
customisations.
This obviously breaks compatibility with previous mainline versions of
U-Boot. Users will need to back up the environment before an update
and restore it afterwards, or manually copy it to the new address
before the update.
Signed-off-by: Sascha Silbe
---
include/configs/openrd.h
From: Sebastian Hesselbarth
This adds a driver for the sdhci controller found on Dove SoCs.
Signed-off-by: Sebastian Hesselbarth
Signed-off-by: Sascha Silbe
---
v3->v4: added header file with exported function
arch/arm/include/asm/arch-dove/mmc.h | 27 ++
drivers/mmc/Makef
handled as part of
cpu/board-specific setup.
Signed-off-by: Sebastian Hesselbarth
Signed-off-by: Sascha Silbe
---
v3->v4: renamed to dove, adjusted description, removed unused
variable, made checkpatch clean
drivers/spi/Makefile | 1 +
drivers/spi/dove_spi.c |
ld in
large parts be compatible with orion5x and kirkwood. As a future
clean-up step, the MPP and GPIO code for the three platforms could be
merged.
Signed-off-by: Sebastian Hesselbarth
Signed-off-by: Sascha Silbe
---
v3->v4: renamed to dove_gpio, adjusted description
drivers/gpio/Makefile
From: Sebastian Hesselbarth
Marvell Dove also uses mvgbe as ethernet driver, therefore add support
for Dove to reuse the current driver.
Signed-off-by: Sebastian Hesselbarth
Signed-off-by: Sascha Silbe
---
v3->v4: removed EBAR_DRAM_CS* for Dove
drivers/net/mvgbe.c | 9 -
driv
From: Sebastian Hesselbarth
Dove SoC also uses mvsata, therefore add a SoC specific include to
allow to reuse the mvsata ide driver.
Signed-off-by: Sebastian Hesselbarth
Acked-by: Prafulla Wadaskar
---
drivers/block/mvsata_ide.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bl
From: Sebastian Hesselbarth
This adds PHY initialization for Marvell Alaska 88E1310 PHY.
Signed-off-by: Sebastian Hesselbarth
---
drivers/net/phy/marvell.c | 48 +++
1 file changed, 48 insertions(+)
diff --git a/drivers/net/phy/marvell.c b/drivers/n
From: Sascha Silbe
Marvell 88AP510 (Armada 510, dove) has two separate USB
controllers. Use the index parameter that already gets passed in to
calculate the base address of the controller.
Signed-off-by: Sascha Silbe
---
v3->v4: new patch
drivers/usb/host/ehci-marvell.c |
From: Sebastian Hesselbarth
This add phylib support to the Marvell GBE driver.
Signed-off-by: Sebastian Hesselbarth
Acked-by: Prafulla Wadaskar
Signed-off-by: Sascha Silbe
---
v3->v4: avoided unused variable warning; made checkpatch clean
drivers/net/mvgbe.c |
RAM access (on CuBox) doesn't
matter. Having a single image that works on both hardware variants
is quite convenient during recovery.
Signed-off-by: Sebastian Hesselbarth
Signed-off-by: Sascha Silbe
---
v3->v4: added second USB port; added 2GiB and UART variants; removed
e SDRAM bank in
attributes)
- removed hard-coded ethaddr
- general clean-ups (checkpatch clean except for one spot now)
I'm assuming Sebastian (CC'ed) is still willing to be the maintainer.
Sascha Silbe (1):
usb: ehci-marvell: add support for second USB controller
Sebastian Hesselb
Sebastian Hesselbarth writes:
> This patch set add support for the Marvell Dove 88AP510 SoC and
> the SolidRun CuBox board based on that SoC. The patch set is divided
> into the four following sections:
[...]
What's the state of this? I tried applying your patch series on top of
current master a
"Paul B. Henson" writes:
> I'm trying to get u-boot to read from a ubifs volume on an mx28evk
> board, and failing :(.
[...]
> MX28EVK U-Boot > ubifsmount recovery
>
> UBIFS error (pid 0): ubifs_get_sb: cannot open "recovery", error -22
> UBIFS error (pid 0): ubifs_mount: Error reading superbloc
52 matches
Mail list logo