public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Enabling Mistral touch screen driver
Date: Mon, 15 May 2006 11:54:20 -0700	[thread overview]
Message-ID: <200605151154.22221.david-b@pacbell.net> (raw)
In-Reply-To: <4468BC84.6050205@gmail.com>

On Monday 15 May 2006 10:38 am, Dirk Behme wrote:
> > 
> > CONFIG_OMAP_OSK_MISTRAL=y
> > CONFIG_INPUT_TOUCHSCREEN=y
> > CONFIG_TOUCHSCREEN_ADS7846=y
> > CONFIG_SPI_OMAP_UWIRE=y
> > 
> > That assumes a recent GIT tree, which includes the board-specific init
> > needed to make that work.
> 
> Any plans to remove CONFIG_OMAP_UWIRE or 
> CONFIG_TOUCHSCREEN_OMAP so that guys like me using their 
> configuration for ages are forced to rethink about it?

Yes.  Given patches merged today, and one I'll post soonish, it's almost
time to get rid of

	drivers/input/touchscreen/omap/
		ads7846.h
		ts_inn1510.c
		ts_osk.c

Until there's a tsc2101.c SPI-framework driver, the ts_hx.c support
(and omap-alsa-tsc2101) will need to stick around though.  

And there will be similar issues for the CONFIG_OMAP_UWIRE too;
likely more than just tsc2101 support needs that for the moment.

- Dave

  reply	other threads:[~2006-05-15 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13  9:37 Enabling Mistral touch screen driver Vishal Borker
2006-05-14 15:45 ` Dirk Behme
2006-05-14 16:55   ` David Brownell
2006-05-15 17:38     ` Dirk Behme
2006-05-15 18:54       ` David Brownell [this message]
2006-05-27  6:32     ` Dirk Behme
2006-05-27 15:57       ` David Brownell

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=200605151154.22221.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=dirk.behme@googlemail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox