Re: RFC: ti_usb-serial: userspace firmware, internal cfg. change, cleanup
Alan Cox <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Organization | Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 |
| Message-ID | <[email protected]> |
> What about specifying file-size limit on the request? I think it's a > common parameter and can be dealt in the loading helper. Also, what about The assumption is that firmware is sane and also arbitary size limits will need updating as firmware and hardware revs change. You can check the size after request_firmware returns and reject it. > making attempt to allocate usual memory first and then doing virtual > allocation? Same parameter can be used as size requesting/memory > allocating status? Very very few callers care about this. I don't think that aspect is worthwhile. You can just grab a page and use that as an intermediate case in your specific special case instance ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel