Minor changes to fix compile on fresh download

The mfc_fw.bin file was not in the repo due to missing
excludes in .gitignore

Change-Id: I8430232dbf001455902b4ee5d69ffc053868ac9c
Revert "exynos4: more cleanup"

This reverts commit 79632044d88fff3fc8f4e4859975270988f2106b.

Prep for renaming mach-exynos4 back to mach-exynos for the purposes of commonality
with other trees.  (Mainline Exynos patches will never apply to this tree no matter
what it is named.)

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
Revert "exynos4: cleanup"

This reverts commit af3ed174f304d9fab6bd01a4a539300f7e991046.

Prep for renaming mach-exynos4 back to mach-exynos for the purposes of commonality
with other trees.  (Mainline Exynos patches will never apply to this tree no matter
what it is named.)

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
Revert "exynos4: path fixes"

This reverts commit 08565793efd66797eeceafdc822571a0de549b25.

Prep for renaming mach-exynos4 back to mach-exynos for the purposes of commonality
with other trees.  (Mainline Exynos patches will never apply to this tree no matter
what it is named.)

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
arm/mach-exynos(4): Rename mach-exynos4 back to mach-exynos

mach-exynos in the Samsung GT-I9100 source tree drop contained a tree
significantly ahead of the mainline kernel, and even farther ahead
of the 3.0.x Linux series, which has not seen an update to mach-exynos(4)
since July 2011.

The mach-exynos tree was improperly renamed from the source drop prior to
committing to git, causing the original rename to not show in git history.
The rename was done in an attempt to improve mainline commonality, however:
1)  Even with the rename, any mainline patches that touch mach-exynos(4) have
no chance of cleanly applying to the Exynos tree due to significant differences
in the directory contents
2)  It just doesn't matter - see above, this tree has not seen a mainline commit
since August 2011, and it is now March 2012.  The rename fragments this tree
from ones that actually will have active development on mach-exynos, compared
to mainline which has had none since 2011 on 3.0.x
3)  It causes any patches coming from other I9100 community development to
fail to apply to this source tree.

For the above reasons, the benefits of mach-exynos outweigh those of mach-exynos4
and similarly, the disadvantages of mach-exynos4 outweigh those of mach-exynos,
and the tree should be renamed.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
mach-exynos: Remove mainline cruft

This causes conflicts with the much newer mach-exynos code.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
config: Regenerate for mach-exynos4->mach-exynos rename

This also regenerates the i777 defconfig from the i9100 defconfig,
instead of from the (rather nonfunctional) u1_usa_att_defconfig

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
Merge pull request #3 from r0m30/buildfixes

Minor changes to fix compile on fresh download
Renamed galaxys2att to i777 for initramfs

Change-Id: I3e15861c74dd14103d18dc9b2999290951d80c09
Merge branch 'exynos_rename' of https://github.com/Entropy512/android_kernel_samsung_smdk4210 into Entropy512-exynos_rename

Conflicts:
	arch/arm/configs/android_i777_defconfig
galaxys2: ondemand by default
cpufreq_conservative: Change default tuning settings

Half the polling rate, but more aggressive up/down thresholds.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
cpufreq_conservative: Reduce minimum polling interval

Conservative's minimum polling interval is very long - this patch reduces
it so the user can tune it downwards, while still respecting hardware
transition_latency limits.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
config: Regenerate Note config for mach-exynos4->mach-exynos rename

Not tested...  But if the old config worked this should too.
config: Enable conservative governor
config: Disable interactive governor temporarily

The interactive governor misbehaves when it is not selected by default
in LPM and recovery modes.  This leads to a hung task timer panicing
the kernel approx. 2 minutes after boot due to kinteractiveup being hung.

Disable it for now, until it can be fixed.