public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] add new board nas62x0
Date: Wed, 21 Mar 2012 11:02:56 +0100	[thread overview]
Message-ID: <201203211102.56474.marex@denx.de> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2F6761A7@SC-VEXCH4.marvell.com>

Dear Prafulla Wadaskar,

> > -----Original Message-----
> > From: Marek Vasut [mailto:marex at denx.de]
> > Sent: 21 March 2012 12:52
> > To: Luka Perkov
> > Cc: u-boot at lists.denx.de; dreagle at doukki.net; Wolfgang Denk; Prafulla
> > Wadaskar
> > Subject: Re: [U-Boot] [PATCH v2] add new board nas62x0
> > 
> > Dear Luka Perkov,
> > 
> > > Hi Marek,
> 
> ...snip...
> 
> > > > > This is my proposal - I'll resend v4 and it should be ok to
> > 
> > commit
> > 
> > > > > without fixes for:
> > > > >  1) IB62x0_OE_LOW and IB62x0_OE_HIGH
> > > > >  2) CONFIG_SKIP_LOWLEVEL_INIT
> > > > >  3) ifdef indentation
> > > > > 
> > > > > Because fixing the 1) and 2) is more than adding support for
> > 
> > this new
> > 
> > > > > board, and if it was in the same patch I would need to separate
> > 
> > it.
> > 
> > > > > That is a different issue.
> > > > 
> > > > You can wait for Prafulla with #1 and #2, also for #2 check my
> > 
> > comment.
> > 
> > > > But we have two bugs going on for granted here at least and
> > 
> > they're not
> > 
> > > > your boards fault. On the other hand, it'd be cool if you could
> > 
> > fix them
> > 
> > > > prior to adding your board ;-)
> 
> Hi Luka
> 
> #1: Defining these values as 0xffffffff, indicates that all GPIOs are
> configured high by default. so this configuration solely depends upon your
> board requirement.
> 
> #2: on kirkwood, you should define CONFIG_SKIP_LOWLEVEL_INIT since
> lowlevel_init is not needed on Kirkwood platforms. (ref:
> doc/README.kwbimage)

Prafulla, you're then missing the fiddling with CPSR bits, which might be quite 
necessary.

> 
> Regards..
> Prafulla . . .

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-21 10:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17 23:40 [U-Boot] [PATCH v2] add new board nas62x0 Luka Perkov
2012-03-17 23:43 ` Luka Perkov
2012-03-18 10:04 ` Wolfgang Denk
2012-03-18 15:15 ` Marek Vasut
2012-03-18 18:31   ` Luka Perkov
2012-03-19 15:50     ` Marek Vasut
2012-03-19 22:42       ` Luka Perkov
2012-03-20  6:48         ` Marek Vasut
2012-03-21  0:34           ` Luka Perkov
2012-03-21  7:21             ` Marek Vasut
2012-03-21  9:51               ` Prafulla Wadaskar
2012-03-21 10:02                 ` Marek Vasut [this message]
2012-03-21 10:15                   ` Prafulla Wadaskar
2012-03-21 10:56                     ` Marek Vasut
2012-03-21 12:01                       ` Prafulla Wadaskar
2012-03-20  7:04       ` DrEagle
2012-03-20  8:21         ` Marek Vasut

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=201203211102.56474.marex@denx.de \
    --to=marex@denx.de \
    --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