<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys/dev/cesa, branch release/10.0.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F10.0.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F10.0.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2013-05-06T13:34:36Z</updated>
<entry>
<title>Move initialization of CESA decoding windows from common section</title>
<updated>2013-05-06T13:34:36Z</updated>
<author>
<name>Grzegorz Bernacki</name>
<email>gber@FreeBSD.org</email>
</author>
<published>2013-05-06T13:34:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=99eef68204bc8958b918c174e37d167d9aaa11cc'/>
<id>urn:sha1:99eef68204bc8958b918c174e37d167d9aaa11cc</id>
<content type='text'>
to driver specific files.

- window initialization is done during device attach
- CESA TDMA decoding windows values are set based on DTS,
 not copied from CPU registers
- remove unnecessary virtual mapping
- update dts file

Obtained from: Semihalf
</content>
</entry>
<entry>
<title>Add support for Marvell 88F6282.</title>
<updated>2012-07-28T21:56:24Z</updated>
<author>
<name>Hiroki Sato</name>
<email>hrs@FreeBSD.org</email>
</author>
<published>2012-07-28T21:56:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=c8953e127335cee6f7f8068c648b523bf4d0c647'/>
<id>urn:sha1:c8953e127335cee6f7f8068c648b523bf4d0c647</id>
<content type='text'>
Sponsored by:	Plat'Home, Co.,Ltd.
</content>
</entry>
<entry>
<title>Final pass at having devices use their bus parent for dma tags.  The</title>
<updated>2012-03-12T19:29:35Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2012-03-12T19:29:35Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=6ac6f295b0b2526750e093d731b1fb618561de20'/>
<id>urn:sha1:6ac6f295b0b2526750e093d731b1fb618561de20</id>
<content type='text'>
remaining drivers that haven't been converted have various problems or
complexities that will be dealt with later.  This list includes:

hptrr, hptmv, hpt27xx - device aggregation across multiple parents
drm - want to talk to the maintainer first
tsec, sec - Openfirmware devices, not sure if changes are warranted
fatm - Done except for unused testing code
usb - want to talk to the maintainer first
ce, cp, ctau, cx - Significant driver changes needed to convey parent info

There are also devices tucked into architecture subtrees that I'll leave
for the respective maintainers to deal with.
</content>
</entry>
<entry>
<title>- There's no need to overwrite the default device method with the default</title>
<updated>2011-11-22T21:28:20Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2011-11-22T21:28:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=4b7ec27007570e0ce4fe9dbb447e7afc131b487a'/>
<id>urn:sha1:4b7ec27007570e0ce4fe9dbb447e7afc131b487a</id>
<content type='text'>
  one. Interestingly, these are actually the default for quite some time
  (bus_generic_driver_added(9) since r52045 and bus_generic_print_child(9)
  since r52045) but even recently added device drivers do this unnecessarily.
  Discussed with: jhb, marcel
- While at it, use DEVMETHOD_END.
  Discussed with: jhb
- Also while at it, use __FBSDID.
</content>
</entry>
<entry>
<title>Initial version of cesa(4) driver for Marvell crypto engine and security</title>
<updated>2011-11-19T16:30:06Z</updated>
<author>
<name>Rafal Jaworowski</name>
<email>raj@FreeBSD.org</email>
</author>
<published>2011-11-19T16:30:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=8817e1bffe0623aed232e43e963cdf56a71f4816'/>
<id>urn:sha1:8817e1bffe0623aed232e43e963cdf56a71f4816</id>
<content type='text'>
accelerator.

The following algorithms and schemes are supported:
 - 3DES, AES, DES
 - MD5, SHA1

Obtained from:	Semihalf
Written by:	Piotr Ziecik
</content>
</entry>
</feed>
