From: Jonathan McDowell <noodles@earth.li>
To: linux-omap-open-source@linux.omap.com
Subject: Re: omap-keypad issues with 2.6.19-rc?
Date: Fri, 27 Oct 2006 17:16:59 +0100 [thread overview]
Message-ID: <20061027161659.GP13361@earth.li> (raw)
In-Reply-To: <20061024110502.GQ1123@earth.li>
On Tue, Oct 24, 2006 at 12:05:02PM +0100, Jonathan McDowell wrote:
> On Mon, Oct 23, 2006 at 11:39:26PM +0300, Tony Lindgren wrote:
> > I've updated our git tree to 2.6.19-rc2. At least following have
> > problems on omap1 (OSK):
> >
> > - CONFIG_DEBUG_LL hangs system
> > - BUG in omap1_mbox_enable_irq
> > - Aic23 NULL pointer exception
> >
> > So YMMV :) Anybody got patches for these issues already?
>
> Haven't hit any of these with the Amstrad Delta defconfig so far (just
> done a compile and boot so far),
However having prodded further I'm seeing incorrect key parsing with
the omap-keypad driver under both -rc2 and -rc3 (works fine in
2.6.18-omap1). Numerous keys now returns strings of characters rather
than the single expected character. A few keys still work as expected
however. Before I dig in further is anyone else seeing anything similar?
J.
--
After a number of decimal places, | Black Cat Networks Ltd
nobody gives a damn. | http://www.blackcatnetworks.co.uk/
| UK Web, domain and email hosting
next prev parent reply other threads:[~2006-10-27 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 20:39 Git tree updated to 2.6.19-rc2 Tony Lindgren
2006-10-24 7:53 ` Komal Shah
2006-10-28 6:31 ` Aic23 NULL pointer exception, was: " Dirk Behme
2006-10-24 11:05 ` [PATCH] ARM: OMAP: Fixup omap-rtc (was: Git tree updated to 2.6.19-rc2) Jonathan McDowell
2006-10-24 17:57 ` David Brownell
2006-10-27 12:45 ` tony
2006-10-27 16:16 ` Jonathan McDowell [this message]
2006-10-27 16:49 ` [PATCH] ARM: OMAP: Fix Amstrad Delta omap-keypad usage Jonathan McDowell
2006-10-24 16:16 ` Git tree updated to 2.6.19-rc2 Dirk Behme
2006-10-27 12:50 ` tony
2006-10-27 15:30 ` Dirk Behme
2006-10-29 22:09 ` Hiroshi DOYU
2006-10-26 20:22 ` David Brownell
2006-10-27 12:53 ` tony
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=20061027161659.GP13361@earth.li \
--to=noodles@earth.li \
--cc=linux-omap-open-source@linux.omap.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 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.