From: Rob Landley <rob@landley.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Re: ZILOG serial port broken in 2.6.32
Date: Sat, 9 Jan 2010 02:17:23 -0600 [thread overview]
Message-ID: <201001090217.25729.rob@landley.net> (raw)
In-Reply-To: <1262919644.2173.704.camel@pasglop>
On Thursday 07 January 2010 21:00:43 Benjamin Herrenschmidt wrote:
> > Ok, here's the fix. It's not the _right_ fix, but it Works For Me (tm)
> > and I'll leave it to you guys to figure out what this _means_:
>
> I've failed to reproduce so far on both a Wallstreet powerbook (similar
> generation and chipset as your beige G3) and a G5 with an added serial
> port using current upstream...
>
> Can you verify it's still there ? I might be able to reproduce on a
> Beige G3 as well next week.
It's still there on qemu 0.11.0's "g3beige" emulation when you use
CONFIG_SERIAL_PMACZILOG as the serial console. (QEMU 0.10.x used a 16550
serial chip for its g3beige emulation instead of the actual ZILOG one.) Still
dunno if it's a qemu or bug or a kernel bug, I just know that kernel patch
fixes it for me, and it comes back without the patch.
I tested 2.6.32. Haven't tried the 2.6.32.3 but don't see why it would change
this...
Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
next prev parent reply other threads:[~2010-01-09 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 7:01 ZILOG serial port broken in 2.6.32 Rob Landley
2009-12-07 1:10 ` Benjamin Herrenschmidt
2009-12-07 20:25 ` Rob Landley
2009-12-08 12:42 ` [PATCH] " Rob Landley
2010-01-08 3:00 ` Benjamin Herrenschmidt
2010-01-09 8:17 ` Rob Landley [this message]
2010-01-11 3:02 ` Benjamin Herrenschmidt
2010-01-11 7:22 ` Rob Landley
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=201001090217.25729.rob@landley.net \
--to=rob@landley.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).