From owner-soc-status@FreeBSD.ORG Mon May 31 20:30:49 2010 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C9FF106566C for ; Mon, 31 May 2010 20:30:49 +0000 (UTC) (envelope-from jceel@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id AE1FF8FC19 for ; Mon, 31 May 2010 20:30:48 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id E35D8C42DA for ; Mon, 31 May 2010 22:17:48 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id smrlVrwrpVZi for ; Mon, 31 May 2010 22:17:48 +0200 (CEST) Received: from [192.168.1.101] (unknown [195.150.224.245]) by smtp.semihalf.com (Postfix) with ESMTPSA id 2FC65C42D5 for ; Mon, 31 May 2010 22:17:48 +0200 (CEST) From: Jakub Klama Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 31 May 2010 22:12:47 +0200 Message-Id: To: soc-status@freebsd.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: [DMA Engine Framework] status report #1 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2010 20:30:49 -0000 Done this week: * Created early skeleton of API for DMA engine drivers=20 (Milesone M1: in progress) * Written basic working driver for DaVinci EDMA3 engine using above = mentioned=20 API (Milestone M2: in progress) * Written basic character device driver to test some transfers * Submitted first DMA transfers and got correct results. :-) Plans for next week: * Improve DMA engine drivers API: - get information from DMA engine about supported transfer types - think about some transfer validation mechanism (eg. "this transfer = can't be done using this device" or "this is illegal transfer because address = ranges overlap") [1] * Write some skeleton of DMA engine API for use in various kernel = subsystems and device drivers. * Think about DMA transfer descriptor structure - can we simplify it? Potential problems: * [1] - transfer descriptors are somewhat complex and transfer = validation can be complex too (checking address ranges, stride sizes/spacings, FIFO widths, etc on source and destination buffers) --=20 Jakub Klama.=