From: Alexander Clouter <alex@digriz.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: Differentiate SheevaPlugs and DockStars on the basis of the memory size.
Date: Thu, 7 Apr 2011 22:44:57 +0100 [thread overview]
Message-ID: <20110407214457.GH26616@chipmunk> (raw)
In-Reply-To: <4D9E2D1C.7070102@ahsoftware.de>
* Alexander Holler <holler@ahsoftware.de> [2011-04-07 23:31:08+0200]:
>
> Requiring a machine ID and the needed stuff to handle that for a
> board which just is using two GPIOs different than another board is
> why the ARM tree exploded. And requiring a machine ID just to follow
> the rule that a machine ID is much better than some pretty unique hw
> feature is in my humble opinion senseless and that the resulting code
> is more readable and better to maintain is a myth.
>
It's something that most people agree with you on too. However, I am
guessing it's around as no one else *at the time* of it's conception
could think of a better way.
Now this is why there is a lot of work being done on device-tree.
> Sorry that I wanted to help there. Will not try it again.
>
Yeah, as obviously no tries to help anyone improve around here:
http://groups.google.com/group/openrd/browse_frm/thread/7ba48f2d7916a88f/2b89c877c4f39098?tvc=1&fwc=1
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/022855.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/024072.html
http://git.kernel.org/?p=linux/kernel/git/nico/orion.git;a=commit;h=f2ac38dc
Regards
--
Alexander Clouter
.sigmonster says: Graduate life: It's not just a job. It's an indenture.
next prev parent reply other threads:[~2011-04-07 21:45 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 [this message]
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 ` [PATCH 0/2] ARM: Unify setup for Marvell SheevaPlugs and Seagate DockStars Nico Erfurth
2011-04-07 9:20 ` 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=20110407214457.GH26616@chipmunk \
--to=alex@digriz.org.uk \
--cc=holler@ahsoftware.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).