summaryrefslogtreecommitdiff
path: root/meta-demoapps/recipes-connectivity/farsight
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2010-11-30 11:51:46 -0500
committerSaul Wold <Saul.Wold@intel.com>2010-12-10 22:01:38 -0800
commitaac5f5c7883595e55e35474ec08033444e13f710 (patch)
treef287e066b12b3034932669845ce027b3ceb1d77a /meta-demoapps/recipes-connectivity/farsight
parent48d00ad8d5134b5bf3215df4faca7c7fd01154eb (diff)
downloadopenembedded-core-aac5f5c7883595e55e35474ec08033444e13f710.tar.gz
openembedded-core-aac5f5c7883595e55e35474ec08033444e13f710.tar.bz2
openembedded-core-aac5f5c7883595e55e35474ec08033444e13f710.tar.xz
openembedded-core-aac5f5c7883595e55e35474ec08033444e13f710.zip
qemu: update arm timer handling
commit e388771458b4ff3ad81ab70e390b24d069647da4 in the upstream kernel factored/cleaned the SP804 timer code. This commit exposed issues in the qemu timer emulation that was dependent on the old behaviour. As a result, no kernel past 2.6.34 would boot on qemu-system-arm. The quick fix is to backport two patches from the latest qemu repositories that fix the timer handling under emulation. Long term, these will be dropped when qemu is upreved. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta-demoapps/recipes-connectivity/farsight')
0 files changed, 0 insertions, 0 deletions