April 2015 - U-Boot

[U-Boot] cmd_mem: cleanups, catch bad usage
by Pavel Machek 07 Apr '15

07 Apr '15

Currently, memtest will silently accept bad data. Perform error checking on user intput. Signed-off-by: Pavel Machek <pavel(a)denx.de> diff --git a/common/cmd_mem.c b/common/cmd_mem.c index bfca59e..e6623b0 100644 --- a/common/cmd_mem.c +++ b/common/cmd_mem.c @@ -994,10 +994,10 @@ static int do_mem_mtest(cmd_tbl_t *cmdtp, int flag, int argc, { ulong start, end; vu_long *buf, *dummy; - int iteration_limit; + int iteration_limit = 0; int ret; ulong errs = 0; /* number of errors, or -1 if interrupted */ - ulong pattern; + ulong pattern = 0; int iteration; #if defined(CONFIG_SYS_ALT_MEMTEST) const int alt_test = 1; @@ -1005,25 +1005,29 @@ static int do_mem_mtest(cmd_tbl_t *cmdtp, int flag, int argc, const int alt_test = 0; #endif + start = CONFIG_SYS_MEMTEST_START; + end = CONFIG_SYS_MEMTEST_END; + if (argc > 1) - start = simple_strtoul(argv[1], NULL, 16); - else - start = CONFIG_SYS_MEMTEST_START; + if (strict_strtoul(argv[1], 16, &start) < 0) + return CMD_RET_USAGE; if (argc > 2) - end = simple_strtoul(argv[2], NULL, 16); - else - end = CONFIG_SYS_MEMTEST_END; + if (strict_strtoul(argv[2], 16, &end) < 0) + return CMD_RET_USAGE; if (argc > 3) - pattern = (ulong)simple_strtoul(argv[3], NULL, 16); - else - pattern = 0; + if (strict_strtoul(argv[3], 16, &pattern) < 0) + return CMD_RET_USAGE; if (argc > 4) - iteration_limit = (ulong)simple_strtoul(argv[4], NULL, 16); - else - iteration_limit = 0; + if (strict_strtoul(argv[4], 16, &iteration_limit) < 0) + return CMD_RET_USAGE; + + if (end < start) { + printf("Refusing to do empty test\n"); + return -1; + } printf("Testing %08x ... %08x:\n", (uint)start, (uint)end); debug("%s:%d: start %#08lx end %#08lx\n", __func__, __LINE__, @@ -1074,7 +1078,7 @@ static int do_mem_mtest(cmd_tbl_t *cmdtp, int flag, int argc, ret = errs != 0; } - return ret; /* not reached */ + return ret; } #endif /* CONFIG_CMD_MEMTEST */ -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

2 2

[U-Boot] [PATCH] ahci: Fix a wrong parameter pass
by Yuantian.Tang＠freescale.com 07 Apr '15

07 Apr '15

From: Tang Yuantian <Yuantian.Tang(a)freescale.com> In stead of user_buffer_size, transfer_size should be used to pass to ahci_device_data_io(). transfer_size is the length that we want the low level function to transfer each time. If we use user_buffer_size which is the totally data length as parameter, low level function will actually create many SGs to transfer as many data as possible each time. That will produce many redundant data transfer. Signed-off-by: Tang Yuantian <Yuantian.Tang(a)freescale.com> --- drivers/block/ahci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/ahci.c b/drivers/block/ahci.c index c908fab..88b90e0 100644 --- a/drivers/block/ahci.c +++ b/drivers/block/ahci.c @@ -785,7 +785,7 @@ static int ata_scsiop_read_write(ccb *pccb, u8 is_write) /* Read/Write from ahci */ if (ahci_device_data_io(pccb->target, (u8 *) &fis, sizeof(fis), - user_buffer, user_buffer_size, + user_buffer, transfer_size, is_write)) { debug("scsi_ahci: SCSI %s10 command failure.\n", is_write ? "WRITE" : "READ"); -- 2.1.0.27.g96db324

3 2

[U-Boot] [PATCH] env_sf: Fix recovery default
by Mario Schuknecht 07 Apr '15

07 Apr '15

The u-boot environment is redundantly stored in a NOR flash on our boards. Redundant means that there are two places to store the environment. But only one of the two is active. I discovered that on one board the u-boot (env_sf) uses the environment from the second place and the Kernel (fw_printenv) uses the environment from the first place. To decide which is the active environment there is a byte inside the environment. 1 means active and 0 means obsolete. But on that board both environments had have a 1. This can happen if a power loss or reset occurs during writing the environment. In this situation the u-boot (env_sf) implementation uses the second environment as default. But the Kernel (fw_printenv) implementation uses the first environment as default. This commit corrects the default in the u-boot env_sf implementation when a problem was detected. Now the recovery default is the same like in all other environment implementations. E.g. fw_printenv and env_flash. This ensures that u-boot and Kernel use the same environment. Signed-off-by: Mario Schuknecht <mario.schuknecht(a)dresearch-fe.de> --- common/env_sf.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/common/env_sf.c b/common/env_sf.c index 5e3729c..e928f57 100644 --- a/common/env_sf.c +++ b/common/env_sf.c @@ -188,15 +188,17 @@ void env_relocate_spec(void) tmp_env2->flags == ACTIVE_FLAG) { gd->env_valid = 2; } else if (tmp_env1->flags == tmp_env2->flags) { - gd->env_valid = 2; + gd->env_valid = 1; } else if (tmp_env1->flags == 0xFF) { + gd->env_valid = 1; + } else if (tmp_env2->flags == 0xFF) { gd->env_valid = 2; } else { /* * this differs from code in env_flash.c, but I think a sane * default path is desirable. */ - gd->env_valid = 2; + gd->env_valid = 1; } if (gd->env_valid == 1) -- 2.1.4

2 2

[U-Boot] Pull request: u-boot-spi/master
by Jagannadha Sutradharudu Teki 07 Apr '15

07 Apr '15

Hi Tom, Please pull this PR. thanks! Jagan. The following changes since commit 662e2acb46250881ec26bc8366fc9eb1856cb7c2: sunxi: UTOO_P66: Add missing MAINTAINERS entry (2015-03-29 14:56:48 +0200) are available in the git repository at: git://git.denx.de/u-boot-spi.git master for you to fetch changes up to 52091ad146d766cdc5ccd65430b2a4e5cb7aec32: spi: designware_spi: revisit FIFO size detection again (2015-03-30 01:42:49 +0530) ---------------------------------------------------------------- Axel Lin (6): spi: cf_qspi: Fixup to_cf_qspi_slave macro spi: davinci: Remove duplicate code to set bus and cs for slave spi: ftssp010_spi: Use to_ftssp010_spi() to ensure free correct address spi: cf_spi: Use to_cf_spi_slave to resolve cfslave from slave spi: cf_spi: Staticize local functions spi: designware_spi: revisit FIFO size detection again Ravi Babu (1): qspi: dra7x: enable quad mode read for ti-qspi driver drivers/spi/cf_qspi.c | 2 +- drivers/spi/cf_spi.c | 31 ++++++++++++++++--------------- drivers/spi/davinci_spi.c | 3 --- drivers/spi/designware_spi.c | 4 ++-- drivers/spi/ftssp010_spi.c | 4 +++- drivers/spi/ti_qspi.c | 7 +++++++ include/configs/dra7xx_evm.h | 1 + 7 files changed, 30 insertions(+), 22 deletions(-)

2 1

[U-Boot] [PATCH 1/2] mtd: vf610_nfc: remove caching of page in buffer
by Stefan Agner 07 Apr '15

07 Apr '15

To improve performance we remember the current page in the buffer and avoid reading it twice. This implicit page cache increases complexity while does not increase performance in real world cases. This patch removes that feature. --- As discussed in the other patchset... http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/215802 ...I did some performance measurements: Time to "Starting kernel ..." - without bad block scan & with UBIFS fastmap: 2.02s - with bad block scan & with UBIFS fastmap: 3.99s - without bad block scan & without UBIFS fastmap: 4.42s - with bad block scan & without UBIFS fastmap: 6.38s Without page cache (with this patch applied): Time to "Starting kernel ..." - without bad block scan & with UBIFS fastmap: 2.02s - with bad block scan & with UBIFS fastmap: 4.01s - without bad block scan & without UBIFS fastmap: 4.41s - with bad block scan & without UBIFS fastmap: 6.39s I then checked whether that reread occurs at least once with a printf in the "Already read?" if. It looks like this access pattern does not occure (anymore?) during a normal boot. Hence I now vote to get rid of it too... drivers/mtd/nand/vf610_nfc.c | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/mtd/nand/vf610_nfc.c b/drivers/mtd/nand/vf610_nfc.c index d98dd28..fa0bb9d 100644 --- a/drivers/mtd/nand/vf610_nfc.c +++ b/drivers/mtd/nand/vf610_nfc.c @@ -147,7 +147,6 @@ struct vf610_nfc { uint column; int spareonly; int page_sz; - int page; /* Status and ID are in alternate locations. */ int alt_buf; #define ALT_BUF_ID 1 @@ -347,7 +346,6 @@ static void vf610_nfc_command(struct mtd_info *mtd, unsigned command, switch (command) { case NAND_CMD_PAGEPROG: - nfc->page = -1; vf610_nfc_transfer_size(nfc->regs, nfc->page_sz); vf610_nfc_send_commands(nfc->regs, NAND_CMD_SEQIN, command, PROGRAM_PAGE_CMD_CODE); @@ -367,10 +365,6 @@ static void vf610_nfc_command(struct mtd_info *mtd, unsigned command, case NAND_CMD_SEQIN: /* Pre-read for partial writes. */ case NAND_CMD_READ0: column = 0; - /* Already read? */ - if (nfc->page == page) - return; - nfc->page = page; vf610_nfc_transfer_size(nfc->regs, nfc->page_sz); vf610_nfc_send_commands(nfc->regs, NAND_CMD_READ0, NAND_CMD_READSTART, READ_PAGE_CMD_CODE); @@ -378,7 +372,6 @@ static void vf610_nfc_command(struct mtd_info *mtd, unsigned command, break; case NAND_CMD_ERASE1: - nfc->page = -1; vf610_nfc_transfer_size(nfc->regs, 0); vf610_nfc_send_commands(nfc->regs, command, NAND_CMD_ERASE2, ERASE_CMD_CODE); @@ -532,10 +525,8 @@ static inline int vf610_nfc_correct_data(struct mtd_info *mtd, u_char *dat) flip = count_written_bits(dat, nfc->chip.ecc.size, ecc_count); /* ECC failed. */ - if (flip > ecc_count) { - nfc->page = -1; + if (flip > ecc_count) return -1; - } /* Erased page. */ memset(dat, 0xff, nfc->chip.ecc.size); -- 2.3.3

2 6

[U-Boot] [PATCH] net/phy: fixup for get_phy_id
by Shengzhou Liu 07 Apr '15

07 Apr '15

commit 3c6928fd7b0f84 "net: phy: fix warnings with W=1" caused some PHYs(e.g. CS4315/CS4340) not working. This patch fixes the warning and make those special PHYs working as well. Signed-off-by: Shengzhou Liu <Shengzhou.Liu(a)freescale.com> --- drivers/net/phy/phy.c | 2 +- include/phy.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c index df7e945..dd665ba 100644 --- a/drivers/net/phy/phy.c +++ b/drivers/net/phy/phy.c @@ -581,7 +581,7 @@ static struct phy_device *phy_device_create(struct mii_dev *bus, int addr, * Description: Reads the ID registers of the PHY at @addr on the * @bus, stores it in @phy_id and returns zero on success. */ -static int get_phy_id(struct mii_dev *bus, int addr, int devad, u32 *phy_id) +int __weak get_phy_id(struct mii_dev *bus, int addr, int devad, u32 *phy_id) { int phy_reg; diff --git a/include/phy.h b/include/phy.h index d117fc1..2adfb44 100644 --- a/include/phy.h +++ b/include/phy.h @@ -241,6 +241,7 @@ int phy_teranetics_init(void); int phy_vitesse_init(void); int board_phy_config(struct phy_device *phydev); +int get_phy_id(struct mii_dev *bus, int addr, int devad, u32 *phy_id); /* PHY UIDs for various PHYs that are referenced in external code */ #define PHY_UID_CS4340 0x13e51002 -- 2.1.0.27.g96db324

2 1

[U-Boot] [PATCH 1/4] mtd: vf610_nfc: use in-band bad block table
by Stefan Agner 07 Apr '15

07 Apr '15

Use in-band bad block table (NAND_BBT_NO_OOB) which allows to use the full OOB for hardare ECC purposes. Since there is no ECC correction on the OOB it is also safer to use in-band area to store the bad block table marker. Signed-off-by: Stefan Agner <stefan(a)agner.ch> --- drivers/mtd/nand/vf610_nfc.c | 29 ++--------------------------- 1 file changed, 2 insertions(+), 27 deletions(-) diff --git a/drivers/mtd/nand/vf610_nfc.c b/drivers/mtd/nand/vf610_nfc.c index 75c2493..8608ac3 100644 --- a/drivers/mtd/nand/vf610_nfc.c +++ b/drivers/mtd/nand/vf610_nfc.c @@ -155,29 +155,6 @@ struct vf610_nfc { #define mtd_to_nfc(_mtd) \ (struct vf610_nfc *)((struct nand_chip *)_mtd->priv)->priv -static u8 bbt_pattern[] = {'B', 'b', 't', '0' }; -static u8 mirror_pattern[] = {'1', 't', 'b', 'B' }; - -static struct nand_bbt_descr bbt_main_descr = { - .options = NAND_BBT_LASTBLOCK | NAND_BBT_CREATE | NAND_BBT_WRITE | - NAND_BBT_2BIT | NAND_BBT_VERSION, - .offs = 11, - .len = 4, - .veroffs = 15, - .maxblocks = 4, - .pattern = bbt_pattern, -}; - -static struct nand_bbt_descr bbt_mirror_descr = { - .options = NAND_BBT_LASTBLOCK | NAND_BBT_CREATE | NAND_BBT_WRITE | - NAND_BBT_2BIT | NAND_BBT_VERSION, - .offs = 11, - .len = 4, - .veroffs = 15, - .maxblocks = 4, - .pattern = mirror_pattern, -}; - static struct nand_ecclayout vf610_nfc_ecc45 = { .eccbytes = 45, .eccpos = {19, 20, 21, 22, 23, @@ -622,10 +599,8 @@ static int vf610_nfc_nand_init(int devnum, void __iomem *addr) /* Bad block options. */ if (cfg.flash_bbt) - chip->bbt_options = NAND_BBT_USE_FLASH | NAND_BBT_CREATE; - - chip->bbt_td = &bbt_main_descr; - chip->bbt_md = &bbt_mirror_descr; + chip->bbt_options = NAND_BBT_USE_FLASH | NAND_BBT_NO_OOB | + NAND_BBT_CREATE; /* Set configuration register. */ vf610_nfc_clear(mtd, NFC_FLASH_CONFIG, CONFIG_ADDR_AUTO_INCR_BIT); -- 2.3.5

3 12

[U-Boot] Copy to Flash... 9Flash not Erased
by Rudolf J Streif 07 Apr '15

07 Apr '15

I am getting the "Flash not Erased" error when writing to NOR flash with cp.b. I checked all of the obvious such as file exceeding the erased area etc. Below is the log including environment settings etc. You can see that about 14k of data is written and then the error occurs for a reason unbeknownst to me. Any suggestions are appreciated. Now, you may want to say "try a newer version of u-boot". However, that is not feasible due to other requirements. However, if there has been a known issue that has been fixed later, please let me know, what it is so that I can eventually backport it. I could not find it while searching the web and the mailing list posts. Thank you, Rudi U-Boot 2011.121.4.4 (Apr 01 2015 - 13:30:37) CPU0: 8572E, Version: 2.1, (0x80e80021) Core: E500, Version: 3.0, (0x80210030) Clock Configuration: CPU0:1250 MHz, CPU1:1250 MHz, CCB:500 MHz, DDR:333.330 MHz (666.660 MT/s data rate) (Asynchronous), LBC:62.500 MHz L1: D-cache 32 kB enabled I-cache 32 kB enabled Board: MyBoard I2C: ready DRAM: Detected UDIMM CT51264AC667.M16FC Detected UDIMM CT51264AC667.M16FC 6 GiB left unmapped 8 GiB (DDR2, 64-bit, CL=5, ECC off) Flash: 128 MiB L2: 1024 KB enabled PORDEVSR[IO_SEL_SRDS] = e NAND: 1536 MiB PCIe1: disabled, devdisr: 0x36000108, sdc: 0 PCIe2: disabled, devdisr: 0x36000108, sdc: 0 PCIe3: disabled, devdisr: 0x36000108, sdc: 0 In: serial Out: serial Err: serial Net: eTSEC1, eTSEC2, eTSEC3, eTSEC4 Hit any key to stop autoboot: 0 => => printenv baudrate=115200 bootcmd=setenv bootargs root=/dev/mtdblock5 rw rootfstype=jffs2 console=$consoledev,$baudrate $othbootargs; bootm $kernel_fladdr - $fdt_fladdr bootdelay=5 bootfile=/export/boot/uImage burnfdt=protect off $fdt_fladdr +$filesize; erase $fdt_fladdr +$filesize; cp.b $fdtaddr $fdt_fladdr $filesize; protect on $fdt_fladdr +$filesize burnkernel=protect off $kernel_fladdr +$filesize; erase $kernel_fladdr +$filesize; cp.b $kernel_addr $kernel_fladdr $filesize; protect on $kernel_fladdr +$filesize burnrootfs=nand device 0; nand erase.chip clean; nand write $rootfs_addr 0x0 $filesize consoledev=ttyS0 eth1addr=00:09:9C:03:80:45 eth2addr=00:09:9C:03:80:46 eth3addr=00:09:9C:03:80:47 ethact=eTSEC1 ethaddr=00:09:9C:03:80:44 fdt_addr=c00000 fdt_fladdr=0xeff00000 fdtaddr=c00000 fdtfile=uImage-myboard_36b.dtb gatewayip=10.0.0.1 getfdt=tftp $fdtaddr $user/$fdtfile getkernel=tftp $kernel_addr $user/$kernelfile getrootfs=tftp $rootfs_addr $user/$rootfsfile hostname=myboard hwconfig=fsl_ddr:ecc=off ipaddr=192.168.100.50 kernel_addr=0x1000000 kernel_fladdr=0xef800000 kernelfile=uImage-myboard.bin loadall=run loadkernel ; run loadfdt ; run loadrootfs loadfdt=run getfdt ; run burnfdt loadkernel=run getkernel ; run burnkernel loadrootfs=run getrootfs ; run burnrootfs loads_echo=1 mtdids=nand0=config-flash-0 netdev=eth0 netmask=255.255.255.0 oldkernelfile=uImage-git-r1318-myboard-20130531192736.bin oldrootfsfile=cssp-bams-myboard2-20140127153741.rootfs.jffs2 othbootargs=rio-scan.scan=1 riohdid=0 enforcing=0 selinux=0 loglevel=8 rootfs_addr=2000000 rootfsfile=core-image-selinux-myboard.jffs2 rootpath=/export/rootfs serverip=192.168.100.196 stderr=serial stdin=serial stdout=serial uboot=/export/u-boot/u-boot.bin uboot_fladdr=0xeff80000 user=streif-selinux Environment size: 1856/8188 bytes => run getkernel Speed: 1000, full duplex Using eTSEC1 device TFTP from server 192.168.100.196; our IP address is 192.168.100.50 Filename 'streif-selinux/uImage-myboard.bin'. Load address: 0x1000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# # done Bytes transferred = 3821142 (3a4e56 hex) => protect off 0xef800000 +0x3a4e56 Un-Protected 30 sectors => erase 0xef800000 +0x3a4e56 .............................. done Erased 30 sectors => flinfo Bank # 1: CFI conformant flash (16 x 16) Size: 128 MB in 1024 Sectors AMD Standard command set, Manufacturer ID: 0x89, Device ID: 0x227E2801 Erase timeout: 4096 ms, write timeout: 2 ms Buffer write timeout: 5 ms, buffer size: 1024 bytes Sector Start Addresses: E8000000 E E8020000 E E8040000 E E8060000 E E8080000 E E80A0000 E E80C0000 E E80E0000 E E8100000 E E8120000 E <omitted> EF800000 E EF820000 E EF840000 E EF860000 E EF880000 E EF8A0000 E EF8C0000 E EF8E0000 E EF900000 E EF920000 E EF940000 E EF960000 E EF980000 E EF9A0000 E EF9C0000 E EF9E0000 E EFA00000 E EFA20000 E EFA40000 E EFA60000 E EFA80000 E EFAA0000 E EFAC0000 E EFAE0000 E EFB00000 E EFB20000 E EFB40000 E EFB60000 E EFB80000 E EFBA0000 E EFBC0000 E EFBE0000 E EFC00000 E EFC20000 E EFC40000 E EFC60000 E EFC80000 E EFCA0000 E EFCC0000 E EFCE0000 E EFD00000 E EFD20000 E EFD40000 E EFD60000 E EFD80000 E EFDA0000 E EFDC0000 E EFDE0000 E EFE00000 E EFE20000 E EFE40000 E EFE60000 E EFE80000 E EFEA0000 E EFEC0000 E EFEE0000 E EFF00000 EFF20000 E EFF40000 E EFF60000 RO EFF80000 RO EFFA0000 RO EFFC0000 RO EFFE0000 => md 0xef800000 ef800000: ffffffff ffffffff ffffffff ffffffff ................ ef800010: ffffffff ffffffff ffffffff ffffffff ................ ef800020: ffffffff ffffffff ffffffff ffffffff ................ ef800030: ffffffff ffffffff ffffffff ffffffff ................ ef800040: ffffffff ffffffff ffffffff ffffffff ................ ef800050: ffffffff ffffffff ffffffff ffffffff ................ ef800060: ffffffff ffffffff ffffffff ffffffff ................ ef800070: ffffffff ffffffff ffffffff ffffffff ................ ef800080: ffffffff ffffffff ffffffff ffffffff ................ ef800090: ffffffff ffffffff ffffffff ffffffff ................ ef8000a0: ffffffff ffffffff ffffffff ffffffff ................ ef8000b0: ffffffff ffffffff ffffffff ffffffff ................ ef8000c0: ffffffff ffffffff ffffffff ffffffff ................ ef8000d0: ffffffff ffffffff ffffffff ffffffff ................ ef8000e0: ffffffff ffffffff ffffffff ffffffff ................ ef8000f0: ffffffff ffffffff ffffffff ffffffff ................ <omitted> ef820000: ffffffff ffffffff ffffffff ffffffff ................ ef820010: ffffffff ffffffff ffffffff ffffffff ................ ef820020: ffffffff ffffffff ffffffff ffffffff ................ ef820030: ffffffff ffffffff ffffffff ffffffff ................ ef820040: ffffffff ffffffff ffffffff ffffffff ................ ef820050: ffffffff ffffffff ffffffff ffffffff ................ ef820060: ffffffff ffffffff ffffffff ffffffff ................ ef820070: ffffffff ffffffff ffffffff ffffffff ................ ef820080: ffffffff ffffffff ffffffff ffffffff ................ ef820090: ffffffff ffffffff ffffffff ffffffff ................ ef8200a0: ffffffff ffffffff ffffffff ffffffff ................ ef8200b0: ffffffff ffffffff ffffffff ffffffff ................ ef8200c0: ffffffff ffffffff ffffffff ffffffff ................ ef8200d0: ffffffff ffffffff ffffffff ffffffff ................ ef8200e0: ffffffff ffffffff ffffffff ffffffff ................ ef8200f0: ffffffff ffffffff ffffffff ffffffff ................ => cp.b 0x1000000 0xef800000 0x3a4e56 Copy to Flash... 9Flash not Erased => md 0xef800000 ef800000: 27051956 d205005a 54a472c4 003a4e16 '..V...ZT.r..:N. ef800010: 00000000 00000000 f6e00283 05070201 ................ ef800020: 4c696e75 782d332e 31302e35 392d6c74 Linux-3.10.59-lt ef800030: 73692d31 2e342e34 00000000 00000000 si-1.4.4........ ef800040: 1f8b0800 00000000 0203dc5a 0d501467 ...........Z.P.g ef800050: 9a7e6718 701c8836 3fc99268 7488c405 .~g.p..6?..ht... ef800060: 41193de2 f6c8808d 98aa118c 0b0a89ba A.=............. ef800070: c965c840 a28839f0 273566bb e919e86c .e.@..9.'5f....l ef800080: 8478558c b05b0614 47c55e45 dcb839af .xU..[..G.^E..9. ef800090: ce4a8c69 374a3cd7 e44ce2dd 25e64748 .J.i7J<..L..%.GH ef8000a0: 4ca9c4dd a03139e3 0f7defdb 3d430041 L....19..}..=C.A ef8000b0: b3757b55 1aaaa8e7 ebefe7fd 9ef7f9de .u{U............ ef8000c0: effdbea6 71014015 805c65b3 c88f4ef5 ....q.@..\e...N. ef8000d0: b6cc8f3e d35b35bd 59e6617c 62557493 ...>.[5.Y.a|bUt. ef8000e0: 5cd5d024 3f1afd6e ef0cce04 55f3d7da \..$?..n....U... ef8000f0: 66cc5755 7e653d5b b5b9de23 aacd1ef1 f.WU~e=[...#.... <omitted> ef803a10: d32ca36c 99696174 83aef728 eaae98b4 .,.l.iat...(.... ef803a20: 9165113c c367c211 e31c27fa e4f014c0 .e.<.g....'..... ef803a30: ffffffff ffffffff ffffffff ffffffff ................ ef803a40: ffffffff ffffffff ffffffff ffffffff ................

3 2

[U-Boot] u-boot summit / miniconf this year?
by Hans de Goede 07 Apr '15

07 Apr '15

Hi, I'm thinking about going to ELCE, assuming I will not have some schedule conflict, one of the reasons is that I would like to attend the u-boot summit / miniconf again this year. Which raises the question will it be held at ELCE again ? Regards, Hans

3 2

[U-Boot] [PATCH v3 0/3] i2c: sunxi: Support every i2c controller on each supported platform
by Paul Kocialkowski 07 Apr '15

07 Apr '15

Changes since v2: * I2C/TWI busses enable for Cubietruck as well Changes since v1: * Kconfig option to enable I2C/TWI controllers 1-4 (when applicable) * Following patch to enable exposed busses on a few community-supported single-board-computers This series adds support for every i2c controller found on sun4i/sun5i/sun6i/sun7i/sun8i platforms and shouldn't break support for Marvell platforms (orion5x, kirkwood, armada xp) the driver was originally written for. Regarding sunxi, I double-checked that this doesn't conflict with VIDEO_LCD_PANEL_I2C. I would be interested in having this tested on sun8i (A23), since I changed TWI0 muxing (to PH2-PH3 instead of PB0-PB1), according to the user manual and what is being done on the upstream Linux kernel. I2C was either not working before, or it was being muxed correctly by the bootrom, probably to communicate with the AXP, which luckily made it work in U-Boot too, since the I/O base address was already correct. My use case here is that I'm writing a slave-side bitbang i2c implementation (with an Arduino) for a school project, using a Cubieboard2 as master and U-Boot as POC. However, only TWI1 was available through the expansion pins, hence the need for this series.

3 10