From: Timur Tabi <timur@tabi.org>
To: "eshe168@gmail.com" <eshe168@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
zhphsearch <zhphsearch@163.com>
Subject: Re: P1022 audio driver help!
Date: Mon, 02 Jun 2014 10:52:25 -0500 [thread overview]
Message-ID: <538C9DB9.80007@tabi.org> (raw)
In-Reply-To: <201406022205351271662@gmail.com>
eshe168@gmail.com wrote:
>
> I have another question. Did you test full duplex in P1022 RDK board?
> Our design is same with P1022 RDK.
No, I don't think I did. The P1022RDK was not a board that my team was
responsible for, so I only did minimal work on it. I added support for
it in the upstream kernel. It was so long ago that I don't really
remember much about it. I still have the board, though.
prev parent reply other threads:[~2014-06-02 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 6:03 P1022 audio driver help! eshe168
2014-05-30 15:48 ` Timur Tabi
2014-06-02 14:05 ` eshe168
2014-06-02 15:52 ` Timur Tabi [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=538C9DB9.80007@tabi.org \
--to=timur@tabi.org \
--cc=eshe168@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=zhphsearch@163.com \
/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).