On 25/04/2013 14:48, Stefan Roese wrote:
On 25.04.2013 14:38, Marek Vasut wrote:
Right, this is also correct. Anyway, BOOT_FROM is used to get the offset
inside the storage, and only to be as much flexible as possible, each
storage has defined its own offset. However, Freescale uses the same
On 25/04/2013 14:49, Benoît Thébaudeau wrote:
Hi Stefan,
On Thursday, April 25, 2013 2:48:59 PM, Stefan Roese wrote:
Subject: Re: [U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK
On 25.04.2013 14:38, Marek Vasut wrote:
Right, this is also correct. Anyway, BOOT_FROM is used to
Hello Heiko,
On 24.04.2013 15:00, Dirk Eibach wrote:
Hello Heiko,
On 24.04.2013 13:43, Dirk Eibach wrote:
Signed-off-by: Dirk Eibach dirk.eib...@gdsys.cc
Cc: Heiko Schocher h...@denx.de
Cc: Stefan Roese s...@denx.de
---
drivers/i2c/Makefile |2 +-
drivers/i2c/ppc4xx_i2c.c | 193
Hi Stefano,
On Thursday, April 25, 2013 3:02:25 PM, Stefano Babic wrote:
On 25/04/2013 14:49, Benoît Thébaudeau wrote:
Hi Stefan,
On Thursday, April 25, 2013 2:48:59 PM, Stefan Roese wrote:
Subject: Re: [U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK
On 25.04.2013
On 25/04/2013 15:16, Benoît Thébaudeau wrote:
Is it padded at the beginnig ? I have thought the pad is between SPL and
u-boot based on CONFIG_SPL_PAD_TO, but we need to flash always at the
right offset.
Here are the image types that we currently have:
- u-boot.imx: imx header +
Dear takeshi.harada...@hitachi.com,
In message XNM2$7$1$4$$7$7$5$A$1011959u51788...@hitachi.com you wrote:
Do you mean the U-Boot contains cryptographic algorithms
that makes 5D002?
I have to admit that I'm not 100% sure about that. U-Boot includes
the sha1 and sha256 message digest
Dear tiger...@viatech.com.cn,
In message fe7aded5c2218b4786c09cd97dc4c49f87c...@exchbj02.viatech.com.bj you
wrote:
Hi, experts:
MIPI(Mobile Industry Processor Interface) has defined many mobile device
interface.
Such as:
CSI --- for Camera
DSI --- for Display
It seems DSI has samples on
Dear Stefano Babic,
On 24/04/2013 20:52, Marek Vasut wrote:
But you forget that a single image can be saved on multiple storage:
u-boot.imx can be stored on SD or NOR or SPI-NOR, and that is the reason
for having SOC-specific extension.
I agree with Benoit: at the moment, only people
Hi Benoît,
On 25.04.2013 14:49, Benoît Thébaudeau wrote:
Yes, I would prefer that.
And being at it, why don't we add the offset to the resulting image as
well? This would make programming the images to the destination (SD,
NAND, MMC etc) easier. We would not have to care for the correct
Hello Dirk,
On 25.04.2013 15:21, Dirk Eibach wrote:
Hello Heiko,
On 24.04.2013 15:00, Dirk Eibach wrote:
Hello Heiko,
On 24.04.2013 13:43, Dirk Eibach wrote:
Signed-off-by: Dirk Eibach dirk.eib...@gdsys.cc
Cc: Heiko Schocher h...@denx.de
Cc: Stefan Roese s...@denx.de
---
Hi Simon,
On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass s...@chromium.org wrote:
Hi,
On Tue, Apr 23, 2013 at 3:11 PM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 3:25 AM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 3:10 AM,
Dear Stefan Roese,
Hi Benoît,
On 25.04.2013 14:49, Benoît Thébaudeau wrote:
Yes, I would prefer that.
And being at it, why don't we add the offset to the resulting image as
well? This would make programming the images to the destination (SD,
NAND, MMC etc) easier. We would not have
On 25/04/2013 15:36, Marek Vasut wrote:
Dear Stefano Babic,
Hi Marek,
At least add documentation in the README. It is only your choice if you
will add two different targets to boards.cfg
I'd prefer not to do that. We're currently booting from NAND and SD, so we
use
u-boot.imx resp.
Dear Stefano Babic,
On 25/04/2013 15:36, Marek Vasut wrote:
Dear Stefano Babic,
Hi Marek,
At least add documentation in the README. It is only your choice if you
will add two different targets to boards.cfg
I'd prefer not to do that. We're currently booting from NAND and SD, so
Greetings,
I've been playing with controlling a bq2415x battery charger chip on I2C on a
custom OMAP4 board. In USB/OTG charging mode the code currently monitors the
charger chip in a loop to which I added a msleep(2000) call.
I did that thinking that since battery parameters don't change very
On Thu, Apr 25, 2013 at 01:59:37PM +0800, Julius Hemanth P wrote:
This code is small snippet from patch
ftp://ftp.linux4sam.org/pub/uboot/u-boot-v2010.06/u-boot-5series_1.0.patch
Bug:-
For board at91sam9x5ek, U-boot doesn't pass serial and revision tags
to Linux kernel, hence kernel fails
While other architectures have enabled these gcc / ld options for some
time on U-Boot itself, ARM has only been doing this on SPL. Enable this
on full U-Boot as well now.
Cc: Albert ARIBAUD albert.u.b...@aribaud.net
Signed-off-by: Tom Rini tr...@ti.com
---
arch/arm/config.mk |3 +++
Hi,
I'm building u-boot from the git master for a powerpc target. I'm using
the P2020RDB_SDCARD configuration.
During the final link I get: uboot/arch/powerpc/cpu/mpc85xx/start.S:1118:
relocation truncated to fit: R_PPC_REL24 against symbol `_start_cont'
defined in .text section in
Hello,
I'm a newbie using U-boot and met several problems
with a customized board based on MPC8315E-RDB board.
On the new board, I have changed the Ethernet PHY to TI's DP83848
and NAND FLASH to 64Mbit (from old 32Mbit).
During U-boot form NOR FLASH , I met two problems :
1, if NAND
Hi Jagan,
On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass s...@chromium.org wrote:
Hi,
On Tue, Apr 23, 2013 at 3:11 PM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 3:25 AM,
On Mon, Apr 01, 2013 at 05:06:16PM +0300, Lubomir Popov wrote:
Signed-off-by: Lubomir Popov lpo...@mm-sol.com
Thought I had reviewed this already, sorry.
---
The som5_evb is an evaluation board for the APM-5 - a OMAP5430-based SOM
(system
On a Module) designed by MMS and manufactured
Hi Simon,
On Fri, Apr 26, 2013 at 12:22 AM, Simon Glass s...@chromium.org wrote:
Hi Jagan,
On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass s...@chromium.org wrote:
Hi,
On Tue, Apr 23, 2013 at 3:11 PM,
Dear Wolfgang Denk,
Dear Marek,
In message 201304220109.14740.ma...@denx.de you wrote:
Looking through the code, it seems CONFIG_SYS_LOAD_ADDR is preferred over
CONFIG_LOADADDR, so this should be fixed on all places then ? Just to be
clear on this.
CONFIG_SYS_LOAD_ADDR is _used_, but
On 11/04/2013 11:39, Stefan Roese wrote:
Add spaces before and after .
Please note that I intentionally didn't wrap the 80 lines for
the sake of better readability.
Signed-off-by: Stefan Roese s...@denx.de
---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
--
On 17/04/2013 16:39, Philip Paeps wrote:
Prior to this fix, calls to mxc_iomux_set_input() for registers
after MUX_IN_GPIO2_IN_19 would write to the wrong registers,
possibly resulting in unexpected behaviour.
Signed-off-by: Philip Paeps phi...@paeps.cx
---
Applied to u-boot-imx, thanks.
On 17/04/2013 20:33, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Setup CCM_CCOSR register to provide a CKO1 clock frequency of 16.5 MHz.
CKO1 drives sgtl5000 codec clock on mx6qsabrelite and doing this setup in the
bootloader will allow us to remove a lot of code
On 18/04/2013 01:09, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
CKO1 drives sgtl5000 codec clock on nitrogen boards and wandboard.
Doing this setup in the bootloader will allow us to remove a lot of code in
arch/arm/mach-imx/mach-imx6q.c from the mainline kernel.
Hi Tom,
On Tue, Apr 23, 2013 at 7:50 AM, Tom Rini tr...@ti.com wrote:
On Mon, Apr 22, 2013 at 06:44:53PM -0500, Kim Phillips wrote:
On Sat, 20 Apr 2013 16:03:20 -0700
Simon Glass s...@chromium.org wrote:
On Mon, Apr 1, 2013 at 5:13 PM, Kim Phillips kim.phill...@freescale.com
wrote:
On
Dear Franck Jullien,
In message cajfokbwjyrtqnhub5gotxcpob_xneirnoz+b97ksvsy0fcx...@mail.gmail.com
you wrote:
I'm building u-boot from the git master for a powerpc target. I'm using
the P2020RDB_SDCARD configuration.
During the final link I get: uboot/arch/powerpc/cpu/mpc85xx/start.S:1118:
Dear du zhenhuan,
In message 202dafde.df1f.13e4197224a.coremail.dev...@163.com you wrote:
1, if NAND flash support is enabled,
U-boot just print out NAND : without size info and then print out text
like machine check ...,,
then print out resetting board ...
So the board keep resetting
On 19/04/2013 15:41, Otavio Salvador wrote:
This allow for easy update of firmware in the SD card from a running
U-Boot.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Applied to u-boot-imx, -next branch, thanks.
Best regards,
Stefano Babic
--
On 19/04/2013 15:41, Otavio Salvador wrote:
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Applied to u-boot-imx, -next branch, thanks.
Best regards,
Stefano Babic
--
=
DENX Software Engineering GmbH, MD:
On 19/04/2013 15:41, Otavio Salvador wrote:
This makes environment and mmcdev/mmcpart in sync with SYS_MMC_ENV_DEV
and SYS_MMC_ENV_PART settings.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Applied to u-boot-imx, -next branch, thanks.
Best regards,
Stefano Babic
--
On 19/04/2013 15:42, Otavio Salvador wrote:
This allow for easy update of firmware in the SD card from a running
U-Boot.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Changes in v3:
- New patch
Changes in v2: None
include/configs/wandboard.h | 16
1
On 19/04/2013 15:42, Otavio Salvador wrote:
This add support to identify if the card is connected or not; so it
does not try to communicate with the controller if no card is
available.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Discharge wrong applied message - patches are
On 19/04/2013 15:42, Otavio Salvador wrote:
Allow use of the carrier board MicroSD card available in the
Wandboard; this allow for loading alternative system from the other
card for testing or upgrade proposes.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Applied to
On 19/04/2013 15:42, Otavio Salvador wrote:
Adds support for 'bmode' command which let user to choose where to
boot from; this allows U-Boot to load system from another storage
without messing with jumpers.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Applied to u-boot-imx,
On 19/04/2013 23:04, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Update the environment as done in other imx boards to allow easy switching
between booting a non-dt kernel and a dt kernel.
Change CONFIG_LOADADDR to 0x9200, so that we can have the:
- uImage
On 19/04/2013 23:04, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Currently mmcrootfstype is set to ext3 type.
It is better not to force it in the env vars, because users may prefer a
different file system type, so let's get rid of 'mmcrootfstype'.
On 25/04/2013 02:44, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
When booting a FSL kernel based on 2.6.35 it is necessary to pass the revision
tag to the kernel.
Place a common weak function into soc.c for such purpose.
Signed-off-by: Fabio Estevam
On 25/04/2013 02:44, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
FSL 2.6.35 kernel expects that revision tag is passed by the bootloader.
Select CONFIG_REVISION_TAG so that mx53 boards can work properly with 2.6.35.
Signed-off-by: Fabio Estevam
On 25/04/2013 02:44, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
imx-regs.h is more appropriate location for containing register masks.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Applied to u-boot-imx, thanks.
Best regards,
Stefano Babic
--
Dear Fabio Estevam,
[..]
Shouldn't this function be placed into a common mx5 location? mx53ard
uses the same.
The WEIM and M4IF configuration is board-specific.
Right, understood. It seems like a duplication of code from mx53ard,
but anyway, what about:
Implement BOOT_OFFSET command for imximage. This command is parallel
to current BOOT_FROM command, but allows more flexibility in configuring
arbitrary image header offset. Also add an imximage.cfg with default
offset values into arm/arch/imx-common/ so the board-specific imximage.cfg
can include
Add basic support for the DENX M53EVK board. Currently supported is:
MMC (incl. booting)
NAND (incl. booting)
Ethernet, I2C, USB, SATA, RTC.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Albert ARIBAUD albert.u.b...@aribaud.net
Cc: Benoît Thébaudeau benoit.thebaud...@advansee.com
Cc: Fabio Estevam
On 10/04/2013 21:32, feste...@gmail.com wrote:
From: Fabio Estevam fabio.este...@freescale.com
Instead of having the same PAD control definition in each MX6 variant pin
file,
place it into a common location.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Hi Fabio,
On Mon, Apr 22, 2013 at 01:46:55PM +0100, Mark Jackson wrote:
NanoBone Specification:
---
CPU:
TI AM335x
Memory:
256MB DDR3
64MB NOR flash
256MB NAND flash
128KB FRAM
Ethernet:
2 x 10/100 connected to SMSC LAN8710 PHY
USB:
1 x USB2.0 Type A
Hi Stefano,
On Thursday, April 25, 2013 10:27:12 PM, Stefano Babic wrote:
On 10/04/2013 21:32, feste...@gmail.com wrote:
From: Fabio Estevam fabio.este...@freescale.com
Instead of having the same PAD control definition in each MX6 variant pin
file,
place it into a common location.
Dear Otavio Salvador,
The MX23 Boot ROM does blindly load from 2048 offset while the MX28
does parse the BCB header to known where to load the image from. We
move the BCB header to 4 sectors offset so same code can be used by
both SoCs avoiding code duplication.
This idea was given by
The arm_freq and ddr_freq variables are unused, so remove. Fixup
whitespace slightly while in here.
Signed-off-by: Tom Rini tr...@ti.com
---
arch/arm/cpu/armv7/am33xx/sys_info.c |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/arch/arm/cpu/armv7/am33xx/sys_info.c
Hi Marek,
On Thursday, April 25, 2013 10:16:02 PM, Marek Vasut wrote:
Implement BOOT_OFFSET command for imximage. This command is parallel
to current BOOT_FROM command, but allows more flexibility in configuring
arbitrary image header offset. Also add an imximage.cfg with default
offset
Dear Marek Vasut,
In message 1366920963-8646-2-git-send-email-ma...@denx.de you wrote:
...
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -954,6 +954,7 @@ Marek Vasut marek.va...@gmail.com
mx23_olinuxino i.MX23
m28evk i.MX28
sc_sps_1i.MX28
+ m53evk
On Thursday, April 25, 2013 10:32:50 PM, Benoît Thébaudeau wrote:
Hi Stefano,
On Thursday, April 25, 2013 10:27:12 PM, Stefano Babic wrote:
On 10/04/2013 21:32, feste...@gmail.com wrote:
From: Fabio Estevam fabio.este...@freescale.com
Instead of having the same PAD control
Hi Benoît,
On Thu, Apr 25, 2013 at 6:51 PM, Benoît Thébaudeau
benoit.thebaud...@advansee.com wrote:
I am working on converting mx25/35/5x to imx-common iomux-v3. I have noticed
in
arch/arm/cpu/armv7/mx5/iomux.c some is_soc_rev(CHIP_REV_2_0) that make this
change quite complicated for mx51.
Hi Vadim,
On Thu, Apr 18, 2013 at 8:50 AM, Vadim Bendebury (вб)
vben...@google.com wrote:
On Wed, Apr 17, 2013 at 7:13 PM, Simon Glass s...@chromium.org wrote:
This series removes unused x86 code based on advice from Graeme Russ. THis
code was used for real mode which is no longer needed in
Hi, Wolf:
Because U-boot is more powerful than before.
So, I want to develop a simple video monitor system based on u-boot code.
So, I care about current CSI support in u-boot code.
Best wishes,
-邮件原件-
发件人: Wolfgang Denk [mailto:w...@denx.de]
发送时间: 2013年4月25日 21:35
收件人: Tiger Liu
抄送:
Dear Benoît Thébaudeau,
Hi Marek,
[...]
@@ -52,6 +57,7 @@ enum imximage_cmd {
CMD_INVALID,
CMD_IMAGE_VERSION,
CMD_BOOT_FROM,
+ CMD_BOOT_OFFSET,
CMD_DATA
};
--
1.7.10.4
This looks good to me.
Yes, and it keeps compat too. Btw can you
Hello Wolfgang,
Dear Marek Vasut,
In message 1366920963-8646-2-git-send-email-ma...@denx.de you wrote:
...
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -954,6 +954,7 @@ Marek Vasut marek.va...@gmail.com
mx23_olinuxino i.MX23
m28evk i.MX28
sc_sps_1
Dear Paul B. Henson,
On 4/19/2013 6:22 PM, Trent Piepho wrote:
Hmm, possibly; I guess that would be conceptually simpler but
require more commands to execute to get done.
Don't see why. If mxsboot wrote both files at once, there'd be the
same number of commands to generate them.
Hi,
On Thu, Apr 25, 2013 at 12:06 PM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Fri, Apr 26, 2013 at 12:22 AM, Simon Glass s...@chromium.org wrote:
Hi Jagan,
On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki jagannadh.t...@gmail.com wrote:
Hi Simon,
On Wed, Apr 24, 2013 at 6:03
Hi Julius,
On 4/25/2013 13:59, Julius Hemanth P wrote:
This code is small snippet from patch
ftp://ftp.linux4sam.org/pub/uboot/u-boot-v2010.06/u-boot-5series_1.0.patch
Bug:-
For board at91sam9x5ek, U-boot doesn't pass serial and revision tags
to Linux kernel, hence kernel fails to identify
The vectoring table has to be placed at 0x0, but U-Boot on MX23/MX28
starts from RAM, so the vectoring table at 0x0 is not present. Craft
code that will be placed at 0x0 and will redirect interrupt vectoring
to proper location of the U-Boot in RAM.
Signed-off-by: Marek Vasut ma...@denx.de
CC:
On Thu, Apr 25, 2013 at 11:37 PM, Marek Vasut ma...@denx.de wrote:
The vectoring table has to be placed at 0x0, but U-Boot on MX23/MX28
starts from RAM, so the vectoring table at 0x0 is not present. Craft
code that will be placed at 0x0 and will redirect interrupt vectoring
to proper location
On 14 April 2013 22:48, Heiko Schocher h...@denx.de wrote:
Hello Naveen Krishna,
On 13.04.2013 06:42, Naveen Krishna Ch wrote:
On 6 April 2013 07:07, Naveen Krishna Chatradhi
naveenkrishna...@gmail.com wrote:
Add support for hsi2c controller available on exynos5420.
Note: driver
Dear Otavio Salvador,
[...]
+/*
+ * This function will craft a jumptable at 0x0 which will redirect
interrupt + * vectoring to proper location of U-Boot in RAM.
+ *
+ * The structure of the jumptable will be as follows:
+ * ldr pc, [pc, #0x18] . for each vector, thus repeated 8
On Fri, Apr 26, 2013 at 12:10 AM, Marek Vasut ma...@denx.de wrote:
Dear Otavio Salvador,
[...]
+/*
+ * This function will craft a jumptable at 0x0 which will redirect
interrupt + * vectoring to proper location of U-Boot in RAM.
+ *
+ * The structure of the jumptable will be as
Hi Andreas,
On Fri, Apr 19, 2013 at 1:48 AM, Andreas Bießmann
andreas.de...@googlemail.com wrote:
This series started with intention to make a hung board visualize the
(end-)user that it does hang(). The first approach was to make all the
different hang() functions weak and provide board
Dear Wolfgang-san
Thanks so much for your kind explanation.
Harry
In message XNM2$7$1$4$$7$7$5$A$1011959u51788...@hitachi.com you wrote:
Do you mean the U-Boot contains cryptographic algorithms
that makes 5D002?
I have to admit that I'm not 100% sure about that. U-Boot includes
the
Dear tiger...@viatech.com.cn,
Please do not top post / full quote!!
In message fe7aded5c2218b4786c09cd97dc4c49f87c...@exchbj02.viatech.com.bj you
wrote:
Because U-boot is more powerful than before.
So, I want to develop a simple video monitor system based on u-boot
code.
So, I care about
Hi,
About debug,
Where should I define the macro to enable debug() function definition?
Is there a place in makefile or head file?
On 2013/4/26 3:36, Wolfgang Denk wrote:
Dear du zhenhuan,
In message 202dafde.df1f.13e4197224a.coremail.dev...@163.com you wrote:
1, if NAND flash support is
On 24/04/2013 20:52, Marek Vasut wrote:
But you forget that a single image can be saved on multiple storage:
u-boot.imx can be stored on SD or NOR or SPI-NOR, and that is the reason
for having SOC-specific extension.
I agree with Benoit: at the moment, only people working with i.MX know
that
On 23/04/2013 22:17, Benoît Thébaudeau wrote:
IIM:
- Homogenize prg_p naming (the reference manuals are not always
self-consistent
for that).
- Add missing SCSx and bank registers.
- Fix the number of banks on i.MX53.
OCOTP:
- Rename iim to ocotp in order to avoid confusion.
-
On 24/04/2013 12:59, Benoît Thébaudeau wrote:
Apart of that and not related to this patch, if we in future use SPL
also for booting from SD, we can get a single way to boot from different
storage. TI based SOCs already do this: same SPL, it checks from SD and
NAND.
With this also comes the
This code is small snippet from patch
ftp://ftp.linux4sam.org/pub/uboot/u-boot-v2010.06/u-boot-5series_1.0.patch
Bug:-
For board at91sam9x5ek, U-boot doesn't pass serial and revision tags
to Linux kernel, hence kernel fails to identify correct revision and assumes
as rev-A, resulting in failing
TWR-P1025 Specification:
---
Memory subsystem:
512MB DDR3 (on board DDR)
64Mbyte 16bit NOR flash
One microSD Card slot
Ethernet:
eTSEC1: Connected to Atheros AR8035 GETH PHY
eTSEC3: Connected to Atheros AR8035 GETH PHY
UART:
Two UARTs are routed to the FDTI
Hi Stefano,
On 25.04.2013 09:31, Stefano Babic wrote:
On 24/04/2013 12:59, Benoît Thébaudeau wrote:
Apart of that and not related to this patch, if we in future use SPL
also for booting from SD, we can get a single way to boot from different
storage. TI based SOCs already do this: same SPL,
Hi, experts:
MIPI(Mobile Industry Processor Interface) has defined many mobile device
interface.
Such as:
CSI --- for Camera
DSI --- for Display
It seems DSI has samples on Exynos board.(in drivers\video directory)
I want to know the status about CSI support in u-boot.
Is there any samples in
Hi, experts:
I found some macro definitions, such as:
#define CONFIG_ARM_ERRATA_743622
#define CONFIG_ARM_ERRATA_751472
So, my question is:
Where do i get these errata descriptions?
Are there related to specific ARM SOC Vendors? Or just ARM Core's common
errata?
Best wishes,
Hi, experts:
I found some macro definitions, such as:
#define CONFIG_ARM_ERRATA_743622
#define CONFIG_ARM_ERRATA_751472
So, my question is:
Where do i get these errata descriptions?
Are there related to specific ARM SOC Vendors? Or just ARM Core's common
errata?
Best wishes,
On Wed, Apr 24, 2013 at 06:20:13PM +0530, Vivek Gautam wrote:
We can use a common global method for calculating minimum of
3 numbers. Put the same in 'common header' and let 'ehci'
use it.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Tom Rini tr...@ti.com
--
Tom
On 25/04/2013 10:38, Stefan Roese wrote:
Hi Stefano,
On 25.04.2013 09:31, Stefano Babic wrote:
On 24/04/2013 12:59, Benoît Thébaudeau wrote:
Apart of that and not related to this patch, if we in future use SPL
also for booting from SD, we can get a single way to boot from different
Dear Stefan Roese,
Hi Stefano,
On 25.04.2013 09:31, Stefano Babic wrote:
On 24/04/2013 12:59, Benoît Thébaudeau wrote:
Apart of that and not related to this patch, if we in future use SPL
also for booting from SD, we can get a single way to boot from
different storage. TI based SOCs
On 25.04.2013 14:38, Marek Vasut wrote:
Right, this is also correct. Anyway, BOOT_FROM is used to get the offset
inside the storage, and only to be as much flexible as possible, each
storage has defined its own offset. However, Freescale uses the same
offset (0x400) for most storages (NAND,
Hi Stefan,
On Thursday, April 25, 2013 2:48:59 PM, Stefan Roese wrote:
Subject: Re: [U-Boot] [PATCH V2 6/6] arm: mx5: Add support for DENX M53EVK
On 25.04.2013 14:38, Marek Vasut wrote:
Right, this is also correct. Anyway, BOOT_FROM is used to get the offset
inside the storage, and only
84 matches
Mail list logo
