All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Make spitz compile again
Date: Wed, 02 Nov 2005 14:44:07 +0000	[thread overview]
Message-ID: <1130942647.8523.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20051102135253.GK30194@elf.ucw.cz>

On Wed, 2005-11-02 at 14:52 +0100, Pavel Machek wrote:
> Hi!
> 
> > On Wed, 2005-11-02 at 13:51 +0100, Pavel Machek wrote:
> > > Did you see any problems with touchscreen? I see "ts" registered,
> > > interrupts coming, but opie does not see any clicks :-(.
> > 
> > Update to udev 071 ;-)
> 
> Is there some other workaround? I'm not able to do that on spitz --
> you know my bitbake capabilities :-(.

Create /dev/input/ and add event0 and event1 nodes. You'll have to hack
the init scripts to do this and fight off udev.

or

Download and copy this to the device:
http://www.rpsys.net/openzaurus/temp/udev_071-r5_armv5te.ipk

and ipkg install udev_071-r5_armv5te.ipk

I'm not sure these kind of things should be going to LKML in future
though...

Richard


  reply	other threads:[~2005-11-02 14:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 13:42 Make spitz compile again Pavel Machek
2005-10-31 15:45 ` Richard Purdie
2005-11-01 19:31   ` Pavel Machek
2005-11-01 20:10     ` Richard Purdie
2005-11-01 20:37       ` Pavel Machek
2005-11-01 20:39       ` Pavel Machek
2005-11-01 20:40       ` Pavel Machek
2005-11-01 20:05   ` Pavel Machek
2005-11-01 20:19     ` Richard Purdie
2005-11-01 21:46     ` Richard Purdie
2005-11-01 22:14       ` Russell King
2005-11-01 22:54         ` Richard Purdie
2005-11-02 11:10       ` Pavel Machek
2005-11-02 12:51   ` Pavel Machek
2005-11-02 13:47     ` Richard Purdie
2005-11-02 13:52       ` Pavel Machek
2005-11-02 14:44         ` Richard Purdie [this message]
2005-10-06  7:16           ` spitz autorepeat Pavel Machek

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=1130942647.8523.19.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.