public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3][repost] nand: Add Marvell Kirkwood NAND driver
Date: Tue, 23 Jun 2009 09:02:52 +0200	[thread overview]
Message-ID: <20090623070252.GA23512@game.jcrosoft.org> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E62E34@SC-VEXCH1.marvell.com>

On 23:08 Mon 22 Jun     , Prafulla Wadaskar wrote:
>  
> 
> > -----Original Message-----
> > From: Scott Wood [mailto:scottwood at freescale.com] 
> > Sent: Tuesday, June 23, 2009 3:35 AM
> > To: Prafulla Wadaskar
> > Cc: u-boot at lists.denx.de; Ashish Karkare; Prabhanjan Sarnaik; 
> > Ronen Shitrit
> > Subject: Re: [U-Boot] [PATCH v2 1/3][repost] nand: Add 
> > Marvell Kirkwood NAND driver
> > 
> > On Sun, Jun 14, 2009 at 10:32:47PM +0530, Prafulla Wadaskar wrote:
> > > diff --git a/drivers/mtd/nand/kirkwood_nand.c 
> > > b/drivers/mtd/nand/kirkwood_nand.c
> > > new file mode 100644
> > > index 0000000..9cdbe20
> > > --- /dev/null
> > > +++ b/drivers/mtd/nand/kirkwood_nand.c
> > > @@ -0,0 +1,81 @@
> > > +/*
> > > + * Copyright (C) Marvell International Ltd. and its affiliates
> > 
> > No year?
> I will correct this.
> 
> > 
> > > +#include <common.h>
> > > +#include <asm/io.h>
> > > +#include <asm/arch/kirkwood.h>
> > > +#include <nand.h>
> > 
> > I don't see kirkwood.h in upstream, so I guess this should go 
> > via an arch tree.
> 
> Kirkwood support is available in arm/next, I hope it will be pulled soon :-)
> Any way this is dependency for this driver but is this blocker?
> 
> I have two options-
> 1. remove dependency from this patch or
> 2. get Basic Kirkwood support up streamed
> There are some other drivers in pipeline i.e. i2c,spi,usb that needs Basic Kirkwood support. So I wish to go for second option
> Hi Jean,
> Can you pls help to resolve this dependency?
Wolfgang is in vacancy so we will have to wait until he will came back
the will be present in the arm tree until and then I will send him a pull
request

Best Regards,
J.

  reply	other threads:[~2009-06-23  7:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 17:02 [U-Boot] [PATCH v2 1/3][repost] nand: Add Marvell Kirkwood NAND driver Prafulla Wadaskar
2009-06-22 22:05 ` Scott Wood
2009-06-23  6:08   ` Prafulla Wadaskar
2009-06-23  7:02     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-06-23  7:52     ` Dieter Kiermaier
2009-06-23  8:01       ` Prafulla Wadaskar
2009-06-23  8:24         ` Dieter Kiermaier
2009-06-23  8:35           ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-23  8:47             ` Dieter Kiermaier
2009-06-23 10:38               ` Prafulla Wadaskar
2009-06-23 11:23                 ` Dieter Kiermaier
2009-06-23 12:06                   ` Stefan Roese
2009-06-23 12:06                   ` Prafulla Wadaskar
2009-06-23 12:14                     ` Dieter Kiermaier
2009-06-26  7:32   ` Prafulla Wadaskar
2009-06-27 15:22     ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-07 10:31       ` Prafulla Wadaskar
2009-07-07 20:26         ` Jean-Christophe PLAGNIOL-VILLARD
  -- strict thread matches above, loose matches on Subject: below --
2009-06-08 12:04 Prafulla Wadaskar
2009-06-13 14:01 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-19  9:27   ` Prafulla Wadaskar
2009-06-19 14:52     ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090623070252.GA23512@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox