summaryrefslogtreecommitdiffstats
path: root/include/hardware_legacy/gscan.h
diff options
context:
space:
mode:
authoreccopark@broadcom.com <eccopark@broadcom.com>2015-03-25 17:21:26 -0700
committereccopark@broadcom.com <eccopark@broadcom.com>2015-03-27 10:55:38 -0700
commit3fabb28c4b19ea110aee0fde881c7dc315980b16 (patch)
tree30e3ae23ca9cb189a533ba28493b7f13256c0202 /include/hardware_legacy/gscan.h
parent3e778d3b8acf9ec3ce76d32255ae2b1aec3ac7d1 (diff)
downloadhardware_libhardware_legacy-3fabb28c4b19ea110aee0fde881c7dc315980b16.zip
hardware_libhardware_legacy-3fabb28c4b19ea110aee0fde881c7dc315980b16.tar.gz
hardware_libhardware_legacy-3fabb28c4b19ea110aee0fde881c7dc315980b16.tar.bz2
net: wireless change the header of Logger
1) add the request_id in wifi_get_logger_supported_feature_set 2) Change the wifi_get_firmware_memory_dump API 1) Normally the size of firmware dump is 700KB. Thus, Driver cannot send the data in one time because of limitation of skb length. In order to send such big data from kernel Driver, we need to send data using event continuously until we send the memory dump completely. In the event handler of hal, it will allocate the big buffer to store the data. Once event handler copy the data completely, event handler will call the function callback(on_firmware_memory_dump). So, upper layer has to free the buffer after handling the buffer. Change-Id: If80b03ec8bd9349d952743e17a001c04096aac95 Signed-off-by: eccopark@broadcom.com <eccopark@broadcom.com>
Diffstat (limited to 'include/hardware_legacy/gscan.h')
0 files changed, 0 insertions, 0 deletions