From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: Keyboard for HTC-Dream
Date: Mon, 16 Aug 2010 07:55:41 +0200 [thread overview]
Message-ID: <20100816055540.GA1455@ucw.cz> (raw)
In-Reply-To: <201008071307.40988.david.lanzendoerfer@o2s.ch>
On Sat 2010-08-07 13:07:32, David Lanzend?rfer wrote:
> heyo
> how hard would it be to introduce a keyboard driver into for-next from dwalkers kernel branch?
> https://www.codeaurora.org/gitweb/quic/kernel/?p=dwalker/linux-msm.git;a=shortlog;h=refs/heads/for-next
> Would be cool, to have such a thing, then we would already have basic functionality needed to debug.
> (dmesg from terminal and so on)
Matrix driver should be capable of doing that... and look into
staging, IIRC the driver is there.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-08-16 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 11:07 Keyboard for HTC-Dream David Lanzendörfer
2010-08-16 5:55 ` Pavel Machek [this message]
2010-09-03 15:01 ` David Lanzendörfer
2010-09-03 15:44 ` Gregory Bean
2010-09-03 17:30 ` David Lanzendörfer
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=20100816055540.GA1455@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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).