From: Timur Tabi <b04825@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kokoris, Ioannis" <ioannis.kokoris@siemens-enterprise.com>
Subject: Re: [PATCH] P1021: set IReady in QE Microcode Upload
Date: Mon, 2 Jul 2012 13:19:17 -0500 [thread overview]
Message-ID: <4FF1E625.9040403@freescale.com> (raw)
In-Reply-To: <9508ABD9-607F-4D41-A169-743ADE625F4A@kernel.crashing.org>
Kumar Gala wrote:
>> > No, I forgot all about it. I'll try it today, assuming the lone 8323
>> > board in the board farm still works.
> Do you remember if you ever tested this?
Well, I tried to test it. We have an 83xx board that has a QE UART that
needs firmware uploaded, but I don't know how to connect that QE to an
actual RS232 port. It needs a riser which I don't think we have.
I can verify that the QE UART driver does not hang which this patch, and
that it appears to still be sending data, but I have no way of knowing for
sure.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-07-02 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:05 [PATCH] P1021: set IReady in QE Microcode Upload Kokoris, Ioannis
2011-11-11 16:39 ` Tabi Timur-B04825
2011-11-14 8:55 ` Kokoris, Ioannis
2011-11-16 3:02 ` Tabi Timur-B04825
2011-11-24 7:55 ` Kumar Gala
2011-11-24 13:57 ` Tabi Timur-B04825
2012-03-16 15:21 ` Kumar Gala
2012-03-16 16:07 ` Timur Tabi
2012-06-29 19:23 ` Kumar Gala
2012-06-29 19:26 ` Timur Tabi
2012-07-02 18:19 ` Timur Tabi [this message]
2012-07-10 12:24 ` Kumar Gala
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=4FF1E625.9040403@freescale.com \
--to=b04825@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=ioannis.kokoris@siemens-enterprise.com \
--cc=linux-kernel@vger.kernel.org \
--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).