For different wlan driver (wcn and ath6kl), it needs to use different
wpa_supplicant.conf. Symbolic link the template wpa_supplicant.conf
as the corresponding wireless module when it's detected.
CRs-Fixed: 465923
Change-Id: If7346ae4a78e83aad2a6f5e58695a60568437977
Enable the trigger of msm8226 wcnss driver during boot up. wcnss firmware
will be loaded and wcnss will be released from reset.
Change-Id: I9a38c9948271172ee5c4e3f53115859743b38727
In MR1-based releases we have expected the nv.bin file to be present
on the data partition. If it did not exist, it would be created,
either from the version on the persist partition (if it had been
created there by the manufacturing process) or from a "canned" version
from the system partition, created there by the build process. In
particular we did not update the nv.bin on the data partition if the
file already existed. This meant that if a device had an nv.bin on
the data partition, and if it's nv.bin on the persist partition was
updated by the manufacturing process, the updated nv.bin on persist
was not being used.
To avoid this issue update the logic to conform to the pre-MR1
behavior. There will only be one nv.bin on the device, and it will
exist on the persist partition.
CRs-fixed: 448163
Change-Id: Iadb74028b1b6f6640e83c73b03a85b2b38b02e95
HSIC host controller don't to be active generally.We en
able it for our device. We check if deivce is plugged a
nd disable HSIC host controller in order to save power.
Change-Id: I75257f2c54bd68294c7536e2bd8fba1cfe48cde8
Support the following semantics for nv.bin and cfg.ini:
nv.bin:
- A "template" nv.bin file will be installed in /system/etc/wifi.
- A "production" nv.bin may be present in /persist as a result of the
manufacturing process
- A symbolic link will be populated in the firmware directory which
points to the /data partition
- The file in the /data partition will be populated from the
production file in /persist if it exits, otherwise it will be
populated from the template file.
cfg.ini:
- A "template" cfg.bin file will be installed in /system/etc/wifi.
- A symbolic link will be populated in the firmware directory which
points to the /data partition
- The file in the /data partition will be populated from the template
file.
Change-Id: I87580ae43f7182b128a4af68f3ad69937d6ba5b6
The default cfg80211 module is for wcnss solution, so move this to wcnss
specific directory at first boot. This move was done in wlan driver
makeifile; however this is preventing the binary only builds to run
because cfg80211 is an open source module and cannot be packaged with
properietary module.
Change-Id: Id180953245cf7cd63ae359bbac77ccf780f5924c
During initialization the system partition needs to be
remounted as read-write in order for changes to be made
to the /system partition (e.g. creating target-specific
symlinks, etc.). Earlier this was done in the post-fs
stage where Android property service has not been
initialized. This change moves these initializations to
the early-boot stage.
Update the wifi initialization script to use command
line parameters since getprop is not yet available in
early-boot. Also fix bug in 8974 changes that breaks
8960 and other targets.
Call audio init script from wifi script rather than
directly from syspart-fixup since retrieving Android
property is not yet available.
TODO: Init sequence needs to be redone for cleanup
and boot up speed.
Change-Id: I2a7338af91df951d0a4617d4f54db123aca839e3
Remove mount and unmount file system from wifi shell script
as they are taken care in init.post_fs.sh.
Change-Id: I49b9659b8081f0cc6adfd34a307c6da76f3eb24f
Add chnages to auto detect AR6004-SDIO wlan card inserted, and link
the ath6kl wlan firmware and boarddata file to corresponding
USB and SDIO versions based on AR6K chipt type.
Set the property 'wlan.driver.ath' to indicate ATH WLAN,
and is used by application to determine the type of AR6K.
if set to 1->AR6003/5, 2->AR6004(USD & SDIO vesrion)
Change-Id: I5d63e9d7a8b82038ed351069c2e4514b00d66357
Some of the qcom services require to remount system partition with read-write
permission. But since all of them running as independent asyncronous services
so this can cause some issue.
init.post_fs.sh is responsible to call all such services syncronously and
in the end remount system partition as read-only.
Change-Id: I4c03a67df5eb429b2ede633f81135e8b5c457673
Squashed commit of the following:
commit fef7046a2ace2c5e766d1eab249f86523213d702
Author: Royston Rodrigues <roystonr@codeaurora.org>
Date: Thu Jul 12 08:42:20 2012 +0530
Bluetooth: Add permissions for smd and rfcomm device nodes.
Change-Id: Id4bbb9269635560ec71880eb340fafc5c6b85878
commit 4eab8848774920ec0ed786f57446f831b2e6a5c9
Author: Peter Krystad <pkrystad@codeaurora.org>
Date: Mon Mar 12 16:46:55 2012 -0700
Bluetooth: Remove references to amploader utility
Amploader utility was specific to 1312 chip, and functionality has been
disabled. Remove these references so the utility itself can be removed.
Change-Id: I40e842309dbd24c98e240753c53748e432583f18
CRs-fixed: 336688
Change-Id: I0474027db9bccffcf4ab42c9f652a2b5a0aaed78
Ming-yi Lin
Linux Build Service Account
Sheng Fang
Jeff Johnson
Duy Truong
Sameer Thalappil
David Ng
Santosh Sajjan
Shashank Mittal
Royston Rodrigues