On Sun, Jan 3, 2010 at 3:10 AM, Wolfgang Denk wrote:
> Dear Grant Likely,
>
> In message you
> wrote:
>
> Note that the FIT image can also be made to contain a number of DT
> blobs, and selection of a "board profile" then can be used to boot the
> very sane FIT image file on any of the supported
Hi Prakash,
On Thursday 31 December 2009 05:39:35 prakash bedge wrote:
> I am modifying the start.S code and I believe this is the basic
> initialization code need to bring up the board at start.
>
> If I flash my sample initialization code in flash and do hard reset then
> board is working, but
Hi,
On Fri, Dec 25, 2009 at 22:41:13, Dirk Behme wrote:
> On 23.12.2009 08:44, Sudhakar Rajashekhara wrote:
> > From: Sekhar Nori
> >
> > This adds a driver for the SPI controller found on davinci
> > based SoCs from Texas Instruments.
> >
> > Signed-off-by: Sekhar Nori
> > Signed-off-by: Sudhakar
On 23/12/09 07:44, Sudhakar Rajashekhara wrote:
> From: Sekhar Nori
>
> This adds a driver for the SPI controller found on davinci
> based SoCs from Texas Instruments.
>
> Signed-off-by: Sekhar Nori
> Signed-off-by: Sudhakar Rajashekhara
> ---
> drivers/spi/Makefile |1 +
> drivers/s
Hi,
On Fri, Dec 25, 2009 at 22:41:13, Dirk Behme wrote:
> On 23.12.2009 08:44, Sudhakar Rajashekhara wrote:
> > From: Sekhar Nori
> >
> > This adds a driver for the SPI controller found on davinci
> > based SoCs from Texas Instruments.
> >
> > Signed-off-by: Sekhar Nori
> > Signed-off-by: Sudhakar
Hi Prakash,
On Thursday 31 December 2009 11:04:50 prakash bedge wrote:
> Why the below code start with the TLB1?
>
> My U-boot image is supposed to boot from flash, so here #else condition is
> valid in my case. I believe it should start from the TLB 0 entry. But I
> think TLB0 is not selected.
>
Hi Nick,
On Mon, Jan 04, 2010 at 15:17:51, Nick Thompson wrote:
> On 23/12/09 07:44, Sudhakar Rajashekhara wrote:
> > From: Sekhar Nori
> >
> > This adds a driver for the SPI controller found on davinci
> > based SoCs from Texas Instruments.
> >
> > Signed-off-by: Sekhar Nori
> > Signed-off-by
> I don't know of an ehci-ppc4xx.c file. Did you create it yourself?
I created the file by myself. But it's nothing more than setting up register
base addresses similar with ehci-ixp4xx.c ...
I checked out from current source a few days ago. Maybe it's not very straight
forward to get ppc4xx
On Monday 04 January 2010 11:46:00 Chris Zhang wrote:
> > I don't know of an ehci-ppc4xx.c file. Did you create it yourself?
>
> I created the file by myself. But it's nothing more than setting up
> register base addresses similar with ehci-ixp4xx.c ...
I see.
> I checked out from current sourc
Hi,
On Mon, Dec 21, 2009 at 15:48:38, Nick Thompson wrote:
> On 18/12/09 10:23, Sudhakar Rajashekhar wrote:
> > Nick Thompson ge.com> writes:
> >
> >>
> >> On 16/12/09 10:24, Sudhakar Rajashekhara wrote:
> >>> Provides initial support for TI OMAP-L138/DA850 SoC devices on
> >>> a Logic PD EVM bo
Hello,
I am working with the Gumxtix Overo OMAP3 based systems.
The Overo expansion boards use an SMSC LAN9221 ethernet
controller. The NET_GPMC_CONFIG timing registers in
include/asm-arm/arch-omap3/mem.h shared by the overo, ti/evm and
tim11/devkit8000 are not optimal for the LAN9221. It looks
On Tue, Dec 15, 2009 at 10:51:14PM +0100, Wolfgang Denk wrote:
> Dear Scott Wood,
>
> In message <4b27faf1.1070...@freescale.com> you wrote:
> >
> > Yes, as part of the set of patches in the custodian tree. Why introduce
> > conflicts by targetting an older tree? What if the new patch depends o
On Dec 17, 2009, at 3:20 PM, Wolfgang Denk wrote:
> Dear Kumar Gala,
>
> In message <1260980679-13236-3-git-send-email-ga...@kernel.crashing.org> you
> wrote:
>> From: Dave Liu
>>
>> It may be different settings of Rtt_nom and Rtt_WR
>> for different boards, adding the override provide the
>>
On Mon, Dec 21, 2009 at 09:37:02PM +0100, Wolfgang Denk wrote:
> > --- u-boot/fs/jffs2/jffs2_1pass.c 2009-12-15 14:20:33.0 -0600
> > +++ uboot/fs/jffs2/jffs2_1pass.c 2009-12-15 14:19:27.0 -0600
> > @@ -158,12 +158,12 @@
> > *
> > */
> >
> > -#define NAND_PAGE_SIZE 512
> > +#def
On 04.01.2010 11:42, Sudhakar Rajashekhara wrote:
> Hi Nick,
>
> On Mon, Jan 04, 2010 at 15:17:51, Nick Thompson wrote:
>> On 23/12/09 07:44, Sudhakar Rajashekhara wrote:
>>> From: Sekhar Nori
>>>
>>> This adds a driver for the SPI controller found on davinci
>>> based SoCs from Texas Instruments.
Hi
I received no further comments on these patches after posting
v2 (the NAND part is ACK-ed by Scott Wood). Could someone
pull these? I applied them to the current u-boot tip without
any problems.
Regads, Magnus
Magnus Lilja skrev:
> Hi all,
>
> This series adds NAND support for i.MX31 using
On Mon, 4 Jan 2010, Magnus Lilja wrote:
> Hi
>
> Magnus Lilja skrev:
> > 2009/12/3 Guennadi Liakhovetski :
> >> On Wed, 2 Dec 2009, Wolfgang Denk wrote:
> >>
> >>> Dear Guennadi,
> >>>
> >>> In message <1257965907-5622-1-git-send-email-lilja.mag...@gmail.com>
> >>> Magnus Lilja wrote:
> dif
Hi
Magnus Lilja skrev:
> 2009/12/3 Guennadi Liakhovetski :
>> On Wed, 2 Dec 2009, Wolfgang Denk wrote:
>>
>>> Dear Guennadi,
>>>
>>> In message <1257965907-5622-1-git-send-email-lilja.mag...@gmail.com> Magnus
>>> Lilja wrote:
diff --git a/drivers/spi/mxc_spi.c b/drivers/spi/mxc_spi.c
in
On Wed, Dec 30, 2009 at 04:38:44PM -0600, ay...@austin.rr.com wrote:
> I've got a custom board that was based on the walnut. I have a 2+ year old
> version of u-boot working on it, but we are trying to go to the newer version
> to match our newer hardware. The hardware is a 405gpr to spansion s29
On Wed, Dec 16, 2009 at 02:48:24PM +0530, Vipin KUMAR wrote:
>
> Signed-off-by: Vipin
Acked-by: Scott Wood
Some of the whitespace is a bit inconsistent, though:
> +int spear_nand_init(struct nand_chip *nand)
> +{
> + writel(FSMC_DEVWID_8 | FSMC_DEVTYPE_NAND | FSMC_ENABLE | FSMC_WAITON,
>
On Monday 04 January 2010 14:50:54 Dirk Behme wrote:
> struct mcspi {
> unsigned char res1[0x10];
> unsigned int sysconfig; /* 0x10 */
> unsigned int sysstatus; /* 0x14 */
> unsigned int irqstatus; /* 0x18 */
> unsigned int irqenable; /*
On Friday 01 January 2010 11:29:41 Joakim Tjernlund wrote:
> Mike Frysinger wrote on 01/01/2010 07:18:44:
> > yes, but that doesnt mean gcc takes care of inlining all of printf_puts()
> > into the puts() and all the new call sites go to puts()
>
> Sure, gcc might not inline the current code in th
On Sunday 03 January 2010 14:51:53 Wolfgang Denk wrote:
> If I try to see trends in the development of U-Boot I notice a
> growing number of systems that boot from NAND flash, DataFlash or
> that come with on-chip ROM code to load images from SDCard and other
> storage media. Such systems cannot ma
Hello Scott,
>
> Acked-by: Scott Wood
>
> Some of the whitespace is a bit inconsistent, though:
>
> > +int spear_nand_init(struct nand_chip *nand)
> > +{
> > + writel(FSMC_DEVWID_8 | FSMC_DEVTYPE_NAND | FSMC_ENABLE |
> FSMC_WAITON,
> > + &fsmc_regs_p->genmemctrl_pc);
> > +
Hi guys,
I am trying to set the load_address same as os.start, which means the
os.load equals os.start, to avoid copying the image from the os.load to
os.start. The uncompressed kernel image Image is employed to generate
the uImage, through following command.
mkimage -A arm -O linux -T kernel -C no
From: Sekhar Nori
This adds a driver for the SPI controller found on davinci
based SoCs from Texas Instruments.
Signed-off-by: Sekhar Nori
Signed-off-by: Sudhakar Rajashekhara
---
>From the previous version following have been modified:
1. Sorted the entries in drivers/spi/Makefile alphabetic
On Monday 04 January 2010 04:46:19 Sudhakar Rajashekhara wrote:
> On Fri, Dec 25, 2009 at 22:41:13, Dirk Behme wrote:
> > I wonder if all (SPI API) functions from include/spi.h should be
> > implemented? I.e. do we need (dummy) functions for spi_cs_is_valid(),
> > spi_cs_activate() and spi_cs_deact
Hi,
I'm trying to compile the u-boot for arm-1026 architecture after adding the
support for a new board. I'm facing the issue in accessing the global data
"gd" (which is declared in "include/asm-arm/global_data.h" as
#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd __asm__
("r8")
).
pawan a écrit :
> Hi,
>
> I'm trying to compile the u-boot for arm-1026 architecture after adding the
> support for a new board. I'm facing the issue in accessing the global data
> "gd" (which is declared in "include/asm-arm/global_data.h" as
> #define DECLARE_GLOBAL_DATA_PTR register volatile
Hello,
I have observed that in the recent commit (file include/ns16550.h), the ns16550
UART register structure declaration is changed so that irrespective of the
CONFIG_SYS_NS16550_REG_SIZE setting the register access will be done at byte
level.
This crates problem when UART space access is r
Dear "Pedanekar, Hemant",
In message <2a3dcf3da181ad40bde86a3150b27b6b03094b2...@dbde02.ent.ti.com> you
wrote:
>
> I have observed that in the recent commit (file include/ns16550.h), the
> ns16550 UART register structure declaration is changed so that irrespective
> of the CONFIG_SYS_NS16550_R
31 matches
Mail list logo
