From: "David Lanzendörfer" <david.lanzendoerfer@o2s.ch>
To: linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Keyboard for HTC-Dream
Date: Sat, 7 Aug 2010 13:07:32 +0200 [thread overview]
Message-ID: <201008071307.40988.david.lanzendoerfer@o2s.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
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)
best regards
leviathan
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: david.lanzendoerfer@o2s.ch (David Lanzendörfer)
To: linux-arm-kernel@lists.infradead.org
Subject: Keyboard for HTC-Dream
Date: Sat, 7 Aug 2010 13:07:32 +0200 [thread overview]
Message-ID: <201008071307.40988.david.lanzendoerfer@o2s.ch> (raw)
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)
best regards
leviathan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100807/2add2cc1/attachment.sig>
next reply other threads:[~2010-08-07 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 11:07 David Lanzendörfer [this message]
2010-08-07 11:07 ` Keyboard for HTC-Dream David Lanzendörfer
2010-08-16 5:55 ` Pavel Machek
2010-08-16 5:55 ` Pavel Machek
2010-08-17 14:12 ` David Lanzendörfer
2010-09-03 15:01 ` David Lanzendörfer
2010-09-03 15:01 ` David Lanzendörfer
2010-09-03 15:44 ` Gregory Bean
2010-09-03 15:44 ` Gregory Bean
2010-09-03 17:30 ` David Lanzendörfer
2010-09-03 17:30 ` David Lanzendörfer
2010-09-03 17:55 ` David Lanzendörfer
2010-09-03 18:44 ` Gregory Bean
2010-09-14 20:51 ` Daniel Walker
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=201008071307.40988.david.lanzendoerfer@o2s.ch \
--to=david.lanzendoerfer@o2s.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.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.