Hi Yamada,
The init.elf is used to debug u-boot boot process on Blackfin via JTAG. You
can't load u-boot binary to memory via JTAG without run the init.elf in
Blackfin L1 SRAM first. So, this can't be removed.
Regards,
Sonic
-Original Message-
From: Masahiro Yamada
The build rules of
- include/autoconf.mk.dep
- include/autoconf.mk
- include/spl-autoconf.mk
- include/tpl-autoconf.mk
were wrong.
They created empty files (which are never updated)
if an error occurrs during preprocessing.
Signed-off-by: Masahiro Yamada yamad...@jp.panasonic.com
---
Hi Tom,
On Tuesday 26 November 2013 08:06 PM, Tom Rini wrote:
On Tue, Nov 26, 2013 at 12:22:19PM +0530, Lokesh Vutla wrote:
Hi Chao,
On Tuesday 26 November 2013 10:32 AM, Chao Xu wrote:
Thank you! Please see the inline reply.
On Mon, Nov 25, 2013 at 10:40 PM, Lokesh Vutla lokeshvu...@ti.com
Hello Sonic
The init.elf is used to debug u-boot boot process on Blackfin via JTAG. You
can't load u-boot binary to memory via JTAG without run the init.elf in
Blackfin L1 SRAM first. So, this can't be removed.
I understand. Thanks!
Please reject this patch.
How about the other one?
NAK
Sonic Zhang
On Fri, Nov 29, 2013 at 2:34 PM, Masahiro Yamada
yamad...@jp.panasonic.com wrote:
Signed-off-by: Masahiro Yamada yamad...@jp.panasonic.com
---
Hello Sonic
This file too.
It looks like arch/blackfin/cpu/init.elf is not used.
Please let me know if this file is necessary or
Hi Kuo-Jung,
On Fri, 2013-11-29 at 08:59 +0800, Kuo-Jung Su wrote:
No it's a common misunderstanding, I also made the same mistake before.
Please check my bug fix for Faraday FTI2C010 I2C driver:
http://patchwork.ozlabs.org/patch/294732/
The address should be rebuild inside the i2c driver
2013/11/29 Alexey Brodkin alexey.brod...@synopsys.com:
Hi Kuo-Jung,
On Fri, 2013-11-29 at 08:59 +0800, Kuo-Jung Su wrote:
No it's a common misunderstanding, I also made the same mistake before.
Please check my bug fix for Faraday FTI2C010 I2C driver:
There's no point in having of dwmmc.h per architecure - we're talking
about device driver (DesignWare MMC controller) which is expected to
work with any CPU it is attached to.
Actually this change should have been an essential part of commit:
===
6f0b7caa671f92c2d4676c84381d17fb90f7d2cd
Herein lie a number of patches to add support for WPJ344 board in
U-Boot. These patches add the following features to the board:
One Ethernet port enabled (the one closest to power jack)
SPI drivers
Nikolaos Pasaloukos (7):
MIPS: AR7240: Address space declaration for SoC ar7240
This file declares many address spaces for ar7240 System On Chip
Signed-off-by: Nikolaos Pasaloukos nikolaos.pasalou...@imgtec.com
Cc: Daniel Schwierzeck daniel.schwierz...@gmail.com
---
arch/mips/include/asm/ar7240_addrspace.h | 387 +++
1 file changed, 387
Add support for DRAM initialization on ar7240 and similar SoC
Signed-off-by: Nikolaos Pasaloukos nikolaos.pasalou...@imgtec.com
Cc: Daniel Schwierzeck daniel.schwierz...@gmail.com
---
arch/mips/cpu/mips32/ar7240/Makefile | 7 +
arch/mips/cpu/mips32/ar7240/ar7240_dram.c | 298
Add ethernet support to ar934x using Atheros phy
Signed-off-by: Nikolaos Pasaloukos nikolaos.pasalou...@imgtec.com
Cc: Joe Hershberger joe.hershber...@gmail.com
---
drivers/net/phy/atheros.c | 42 +++
1 file changed, 42 insertions(+)
diff --git
Add SPI drivers for ar7240 SoC
Signed-off-by: Nikolaos Pasaloukos nikolaos.pasalou...@imgtec.com
Cc: Jagannadha Sutradharudu Teki jagannadh.t...@gmail.com
---
drivers/spi/Makefile | 1 +
drivers/spi/ar7240_spi.c | 97
2 files changed, 98
Add Ethernet support for AR934x SoC. Since it uses Atheros generic phy
support, only one Ethernet port is being set up.
Signed-off-by: Nikolaos Pasaloukos nikolaos.pasalou...@imgtec.com
Cc: Joe Hershberger joe.hershber...@gmail.com
---
drivers/net/Makefile | 1 +
drivers/net/ar934x.c | 572
Hi Alexey,
On 11/29/2013 04:41 PM, Alexey Brodkin wrote:
Hi Jaehoon,
On Fri, 2013-11-29 at 12:46 +0900, Jaehoon Chung wrote:
Hi, Alexey,
I didn't know exactly which version is used this register.
I known this register is used only the exynos series.
I have checked the IP version 2.70a,
On Fri, 2013-11-29 at 17:32 +0800, Kuo-Jung Su wrote:
Unfortunately I still cannot agree with you.
In my opinion I2C driver has nothing to do with current situation.
Yes, that's why I said the root cause is U-Boot's I2C model.
The address should never be rebuilt/reformated inside the I2C
Hi Alexey,
I have replied the previous patch.
On 11/29/2013 06:39 PM, Alexey Brodkin wrote:
There's no point in having of dwmmc.h per architecure - we're talking
about device driver (DesignWare MMC controller) which is expected to
work with any CPU it is attached to.
Actually this change
On Fri, 2013-11-29 at 18:57 +0900, Jaehoon Chung wrote:
I think good that just removed the #include asm/arch/dwmmc.h.
Instead, Exnyos specific code can move into dw-mmc-exynos.c with callback
function.
(I didn't know whcih Soc is used with MPSCTRL register.)
Because of this you selected
On 11/29/2013 07:02 PM, Alexey Brodkin wrote:
On Fri, 2013-11-29 at 18:57 +0900, Jaehoon Chung wrote:
I think good that just removed the #include asm/arch/dwmmc.h.
Instead, Exnyos specific code can move into dw-mmc-exynos.c with callback
function.
(I didn't know whcih Soc is used with
On Fri, 2013-11-29 at 19:00 +0900, Jaehoon Chung wrote:
remove this and use callback function like the host-board_init()?
if (host-board_init())
host-board_init(host);
Then we can reuse the this function for board specific code.
Anyway, I think that exynos code didn't exist at
Hi Nikita,
2013/11/28 Nikita Kiryanov nik...@compulab.co.il:
Writing zero into I2Ci.I2C_CNT register causes random I2C failures in OMAP3
based devices. This seems to be related to the following advisory which
apears in multiple erratas for OMAP3 SoCs (OMAP35xx, DM37xx), as well as
OMAP4430
From: Jens Scharsig (BuS Elektronik) e...@bus-elektronik.de
* remove mature defines from board config
Signed-off-by: Jens Scharsig (BuS Elektronik) e...@bus-elektronik.de
---
include/configs/eb_cpux9k2.h | 4
1 file changed, 4 deletions(-)
diff --git a/include/configs/eb_cpux9k2.h
Dear Masahiro Yamada,
Hello
How come 13/13 is missing?
I see it here.
Best regards,
Marek Vasut
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hello!
I'm trying to compile fw_printenv, to work with U-Boot environment
variables under my linux os. I'm using commands:
$ cd u-boot/
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- env
The tool compiles successfully, I get the executable under
u-boot/tools/env/fw_printenv, but it
On Thu, Nov 28, 2013 at 5:57 PM, Tom Rini tr...@ti.com wrote:
On Thu, Nov 28, 2013 at 05:39:09PM +0100, Yegor Yefremov wrote:
I'm having problems with the new u-boot (November 2013) and am3517
SoC. When I start Debian 7.0 armhf I get lots of Segmentation faults,
I can't even perform apt-get
dw-mmc.c is the general driver file.
So, remove the exynos specific code at dw-mmc.c.
Instead, exynos specific cod can be move into exynos-dw_mmc.c.
Signed-off-by: Jaehoon Chung jh80.ch...@samsung.com
---
drivers/mmc/dw_mmc.c| 12 ++--
drivers/mmc/exynos_dw_mmc.c | 14
This series adds new macros to name a GPIO, it uses again a single number
(as the legacy at91_pio api does).
It converts the at91-nand and the at91-led stuff to use these new GPIO
numbers. But it is not the whole thing at once, I have another RFC to add new
portmux API which is more close to the
This patch define new names for GPIO pins on at91 devices. Follow up patches
will convert the whole infrastructure to use these new definitions.
Signed-off-by: Andreas Bießmann andreas.de...@googlemail.com
---
arch/arm/include/asm/arch-at91/gpio.h | 24 +++-
In order to get the very same value for legacy pin definitions and new gpio
definitions set the legacy PIN_BASE to 0.
Signed-off-by: Andreas Bießmann andreas.de...@googlemail.com
---
arch/arm/include/asm/arch-at91/gpio.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Signed-off-by: Andreas Bießmann andreas.de...@googlemail.com
---
board/BuS/vl_ma2sc/vl_ma2sc.c |5 +++--
board/egnite/ethernut5/ethernut5.c |3 ++-
board/esd/meesc/meesc.c|5 +++--
board/esd/otc570/otc570.c |5 +++--
board/eukrea/cpu9260/cpu9260.c |
Signed-off-by: Andreas Bießmann andreas.de...@googlemail.com
---
arch/arm/cpu/arm926ejs/at91/led.c | 16 +++-
board/ronetix/pm9261/led.c| 14 +++---
board/ronetix/pm9263/led.c| 10 +-
include/configs/pm9261.h |6 +++---
Hi Alexey,
I'm trying to compile fw_printenv, to work with U-Boot environment
variables under my linux os. I'm using commands:
$ cd u-boot/
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- env
The tool compiles successfully, I get the executable under
u-boot/tools/env/fw_printenv, but
From: Yegor Yefremov yegorsli...@googlemail.com
Pin 30 is connected to PHY's RESET# signal, so it must be
put to high. Otherwize PHY won't be found via MDIO interface.
Signed-off-by: Yegor Yefremov yegorsli...@googlemail.com
---
board/logicpd/am3517evm/am3517evm.c | 34
As mEMAC1 and mEMAC2 are dual-role MACs, which are used as 1G or 10G MAC.
So we update dynamically 'cell-index' to '2' and '3' for 10GEC3 and 10GEC4.
Also change 'fsl,fman-port-1g-rx' to 'fsl,fman-port-10g-rx', ditto for Tx.
Signed-off-by: Shengzhou Liu shengzhou@freescale.com
---
Plz pull the patch mentioned above, and much of things should be cleaned up
http://lists.denx.de/pipermail/u-boot/2013-November/167696.html
Thank you for the reply Pekon, but sadly even after applying your
patch the earlier compile issue is still present. Starting from a copy
of mainline
Acked-by: Alexey Brodkin abrod...@synopsys.com
On Fri, 2013-11-29 at 20:08 +0900, Jaehoon Chung wrote:
dw-mmc.c is the general driver file.
So, remove the exynos specific code at dw-mmc.c.
Instead, exynos specific cod can be move into exynos-dw_mmc.c.
Signed-off-by: Jaehoon Chung
Dear Mateusz Kulikowski,
On 11/28/2013 10:29 PM, Mateusz Kulikowski wrote:
On 11.11.2013 12:03, Andreas Bießmann wrote:
snip
+
+/* Enable NandFlash */
+at91_set_gpio_output(CONFIG_SYS_NAND_ENABLE_PIN, 1);
Here you could really use the gpio_direction_output(). I sent out an RFC
Hi,
Had raised this point when I had got comments for the patch
[10/10,V4] DWMMC: SMDK5420: Disable SMU for eMMC
https://patches.linaro.org/20666/
Acked-by:Rajeshwari Shinde rajeshwar...@samsung.com
Regards,
Rajeshwari Shinde
On Fri, Nov 29, 2013 at 4:53 PM, Alexey Brodkin
Hi Jaehoon,
Looks good
On Nov 29, 2013, at 1:08 PM, Jaehoon Chung wrote:
dw-mmc.c is the general driver file.
So, remove the exynos specific code at dw-mmc.c.
Instead, exynos specific cod can be move into exynos-dw_mmc.c.
Signed-off-by: Jaehoon Chung jh80.ch...@samsung.com
---
Hi Alexey,
On Nov 29, 2013, at 12:08 PM, Alexey Brodkin wrote:
On Fri, 2013-11-29 at 19:00 +0900, Jaehoon Chung wrote:
remove this and use callback function like the host-board_init()?
if (host-board_init())
host-board_init(host);
Then we can reuse the this function for board
All looks good from my side;
Please do a boot test on the real hardware and let me know before
I can apply.
Hi Pantelis,
confirming - builds/works good for me.
-Alexey
___
U-Boot mailing list
U-Boot@lists.denx.de
Hm... I'm notr sure what exactly you are trying to do here - I cannot
find the string tsec_miiphy_write anywhere in the U-Boot source
code.
Hi Wolfgang,
tsec_miiphy_write function is present in drivers/net/tsec.c of the
U-Boot-201009 version which I downloaded.
The flow of calls is:
2013/11/29 Wolfgang Denk w...@denx.de:
Dear Abraham V.,
In message
canie1qo9fdokevjq89w3ceoxryic9d_do71vv9brtg7bnj-...@mail.gmail.com you
wrote:
I didn't notice that difference until you pointed it out. Till now, I was
under the assumption that both toolchains were (feature-wise)
Hello Pekon,
An addendum to my last mail; I tried digging into the build mechanism
and finally got the system to build without errors with the following
patch,
diff --git a/arch/arm/cpu/armv7/omap-common/Makefile
b/arch/arm/cpu/armv7/omap-common/Makefile
index 4d3a165..5eeecce 100644
---
Dear Detlev,
I ran
$ make HOSTCC=arm-none-linux-gnueabi-gcc env
and got the tools/env/fw_printenv executable. But the Make command
returned error:
strip: Unable to recognise the format of the input file `fw_printenv'
make[1]: *** [fw_printenv] Error 1
I guess, HOSTSTRIP variable also has to
hi Bhupesh,
Thank you for reviewing of the patch.
+/*
+ * Generic timer implementation of timer_read_counter()
+ */
+unsigned long timer_read_counter(void)
+{
+ unsigned long cntpct;
+ isb();
+ asm volatile(mrs %0, cntpct_el0 : =r (cntpct));
+ return cntpct;
+}
2013/11/29 Alexey Brodkin alexey.brod...@synopsys.com:
On Fri, 2013-11-29 at 17:32 +0800, Kuo-Jung Su wrote:
Unfortunately I still cannot agree with you.
In my opinion I2C driver has nothing to do with current situation.
Yes, that's why I said the root cause is U-Boot's I2C model.
The
Align with the context to use readl() to read the CCM_CCGR3
register with memory barrier instead of __raw_readl().
Signed-off-by: Liu Ying ying@freescale.com
---
board/freescale/mx6sabresd/mx6sabresd.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Hi Nikita,
On 28/11/13 18:04, Nikita Kiryanov wrote:
Writing zero into I2Ci.I2C_CNT register causes random I2C failures in OMAP3
based devices. This seems to be related to the following advisory which
apears in multiple erratas for OMAP3 SoCs (OMAP35xx, DM37xx), as well as
OMAP4430 TRM:
On Fri, Nov 29, 2013 at 12:38 PM, Liu Ying ying@freescale.com wrote:
Align with the context to use readl() to read the CCM_CCGR3
register with memory barrier instead of __raw_readl().
Signed-off-by: Liu Ying ying@freescale.com
Reviewed-by: Fabio Estevam fabio.este...@freescale.com
Dear rvijay435,
In message 1385728248832-168658.p...@n7.nabble.com you wrote:
Hm... I'm notr sure what exactly you are trying to do here - I cannot
find the string tsec_miiphy_write anywhere in the U-Boot source
code.
Hi Wolfgang,
tsec_miiphy_write function is present in
Dear Christian Gmeiner,
In message cah9nwweb6s+3s4o25d7cifob9y3_7jmhosjo6o78fijquwz...@mail.gmail.com
you wrote:
I am running into the same problem. Me wonders which patch/change
triggers this problem. I am using
the same toolchain since I started to work with u-boot and it fails
with the
Hi Eric,
Thanks Marek,
On 11/11/2013 09:22 AM, Marek Vasut wrote:
Enable PCI express on MX6 Sabrelite.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Albert Aribaud albert.u.b...@aribaud.net
Cc: Eric Nelson eric.nel...@boundarydevices.com
Cc: Fabio Estevam
Dear Stefano Babic,
Hi Eric, Marek,
On 27/11/2013 17:19, Eric Nelson wrote:
It seems to lock up the system if you don't have the proper
device connected.
Without this bit, I was able to confirm proper enumeration
of a PCIe bus with a USB 3.0 controller:
00:01.0 -
2013/11/28 Axel Lin axel@ingics.com:
Hi list,
I use sf erase + sf write commands to write root image to spi nor flash.
It works for writing a ext2 image.
However, if I use the same commands to write a jffs2 image I got a lot
of Magic bitmask 0x1985 not found at... messages and
jffs2:
For invalid bus number, current code returns NULL in the default case of
switch-case statements. In additional, pins[bus] is always not NULL because
it is the address of specific row of the two-dimensional array.
Thus this patch removes these unnecessary test.
Signed-off-by: Axel Lin
For invalid bus number, current code returns NULL in the default case of
switch-case statements. In additional, pins[bus] is always not NULL because
it is the address of specific row of the two-dimensional array.
Thus this patch removes these unnecessary test.
Signed-off-by: Axel Lin
This patch change the per_clocks_enable() function used in OMAP3
code to enable peripherals clocks. Only required clock should be
activated. So if the board use the uart(x) as a console we need
to activate it. The Board's config should include define to enable
every subsystem that the board use.
58 matches
Mail list logo
