From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM Machine SoC I/O setup and PAD initialization code
Date: Fri, 23 Jul 2010 14:02:43 +0100 [thread overview]
Message-ID: <20100723130243.GB750@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201007231235.40625.david.jander@protonic.nl>
On Fri, Jul 23, 2010 at 12:35:40PM +0200, David Jander wrote:
> On Thursday 22 July 2010 03:54:31 pm Russell King - ARM Linux wrote:
> > > There are important hardware-design decisions after each of those
> > > settings! If we continue this amateuristic approach, ARM-linux
> > > platforms will never get taken seriously in more demanding
> > > environments. This really needs to change.
> >
> > "we continue this amateuristic approach" - you think we really have some
> > choice in this? We have very little influence on this point.
>
> You do. I work for a hardware manufacturer and we are listening!
Well, do _something_ about it then rather than endlessly discussing it.
Make sure that your boot loader is correct for all your platforms, and
then we can rely on it to be right for your platforms and omit the
setup on them.
But you won't be able to influence all hardware manufacturers.
> Also, Canonical might have some important weight here (Linaro).... and they
> may just as well listen also.
I doubt Linaro can change the way hardware manufacturers behave either.
ARM Ltd have been going around trying to teach silicon vendors about
feeding their changes back to the kernel, and it's taken them about a
decade for this stuff to happen.
How long do you think it'll take for board-level manufacturers to get
the big picture? I wouldn't be surprised if it takes at least another
decade.
As you seem to have a problem with the current setup, then please pick
up the campaign banner and start trying to teach the hardware vendors
about the Right Way(tm) to do things - which means addressing your
concerns _to_ the people who create them, not the people who end up
having to live with the resulting mess.
next prev parent reply other threads:[~2010-07-23 13:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 8:29 ARM Machine SoC I/O setup and PAD initialization code David Jander
2010-07-21 8:47 ` Russell King - ARM Linux
2010-07-22 2:32 ` Simon Horman
2010-07-22 7:20 ` Russell King - ARM Linux
2010-07-22 7:29 ` Simon Horman
2010-07-22 8:38 ` Magnus Damm
2010-07-22 8:49 ` Eric Miao
2010-07-22 9:01 ` Magnus Damm
2010-07-22 9:02 ` Russell King - ARM Linux
2010-07-22 8:46 ` Russell King - ARM Linux
2010-07-22 9:14 ` Simon Horman
2010-07-24 21:36 ` Grant Likely
2010-07-22 8:16 ` Magnus Damm
2010-07-22 12:10 ` David Jander
2010-07-22 12:35 ` Russell King - ARM Linux
2010-07-22 12:56 ` Mark Brown
2010-07-22 13:31 ` David Jander
2010-07-22 13:54 ` Russell King - ARM Linux
2010-07-23 10:35 ` David Jander
2010-07-23 13:02 ` Russell King - ARM Linux [this message]
2010-07-22 14:20 ` Mark Brown
2010-07-23 10:18 ` David Jander
2010-07-23 12:57 ` Russell King - ARM Linux
2010-07-23 14:17 ` Mark Brown
2010-07-23 18:38 ` david at protonic.nl
2010-07-23 19:59 ` Jason McMullan
2010-07-23 21:03 ` Robert Schwebel
2010-07-26 1:37 ` Magnus Damm
2010-07-26 6:56 ` Robert Schwebel
2010-07-24 18:50 ` Mark Brown
2010-07-22 15:00 ` Nicolas Pitre
2010-07-23 10:31 ` David Jander
2010-07-22 13:41 ` Rob Herring
2010-07-22 21:20 ` Linus Walleij
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=20100723130243.GB750@n2100.arm.linux.org.uk \
--to=linux@arm.linux.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 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).