From: Thomas Chou <thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
To: Mike Frysinger <vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org,
Nios2 development list
<nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: touch screen ads7846/7843 devicetree support
Date: Thu, 27 Jan 2011 18:58:53 +0800 [thread overview]
Message-ID: <4D414FED.706@wytron.com.tw> (raw)
In-Reply-To: <AANLkTinJheHYyjUUAK7guNXqepp9KJ3xk6u-4JrmAbee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 01/27/2011 02:18 PM, Mike Frysinger wrote:
> On Thu, Jan 27, 2011 at 01:10, Thomas Chou wrote:
>> We need devicetree support on ads7846/7843 touch screen driver. Do you have
>> plan on it? We are moving to devicetree on nios2, so do arm/mips/x86.
>
> what part are you using exactly ?
> -mike
>
ad7843 is used in a popular nios2 dev kit, NEEK.
- Thomas
next prev parent reply other threads:[~2011-01-27 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 6:10 touch screen ads7846/7843 devicetree support Thomas Chou
[not found] ` <4D410C4C.7070005-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-27 6:18 ` Mike Frysinger
[not found] ` <AANLkTinJheHYyjUUAK7guNXqepp9KJ3xk6u-4JrmAbee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-27 10:58 ` Thomas Chou [this message]
[not found] ` <4D414FED.706-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-01-27 12:24 ` Hennerich, Michael
[not found] ` <544AC56F16B56944AEC3BD4E3D591771324C105D75-gpnycfiEEVR7xzP2fcxY8GoKb0G9Rp+C@public.gmane.org>
2011-01-27 13:31 ` [uclinux-dist-devel] " Thomas Chou
2011-02-02 16:03 ` Grant Likely
[not found] ` <20110202160355.GE20275-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-02-03 0:07 ` Thomas Chou
2011-06-09 6:07 ` Barry Song
[not found] ` <BANLkTik5BfiUeNFn-dXah86h+nhK6hU6vg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-09 8:12 ` Mike Frysinger
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=4D414FED.706@wytron.com.tw \
--to=thomas-sdxuxyehebicupeqfhbrbg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org \
--cc=uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org \
--cc=vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.