All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: Hardware for testing Dead Pixel API
Date: Tue, 28 Oct 2014 15:21:14 +0200	[thread overview]
Message-ID: <3291269.yV9E63i4de@avalon> (raw)
In-Reply-To: <544F95BE.1070608@iki.fi>

Hello,

On Tuesday 28 October 2014 15:10:22 Sakari Ailus wrote:
> Ricardo Ribalda Delgado wrote:
> > Hello
> > 
> > As we discussed in the mini-summit I am interested in upstreaming an
> > API for Dead Pixels.
> > 
> > Since it is not viable to push my camera code, I would like to add it
> > to an already supported camera.
> > 
> > On the summit somebody mention a board that also has hardware support
> > for Dead Pixels, but the driver did not support it. If my memory is
> > right it was a beagle board plus a sensor board.
> > 
> > Could somebody point me to the right hardware to buy ?
> 
> The OMAP 3 ISP does have dead pixel correction but I'm not sure if it's
> documented well enough to actually implement it in public documentation.
> 
> A used Nokia N9 or N900 would be one possibility. I think the only
> cameras I've seen dead pixels in are either of the front cameras,
> probably the one in N900. At the moment only the N9 main camera works
> for sure however. The N9 or N900 front cameras will need some debugging
> work / DT snippets at least.
> 
> There are cameras for Beagle boards, too. Laurent, do you happen to
> remember if you've seen any with dead pixels in it?

I haven't seen any, but on the other hand I haven't really paid attention. It 
shouldn't be difficult to damage pixels on a sensor :-)

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2014-10-28 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  9:15 Hardware for testing Dead Pixel API Ricardo Ribalda Delgado
2014-10-28 13:10 ` Sakari Ailus
2014-10-28 13:21   ` Laurent Pinchart [this message]

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=3291269.yV9E63i4de@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ricardo.ribalda@gmail.com \
    --cc=sakari.ailus@iki.fi \
    /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.