From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kevin diggs <diggskevin38@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: 750gx cpufreq induced kernel panic in 2.6.36
Date: Thu, 27 Jan 2011 15:25:52 +1100 [thread overview]
Message-ID: <1296102352.2349.164.camel@pasglop> (raw)
In-Reply-To: <AANLkTinS8wJq-wr1=yoeC-f-FcToPzsKLmA3hrshaUms@mail.gmail.com>
On Wed, 2011-01-26 at 21:59 -0600, kevin diggs wrote:
> Ok! Thanks!
>
> One thing. The 2.6 driver for the serial ports on this machine does
> not work very well. Can I use a slower speed to avoid missing stuff?
pmac zilog ? It should work fine on tx... unless your receiving side is
the one with a problem or we have a bug :-)
> And I'll need to build the serial stuff into the kernel, right?
Yes.
Cheers,
Ben.
prev parent reply other threads:[~2011-01-27 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 23:54 750gx cpufreq induced kernel panic in 2.6.36 kevin diggs
2011-01-26 4:32 ` Benjamin Herrenschmidt
2011-01-26 17:20 ` kevin diggs
2011-01-26 21:43 ` Benjamin Herrenschmidt
2011-01-27 3:59 ` kevin diggs
2011-01-27 4:25 ` Benjamin Herrenschmidt [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=1296102352.2349.164.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=diggskevin38@gmail.com \
--cc=linuxppc-dev@lists.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).