Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Alpha Lin <Alpha.Lin@rock-chips.com>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Chen Herman <herman.chen@rock-chips.com>,
	Jeffy Chen <jeffy.chen@rock-chips.com>
Subject: Re: rockchip v4l support ?
Date: Mon, 13 Jul 2015 10:04:52 +0200	[thread overview]
Message-ID: <1436774692.2187.28.camel@googlemail.com> (raw)
In-Reply-To: <55A36EB8.4070401@xs4all.nl>

Hi Alpha Lin,

 please see my question below.

On Mon, 2015-07-13 at 09:54 +0200, Hans Verkuil wrote:
> Hi Christoph,
> 
> On 07/13/2015 09:20 AM, Christoph Fritz wrote:
> > Hi,
> > 
> >  is someone working on v4l (camera stack) support for rockchip SoCs?
> 
> I'm not aware of any activity, you're the first to ask about this on the linux-media
> mailinglist.
> 
> However, a quick google turns up this:
> 
> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-reviews/DMCeSXLwoKY
> 
> > Currently, it lacks pretty much everything. So what is your guess in the
> > amount of work at a rough estimate?
> 
> Hard to tell since I do not know the hardware. Basically anything from a week
> to a year or more :-)
> 
> It depends on whether there is any code out there for driving the camera stack
> that you can base your work on and whether you have datasheets and how complex
> the HW is.

Could you please answer or comment some of the questions raised in the
text above?

 Thanks
  -- chf

      reply	other threads:[~2015-07-13  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  7:20 rockchip v4l support ? Christoph Fritz
2015-07-13  7:54 ` Hans Verkuil
2015-07-13  8:04   ` Christoph Fritz [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=1436774692.2187.28.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --cc=Alpha.Lin@rock-chips.com \
    --cc=herman.chen@rock-chips.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jeffy.chen@rock-chips.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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