From: Sakari Ailus <sakari.ailus@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>,
Arnd Bergmann <arnd@arndb.de>, Takashi Iwai <tiwai@suse.de>,
LMML <linux-media@vger.kernel.org>
Subject: Re: Device driver memory 'mmap()' function helper cleanup
Date: Mon, 13 May 2013 00:52:22 +0300 [thread overview]
Message-ID: <20130512215221.GD6748@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <20130417074300.33d05475@redhat.com>
Hi Mauro,
On Wed, Apr 17, 2013 at 07:43:00AM -0300, Mauro Carvalho Chehab wrote:
> and a camera anymore. The OMAP2 were used on some Nokia phones.
> They used to maintain that code, but now that they moved to the dark
> side of the moon, they lost their interests on it. So, it may not
> be easily find testers for patches there.
There's one more underlying issue there than potentially having both no-one
with the device and time to test it: the driver does not function as-is in
mainline (nor any recent non-mainline kernel either). Quite some work would
be required to update it (both to figure out why the whole system crashes
when trying to capture images and change the driver use modern APIs). A
small while back we decided to still keep the driver in the tree:
<URL:http://www.spinics.net/lists/linux-media/msg56237.html>
(The rest of the discussion took place in #v4l AFAIR.)
So, what could be done now is either 1) write a patch that changes the
driver to use the right API and take a risk of adding one more bug to the
driver; or 2) remove the driver now and bring it back only if someone really
has time to make it work first.
--
Kind regards,
Sakari Ailus
e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
next prev parent reply other threads:[~2013-05-13 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 3:12 Linus Torvalds
2013-04-17 7:20 ` Takashi Iwai
2013-04-17 9:15 ` Arnd Bergmann
2013-04-17 9:45 ` Clemens Ladisch
2013-04-17 17:58 ` Linus Torvalds
2013-04-17 21:28 ` Arnd Bergmann
2013-04-17 21:31 ` Linus Torvalds
2013-04-17 10:43 ` Mauro Carvalho Chehab
2013-04-17 12:22 ` [PATCH 1/2] [media] videobuf-dma-contig: remove support for cached mem Mauro Carvalho Chehab
2013-04-17 12:22 ` [PATCH 2/2] [media] videobuf-dma-contig: use vm_iomap_memory() Mauro Carvalho Chehab
2013-04-17 12:56 ` Mauro Carvalho Chehab
2013-04-17 12:49 ` [PATCH 1/2] [media] videobuf-dma-contig: remove support for cached mem Hans Verkuil
2013-05-12 21:52 ` Sakari Ailus [this message]
2013-04-17 11:34 ` Device driver memory 'mmap()' function helper cleanup Tomi Valkeinen
2013-04-17 14:44 ` Linus Torvalds
2013-04-17 17:11 ` David Miller
2013-04-17 17:20 ` Linus Torvalds
2013-04-17 17:27 ` David Miller
2013-04-17 17:48 ` Linus Torvalds
2013-04-19 15:43 ` Michel Lespinasse
2013-04-19 23:07 ` Linus Torvalds
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=20130512215221.GD6748@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=arnd@arndb.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®