From: david.jander@protonic.nl (David Jander)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM Machine SoC I/O setup and PAD initialization code
Date: Thu, 22 Jul 2010 15:31:58 +0200 [thread overview]
Message-ID: <201007221531.58744.david.jander@protonic.nl> (raw)
In-Reply-To: <20100722125652.GL10930@sirena.org.uk>
On Thursday 22 July 2010 02:56:52 pm Mark Brown wrote:
> On Thu, Jul 22, 2010 at 02:10:09PM +0200, David Jander wrote:
> > IMO, if a bootloader is broken (in any way), it needs replacing. Be it
> > with another bootloader or directly with the kernel.
>
> If you don't have JTAG access (either due to device limitations or due
> to lack of data from the vendor of a reference platform you're using)
> replacing a bootloader can be rather more stressful than it's worth.
I agree, but I simply can't believe ARM platform designers all do such a bad
job at firmware (=bootloader) development in general, which is in sharp
contrast to what I have learned from previous PowerPC developments.
Maybe the difference is in the market: PowerPC is more geared towards an
industrial embedded market (high demand of robustness and reliability), while
ARM comes from a pure consumer market, and is just lately making inroads into
industrial applications.
> > That sounds a lot "saner" to me than having two asynchronous and
> > different copies of setup-code, which could be a potential nightmare,
> > besides not being really maintainable.
>
> Well, from the point of view of using systems like this all you need the
> bootloader to do is to set the system up enough to load the kernel and
> start it running. You don't need it to understand anything else about
> the rest of the system, which means you're less reliant on the quality
> of the bootloader.
How can you assume that kernel-developers know how to correcly set-up the slew
rate and drive-strength of an I/O-pin for a given platform if the manufacturer
itself didn't do it nor document it!??
Even if it works with one guessed setting, there is a potential EMC impact
that needs to be taken care of.
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.
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2010-07-22 13:31 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 [this message]
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
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=201007221531.58744.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--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).