summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorKevin Cernekee <cernekee@gmail.com>2010-10-16 14:22:30 -0700
committerRalf Baechle <ralf@linux-mips.org>2010-10-29 19:08:50 +0100
commit602977b0d672687909b0cb0542ede134ed6ef858 (patch)
tree8f40b3cfbf2cc32a445a69a548837521fcdfd7d6 /COPYING
parent3a9ab99e0341558e451327fbbfc39b0d3cff7e9a (diff)
downloadlinux-3.10-602977b0d672687909b0cb0542ede134ed6ef858.tar.gz
linux-3.10-602977b0d672687909b0cb0542ede134ed6ef858.tar.bz2
linux-3.10-602977b0d672687909b0cb0542ede134ed6ef858.zip
MIPS: Decouple BMIPS CPU support from bcm47xx/bcm63xx SoC code
BMIPS processor cores are used in 50+ different chipsets spread across 5+ product lines. In many cases the chipsets do not share the same peripheral register layouts, the same register blocks, the same interrupt controllers, the same memory maps, or much of anything else. But, across radically different SoCs that share nothing more than the same BMIPS CPU, a few things are still mostly constant: SMP operations Access to performance counters DMA cache coherency quirks Cache and memory bus configuration So, it makes sense to treat each BMIPS processor type as a generic "building block," rather than tying it to a specific SoC. This makes it easier to support a large number of BMIPS-based chipsets without unnecessary duplication of code, and provides the infrastructure needed to support BMIPS-proprietary features. Signed-off-by: Kevin Cernekee <cernekee@gmail.com> Cc: mbizon@freebox.fr Cc: linux-mips@linux-mips.org Cc: linux-kernel@vger.kernel.org Tested-by: Florian Fainelli <ffainelli@freebox.fr> Patchwork: https://patchwork.linux-mips.org/patch/1706/ Signed-off-by: Ralf Baechle <ralf@linux-mips.org
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions