All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Kirkwood: Marvell GuruPlug support
Date: Tue, 23 Mar 2010 13:23:31 +0000	[thread overview]
Message-ID: <20100323132331.GT13429@chipmunk> (raw)
In-Reply-To: <1269348203.23313.198.camel@pe-dt434>

Hi,

* Siddarth Gore <gores@marvell.com> [2010-03-23 18:13:23+0530]:
>
> On Mon, 2010-03-22 at 05:05 -0700, Alexander Clouter wrote:
>
> > Any harm in merging this into the sheevaplug-setup code, like the openrd 
> > code?
> > 
> > http://git.marvell.com/?p=orion.git;a=commit;h=b2fdb5660fccc060e47658baad8911a963397ced
> 
> No harm as such. but i think having separate setup files will be a
> cleaner approach, instead of adding more if(machine_is_<>) statements.
> 
> Looks like openrd base/client are same boards with client having an
> extra ethernet port. sheevaplug and guruplug are two different boards
> (pcb's) having different gpio settings, peripherals, etc.
> 
Fair enough, I thought (with the exception of the shameful removal of 
the onboard questionable serial/jtag) the boards were identical, just 
with extra USB/NIC ports added.

Cheers

-- 
Alexander Clouter
.sigmonster says: Real Users know your home telephone number.

  reply	other threads:[~2010-03-23 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  9:28 [PATCH] Kirkwood: Marvell GuruPlug support Siddarth Gore
2010-03-22 12:05 ` Alexander Clouter
2010-03-23 12:43   ` Siddarth Gore
2010-03-23 13:23     ` Alexander Clouter [this message]
2010-03-23 16:48       ` Nicolas Pitre
2010-03-23 18:35         ` Alexander Clouter

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=20100323132331.GT13429@chipmunk \
    --to=alex@digriz.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.