public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Erfurth <ne@erfurth.eu>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-arm-kernel@lists.infradead.org, Eric Cooper <ecc@cmu.edu>,
	linux-kernel@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars
Date: Thu, 07 Apr 2011 00:50:12 +0200	[thread overview]
Message-ID: <4D9CEE24.1080501@erfurth.eu> (raw)
In-Reply-To: <1302122121-3652-1-git-send-email-holler@ahsoftware.de>

Alexander Holler wrote:

> The first patch merges the setup for Seagate DockStars into the setup
> for Marvell SheevaPlugs and the second one removes the machine type for
> DockStars at all.

That looks fine so far.

> Removing the machine type for DockStar shouldn't be a big problem. Support
> for them is already broken in mainline U-Boot since 2 versions, so changing the
> stuff there is already needed and it shouldn't be a problem to use the same
> machine type as used for SheevaPlugs there.

This sounds like very bad reasoning to me. The Dockstar has a machine-id
assigned, if the bootloader is broken, people should either use a
working version, or fix the current one.

Also, using the memory-size to differ between these two machines sounds
like something thats doomed to fail in the future.

Nico

  parent reply	other threads:[~2011-04-06 23:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 20:35 [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars Alexander Holler
2011-04-06 20:35 ` [PATCH 1/2] ARM: Differentiate SheevaPlugs and DockStars on the basis of the memory size Alexander Holler
2011-04-06 21:44   ` Nicolas Pitre
2011-04-06 22:45     ` Alexander Holler
2011-04-06 23:01       ` Nicolas Pitre
2011-04-06 23:22         ` Alexander Holler
2011-04-07  2:55           ` Nicolas Pitre
2011-04-07  8:55           ` Alexander Clouter
2011-04-07 21:31             ` Alexander Holler
2011-04-07 21:44               ` Alexander Clouter
2011-04-07 21:59                 ` Alexander Holler
2011-04-07 22:08               ` Russell King - ARM Linux
2011-04-07 23:04                 ` Alexander Holler
2011-04-08  7:24                   ` Russell King - ARM Linux
2011-04-08  8:38                     ` Alexander Holler
2011-04-09  8:29                   ` Bernd Petrovitsch
2011-04-10 18:14                     ` Alexander Holler
2011-04-10 19:29                       ` Alexander Holler
2011-04-06 23:23         ` Eric Cooper
2011-04-06 20:35 ` [PATCH 2/2] ARM: Remove machine type dockstar (use sheevaplug instead) Alexander Holler
2011-04-06 21:02   ` Nicolas Pitre
2011-04-06 21:43     ` Alexander Holler
2011-04-06 22:50 ` Nico Erfurth [this message]
2011-04-07  9:20   ` [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars Alexander Holler
2011-04-07  9:37     ` Nico Erfurth
2011-04-07  9:44       ` Alexander Holler
2011-04-07 17:39         ` Russell King - ARM Linux
2011-04-08  3:38           ` Alexander Holler

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=4D9CEE24.1080501@erfurth.eu \
    --to=ne@erfurth.eu \
    --cc=ecc@cmu.edu \
    --cc=holler@ahsoftware.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@fluxnic.net \
    /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