An error occurred fetching the project authors.
- 22 Feb, 2011 1 commit
-
-
Kukjin Kim authored
This patch adds EXYNOS4 CPU support files in mach-exynos4, and basically they are moved from mach-s5pv310 so that it can support Samsung's new CPU name, EXYNOS4. The EXYNOS4 ingegrates a ARM Cortex A9 multi-core. Signed-off-by:
Kukjin Kim <kgene.kim@samsung.com>
-
- 25 Oct, 2010 1 commit
-
-
Kukjin Kim authored
This patch changes VMALLOC_END from 0xE0000000 to 0xF6000000, because some systems want to use more vmalloc()/ioremap() area and now don't use from at 0xE0000000 to 0xF6000000 (the start of Samsung SoCs' VA space) Cc: Ben Dooks <ben-linux@fluff.org> Signed-off-by:
Kukjin Kim <kgene.kim@samsung.com>
-
- 23 Aug, 2010 1 commit
-
-
Kyungmin Park authored
Silences following build warning: arch/arm/mm/init.c: In function 'mem_init': arch/arm/mm/init.c:644: warning: format '%08lx' expects type 'long unsigned int', but argument 12 has type 'unsigned int' Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Kukjin Kim <kgene.kim@samsung.com>
-
- 05 Aug, 2010 1 commit
-
-
Changhwan Youn authored
This patch adds Samsung S5PV310/S5PC210 CPU support. The S5PV310/S5PC210 integrates a ARM Cortex A9 multi-core. Signed-off-by:
Changhwan Youn <chaos.youn@samsung.com> Signed-off-by:
Jongpill Lee <boyko.lee@samsung.com> Signed-off-by:
Jiseong Oh <jiseong.oh@samsung.com> [kgene.kim@samsung.com: fix build errors] Signed-off-by:
Kukjin Kim <kgene.kim@samsung.com>
-
- 24 Feb, 2010 3 commits
-
-
Kukjin Kim authored
This patch adds support for Samsung S5PV210 CPU. This patch also adds an entry for S5PV210 cpu in plat-s5p cpu table. Signed-off-by:
Thomas Abraham <thomas.ab@samsung.com> Signed-off-by:
Kukjin Kim <kgene.kim@samsung.com> Signed-off-by:
Ben Dooks <ben-linux@fluff.org>
-
Ben Dooks authored
Move the include/mach files out of plat-s3c and into the relevant machine files. This does mean copying the files, but there is nowhere else to put them. Signed-off-by:
Ben Dooks <ben-linux@fluff.org>
-
Ben Dooks authored
Move the Kconfig entries from plat-s3c to plat-samsung and plat-s3c24xx as necessary. The S3C_BOOT entries and the DMA configuration can go to plat-samsung. The low-level UART configurations are currently S3C2XX specific and can go to plat-s3c24xx. Eliminating plat-s3c from the build process will be submitted seperately. Signed-off-by:
Ben Dooks <ben-linux@fluff.org>
-
- 15 Feb, 2010 1 commit
-
-
Fenkart/Bostandzhyan authored
Makes it consistent with VMALLOC_START Tested-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Signed-off-by:
Andreas Fenkart <andreas.fenkart@streamunlimited.com> Signed-off-by:
Russell King <rmk+kernel@arm.linux.org.uk>
-
- 15 Dec, 2008 2 commits
-
-
Ben Dooks authored
Initial architecture support for the S3C24A0 ARCH_S3C24A0. We don't yet add an kconfig entry in the main arch/arm/Kconfig file as the series is not complete, so that is left until enough support is in to be useful. Signed-off-by:
Ben Dooks <ben-linux@fluff.org>
-
Ben Dooks authored
vmalloc.h is common across all the current s3c platforms, so move it to arch/arm/plat-s3c/include/mach to be used for all the targets. Signed-off-by:
Ben Dooks <ben-linux@fluff.org>
-
- 07 Aug, 2008 1 commit
-
-
Russell King authored
This just leaves include/asm-arm/plat-* to deal with. Signed-off-by:
Russell King <rmk+kernel@arm.linux.org.uk>
-
- 09 Sep, 2006 1 commit
-
-
Ben Dooks authored
Patch from Ben Dooks Remove the last of the hangelogs from include/asm-arm/arch-s3c2410, as this information is available from the revision control system Signed-off-by:
Ben Dooks <ben-linux@fluff.org> Signed-off-by:
Russell King <rmk+kernel@arm.linux.org.uk>
-
- 03 May, 2005 1 commit
-
-
Russell King authored
VMALLOC_START and VMALLOC_OFFSET are common between all ARM machine classes. Move them into include/asm-arm/pgtable.h, but allow a machine class to override them if required. Signed-off-by:
Russell King <rmk@arm.linux.org.uk>
-
- 16 Apr, 2005 1 commit
-
-
Linus Torvalds authored
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-