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 k
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 confusi
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
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 t
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 d
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:
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 u-bo
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
Acked-by: Tom Rini
--
Tom
signature.asc
Description: Digital si
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 dif
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.
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 storage
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,
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 use
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_FRO
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
Cc: Heiko Schocher
Cc: Stefan Roese
---
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
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 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 code, and the AES crypto library.
My understanding
Dear tiger...@viatech.com.cn,
In message 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 Exynos board.(in drivers\video directory)
> I want to
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 momen
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 f
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
> Cc: Heiko Schocher
> Cc: Stefan Roese
> ---
> drivers/i2c/Makefi
Hi Simon,
On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass wrote:
> Hi,
>
> On Tue, Apr 23, 2013 at 3:11 PM, Jagan Teki wrote:
>> Hi Simon,
>>
>> On Wed, Apr 24, 2013 at 3:25 AM, Jagan Teki wrote:
>>> Hi Simon,
>>>
>>> On Wed, Apr 24, 2013 at 3:10 AM, Simon Glass wrote:
Hi Jagan,
On
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
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.im
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 NA
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
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
Signed-off-by: Tom Rini
---
arch/arm/config.mk |3 +++
arch/arm/cpu/ixp/config.mk |4 ---
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 arch/powerpc/c
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 flash
Hi Jagan,
On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki wrote:
> Hi Simon,
>
> On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass wrote:
>> Hi,
>>
>> On Tue, Apr 23, 2013 at 3:11 PM, Jagan Teki wrote:
>>> Hi Simon,
>>>
>>> On Wed, Apr 24, 2013 at 3:25 AM, Jagan Teki
>>> wrote:
Hi Simon,
>>>
On Mon, Apr 01, 2013 at 05:06:16PM +0300, Lubomir Popov wrote:
> Signed-off-by: Lubomir Popov
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 under licen
Hi Simon,
On Fri, Apr 26, 2013 at 12:22 AM, Simon Glass wrote:
> Hi Jagan,
>
> On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki wrote:
>> Hi Simon,
>>
>> On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass wrote:
>>> Hi,
>>>
>>> On Tue, Apr 23, 2013 at 3:11 PM, Jagan Teki
>>> wrote:
Hi Simon,
>
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
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
> ---
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
> ---
Applied to u-boot-imx, thanks.
Best regar
On 17/04/2013 20:33, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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 in
> arch/arm/mach-im
On 18/04/2013 01:09, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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.
>
> Also, according
Hi Tom,
On Tue, Apr 23, 2013 at 7:50 AM, Tom Rini 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 wrote:
>>
>> > On Mon, Apr 1, 2013 at 5:13 PM, Kim Phillips
>> > wrote:
>> > > On Mon, 18 Mar 2013 16:51:20 -0700
>> > >
Dear Franck Jullien,
In message
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:
> relocation truncated to fit: R_PPC_REL24 against symbol `_s
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
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
> ---
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
> ---
Applied to u-boot-imx, -next branch, thanks.
Best regards,
Stefano Babic
--
=
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev
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
> ---
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
> ---
> Changes in v3:
> - New patch
>
> Changes in v2: None
>
> include/configs/wandboard.h | 16
> 1 file changed,
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
> ---
Discharge wrong applied message - patches are applied to u-boot-
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
> ---
Applied to u-boot-imx, thanks.
Best r
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
> ---
Applied to u-boot-imx, thanks.
Best rega
On 19/04/2013 23:04, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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 at 0x9200
> - im
On 19/04/2013 23:04, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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'.
>
> Signed-off-by: Fabio Estevam
> -
On 25/04/2013 02:44, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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
> ---
Applied to u-boot-imx, t
On 25/04/2013 02:44, Fabio Estevam wrote:
> From: Fabio Estevam
>
> 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
> ---
Applied to u-boot-imx, thanks.
On 25/04/2013 02:44, Fabio Estevam wrote:
> From: Fabio Estevam
>
> imx-regs.h is more appropriate location for containing register masks.
>
> Signed-off-by: Fabio Estevam
> ---
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:
>
> clrbits_le32
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 t
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
Cc: Albert ARIBAUD
Cc: Benoît Thébaudeau
Cc: Fabio Estevam
Cc: Scott Wood
Cc: Stefano Babic
Cc: Tom Rini
Cc: Wolfgang Denk
On 10/04/2013 21:32, feste...@gmail.com wrote:
> From: Fabio Estevam
>
> 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
> ---
Hi Fabio,
> Changes since v2:
> - None
> Changes since v1:
> -
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 US
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
> >
> > Instead of having the same PAD control definition in each MX6 variant pin
> > file,
> > place it into a common location.
> >
> > Signed-off-
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
---
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
b/arch/arm/cpu/a
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 va
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
> mx23_olinuxino i.MX23
> m28evk i.MX28
> sc_sps_1i.MX28
> + m53evk i.MX53
Pleas
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
> > >
> > > Instead of having the same PAD control definition in each MX6
Hi Benoît,
On Thu, Apr 25, 2013 at 6:51 PM, Benoît Thébaudeau
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. There is no such thing in
Hi Vadim,
On Thu, Apr 18, 2013 at 8:50 AM, Vadim Bendebury (вб)
wrote:
> On Wed, Apr 17, 2013 at 7:13 PM, Simon Glass 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 U-Boot.
>>
>> A new more accu
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
抄送: u-b
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 ke
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
> >
> > mx23_olinuxino i.MX23
> > m28evk i.MX28
> > sc_sps_1i.MX2
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 generat
Hi,
On Thu, Apr 25, 2013 at 12:06 PM, Jagan Teki wrote:
> Hi Simon,
>
> On Fri, Apr 26, 2013 at 12:22 AM, Simon Glass wrote:
>> Hi Jagan,
>>
>> On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki wrote:
>>> Hi Simon,
>>>
>>> On Wed, Apr 24, 2013 at 6:03 AM, Simon Glass wrote:
Hi,
On Tue
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 co
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
CC: Stefano Babic
CC
On Thu, Apr 25, 2013 at 11:37 PM, Marek Vasut 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 of the U-B
On 14 April 2013 22:48, Heiko Schocher wrote:
> Hello Naveen Krishna,
>
>
> On 13.04.2013 06:42, Naveen Krishna Ch wrote:
>>
>> On 6 April 2013 07:07, Naveen Krishna Chatradhi
>> wrote:
>>>
>>> Add support for hsi2c controller available on exynos5420.
>>>
>>> Note: driver currently supports only
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
On Fri, Apr 26, 2013 at 12:10 AM, Marek Vasut 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 f
Hi Andreas,
On Fri, Apr 19, 2013 at 1:48 AM, Andreas Bießmann
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 specific versions to
> implemen
Dear Wolfgang-san
Thanks so much for your kind explanation.
Harry
>In message 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 code, an
Dear tiger...@viatech.com.cn,
Please do not top post / full quote!!
In message 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 current CSI support in u-boot code.
This makes no sense.
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
From: Dirk Eibach
Signed-off-by: Dirk Eibach
Signed-off-by: Dirk Eibach
---
Changes in v2: None
arch/powerpc/lib/Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/lib/Makefile b/arch/powerpc/lib/Makefile
index 59c723b..8c4920b 100644
--- a/arch/po
From: Reinhard Pfau
if alen is 0: no longer start a write cycle before reading data.
Signed-off-by: Dirk Eibach
Signed-off-by: Reinhard Pfau
Signed-off-by: Dirk Eibach
---
Changes in v2:
- whitespace fixes
drivers/i2c/fsl_i2c.c |9 ++---
1 files changed, 6 insertions(+), 3 deletio
Signed-off-by: Dirk Eibach
---
Changes in v2: None
MAINTAINERS |2 +-
arch/powerpc/cpu/ppc4xx/cmd_chip_config.c |2 +-
arch/powerpc/include/asm/ppc4xx_config.h |2 +-
board/gdsys/405ep/405ep.c |2 +-
board/gdsys/405ep/dlvision-10g.c
From: Dirk Eibach
Add support for Atmel TPM devices with two wire interface.
Signed-off-by: Dirk Eibach
Signed-off-by: Reinhard Pfau
Signed-off-by: Dirk Eibach
---
Changes in v2: None
README |6 ++
drivers/tpm/Makefile|1 +
drivers/tpm/atmel_twi_tpm.c |
From: Reinhard Pfau
Extend the tpm library with support for single authorized (AUTH1) commands
as specified in the TCG Main Specification 1.2. (The internally used helper
functions are implemented in a way that they could also be used for double
authorized commands if someone needs it.)
Provide
Hi Simon,
On Fri, Apr 26, 2013 at 7:13 AM, Simon Glass wrote:
> Hi,
>
> On Thu, Apr 25, 2013 at 12:06 PM, Jagan Teki wrote:
>> Hi Simon,
>>
>> On Fri, Apr 26, 2013 at 12:22 AM, Simon Glass wrote:
>>> Hi Jagan,
>>>
>>> On Thu, Apr 25, 2013 at 6:55 AM, Jagan Teki
>>> wrote:
Hi Simon,
From: Dirk Eibach
If CONFIG_RELEASE_CORE0_ONLY is set, all cores except core0 are kept in
holdoff mode.
Signed-off-by: Dirk Eibach
Signed-off-by: Dirk Eibach
---
Changes in v2: None
arch/powerpc/cpu/mpc85xx/mp.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/
Changes in v2:
- replace some numeric constants with named constants
- style fixes (as shown by checkpatch.pl) in common/cmd_tpm.c and lib/tpm.c
- whitespace fixes
- configuration for SPI builds was missing
- whitespace fixes
Dirk Eibach (5):
Update gdsys email account
mpc85xx: Add CONFIG_RE
From: Reinhard Pfau
Extend the tpm library with support for single authorized (AUTH1) commands
as specified in the TCG Main Specification 1.2. (The internally used helper
functions are implemented in a way that they could also be used for double
authorized commands if someone needs it.)
Provide
From: Reinhard Pfau
if alen is 0: no longer start a write cycle before reading data.
Signed-off-by: Dirk Eibach
Signed-off-by: Reinhard Pfau
---
Changes in v3: None
Changes in v2:
- whitespace fixes
drivers/i2c/fsl_i2c.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
d
From: Dirk Eibach
Add support for Atmel TPM devices with two wire interface.
Signed-off-by: Dirk Eibach
Signed-off-by: Reinhard Pfau
---
Changes in v3: None
Changes in v2: None
README |6 ++
drivers/tpm/Makefile|1 +
drivers/tpm/atmel_twi_tpm.c | 119 +++
Signed-off-by: Dirk Eibach
---
Changes in v3:
- fix email addresses
Changes in v2: None
MAINTAINERS |2 +-
arch/powerpc/cpu/ppc4xx/cmd_chip_config.c |2 +-
arch/powerpc/include/asm/ppc4xx_config.h |2 +-
board/gdsys/405ep/405ep.c |
Changes in v3:
- fix email addresses
Changes in v2:
- replace some numeric constants with named constants
- style fixes (as shown by checkpatch.pl) in common/cmd_tpm.c and lib/tpm.c
- configuration for SPI builds was missing
- whitespace fixes
Dirk Eibach (5):
Update gdsys email account
mpc
From: Dirk Eibach
Signed-off-by: Dirk Eibach
---
Changes in v3: None
Changes in v2: None
arch/powerpc/lib/Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/lib/Makefile b/arch/powerpc/lib/Makefile
index 59c723b..8c4920b 100644
--- a/arch/powerpc/li
From: Dirk Eibach
If CONFIG_RELEASE_CORE0_ONLY is set, all cores except core0 are kept in
holdoff mode.
Signed-off-by: Dirk Eibach
---
Changes in v3: None
Changes in v2: None
arch/powerpc/cpu/mpc85xx/mp.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/pow
On 25/04/2013 22:32, Benoît Thébaudeau wrote:
>> Checking in the manual, I see that values in iomux-mx51.h are correct,
>> and they simply differs from the ones of MX6. We can simply add a #ifdef
>> CONFIG_MX51 in arch/arm/include/asm/imx-common/iomux-v3.h to fix it, but
>> anyway I suppose that t
1 - 100 of 101 matches
Mail list logo
