From: Murray Jensen <Murray.Jensen@csiro.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] 8xx_io/uart.c
Date: Wed, 12 Feb 2003 10:11:03 +1100 [thread overview]
Message-ID: <23285.1045005063@msa.cmst.csiro.au> (raw)
In-Reply-To: Your message of "Tue, 11 Feb 2003 11:40:45 -0500" <3E49278D.3020306@embeddededge.com>
On Tue, 11 Feb 2003 11:40:45 -0500, Dan Malek <dan@embeddededge.com> writes:
>I've looked at it. I know it well. I wrote it. I know how its used.
>xmon and kgdb format their own strings/packets and expect read/write of
>a simple uart fifo.
The point was, and always has been, can it be guaranteed that kgdb/xmon will
never output a character with decimal value 10? As a simple logic exercise,
it cannot be guaranteed - of course, in practice it is unlikely to happen,
because they encode everything as two hex digits.
But someone in the future may decide to make everything scroll nicely on
output by adding a (redundant) linefeed to the end of every packet - then
the kernel starts crashing in early boot when KGDB or XMON is enabled and
they will have no idea why.
>> http://lists.linuxppc.org/linuxppc-embedded/200205/msg00268.html
>
>Well, ahhh, there isn't anything mentioned there about fixing bugs.
It wasn't mentioned because it is trivial - the code as it stood was
logically inconsistent - I fixed it, as have (many?) others.
>From
>your description it's all about yet another scc uart configuration method.
>I have lots of those on the shelf, all conflicting, that always seem to
>be useful to the person/platform/application. The easiest way to keep
>everyone (un)happy is to leave things alone. I used to apply those,
>a new one every other week, and the only person happy about it was the
>last one that had the patch applied. :-)
This illustrates my point(s) - linuxppc on the 8260 is stuck with the amazingly
bad uart configuration/management arrangement it has had for years (and which
was spawned back in the 8xx days) because I don't work for the right company.
Like I said - I will shut up now - it isn't that important to me. I made my
points in the previous message, and it is on the public record (such as it
is), but now I don't want to distract either of us from our work. Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen@csiro.au
Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-11 23:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 13:36 [PATCH] 8xx_io/uart.c Joakim Tjernlund
2003-02-07 16:08 ` Dan Malek
2003-02-07 17:21 ` Joakim Tjernlund
2003-02-09 20:52 ` Dan Malek
2003-02-10 0:29 ` Joakim Tjernlund
2003-02-10 1:08 ` Murray Jensen
2003-02-10 18:52 ` Dan Malek
2003-02-11 1:13 ` Murray Jensen
2003-02-11 16:40 ` Dan Malek
2003-02-11 23:11 ` Murray Jensen [this message]
2003-02-11 23:16 ` Murray Jensen
2003-02-11 18:56 ` Tom Rini
2003-02-11 11:16 ` Joakim Tjernlund
2003-02-11 16:03 ` Dan Malek
2003-02-11 18:07 ` Joakim Tjernlund
2003-02-11 23:54 ` Paul Mackerras
2003-02-14 15:13 ` Joakim Tjernlund
2003-02-14 20:12 ` Dan Malek
2003-02-19 8:43 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 16:54 Ruhland, Paul
2003-02-07 18:43 ` Joakim Tjernlund
2003-02-10 14:45 ` Joakim Tjernlund
2003-02-10 17:25 ` Tom Rini
2003-02-11 8:33 ` Joakim Tjernlund
[not found] <dan@embeddededge.com>
[not found] ` <3C98DA15.50302@embeddededge.com>
2002-03-21 1:11 ` EV-64260-BP & GT64260 bi_recs Murray Jensen
2002-03-21 6:50 ` Dan Malek
2002-03-21 11:05 ` Murray Jensen
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=23285.1045005063@msa.cmst.csiro.au \
--to=murray.jensen@csiro.au \
--cc=linuxppc-embedded@lists.linuxppc.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).