From owner-svn-doc-all@FreeBSD.ORG Mon Apr 7 21:45:11 2014
Return-Path:
Delivered-To: svn-doc-all@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 7B2CA3B5;
Mon, 7 Apr 2014 21:45:11 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 5BC338D8;
Mon, 7 Apr 2014 21:45:11 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s37LjBot064026;
Mon, 7 Apr 2014 21:45:11 GMT (envelope-from pgj@svn.freebsd.org)
Received: (from pgj@localhost)
by svn.freebsd.org (8.14.8/8.14.8/Submit) id s37LjBH9064025;
Mon, 7 Apr 2014 21:45:11 GMT (envelope-from pgj@svn.freebsd.org)
Message-Id: <201404072145.s37LjBH9064025@svn.freebsd.org>
From: Gabor Pali
Date: Mon, 7 Apr 2014 21:45:11 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r44482 - head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-all@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "SVN commit messages for the entire doc trees \(except for "
user" , " projects" , and " translations"
\)"
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 07 Apr 2014 21:45:11 -0000
Author: pgj
Date: Mon Apr 7 21:45:10 2014
New Revision: 44482
URL: http://svnweb.freebsd.org/changeset/doc/44482
Log:
- Add 2014Q1 status report for the SDIO driver
Submitted by: Ilya Bakulin
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Mon Apr 7 21:37:23 2014 (r44481)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Mon Apr 7 21:45:10 2014 (r44482)
@@ -18,7 +18,7 @@
Thanks to all the reporters for the excellent work! This report
- contains 29 entries and we hope you enjoy reading it.
+ contains 30 entries and we hope you enjoy reading it.
The deadline for submissions covering between April and
June 2014 is July 7th, 2014.
@@ -1844,4 +1844,58 @@ device vt_efifb
The &os; Foundation
+
+
+ SDIO driver
+
+
+
+
+ Ilya
+ Bakulin
+
+ ilya@bakulin.de
+
+
+
+
+ SDIO project page on &os; wiki
+ Source code
+
+
+
+ SDIO is an interface designed as an extension of the existing
+ SD card standard, to allow connecting different peripherals to
+ the host with the standard SD controller. Peripherals currently
+ sold at the general market include WLAN/BT modules, cameras,
+ fingerprint readers, and barcode scanners. The &os; driver is
+ implemented as an extension to the existing MMC bus, adding a
+ lot of new SDIO-specific bus methods. A prototype of the driver
+ for the Marvell SDIO WLAN/BT (Avastar 88W8787) module is also
+ being developed, using the existing Linux driver as the
+ reference.
+
+ SDIO card detection and initialization already work, most
+ needed bus methods are implemented and tested.
+
+ WiFi driver is able to load a firmware onto the card and
+ initialize it. Migration of the MMC stack to the new locking
+ model is necessary in order to work with SDIO cards effectively.
+ The &os; CAM implementation is believed to be a good choice.
+ There is an ongoing work to implement an MMC transport for
+ CAM.
+
+
+
+ SDIO stack: finish CAM migration. The XPT layer is almost
+ ready, what is missing is a SIM module, for which a modified
+ version of SDHCI controller driver will be used, and a
+ peripheral module, where porting the mmcsd(4) driver is
+ required.
+
+ Marvell SDIO WiFi: connect it to the &os; network stack,
+ write the code to implement required functions, such as sending
+ and receiving data, network scanning and so on.
+
+