public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Karl O. Pinc <kop@meme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Merging the pogo_e02 and sheevaplug code
Date: Thu, 02 Aug 2012 12:37:13 -0500	[thread overview]
Message-ID: <1343929033.23754.5@mofo> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A585306A6@SC-VEXCH4.marvell.com> (from prafulla@marvell.com on Thu Aug  2 12:10:28 2012)

On 08/02/2012 12:10:28 PM, Prafulla Wadaskar wrote:
> 
> 
> > -----Original Message-----
> > From: Karl O. Pinc [mailto:kop at meme.com]
> > Sent: 01 August 2012 21:13
> > To: u-boot at lists.denx.de; david.c.purdy at gmail.com; Prafulla 
> Wadaskar
> > Subject: Merging the pogo_e02 and sheevaplug code
> > 
> > Hi,
> > 
> > I'm looking at possibly merging the pogo_e02 and sheevaplug code
> > and have some general questions before doing anything.
> > 
> > The pogoplug POGO-E02 (pogo_e02 target) and the sheevaplug
> (sheevaplug
> > development kit) (sheevaplug target) board are very similar.
> > They are arm (Marvell) kirkwood boards.
> > The sheevaplug has 1G of ram the pogo_e02 has 256M.
> > Code-wise, the two boards have slightly different
> > kwbimage.cfg files.  There is something going on in the
> > kwmpp_config[] array, the current pogo_e02 code omits a lot
> > of elements of this array that are present in the sheevaplug
> > but are otherwise identical.  I can look into this myself
> > unless someone wants to hand me a clue.  Finally, there's
> > the board initialization: board_init(void).  The
> > sheevaplug has
> >   gd->bd->bi_arch_number = MACH_TYPE_SHEEVAPLUG;
> > wheras the pogo_e02 does something different
> >   gd->bd->bi_boot_params = kw_sdram_bar(0) + 0x100;
> 
> There are several other custom boards which are clone of sheevaplug
> and u-boot image works as it is for them.
> 
> Does sheevaplug u-boot image boots as it is on pogo-plug_e02?

I'm afraid to try it.  I don't have any jtag hardware.
(If you know of any that will work on Linux for a 10-pin
jtag (probably for OpenOCD -- something on Debian would
be helpful, that will support the cpu).

One reason I'm afraid is that the kwbimage.cfg file from
the factory is different from the stock sheevaplug
kwbimage.cfg.  (It also seems to be different from the
kwbimage.cfg in the current pogo_e02 target.)

FYI, the "example" patch I sent here:
http://lists.denx.de/pipermail/u-boot/2012-July/129182.html
includes the kwbimage.cfg file I've verified against
the factory pogo_e02 values -- except that my file
includes
  DATA 0xFFD01500 0x00000000	# CS[0]n Base address to 0x0
which was not in the original but is in the
sheevaplug's kwbimage.cfg file.  It seemed
a good idea to add this.

The main point of the "example patch"
was to use a different kwbimage.cfg file
while retaining the rest of the sheevaplug
code.

Thanks for the help.

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein

  reply	other threads:[~2012-08-02 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 15:42 [U-Boot] Merging the pogo_e02 and sheevaplug code Karl O. Pinc
2012-08-02 17:10 ` Prafulla Wadaskar
2012-08-02 17:37   ` Karl O. Pinc [this message]
2012-08-03  6:48     ` Prafulla Wadaskar
2012-08-03 15:40       ` Karl O. Pinc

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=1343929033.23754.5@mofo \
    --to=kop@meme.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