svn commit: r45760 - head/en_US.ISO8859-1/htdocs/news/status

Warren Block wblock at
Thu Oct 9 22:37:50 UTC 2014

Author: wblock
Date: Thu Oct  9 22:37:49 2014
New Revision: 45760

  Add SDIO report.


Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml	Thu Oct  9 19:46:41 2014	(r45759)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml	Thu Oct  9 22:37:49 2014	(r45760)
@@ -1021,7 +1021,7 @@
   <project cat='bin'>
-    <title>SSE Variants of libc Routines for amd64</title>
+    <title>SSE Variants of <tt>libc</tt> Routines for amd64</title>
@@ -1038,7 +1038,7 @@
-      <p>I have written SSE/AVX-optimized versions of a few libc
+      <p>I have written SSE/AVX-optimized versions of a few <tt>libc</tt>
 	routines for amd64.  So far the list includes <tt>memcpy</tt>,
 	<tt>memset</tt>, and <tt>strlen</tt>.  For each routine I have
 	written a simple regression test as well as performed some
@@ -1049,7 +1049,7 @@
 	<tt>memset</tt> have proven trickier as different variants can
 	behave quite differently on different CPUs.</p>
-      <p>At present, I do not yet have a patch relative to libc.  Once
+      <p>At present, I do not yet have a patch relative to <tt>libc</tt>.  Once
 	I do, this will be suitable for more testing.  I'd like to see
 	some real-world benchmarks that show measurable improvement
 	before pushing any of this up into the tree.</p>
@@ -1057,7 +1057,7 @@
-	<p>Create a branch that holds a modified libc and is suitable
+	<p>Create a branch that holds a modified <tt>libc</tt> and is suitable
 	  for testing</p>
@@ -1127,4 +1127,76 @@
+  <project cat='kern'>
+    <title>SDIO Driver</title>
+    <contact>
+      <person>
+	<name>
+	  <given>Ilya</given>
+	  <common>Bakulin</common>
+	</name>
+	<email>ilya at</email>
+      </person>
+    </contact>
+    <links>
+      <url href="">SDIO project page on FreeBSD wiki</url>
+      <url href="">Source code</url>
+      <url href="">Patch for review</url>
+    </links>
+    <body>
+      <p>SDIO is an interface designed as an extension of the existing
+	SD card standard, allowing connection of different peripherals
+	to the host with the standard SD controller.  Peripherals
+	currently sold in the general market include WLAN/BT modules,
+	cameras, fingerprint readers, and barcode scanners.  SDIO is
+	also used to connect some peripherals in products like
+	Chromebooks and Wandboard.</p>
+      <p>The current main focus of the project is to reimplement the
+	existing MMC/SD stack using the CAM framework.  This will
+	allow utilizing the well-tested CAM locking model and debug
+	features.</p>
+      <p>The first version of the code was uploaded on Phabricator for
+	review.  The new stack is able to attach to the SD card and
+	bring it to an operational state.  The only supported SD
+	controller driver is <tt>ti_sdhci</tt> which is used by the
+	BeagleBone Black.  Modifying other SDHCI-compliant drivers
+	should not be a hard task.</p>
+    </body>
+    <help>
+      <task>
+	<p>At this point, feedback from kernel developers is really
+	  needed.  This may be done in the form of code review.  If
+	  the chosen way of implementing the CAM-aware MMC stack is
+	  considered correct, then adding code for interacting with SD
+	  cards (for example, setting the optimal transfer rates) will
+	  be the next task.</p>
+      </task>
+      <task>
+	<p>Write a CAM peripheral driver that implements an interface
+	  to the FreeBSD <tt>disk(9)</tt>.  It will send MMC I/O
+	  commands using the MMC XPT layer.</p>
+      </task>
+      <task>
+	<p>Extending <tt>camcontrol(8)</tt> to make it possible to
+	  send MMC-specific commands directly to the MMC/SD card using
+	  pass(4) will greatly assist in developing new features for
+	  the stack.</p>
+      </task>
+      <task>
+	<p>Modify the <tt>sdhci(4)</tt> driver to work with the new
+	  stack.  This is required to work on the new stack using PC
+	  hardware, not only the BeagleBone Black.</p>
+      </task>
+    </help>
+  </project>

More information about the svn-doc-all mailing list