dlx: update adreno from qdevenet 30 May 14 KOT49H

Change-Id: I8eeed8aec9510275aae169511f176936f3ad7302
dlx: Kang extract-files.sh / setup-makefiles.sh

.. from mondrianwifi from hlte to allow me to pull the blobs from
a local copy instead of the device.

Change-Id: Ib6223c358c76b0ebaccc8ffe2d5505e79a11710d

Conflicts:

	extract-files.sh
	setup-makefiles.sh
dlx: proprietary_files: Pull out bits I am going to update

This file is a mess.  This commit just pulls out the few
filest that I am going to update in the next commit to make
it easier to see what it changing.

Change-Id: Ifcc43658dfbd1c79507fef063d7b9e23bbf048b0
dlx: wifi: Update BCM firmware / calibration

Change-Id: I0f57ef41480463cbdd3de5a307562f70a7bc7780
dlx: Fix DRM and update to 4.4.2 blobs

Change-Id: I23cd10e201f05e4bee8d8e386f1ddf00fa36ff69
dlx: init: Set read-ahead to 512 KB

Change-Id: I632d65907803c9328f2db694ead35164c631ca24
dlx: init: Fix configuration of cpu-boost sync_freq

When a thread migrates, the cpu-boost driver adds a boost to:

* the current frequency if it is less than sync_freq
* sync_freq if the current frequency is greater than sync_freq

The idea being that you want to keep it boosted but not going
crazy.  The way this was previously configured always kept it
at the current frequency which could be needlessly burning
battery power.

Change-Id: If1074294b7c55024a5820c255bf2e81d9884d2b6
dlx: init: Configure cpu-boost's plug_boost

Using only a 1 ms boost for dlx because the dlx mpdecision is
very aggressive about bringing cores online.

The only purpose of this boost on dlx is to ensure that the core
doesn't come online at very low frequency and then take a little
time for the governor to correctly identify the load on it.

Change-Id: Ic56d375b91d35271cb593499ea172f877326a7fe
dlx: init: Tone down the cpu-boost driver

Change-Id: I8b52530d5ed7f5a3b88c4a148d235fee8881457d