* [PATCHv1 000/211] unicore32 architecture support
@ 2010-12-09 9:28 ` Guan Xuetao
0 siblings, 0 replies; 15+ messages in thread
From: Guan Xuetao @ 2010-12-09 9:28 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linux-arch, linux-kernel
From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
These patches add support for UniCore-32 ISA in linux kernel.
UniCore ISA is defined and developed by Micro-Processor R&D Center of
Peking University, and over the years, the CPUs and SoCs using UniCore ISA
have been successfully applied in a variety of products in China.
---
arch/unicore32/.gitignore | 68 +
arch/unicore32/Kconfig | 275 ++++
arch/unicore32/Kconfig.debug | 86 +
arch/unicore32/Makefile | 151 ++
arch/unicore32/boot/Makefile | 47 +
arch/unicore32/boot/compressed/Makefile | 71 +
arch/unicore32/boot/compressed/head.S | 203 +++
arch/unicore32/boot/compressed/misc.c | 143 ++
arch/unicore32/boot/compressed/piggy.S.in | 6 +
arch/unicore32/boot/compressed/vmlinux.lds.in | 61 +
arch/unicore32/configs/debug_defconfig | 208 +++
arch/unicore32/configs/nb0916_defconfig | 203 +++
arch/unicore32/include/asm/Kbuild | 4 +
arch/unicore32/include/asm/assembler.h | 193 +++
arch/unicore32/include/asm/auxvec.h | 4 +
arch/unicore32/include/asm/bitops.h | 47 +
arch/unicore32/include/asm/byteorder.h | 24 +
arch/unicore32/include/asm/cache.h | 27 +
arch/unicore32/include/asm/cacheflush.h | 212 +++
arch/unicore32/include/asm/checksum.h | 142 ++
arch/unicore32/include/asm/cpu-single.h | 45 +
arch/unicore32/include/asm/cputype.h | 33 +
arch/unicore32/include/asm/delay.h | 52 +
arch/unicore32/include/asm/div64.h | 230 +++
arch/unicore32/include/asm/dma-mapping.h | 298 ++++
arch/unicore32/include/asm/dma.h | 23 +
arch/unicore32/include/asm/elf.h | 95 ++
arch/unicore32/include/asm/fpstate.h | 41 +
arch/unicore32/include/asm/ftrace.h | 4 +
arch/unicore32/include/asm/futex.h | 131 ++
arch/unicore32/include/asm/gpio.h | 103 ++
arch/unicore32/include/asm/hwcap.h | 32 +
arch/unicore32/include/asm/io.h | 83 +
arch/unicore32/include/asm/irq.h | 107 ++
arch/unicore32/include/asm/irqflags.h | 103 ++
arch/unicore32/include/asm/linkage.h | 22 +
arch/unicore32/include/asm/mach/PKUnity.h | 104 ++
arch/unicore32/include/asm/mach/bitfield.h | 24 +
arch/unicore32/include/asm/mach/debug-macro.S | 138 ++
arch/unicore32/include/asm/mach/dma.h | 41 +
arch/unicore32/include/asm/mach/hardware.h | 45 +
arch/unicore32/include/asm/mach/map.h | 20 +
arch/unicore32/include/asm/mach/memory.h | 51 +
arch/unicore32/include/asm/mach/ocd.h | 36 +
arch/unicore32/include/asm/mach/pm.h | 32 +
arch/unicore32/include/asm/mach/regs-ac97.h | 26 +
arch/unicore32/include/asm/mach/regs-dmac.h | 41 +
arch/unicore32/include/asm/mach/regs-gpio.h | 45 +
arch/unicore32/include/asm/mach/regs-i2c.h | 38 +
arch/unicore32/include/asm/mach/regs-intc.h | 10 +
arch/unicore32/include/asm/mach/regs-nand.h | 28 +
arch/unicore32/include/asm/mach/regs-ost.h | 29 +
arch/unicore32/include/asm/mach/regs-pci.h | 81 +
arch/unicore32/include/asm/mach/regs-pm.h | 63 +
arch/unicore32/include/asm/mach/regs-ps2.h | 8 +
arch/unicore32/include/asm/mach/regs-resetc.h | 13 +
arch/unicore32/include/asm/mach/regs-rtc.h | 13 +
arch/unicore32/include/asm/mach/regs-sdc.h | 57 +
arch/unicore32/include/asm/mach/regs-spi.h | 32 +
arch/unicore32/include/asm/mach/regs-uart.h | 3 +
arch/unicore32/include/asm/mach/regs-umal.h | 133 ++
arch/unicore32/include/asm/mach/regs-unigfx.h | 86 +
arch/unicore32/include/asm/mach/uncompress.h | 34 +
arch/unicore32/include/asm/memblock.h | 20 +
arch/unicore32/include/asm/memory.h | 123 ++
arch/unicore32/include/asm/mmu.h | 17 +
arch/unicore32/include/asm/mmu_context.h | 87 ++
arch/unicore32/include/asm/mutex.h | 20 +
arch/unicore32/include/asm/page.h | 82 +
arch/unicore32/include/asm/pci.h | 46 +
arch/unicore32/include/asm/pgalloc.h | 114 ++
arch/unicore32/include/asm/pgtable-hwdef.h | 54 +
arch/unicore32/include/asm/pgtable.h | 333 ++++
arch/unicore32/include/asm/processor.h | 92 ++
arch/unicore32/include/asm/ptrace.h | 188 +++
arch/unicore32/include/asm/setup.h | 51 +
arch/unicore32/include/asm/sigcontext.h | 61 +
arch/unicore32/include/asm/sizes.h | 47 +
arch/unicore32/include/asm/stacktrace.h | 31 +
arch/unicore32/include/asm/stat.h | 71 +
arch/unicore32/include/asm/string.h | 52 +
arch/unicore32/include/asm/suspend.h | 30 +
arch/unicore32/include/asm/swab.h | 28 +
arch/unicore32/include/asm/system.h | 174 +++
arch/unicore32/include/asm/thread_info.h | 152 ++
arch/unicore32/include/asm/timex.h | 34 +
arch/unicore32/include/asm/tlb.h | 98 ++
arch/unicore32/include/asm/tlbflush.h | 192 +++
arch/unicore32/include/asm/traps.h | 32 +
arch/unicore32/include/asm/uaccess.h | 405 +++++
arch/unicore32/include/asm/uc-f64.h | 60 +
arch/unicore32/include/asm/unistd.h | 450 ++++++
arch/unicore32/include/asm/user.h | 85 +
arch/unicore32/kernel/Makefile | 36 +
arch/unicore32/kernel/asm-offsets.c | 110 ++
arch/unicore32/kernel/calls.S | 390 +++++
arch/unicore32/kernel/clock.c | 398 +++++
arch/unicore32/kernel/cpu-ucv2.c | 100 ++
arch/unicore32/kernel/debug.S | 85 +
arch/unicore32/kernel/early_printk.c | 59 +
arch/unicore32/kernel/elf.c | 38 +
arch/unicore32/kernel/entry-common.S | 339 ++++
arch/unicore32/kernel/entry-header.S | 144 ++
arch/unicore32/kernel/entry-unicore.S | 627 ++++++++
arch/unicore32/kernel/head.S | 261 ++++
arch/unicore32/kernel/hibernate.c | 167 ++
arch/unicore32/kernel/hibernate.h | 9 +
arch/unicore32/kernel/hibernate_asm.S | 124 ++
arch/unicore32/kernel/init_task.c | 44 +
arch/unicore32/kernel/irq.c | 434 ++++++
arch/unicore32/kernel/ksyms.c | 87 ++
arch/unicore32/kernel/module.c | 152 ++
arch/unicore32/kernel/pci.c | 395 +++++
arch/unicore32/kernel/pm.c | 130 ++
arch/unicore32/kernel/process.c | 399 +++++
arch/unicore32/kernel/ptrace.c | 577 +++++++
arch/unicore32/kernel/ptrace.h | 53 +
arch/unicore32/kernel/puv3-core.c | 266 ++++
arch/unicore32/kernel/puv3-nb0916.c | 180 +++
arch/unicore32/kernel/puv3-smw0919.c | 119 ++
arch/unicore32/kernel/setup.c | 369 +++++
arch/unicore32/kernel/setup.h | 27 +
arch/unicore32/kernel/signal.c | 569 +++++++
arch/unicore32/kernel/signal.h | 16 +
arch/unicore32/kernel/sleep.S | 210 +++
arch/unicore32/kernel/stacktrace.c | 131 ++
arch/unicore32/kernel/sys_unicore.c | 131 ++
arch/unicore32/kernel/time.c | 159 ++
arch/unicore32/kernel/traps.c | 514 +++++++
arch/unicore32/kernel/vmlinux.lds.S | 121 ++
arch/unicore32/lib/Makefile | 16 +
arch/unicore32/lib/backtrace.S | 163 ++
arch/unicore32/lib/clear_user.S | 59 +
arch/unicore32/lib/copy_from_user.S | 107 ++
arch/unicore32/lib/copy_page.S | 39 +
arch/unicore32/lib/copy_template.S | 214 +++
arch/unicore32/lib/copy_to_user.S | 97 ++
arch/unicore32/lib/csumipv6.S | 36 +
arch/unicore32/lib/csumpartial.S | 126 ++
arch/unicore32/lib/csumpartialcopy.S | 61 +
arch/unicore32/lib/csumpartialcopygeneric.S | 335 ++++
arch/unicore32/lib/csumpartialcopyuser.S | 92 ++
arch/unicore32/lib/delay.S | 51 +
arch/unicore32/lib/div64.S | 152 ++
arch/unicore32/lib/findbit.S | 98 ++
arch/unicore32/lib/getuser.S | 65 +
arch/unicore32/lib/io-readsb.S | 130 ++
arch/unicore32/lib/io-readsl.S | 83 +
arch/unicore32/lib/io-readsw.S | 110 ++
arch/unicore32/lib/io-writesb.S | 90 ++
arch/unicore32/lib/io-writesl.S | 69 +
arch/unicore32/lib/io-writesw.S | 87 ++
arch/unicore32/lib/putuser.S | 73 +
arch/unicore32/lib/sha1.S | 200 +++
arch/unicore32/lib/strncpy_from_user.S | 45 +
arch/unicore32/lib/strnlen_user.S | 42 +
arch/unicore32/mm/Kconfig | 43 +
arch/unicore32/mm/Makefile | 14 +
arch/unicore32/mm/alignment.c | 563 +++++++
arch/unicore32/mm/cache-ucv2.S | 236 +++
arch/unicore32/mm/dma-mapping.c | 301 ++++
arch/unicore32/mm/extable.c | 24 +
arch/unicore32/mm/fault-unicore.c | 65 +
arch/unicore32/mm/fault.c | 524 +++++++
arch/unicore32/mm/fault.h | 14 +
arch/unicore32/mm/flush.c | 98 ++
arch/unicore32/mm/init.c | 527 +++++++
arch/unicore32/mm/iomap.c | 56 +
arch/unicore32/mm/ioremap.c | 261 ++++
arch/unicore32/mm/mm.h | 39 +
arch/unicore32/mm/mmu.c | 494 ++++++
arch/unicore32/mm/pgd.c | 102 ++
arch/unicore32/mm/proc-macros.S | 150 ++
arch/unicore32/mm/proc-syms.c | 28 +
arch/unicore32/mm/proc-ucv2.S | 134 ++
arch/unicore32/mm/tlb-ucv2.S | 89 ++
arch/unicore32/uc-f64/Makefile | 13 +
arch/unicore32/uc-f64/entry.S | 32 +
arch/unicore32/uc-f64/f64_double_cmp.h | 245 +++
arch/unicore32/uc-f64/f64_single_cmp.h | 245 +++
arch/unicore32/uc-f64/f64double.c | 750 +++++++++
arch/unicore32/uc-f64/f64hw.S | 154 ++
arch/unicore32/uc-f64/f64instr.h | 101 ++
arch/unicore32/uc-f64/f64module.c | 181 +++
arch/unicore32/uc-f64/f64single.c | 763 +++++++++
arch/unicore32/uc-f64/f64sint.c | 94 ++
arch/unicore32/uc-f64/uc-f64.h | 340 ++++
drivers/input/keyboard/Kconfig | 11 +
drivers/input/keyboard/atkbd.c | 4 +
drivers/input/mouse/psmouse-base.c | 41 +
drivers/input/serio/i8042.h | 2 +
drivers/pci/Makefile | 1 +
drivers/staging/puv3/Kconfig | 142 ++
drivers/staging/puv3/Makefile | 27 +
drivers/staging/puv3/i8042-ucio.h | 96 ++
drivers/staging/puv3/nb0916-atkbd.h | 27 +
drivers/staging/puv3/puv3_ac97.c | 383 +++++
drivers/staging/puv3/puv3_dma.c | 187 +++
drivers/staging/puv3/puv3_gpio.c | 129 ++
drivers/staging/puv3/puv3_i2c.c | 325 ++++
drivers/staging/puv3/puv3_pcm.c | 448 ++++++
drivers/staging/puv3/puv3_pcm.h | 33 +
drivers/staging/puv3/puv3_pwm.c | 271 ++++
drivers/staging/puv3/puv3_rtc.c | 388 +++++
drivers/staging/puv3/puv3_umal.c | 2053
+++++++++++++++++++++++++
drivers/staging/puv3/puv3_unifb.c | 972 ++++++++++++
firmware/Makefile | 2 +-
include/linux/fb.h | 2 +
include/linux/serial_core.h | 3 +
init/Kconfig | 2 +-
lib/Kconfig.debug | 2 +-
211 files changed, 30875 insertions(+), 3 deletions(-)
Guan Xuetao
^ permalink raw reply [flat|nested] 15+ messages in thread
* [PATCHv1 000/211] unicore32 architecture support
@ 2010-12-09 9:28 ` Guan Xuetao
0 siblings, 0 replies; 15+ messages in thread
From: Guan Xuetao @ 2010-12-09 9:28 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linux-arch, linux-kernel
From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
These patches add support for UniCore-32 ISA in linux kernel.
UniCore ISA is defined and developed by Micro-Processor R&D Center of
Peking University, and over the years, the CPUs and SoCs using UniCore ISA
have been successfully applied in a variety of products in China.
---
arch/unicore32/.gitignore | 68 +
arch/unicore32/Kconfig | 275 ++++
arch/unicore32/Kconfig.debug | 86 +
arch/unicore32/Makefile | 151 ++
arch/unicore32/boot/Makefile | 47 +
arch/unicore32/boot/compressed/Makefile | 71 +
arch/unicore32/boot/compressed/head.S | 203 +++
arch/unicore32/boot/compressed/misc.c | 143 ++
arch/unicore32/boot/compressed/piggy.S.in | 6 +
arch/unicore32/boot/compressed/vmlinux.lds.in | 61 +
arch/unicore32/configs/debug_defconfig | 208 +++
arch/unicore32/configs/nb0916_defconfig | 203 +++
arch/unicore32/include/asm/Kbuild | 4 +
arch/unicore32/include/asm/assembler.h | 193 +++
arch/unicore32/include/asm/auxvec.h | 4 +
arch/unicore32/include/asm/bitops.h | 47 +
arch/unicore32/include/asm/byteorder.h | 24 +
arch/unicore32/include/asm/cache.h | 27 +
arch/unicore32/include/asm/cacheflush.h | 212 +++
arch/unicore32/include/asm/checksum.h | 142 ++
arch/unicore32/include/asm/cpu-single.h | 45 +
arch/unicore32/include/asm/cputype.h | 33 +
arch/unicore32/include/asm/delay.h | 52 +
arch/unicore32/include/asm/div64.h | 230 +++
arch/unicore32/include/asm/dma-mapping.h | 298 ++++
arch/unicore32/include/asm/dma.h | 23 +
arch/unicore32/include/asm/elf.h | 95 ++
arch/unicore32/include/asm/fpstate.h | 41 +
arch/unicore32/include/asm/ftrace.h | 4 +
arch/unicore32/include/asm/futex.h | 131 ++
arch/unicore32/include/asm/gpio.h | 103 ++
arch/unicore32/include/asm/hwcap.h | 32 +
arch/unicore32/include/asm/io.h | 83 +
arch/unicore32/include/asm/irq.h | 107 ++
arch/unicore32/include/asm/irqflags.h | 103 ++
arch/unicore32/include/asm/linkage.h | 22 +
arch/unicore32/include/asm/mach/PKUnity.h | 104 ++
arch/unicore32/include/asm/mach/bitfield.h | 24 +
arch/unicore32/include/asm/mach/debug-macro.S | 138 ++
arch/unicore32/include/asm/mach/dma.h | 41 +
arch/unicore32/include/asm/mach/hardware.h | 45 +
arch/unicore32/include/asm/mach/map.h | 20 +
arch/unicore32/include/asm/mach/memory.h | 51 +
arch/unicore32/include/asm/mach/ocd.h | 36 +
arch/unicore32/include/asm/mach/pm.h | 32 +
arch/unicore32/include/asm/mach/regs-ac97.h | 26 +
arch/unicore32/include/asm/mach/regs-dmac.h | 41 +
arch/unicore32/include/asm/mach/regs-gpio.h | 45 +
arch/unicore32/include/asm/mach/regs-i2c.h | 38 +
arch/unicore32/include/asm/mach/regs-intc.h | 10 +
arch/unicore32/include/asm/mach/regs-nand.h | 28 +
arch/unicore32/include/asm/mach/regs-ost.h | 29 +
arch/unicore32/include/asm/mach/regs-pci.h | 81 +
arch/unicore32/include/asm/mach/regs-pm.h | 63 +
arch/unicore32/include/asm/mach/regs-ps2.h | 8 +
arch/unicore32/include/asm/mach/regs-resetc.h | 13 +
arch/unicore32/include/asm/mach/regs-rtc.h | 13 +
arch/unicore32/include/asm/mach/regs-sdc.h | 57 +
arch/unicore32/include/asm/mach/regs-spi.h | 32 +
arch/unicore32/include/asm/mach/regs-uart.h | 3 +
arch/unicore32/include/asm/mach/regs-umal.h | 133 ++
arch/unicore32/include/asm/mach/regs-unigfx.h | 86 +
arch/unicore32/include/asm/mach/uncompress.h | 34 +
arch/unicore32/include/asm/memblock.h | 20 +
arch/unicore32/include/asm/memory.h | 123 ++
arch/unicore32/include/asm/mmu.h | 17 +
arch/unicore32/include/asm/mmu_context.h | 87 ++
arch/unicore32/include/asm/mutex.h | 20 +
arch/unicore32/include/asm/page.h | 82 +
arch/unicore32/include/asm/pci.h | 46 +
arch/unicore32/include/asm/pgalloc.h | 114 ++
arch/unicore32/include/asm/pgtable-hwdef.h | 54 +
arch/unicore32/include/asm/pgtable.h | 333 ++++
arch/unicore32/include/asm/processor.h | 92 ++
arch/unicore32/include/asm/ptrace.h | 188 +++
arch/unicore32/include/asm/setup.h | 51 +
arch/unicore32/include/asm/sigcontext.h | 61 +
arch/unicore32/include/asm/sizes.h | 47 +
arch/unicore32/include/asm/stacktrace.h | 31 +
arch/unicore32/include/asm/stat.h | 71 +
arch/unicore32/include/asm/string.h | 52 +
arch/unicore32/include/asm/suspend.h | 30 +
arch/unicore32/include/asm/swab.h | 28 +
arch/unicore32/include/asm/system.h | 174 +++
arch/unicore32/include/asm/thread_info.h | 152 ++
arch/unicore32/include/asm/timex.h | 34 +
arch/unicore32/include/asm/tlb.h | 98 ++
arch/unicore32/include/asm/tlbflush.h | 192 +++
arch/unicore32/include/asm/traps.h | 32 +
arch/unicore32/include/asm/uaccess.h | 405 +++++
arch/unicore32/include/asm/uc-f64.h | 60 +
arch/unicore32/include/asm/unistd.h | 450 ++++++
arch/unicore32/include/asm/user.h | 85 +
arch/unicore32/kernel/Makefile | 36 +
arch/unicore32/kernel/asm-offsets.c | 110 ++
arch/unicore32/kernel/calls.S | 390 +++++
arch/unicore32/kernel/clock.c | 398 +++++
arch/unicore32/kernel/cpu-ucv2.c | 100 ++
arch/unicore32/kernel/debug.S | 85 +
arch/unicore32/kernel/early_printk.c | 59 +
arch/unicore32/kernel/elf.c | 38 +
arch/unicore32/kernel/entry-common.S | 339 ++++
arch/unicore32/kernel/entry-header.S | 144 ++
arch/unicore32/kernel/entry-unicore.S | 627 ++++++++
arch/unicore32/kernel/head.S | 261 ++++
arch/unicore32/kernel/hibernate.c | 167 ++
arch/unicore32/kernel/hibernate.h | 9 +
arch/unicore32/kernel/hibernate_asm.S | 124 ++
arch/unicore32/kernel/init_task.c | 44 +
arch/unicore32/kernel/irq.c | 434 ++++++
arch/unicore32/kernel/ksyms.c | 87 ++
arch/unicore32/kernel/module.c | 152 ++
arch/unicore32/kernel/pci.c | 395 +++++
arch/unicore32/kernel/pm.c | 130 ++
arch/unicore32/kernel/process.c | 399 +++++
arch/unicore32/kernel/ptrace.c | 577 +++++++
arch/unicore32/kernel/ptrace.h | 53 +
arch/unicore32/kernel/puv3-core.c | 266 ++++
arch/unicore32/kernel/puv3-nb0916.c | 180 +++
arch/unicore32/kernel/puv3-smw0919.c | 119 ++
arch/unicore32/kernel/setup.c | 369 +++++
arch/unicore32/kernel/setup.h | 27 +
arch/unicore32/kernel/signal.c | 569 +++++++
arch/unicore32/kernel/signal.h | 16 +
arch/unicore32/kernel/sleep.S | 210 +++
arch/unicore32/kernel/stacktrace.c | 131 ++
arch/unicore32/kernel/sys_unicore.c | 131 ++
arch/unicore32/kernel/time.c | 159 ++
arch/unicore32/kernel/traps.c | 514 +++++++
arch/unicore32/kernel/vmlinux.lds.S | 121 ++
arch/unicore32/lib/Makefile | 16 +
arch/unicore32/lib/backtrace.S | 163 ++
arch/unicore32/lib/clear_user.S | 59 +
arch/unicore32/lib/copy_from_user.S | 107 ++
arch/unicore32/lib/copy_page.S | 39 +
arch/unicore32/lib/copy_template.S | 214 +++
arch/unicore32/lib/copy_to_user.S | 97 ++
arch/unicore32/lib/csumipv6.S | 36 +
arch/unicore32/lib/csumpartial.S | 126 ++
arch/unicore32/lib/csumpartialcopy.S | 61 +
arch/unicore32/lib/csumpartialcopygeneric.S | 335 ++++
arch/unicore32/lib/csumpartialcopyuser.S | 92 ++
arch/unicore32/lib/delay.S | 51 +
arch/unicore32/lib/div64.S | 152 ++
arch/unicore32/lib/findbit.S | 98 ++
arch/unicore32/lib/getuser.S | 65 +
arch/unicore32/lib/io-readsb.S | 130 ++
arch/unicore32/lib/io-readsl.S | 83 +
arch/unicore32/lib/io-readsw.S | 110 ++
arch/unicore32/lib/io-writesb.S | 90 ++
arch/unicore32/lib/io-writesl.S | 69 +
arch/unicore32/lib/io-writesw.S | 87 ++
arch/unicore32/lib/putuser.S | 73 +
arch/unicore32/lib/sha1.S | 200 +++
arch/unicore32/lib/strncpy_from_user.S | 45 +
arch/unicore32/lib/strnlen_user.S | 42 +
arch/unicore32/mm/Kconfig | 43 +
arch/unicore32/mm/Makefile | 14 +
arch/unicore32/mm/alignment.c | 563 +++++++
arch/unicore32/mm/cache-ucv2.S | 236 +++
arch/unicore32/mm/dma-mapping.c | 301 ++++
arch/unicore32/mm/extable.c | 24 +
arch/unicore32/mm/fault-unicore.c | 65 +
arch/unicore32/mm/fault.c | 524 +++++++
arch/unicore32/mm/fault.h | 14 +
arch/unicore32/mm/flush.c | 98 ++
arch/unicore32/mm/init.c | 527 +++++++
arch/unicore32/mm/iomap.c | 56 +
arch/unicore32/mm/ioremap.c | 261 ++++
arch/unicore32/mm/mm.h | 39 +
arch/unicore32/mm/mmu.c | 494 ++++++
arch/unicore32/mm/pgd.c | 102 ++
arch/unicore32/mm/proc-macros.S | 150 ++
arch/unicore32/mm/proc-syms.c | 28 +
arch/unicore32/mm/proc-ucv2.S | 134 ++
arch/unicore32/mm/tlb-ucv2.S | 89 ++
arch/unicore32/uc-f64/Makefile | 13 +
arch/unicore32/uc-f64/entry.S | 32 +
arch/unicore32/uc-f64/f64_double_cmp.h | 245 +++
arch/unicore32/uc-f64/f64_single_cmp.h | 245 +++
arch/unicore32/uc-f64/f64double.c | 750 +++++++++
arch/unicore32/uc-f64/f64hw.S | 154 ++
arch/unicore32/uc-f64/f64instr.h | 101 ++
arch/unicore32/uc-f64/f64module.c | 181 +++
arch/unicore32/uc-f64/f64single.c | 763 +++++++++
arch/unicore32/uc-f64/f64sint.c | 94 ++
arch/unicore32/uc-f64/uc-f64.h | 340 ++++
drivers/input/keyboard/Kconfig | 11 +
drivers/input/keyboard/atkbd.c | 4 +
drivers/input/mouse/psmouse-base.c | 41 +
drivers/input/serio/i8042.h | 2 +
drivers/pci/Makefile | 1 +
drivers/staging/puv3/Kconfig | 142 ++
drivers/staging/puv3/Makefile | 27 +
drivers/staging/puv3/i8042-ucio.h | 96 ++
drivers/staging/puv3/nb0916-atkbd.h | 27 +
drivers/staging/puv3/puv3_ac97.c | 383 +++++
drivers/staging/puv3/puv3_dma.c | 187 +++
drivers/staging/puv3/puv3_gpio.c | 129 ++
drivers/staging/puv3/puv3_i2c.c | 325 ++++
drivers/staging/puv3/puv3_pcm.c | 448 ++++++
drivers/staging/puv3/puv3_pcm.h | 33 +
drivers/staging/puv3/puv3_pwm.c | 271 ++++
drivers/staging/puv3/puv3_rtc.c | 388 +++++
drivers/staging/puv3/puv3_umal.c | 2053
+++++++++++++++++++++++++
drivers/staging/puv3/puv3_unifb.c | 972 ++++++++++++
firmware/Makefile | 2 +-
include/linux/fb.h | 2 +
include/linux/serial_core.h | 3 +
init/Kconfig | 2 +-
lib/Kconfig.debug | 2 +-
211 files changed, 30875 insertions(+), 3 deletions(-)
Guan Xuetao
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 9:28 ` Guan Xuetao
(?)
@ 2010-12-09 9:50 ` Tejun Heo
2010-12-09 13:49 ` Thomas Gleixner
-1 siblings, 1 reply; 15+ messages in thread
From: Tejun Heo @ 2010-12-09 9:50 UTC (permalink / raw)
To: Guan Xuetao; +Cc: Arnd Bergmann, linux-arch, linux-kernel
Hello,
On 12/09/2010 10:28 AM, Guan Xuetao wrote:
> From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
>
> These patches add support for UniCore-32 ISA in linux kernel.
> UniCore ISA is defined and developed by Micro-Processor R&D Center of
> Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> have been successfully applied in a variety of products in China.
* Patches should be split according to logical steps of changes, not
per-file.
* Patches should be bisectable. IOW, after applying upto any patch in
the series, the tree should be buildable and working.
* When posting a patch series, especially one as large as 211, please
make the mails for the actual patches replies to the head message.
Don't post it as 212 separate messages or replies to the immediate
previous patch.
So, in short, if you're adding a whole new arch, just post it as a
single patch or a series of several patches if it requires changes
outside of the specific arch subtree.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 9:50 ` Tejun Heo
@ 2010-12-09 13:49 ` Thomas Gleixner
2010-12-09 14:05 ` Tejun Heo
` (2 more replies)
0 siblings, 3 replies; 15+ messages in thread
From: Thomas Gleixner @ 2010-12-09 13:49 UTC (permalink / raw)
To: Tejun Heo; +Cc: Guan Xuetao, Arnd Bergmann, linux-arch, linux-kernel
B1;2401;0cOn Thu, 9 Dec 2010, Tejun Heo wrote:
> Hello,
>
> On 12/09/2010 10:28 AM, Guan Xuetao wrote:
> > From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> >
> > These patches add support for UniCore-32 ISA in linux kernel.
> > UniCore ISA is defined and developed by Micro-Processor R&D Center of
> > Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> > have been successfully applied in a variety of products in China.
>
> * Patches should be split according to logical steps of changes, not
> per-file.
>
> * Patches should be bisectable. IOW, after applying upto any patch in
> the series, the tree should be buildable and working.
That does not work for a new architecture. There is nothing to bisect.
> * When posting a patch series, especially one as large as 211, please
> make the mails for the actual patches replies to the head message.
> Don't post it as 212 separate messages or replies to the immediate
> previous patch.
>
> So, in short, if you're adding a whole new arch, just post it as a
> single patch or a series of several patches if it requires changes
> outside of the specific arch subtree.
Crap. a single patch is a major PITA for review. It's even worse than
211 per file patches.
It's ok to have several patches ordered by topics
- generic header stuff
- processor and system headers
- low level entry and setup code
- process/thread related code
- mm related code
- timers
- interrupts
- ptrace
- signals
- fault handling
- misc
- build system, main makefile, Kconfig
That makes it actually feasible to review.
Thanks,
tglx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 13:49 ` Thomas Gleixner
@ 2010-12-09 14:05 ` Tejun Heo
2010-12-09 14:18 ` Thomas Gleixner
2010-12-10 8:56 ` Guan Xuetao
2010-12-10 12:16 ` Arnd Bergmann
2 siblings, 1 reply; 15+ messages in thread
From: Tejun Heo @ 2010-12-09 14:05 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: Guan Xuetao, Arnd Bergmann, linux-arch, linux-kernel
On 12/09/2010 02:49 PM, Thomas Gleixner wrote:
>> * Patches should be split according to logical steps of changes, not
>> per-file.
>>
>> * Patches should be bisectable. IOW, after applying upto any patch in
>> the series, the tree should be buildable and working.
>
> That does not work for a new architecture. There is nothing to bisect.
Sure, but at least it shouldn't introduce build scripts first which
wouldn't work at all.
>> * When posting a patch series, especially one as large as 211, please
>> make the mails for the actual patches replies to the head message.
>> Don't post it as 212 separate messages or replies to the immediate
>> previous patch.
>>
>> So, in short, if you're adding a whole new arch, just post it as a
>> single patch or a series of several patches if it requires changes
>> outside of the specific arch subtree.
>
> Crap. a single patch is a major PITA for review. It's even worse than
> 211 per file patches.
Cut the crap. A single patch may not be perfect for reviewing but
archs are often merged as a single giant patch as bisection is
meaningless anyway.
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 14:05 ` Tejun Heo
@ 2010-12-09 14:18 ` Thomas Gleixner
2010-12-09 14:27 ` Tejun Heo
0 siblings, 1 reply; 15+ messages in thread
From: Thomas Gleixner @ 2010-12-09 14:18 UTC (permalink / raw)
To: Tejun Heo; +Cc: Guan Xuetao, Arnd Bergmann, linux-arch, linux-kernel
On Thu, 9 Dec 2010, Tejun Heo wrote:
> On 12/09/2010 02:49 PM, Thomas Gleixner wrote:
> >> * Patches should be split according to logical steps of changes, not
> >> per-file.
> >>
> >> * Patches should be bisectable. IOW, after applying upto any patch in
> >> the series, the tree should be buildable and working.
> >
> > That does not work for a new architecture. There is nothing to bisect.
>
> Sure, but at least it shouldn't introduce build scripts first which
> wouldn't work at all.
>
> >> * When posting a patch series, especially one as large as 211, please
> >> make the mails for the actual patches replies to the head message.
> >> Don't post it as 212 separate messages or replies to the immediate
> >> previous patch.
> >>
> >> So, in short, if you're adding a whole new arch, just post it as a
> >> single patch or a series of several patches if it requires changes
> >> outside of the specific arch subtree.
> >
> > Crap. a single patch is a major PITA for review. It's even worse than
> > 211 per file patches.
>
> Cut the crap. A single patch may not be perfect for reviewing but
> archs are often merged as a single giant patch as bisection is
> meaningless anyway.
It's not a question of merging. It's a question of reviewing and I've
done quite a bunch of reviews on new archs, so I know what I'm talking
about. Reviewing a single patch with everything and the world included
is just not workable.
Thanks,
tglx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 14:18 ` Thomas Gleixner
@ 2010-12-09 14:27 ` Tejun Heo
0 siblings, 0 replies; 15+ messages in thread
From: Tejun Heo @ 2010-12-09 14:27 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: Guan Xuetao, Arnd Bergmann, linux-arch, linux-kernel
On 12/09/2010 03:18 PM, Thomas Gleixner wrote:
> It's not a question of merging. It's a question of reviewing and I've
> done quite a bunch of reviews on new archs, so I know what I'm talking
> about. Reviewing a single patch with everything and the world included
> is just not workable.
Sure, I agree the per-topic patch series would be much better for
reviewing. Then, just make _that_ point. Don't go to the opposite
extreme and claim unthreaded per-file 200+ patches in whatever order
are better as that's painful for everyone on the mailing list.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 9:28 ` Guan Xuetao
(?)
(?)
@ 2010-12-09 17:50 ` James Bottomley
[not found] ` <028701cb9919$df3b7900$9db26b00$@mprc.pku.edu.cn>
-1 siblings, 1 reply; 15+ messages in thread
From: James Bottomley @ 2010-12-09 17:50 UTC (permalink / raw)
To: Guan Xuetao; +Cc: Arnd Bergmann, linux-arch, linux-kernel
On Thu, 2010-12-09 at 17:28 +0800, Guan Xuetao wrote:
> From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
>
> These patches add support for UniCore-32 ISA in linux kernel.
> UniCore ISA is defined and developed by Micro-Processor R&D Center of
> Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> have been successfully applied in a variety of products in China.
Could we at least have these 212 emails threaded at least below this
email ... for those of us who may be tempted to skip a full review with
a thread delete?
Thanks,
James
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 13:49 ` Thomas Gleixner
@ 2010-12-10 8:56 ` Guan Xuetao
2010-12-10 8:56 ` Guan Xuetao
2010-12-10 12:16 ` Arnd Bergmann
2 siblings, 0 replies; 15+ messages in thread
From: Guan Xuetao @ 2010-12-10 8:56 UTC (permalink / raw)
To: 'Thomas Gleixner', 'Tejun Heo'
Cc: 'Arnd Bergmann', linux-arch, linux-kernel
> -----Original Message-----
> From: linux-arch-owner@vger.kernel.org [mailto:linux-arch-
> owner@vger.kernel.org] On Behalf Of Thomas Gleixner
> Sent: Thursday, December 09, 2010 9:50 PM
> To: Tejun Heo
> Cc: Guan Xuetao; Arnd Bergmann; linux-arch@vger.kernel.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCHv1 000/211] unicore32 architecture support
>
> B1;2401;0cOn Thu, 9 Dec 2010, Tejun Heo wrote:
>
> > Hello,
> >
> > On 12/09/2010 10:28 AM, Guan Xuetao wrote:
> > > From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> > >
> > > These patches add support for UniCore-32 ISA in linux kernel.
> > > UniCore ISA is defined and developed by Micro-Processor R&D Center
> > > of Peking University, and over the years, the CPUs and SoCs using
> > > UniCore ISA have been successfully applied in a variety of products in
> China.
> >
> > * Patches should be split according to logical steps of changes, not
> > per-file.
> >
> > * Patches should be bisectable. IOW, after applying upto any patch in
> > the series, the tree should be buildable and working.
>
> That does not work for a new architecture. There is nothing to bisect.
>
> > * When posting a patch series, especially one as large as 211, please
> > make the mails for the actual patches replies to the head message.
> > Don't post it as 212 separate messages or replies to the immediate
> > previous patch.
> >
> > So, in short, if you're adding a whole new arch, just post it as a
> > single patch or a series of several patches if it requires changes
> > outside of the specific arch subtree.
>
> Crap. a single patch is a major PITA for review. It's even worse than
> 211 per file patches.
>
> It's ok to have several patches ordered by topics
>
> - generic header stuff
> - processor and system headers
> - low level entry and setup code
> - process/thread related code
> - mm related code
> - timers
> - interrupts
> - ptrace
> - signals
> - fault handling
> - misc
> - build system, main makefile, Kconfig
>
> That makes it actually feasible to review.
Thanks,
I will rearrange my patches.
Guan Xuetao
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [PATCHv1 000/211] unicore32 architecture support
@ 2010-12-10 8:56 ` Guan Xuetao
0 siblings, 0 replies; 15+ messages in thread
From: Guan Xuetao @ 2010-12-10 8:56 UTC (permalink / raw)
To: 'Thomas Gleixner', 'Tejun Heo'
Cc: 'Arnd Bergmann', linux-arch, linux-kernel
> -----Original Message-----
> From: linux-arch-owner@vger.kernel.org [mailto:linux-arch-
> owner@vger.kernel.org] On Behalf Of Thomas Gleixner
> Sent: Thursday, December 09, 2010 9:50 PM
> To: Tejun Heo
> Cc: Guan Xuetao; Arnd Bergmann; linux-arch@vger.kernel.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCHv1 000/211] unicore32 architecture support
>
> B1;2401;0cOn Thu, 9 Dec 2010, Tejun Heo wrote:
>
> > Hello,
> >
> > On 12/09/2010 10:28 AM, Guan Xuetao wrote:
> > > From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> > >
> > > These patches add support for UniCore-32 ISA in linux kernel.
> > > UniCore ISA is defined and developed by Micro-Processor R&D Center
> > > of Peking University, and over the years, the CPUs and SoCs using
> > > UniCore ISA have been successfully applied in a variety of products in
> China.
> >
> > * Patches should be split according to logical steps of changes, not
> > per-file.
> >
> > * Patches should be bisectable. IOW, after applying upto any patch in
> > the series, the tree should be buildable and working.
>
> That does not work for a new architecture. There is nothing to bisect.
>
> > * When posting a patch series, especially one as large as 211, please
> > make the mails for the actual patches replies to the head message.
> > Don't post it as 212 separate messages or replies to the immediate
> > previous patch.
> >
> > So, in short, if you're adding a whole new arch, just post it as a
> > single patch or a series of several patches if it requires changes
> > outside of the specific arch subtree.
>
> Crap. a single patch is a major PITA for review. It's even worse than
> 211 per file patches.
>
> It's ok to have several patches ordered by topics
>
> - generic header stuff
> - processor and system headers
> - low level entry and setup code
> - process/thread related code
> - mm related code
> - timers
> - interrupts
> - ptrace
> - signals
> - fault handling
> - misc
> - build system, main makefile, Kconfig
>
> That makes it actually feasible to review.
Thanks,
I will rearrange my patches.
Guan Xuetao
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [PATCHv1 000/211] unicore32 architecture support
2010-12-10 8:56 ` Guan Xuetao
(?)
@ 2010-12-10 11:01 ` Thomas Gleixner
2010-12-10 12:35 ` Arnd Bergmann
-1 siblings, 1 reply; 15+ messages in thread
From: Thomas Gleixner @ 2010-12-10 11:01 UTC (permalink / raw)
To: Guan Xuetao
Cc: 'Tejun Heo', 'Arnd Bergmann', linux-arch, linux-kernel
On Fri, 10 Dec 2010, Guan Xuetao wrote:
>
> > -----Original Message-----
> > From: linux-arch-owner@vger.kernel.org [mailto:linux-arch-
> > owner@vger.kernel.org] On Behalf Of Thomas Gleixner
> > Sent: Thursday, December 09, 2010 9:50 PM
> > To: Tejun Heo
> > Cc: Guan Xuetao; Arnd Bergmann; linux-arch@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Subject: Re: [PATCHv1 000/211] unicore32 architecture support
Please fix your mail client to do proper citations. A single line
On Thu, 9 Dec 2010, Thomas Gleixner wrote:
or whatever your preferred cite line is, is sufficient. We all have
the mail header already.
> > It's ok to have several patches ordered by topics
> >
> > - generic header stuff
> > - processor and system headers
> > - low level entry and setup code
> > - process/thread related code
> > - mm related code
> > - timers
> > - interrupts
> > - ptrace
> > - signals
> > - fault handling
> > - misc
> > - build system, main makefile, Kconfig
> >
> > That makes it actually feasible to review.
> Thanks,
> I will rearrange my patches.
And please mail them to yourself before you post them and make sure
they apply and resemble exaclty what you wanted to send. I just
noticed, that your mailer line-wrapped the patches:
+ /*
+ * actually the registers should be pushed and pop'd conditionally,
but
+ * after bl the flags are certainly clobbered
+ */
Thanks,
tglx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-09 13:49 ` Thomas Gleixner
2010-12-09 14:05 ` Tejun Heo
2010-12-10 8:56 ` Guan Xuetao
@ 2010-12-10 12:16 ` Arnd Bergmann
2 siblings, 0 replies; 15+ messages in thread
From: Arnd Bergmann @ 2010-12-10 12:16 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: Tejun Heo, Guan Xuetao, linux-arch, linux-kernel
On Thursday 09 December 2010, Thomas Gleixner wrote:
> Crap. a single patch is a major PITA for review. It's even worse than
> 211 per file patches.
It doesn't matter which way is worse than the other. Both are
impractical for people to look at and not helpful.
> It's ok to have several patches ordered by topics
>
> - generic header stuff
> - processor and system headers
> - low level entry and setup code
> - process/thread related code
> - mm related code
> - timers
> - interrupts
> - ptrace
> - signals
> - fault handling
> - misc
> - build system, main makefile, Kconfig
>
> That makes it actually feasible to review.
Agreed.
One important step is to send patches that touch existing
architecture independent code separately from new files
that depend on the changes.
In some cases, it's also useful to send out less than the
complete set of patches at a time, but only if it is possible
to understand the patches that did get sent by themselves.
For instance, don't send a device driver implementation but
not the header files that defines the user interface and the
hardware registers.
My personal upper bound would be on the order of ten large
patches or (alternatively) twenty small patches. The size of
the individual mails often varies a lot and that's fine.
A patch containing 100kb of register definitions may be
easier to review than a one-line change in an important
place.
Arnd
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCHv1 000/211] unicore32 architecture support
2010-12-10 11:01 ` Thomas Gleixner
@ 2010-12-10 12:35 ` Arnd Bergmann
0 siblings, 0 replies; 15+ messages in thread
From: Arnd Bergmann @ 2010-12-10 12:35 UTC (permalink / raw)
To: Thomas Gleixner
Cc: Guan Xuetao, 'Tejun Heo', linux-arch, linux-kernel
On Friday 10 December 2010, Thomas Gleixner wrote:
> And please mail them to yourself before you post them and make sure
> they apply and resemble exaclty what you wanted to send. I just
> noticed, that your mailer line-wrapped the patches:
>
> + /*
> + * actually the registers should be pushed and pop'd conditionally,
> but
> + * after bl the flags are certainly clobbered
> + */
>
Note that this and the threading automatically get handled by
'git send-email', there is probably not much point in trying
to make the currently used email program do the right thing.
Feel free to send the patches to me in private first to make
sure that the formalities of patch submission are right, then
send them to the mailing list again for discussion.
Arnd
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [PATCHv1 000/211] unicore32 architecture support
[not found] ` <1292078266.4722.2.camel@mulgrave.site>
@ 2010-12-13 6:58 ` Guan Xuetao
2010-12-13 9:51 ` Thomas Gleixner
0 siblings, 1 reply; 15+ messages in thread
From: Guan Xuetao @ 2010-12-13 6:58 UTC (permalink / raw)
To: 'James Bottomley'; +Cc: linux-arch
> > > > These patches add support for UniCore-32 ISA in linux kernel.
> > > > UniCore ISA is defined and developed by Micro-Processor R&D Center of
> > > > Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> > > > have been successfully applied in a variety of products in China.
> > >
> > > Could we at least have these 212 emails threaded at least below this
> > > email ... for those of us who may be tempted to skip a full review with
> > > a thread delete?
>
> Please don't drop cc's ... someone else may be wondering the same thing
> so keeping the archive preserves the searchable knowledge.
Ok, I see.
> > What's meaning for '212 email threaded below this email'?
>
> Your subject [PATCHv1 000/211] means there are 211 patches plus a
> description in the set ... that means 212 emails. If you thread them
> all below the 000/211 email, it's far easier to handle.
The rule in Documentations/SubmittingPatches:
Do not send more than 15 patches at once to the vger mailing lists!
So, I suppose I could post 15 patches every two or three days.
Thanks.
Guan Xuetao
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: [PATCHv1 000/211] unicore32 architecture support
2010-12-13 6:58 ` Guan Xuetao
@ 2010-12-13 9:51 ` Thomas Gleixner
0 siblings, 0 replies; 15+ messages in thread
From: Thomas Gleixner @ 2010-12-13 9:51 UTC (permalink / raw)
To: Guan Xuetao; +Cc: 'James Bottomley', linux-arch
On Mon, 13 Dec 2010, Guan Xuetao wrote:
> > > > > These patches add support for UniCore-32 ISA in linux kernel.
> > > > > UniCore ISA is defined and developed by Micro-Processor R&D Center of
> > > > > Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> > > > > have been successfully applied in a variety of products in China.
> > > >
> > > > Could we at least have these 212 emails threaded at least below this
> > > > email ... for those of us who may be tempted to skip a full review with
> > > > a thread delete?
> >
> > Please don't drop cc's ... someone else may be wondering the same thing
> > so keeping the archive preserves the searchable knowledge.
> Ok, I see.
>
> > > What's meaning for '212 email threaded below this email'?
> >
> > Your subject [PATCHv1 000/211] means there are 211 patches plus a
> > description in the set ... that means 212 emails. If you thread them
> > all below the 000/211 email, it's far easier to handle.
> The rule in Documentations/SubmittingPatches:
> Do not send more than 15 patches at once to the vger mailing lists!
> So, I suppose I could post 15 patches every two or three days.
As Arnd and myself said before, having less but larger patches which
group the files into topics is a far better solution than sending 200+
patches which touch single files.
Thanks,
tglx
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2010-12-13 9:51 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-09 9:28 [PATCHv1 000/211] unicore32 architecture support Guan Xuetao
2010-12-09 9:28 ` Guan Xuetao
2010-12-09 9:50 ` Tejun Heo
2010-12-09 13:49 ` Thomas Gleixner
2010-12-09 14:05 ` Tejun Heo
2010-12-09 14:18 ` Thomas Gleixner
2010-12-09 14:27 ` Tejun Heo
2010-12-10 8:56 ` Guan Xuetao
2010-12-10 8:56 ` Guan Xuetao
2010-12-10 11:01 ` Thomas Gleixner
2010-12-10 12:35 ` Arnd Bergmann
2010-12-10 12:16 ` Arnd Bergmann
2010-12-09 17:50 ` James Bottomley
[not found] ` <028701cb9919$df3b7900$9db26b00$@mprc.pku.edu.cn>
[not found] ` <1292078266.4722.2.camel@mulgrave.site>
2010-12-13 6:58 ` Guan Xuetao
2010-12-13 9:51 ` Thomas Gleixner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.