Enji Cooper ea36ade1d1 Limit RESOLUTION_MAX to INT_MAX, not UINT_MAX (all spelled out) so the ... mode value isn't always clipped to -1 when (resolution * size) == 32, which would have been the case with values => {4i,32b,32t}. This seems to have been broken in r64382. MFC after: 1 week X-MFC with: r289915 PR: 200619 Reported by: Michael Baptist Submitted by: Lars Skodje Sponsored by: EMC / Isilon Storage Division		2015-10-25 04:37:00 +00:00
..
attrib.c	Add support for reading MAM attributes to camcontrol(8) and libcam(3).	2015-06-09 21:39:38 +00:00
camcontrol.8	Revamp camcontrol(8) fwdownload support and add the opcodes subcommand.	2015-08-20 16:07:51 +00:00
camcontrol.c	Revamp camcontrol(8) fwdownload support and add the opcodes subcommand.	2015-08-20 16:07:51 +00:00
camcontrol.h	Revamp camcontrol(8) fwdownload support and add the opcodes subcommand.	2015-08-20 16:07:51 +00:00
fwdownload.c	Revamp camcontrol(8) fwdownload support and add the opcodes subcommand.	2015-08-20 16:07:51 +00:00
Makefile	Add support for reading MAM attributes to camcontrol(8) and libcam(3).	2015-06-09 21:39:38 +00:00
Makefile.depend	Add META_MODE support.	2015-06-13 19:20:56 +00:00
modeedit.c	Limit RESOLUTION_MAX to INT_MAX, not UINT_MAX (all spelled out) so the	2015-10-25 04:37:00 +00:00
persist.c	Remove unused variables reported by clang.	2015-06-02 09:05:45 +00:00
progress.c	Revamp camcontrol(8) fwdownload support and add the opcodes subcommand.	2015-08-20 16:07:51 +00:00
progress.h	Add progress.c and progress.h, missed in the previous commit to camcontrol.	2012-06-20 04:11:34 +00:00
util.c	Fix build.	2011-11-25 07:11:02 +00:00