linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Meade <chuck@ThePTRGroup.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: UCC interactions
Date: Tue, 22 Jun 2010 11:15:18 -0400	[thread overview]
Message-ID: <4C20D386.2000506@ThePTRGroup.com> (raw)
In-Reply-To: <AANLkTinyt8phAgxJk30G0XuA5kJ78Xy1WdTg_yQpTCsS@mail.gmail.com>

On 06/22/2010 10:51 AM, Timur Tabi wrote:
> On Mon, Jun 21, 2010 at 2:00 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I'm running 2.6.33.3 on MPC8358.  I have UCC1+UCC2 working fine
>> for ethernet, but when I add UCC3 as a UART, the network devices
>> quit working.
> 
> Since you're using QE UART, would you mind testing this patch:
> 
> http://patchwork.ozlabs.org/patch/56181/
> 
> and letting us know if it works for you?
> 

Hi Timur,

His UART is not working yet.  I am fine with him testing my patch (I hope he does),
just he still is working on getting his UART to work at all.  I think since he is
using MPC8358, he needs the soft UART mode microcode patch.

The patch that you mention above is one I wrote that affects how the UART close
operation handles being closed when buffered output is still present.  I fixed the
timeout so it closes in the correct amount of time.  Gary is not quite ready for
testing this yet.

Thanks,
Chuck

      reply	other threads:[~2010-06-22 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:00 UCC interactions Gary Thomas
2010-06-21 19:19 ` Steven Blakeslee
2010-06-21 20:23   ` Gary Thomas
2010-06-22 14:51 ` Timur Tabi
2010-06-22 15:15   ` Chuck Meade [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=4C20D386.2000506@ThePTRGroup.com \
    --to=chuck@theptrgroup.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).