From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-media-owner@vger.kernel.org>
Received: from mail.atmel.fr ([81.80.104.162]:55044 "EHLO atmel-es2.atmel.fr"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754818AbZCWQAy (ORCPT <rfc822;linux-media@vger.kernel.org>);
	Mon, 23 Mar 2009 12:00:54 -0400
Message-ID: <49C7B226.6000302@atmel.com>
Date: Mon, 23 Mar 2009 17:00:38 +0100
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
MIME-Version: 1.0
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
CC: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: atmel v4l2 soc driver
References: <49B789F8.3070906@atmel.com> <Pine.LNX.4.64.0903111100050.4818@axis700.grange> <49C7A8DF.3040101@atmel.com> <Pine.LNX.4.64.0903231632020.6370@axis700.grange>
In-Reply-To: <Pine.LNX.4.64.0903231632020.6370@axis700.grange>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-media-owner@vger.kernel.org
List-ID: <linux-media.vger.kernel.org>

Guennadi Liakhovetski a écrit :
> 
> Wouldn't ov9655 be similar enough to ov9650 as used in stk-sensor.c? Hans, 
> would that one also be converted to v4l2-device? If so, Sedji, you don't 
> need to write yet another driver for it. 

I had a look at the stk-sensor file. Does it follow the soc arch?

Regards,
sedji