From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.atmel.fr ([81.80.104.162]:34396 "EHLO atmel-es2.atmel.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932720Ab0ECPjm (ORCPT ); Mon, 3 May 2010 11:39:42 -0400 Message-ID: <4BDEEE38.9070801@atmel.com> Date: Mon, 03 May 2010 17:39:36 +0200 From: Sedji Gaouaou MIME-Version: 1.0 To: Guennadi Liakhovetski CC: Linux Media Mailing List , linux-input@vger.kernel.org Subject: Re: ATMEL camera interface References: <4BD9AA8A.7030306@atmel.com> <4BDED3A8.4090606@atmel.com> <4BDEDB06.9090909@atmel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-media-owner@vger.kernel.org List-ID: Well sorry to bother you again but I am looking at the mx1_camera.c file, and I wonder where are implemented the queue and dqueue functions? The atmel IP is using linked list for the buffers, and previously I was managing it in the queue and dqueue functions. I am not sure where I should take care of it now? Regards, Sedji Le 5/3/2010 4:26 PM, Guennadi Liakhovetski a écrit : > On Mon, 3 May 2010, Sedji Gaouaou wrote: > >> Well I need contiguous memory, so I guess I will have a look at mx1_camera.c? >> Is there another example? >> >> What do you mean by videobuf implementation? As I said I just need a >> contiguous memory. > > I mean, whether you're gping to use videobuf-dma-contig.c or > videobuf-dma-sg.c, respectively, whether you'll be calling > videobuf_queue_dma_contig_init() or videobuf_queue_sg_init() in your > driver. > > Regards > Guennadi > --- > Guennadi Liakhovetski, Ph.D. > Freelance Open-Source Software Developer > http://www.open-technology.de/ >