From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: I always encouter this simple error message compiling 2.6 for ML403 UART 16550
Date: Tue, 01 May 2007 00:44:53 -0400 [thread overview]
Message-ID: <4636C5C5.8050408@dlasys.net> (raw)
In-Reply-To: <528646bc0704300122r29747b36q648fcde3da755a36@mail.gmail.com>
Grant Likely wrote:
>
> Oops; that patch won't work. Try this one instead.
What really needs to be done is to create some kind of mini-driver
architecture for the boot and debug serial drivers.
There are only something like 4 or 5 simple functions, and in many
cases only putchar() needs implimented.
The whole boot/debug early serial stuff is highly and unescesarily
8250 specific. While there are several alternatives,
these typically involve numerous #ifdef's and then end up being
board specific.
Being able to output data, before linux has loaded, or before the
standard serial drivers have initialized is probably not important for
working systems, but is incredibly useful when trying to bring up a
new board - particularly if you are trying to do so with
silly scopes, logic analyzers, and other electronic gizmo's
"give me an output bit and an LED to hang on it, and I can flash the
world"
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
prev parent reply other threads:[~2007-05-01 4:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 6:43 I always encouter this simple error message compiling 2.6 for ML403 UART 16550 Mohammad Sadegh Sadri
2007-04-30 7:32 ` Grant Likely
2007-04-30 8:22 ` Grant Likely
2007-05-01 4:44 ` David H. Lynch Jr. [this message]
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=4636C5C5.8050408@dlasys.net \
--to=dhlii@dlasys.net \
--cc=linuxppc-embedded@ozlabs.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).