public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	niklas.soderlund@ragnatech.se, jerry.w.hu@intel.com,
	mario.limonciello@dell.com
Subject: Re: Software-only image processing for Intel "complex" cameras
Date: Wed, 20 Jun 2018 23:11:44 +0200	[thread overview]
Message-ID: <20180620211144.GA16945@amd> (raw)
In-Reply-To: <b7707ec241d9d2d2966bdc32f7bb9bc55ac55c5d.camel@ndufresne.ca>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

Hi!

> > On Nokia N900, I have similar problems as Intel IPU3 hardware.
> > 
> > Meeting notes say that pure software implementation is not fast
> > enough, but that it may be useful for debugging. It would be also
> > useful for me on N900, and probably useful for processing "raw"
> > images
> > from digital cameras.
> > 
> > There is sensor part, and memory-to-memory part, right? What is
> > the format of data from the sensor part? What operations would be
> > expensive on the CPU? If we did everthing on the CPU, what would be
> > maximum resolution where we could still manage it in real time?
> 
> The IPU3 sensor produce a vendor specific form of bayer. If we manage
> to implement support for this format, it would likely be done in
> software. I don't think anyone can answer your other questions has no
> one have ever implemented this, hence measure performance.

I believe Intel has some estimates.

What is the maximum resolution of camera in the current Dell systems?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-06-20 21:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 20:38 Software-only image processing for Intel "complex" cameras Pavel Machek
2018-06-20 20:57 ` Nicolas Dufresne
2018-06-20 21:11   ` Pavel Machek [this message]
2018-06-21 13:41     ` Mario.Limonciello
2018-06-21 18:49       ` Mauro Carvalho Chehab
2018-06-21 18:58         ` Mario.Limonciello
2018-06-21 21:08           ` Mauro Carvalho Chehab
2018-06-21 21:40             ` Mauro Carvalho Chehab
2018-06-25  9:48               ` Zheng, Jian Xu
2018-06-25 13:10                 ` Mauro Carvalho Chehab
2018-07-27 10:58                   ` Javier Martinez Canillas
2018-06-23 21:29             ` Pavel Machek
2018-06-21 18:36   ` Mauro Carvalho Chehab
2018-06-29  6:02 ` Tomasz Figa
2018-06-29  9:18   ` Pavel Machek
2018-06-29  9:28     ` Tomasz Figa
2018-06-29 10:52       ` 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=20180620211144.GA16945@amd \
    --to=pavel@ucw.cz \
    --cc=jerry.w.hu@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=nicolas@ndufresne.ca \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=sakari.ailus@linux.intel.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