John Baldwin ce4857d146 The amr(4) firmware contains a rather dubious "feature" where it ... assumes for small buffers (< 64k) that the OS driver is actually using a buffer rounded up to the next power of 2. It also assumes that the buffer is at least 4k in size. Furthermore, there is at least one known instance of megarc sending a request with a 12k buffer where the firmware writes out a 24k-ish reply. To workaround the data corruption triggered by this "feature", ensure that buffers for user commands use a minimum size of 32k, and that buffers between 32k and 64k use a 64k buffer. PR: kern/155658 Submitted by: Andreas Longwitz longwitz incore de Reviewed by: scottl MFC after: 1 week		2012-04-20 20:27:31 +00:00
..
amr_cam.c	Mark MALLOC_DEFINEs static that have no corresponding MALLOC_DECLAREs.	2011-11-07 06:44:47 +00:00
amr_disk.c
amr_linux.c	Second-to-last commit implementing Capsicum capabilities in the FreeBSD	2011-08-11 12:30:23 +00:00
amr_pci.c	Convert a number of drivers to obtaining their parent DMA tag from their	2012-03-12 08:03:51 +00:00
amr_tables.h
amr.c	The amr(4) firmware contains a rather dubious "feature" where it	2012-04-20 20:27:31 +00:00
amrio.h
amrreg.h
amrvar.h