linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Murray Jensen <Murray.Jensen@csiro.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] 8xx_io/uart.c
Date: Tue, 11 Feb 2003 11:40:45 -0500	[thread overview]
Message-ID: <3E49278D.3020306@embeddededge.com> (raw)
In-Reply-To: 30768.1044926029@ull


Murray Jensen wrote:

> If you simply looked at the code you would see the problem we are talking
> about. What are you suggesting? That kgdb and xmon will _NEVER_ send a
> character with decimal value 10 via my_console_write()?

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.

> http://lists.linuxppc.org/linuxppc-embedded/200205/msg00268.html

Well, ahhh, there isn't anything mentioned there about fixing bugs.  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.  :-)

You can pull the uart "bugfix" from the 2_4_devel tree now, if you wish.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-02-11 16:40 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 [this message]
2003-02-11 23:11               ` Murray Jensen
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=3E49278D.3020306@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=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).