05 Dec, 2009
12 commits
-
Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
IXP4xx CPUs can indirectly access the whole 4 GB PCI MMIO address space (using
the non-prefetch registers). Previously the available space depended on the CPU
variant, since one of the IXP43x platforms needed more than the usual 128 MB.
1 GB should be enough for everyone, and if not, we can trivially increase it.Signed-off-by: Krzysztof Hałasa
-
Instead of including the heavy linux/mm.h for VMALLOC_START, test the addresses
against PCI MIN and MAX addresses. Indirect PCI uses 1:1 mapping for MMIO space
making this change possible.Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
Signed-off-by: Krzysztof Hałasa
-
The indexes were signed, so negatives were possible.
Signed-off-by: Roel Kluin
Signed-off-by: Krzysztof Hałasa -
The repetitive in/out functions must preserve order, not value.
Signed-off-by: Krzysztof Hałasa
-
Clock generators used by IXP4xx processors are usually 33.333 MHz, sometimes
33.33 MHz and few platforms use 33 MHz. The timers tick twice as fast,
that means 66.666, 66.66 or 66 MHz. Current 66.666666 MHz means 10 ppm
offset from the usual 66.666 MHz.Signed-off-by: Krzysztof Hałasa
03 Dec, 2009
2 commits
-
We should now use dev_set_drvdata to set the driver driver_data field.
Signed-off-by: Florian Fainelli
Patchwork: http://patchwork.linux-mips.org/patch/747/
Signed-off-by: Ralf Baechle -
Broken by d63c63e889bbeeaa461a8addf1245f89f3ce4ece (lmo) rsp.
f1e39a4a616cd9981a9decfd5332fd07a01abb8b (kernel.org).Signed-off-by: Ralf Baechle
Patchwork: http://patchwork.linux-mips.org/patch/746/
02 Dec, 2009
6 commits
-
* 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus:
MIPS: Loongson: Switch from flatmem to sparsemem
MIPS: Loongson: Disallow 4kB pages
MIPS: Add missing definition for MADV_HWPOISON.
MIPS: Fix build error if __xchg() is not getting inlined.
MIPS: IP22/IP28 Disable early printk to fix boot problems on some systems. -
With flatmem hibernation for Loongson will fail, and there are also some
other problems such as broken files when using NFS or CIFS / Samba.The config help of sparsemem says:
"This option provides some potential performance benefits, along with
decreased code complexity."So to avoid the potential problems of FLATMEM, we disable FLATMEM directly
and use SPARSEMEM instead.Related email thread:
http://groups.google.com/group/loongson-dev/browse_thread/thread/b6b65890ec2b0f24/feb43e5aa7f55d9b?show_docid=feb43e5aa7f55d9b
Reported-by: Tatu Kilappa
Signed-off-by: Wu Zhangjin
Patchwork: http://patchwork.linux-mips.org/patch/737/
Cc: linux-mips@linux-mips.org
Cc: zhangfx@lemote.com
Signed-off-by: Ralf Baechle -
Currently, with PAGE_SIZE_4KB, the kernel for loongson will hang on:
Kernel panic - not syncing: Attempted to kill init!
The possible reason is the cache aliases problem:
Loongson 2F has 64kb, 4 way L1 Cache, the way size is 16kb, which is bigger
then 4kb. so, If using 4kb page size, there is cache aliases problem.
To avoid this kind of problem, extra cache flushing. The 2nd possible
solution is 16kb page size which avoids cache aliases without the need for
extra cache flushes. So we disable 4kB pages until the aliasing issue is
solved.Signed-off-by: Wu Zhangjin
Patchwork: http://patchwork.linux-mips.org/patch/736/
Cc: linux-mips@linux-mips.org
Cc: zhangfx@lemote.com
Signed-off-by: Ralf Baechle -
Thanks to Joseph S. Myers for reporting this.
Signed-off-by: Ralf Baechle
Cc: "Joseph S. Myers"
Patchwork: http://patchwork.linux-mips.org/patch/723/ -
If __xchg() is not getting inlined the outline version of the function
will have a reference to __xchg_called_with_bad_pointer() which does not
exist remaining. Fixed by using BUILD_BUG_ON() to check for allowable
operand sizes.Signed-off-by: Ralf Baechle
Patchwork: http://patchwork.linux-mips.org/patch/705/ -
Some Debian users have reported that the kernel hangs early during boot on
some IP22 systems. Thomas Bogendoerfer found that this is due to a "bad
interaction between CONFIG_EARLY_PRINTK and overwritten prom memory during
early boot". Since there's no fix yet, disable CONFIG_EARLY_PRINTK for now.Signed-off-by: Martin Michlmayr
Cc: linux-mips@linux-mips.org
Cc: Thomas Bogendoerfer
Cc: Dmitri Vorobiev
Patchwork: http://patchwork.linux-mips.org/patch/702/
Signed-off-by: Ralf Baechle
01 Dec, 2009
12 commits
-
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha-2.6:
alpha: Fixup last users of irq_chip->typename
Alpha: Rearrange thread info flags fixing two regressions
arch/alpha/kernel: Add kmalloc NULL tests
arch/alpha/kernel/sys_ruffian.c: Use DIV_ROUND_CLOSEST -
The typename member of struct irq_chip was kept for migration purposes
and is obsolete since more than 2 years. Fix up the leftovers.Signed-off-by: Thomas Gleixner
Cc: Richard Henderson
Cc: linux-alpha@vger.kernel.org
Signed-off-by: Matt Turner -
The removal of the TIF_NOTIFY_RESUME flag, commit a583f1b54249b
"remove unused TIF_NOTIFY_RESUME flag," resulted in incorrect
setting of the unaligned access control flags by the prctl syscall.The re-addition of the TIF_NOTIFY_RESUME flag, commit d0420c83f39f
"KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures [try #6]"
further caused problems, namely incorrect operands to assembler code
as evidenced by:AS arch/alpha/kernel/entry.o
arch/alpha/kernel/entry.S: Assembler messages:
arch/alpha/kernel/entry.S:326: Warning: operand out of range
(0x0000000000000406 is not between 0x0000000000000000 and
0x00000000000000ff)Both regressions fixed by (1) rearranging TIF_NOTIFY_RESUME flag to be
in lower 8 bits of the thread info flags, and (2) making sure that
ALPHA_UAC_SHIFT matches the rearrangement of the thread info flags.Signed-off-by: Michael Cree
Cc: Richard Henderson
Cc: Ivan Kokshaysky
Cc: David Howells ,
Signed-off-by: Matt Turner -
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin:
Blackfin: fix SMP build error in start_thread()
Blackfin: fix memset in smp_send_reschedule() and -stop()
Blackfin: fix typo in ptrace poking
Blackfin: check for anomaly 05000475
Blackfin: work around testset anomaly 05000477
Blackfin: update anomaly lists
Blackfin: fix cache Kconfig typo
Blackfin: fix suspend/resume failure with some on-chip ROMs -
* 'for-linus' of master.kernel.org:/home/rmk/linux-2.6-arm:
[ARM] Update mach-types
ARM: 5793/1: ARM: Check put_user fail in do_signal when enable OABI_COMPAT
MAINTAINERS: add maintainer information for AMBA primecell drivers
[ARM] pxa/spitz: fix compile regression on spitz
ARM: PNX4008: i2c-pnx: use the same dev_id for request_irq and free_irq
[ARM] pxa/cpufreq: fix index assignments for end marker
ARM: PNX4008: fix watchdog device driver name
[ARM] kmap: fix build errors with DEBUG_HIGHMEM enabled -
* 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc:
powerpc: Fix DEBUG_HIGHMEM build break from d4515646699 -
Code was added to mm/higmem.c that depends on several
kmap types that powerpc does not support. We add dummy
invalid definitions for KM_NMI, KM_NM_PTE, and KM_IRQ_PTE.According to list discussion, this fix should not be needed
anymore starting with 2.6.33. The code is commented to this
effect so hopefully we will remember to remove this.Signed-off-by: Becky Bruce
Signed-off-by: Benjamin Herrenschmidt -
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6:
sunsu: Use sunserial_console_termios() in sunsu_console_setup().
sunsu: Pass true 'ignore_line' to console match when RSC or LOM console.
serial: suncore: Fix RSC/LOM handling in sunserial_console_termios().
serial: suncore: Add 'ignore_line' argument to sunserial_console_match().
sunsu: Fix detection of SU ports which are RSC console or control.
sunsab: Do not set sunsab_reg.cons right before registering minors.
sparc64: Fix definition of VMEMMAP_SIZE. -
* 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq:
[CPUFREQ] Enable ACPI PDC handshake for VIA/Centaur CPUs -
Check that the result of kmalloc is not NULL before passing it to other
functions.The semantic match that finds this problem is as follows:
(http://www.emn.fr/x-info/coccinelle/)//
@@
expression *x;
identifier f;
constant char *C;
@@x = \(kmalloc\|kcalloc\|kzalloc\)(...);
... when != x == NULL
when != x != NULL
when != (x || ...)
(
kfree(x)
f(...,C,...,x,...)
|
*f(...,x,...)
|
*x->f
)
//Signed-off-by: Julia Lawall
Cc: Ivan Kokshaysky
Cc: Richard Henderson
Signed-off-by: Matt Turner -
The kernel.h macro DIV_ROUND_CLOSEST performs the computation (x + d/2)/d
but is perhaps more readable.The semantic patch that makes this change is as follows:
(http://www.emn.fr/x-info/coccinelle/)//
@haskernel@
@@@depends on haskernel@
expression x,__divisor;
@@- (((x) + ((__divisor) / 2)) / (__divisor))
+ DIV_ROUND_CLOSEST(x,__divisor)
//Signed-off-by: Julia Lawall
Cc: Ivan Kokshaysky
Cc: Richard Henderson
Signed-off-by: Matt Turner -
kernel unwinding is broken with gcc >= 4.x. Part of the problem is that
binutils seems very sensitive to where the unwind information is stored.Signed-off-by: Helge Deller
Signed-off-by: Kyle McMartin
Signed-off-by: Linus Torvalds
26 Nov, 2009
2 commits
-
Signed-off-by: Russell King
25 Nov, 2009
6 commits
-
Commit d5ce528c8e46fa5afb9 (Blackfin: convert irq/process to asm-generic)
incorrectly merged the smp and non-smp cases of start_thread() causing the
L1 stack to be setup on the SMP port instead of the UP port.Signed-off-by: Graf Yang
Signed-off-by: Mike Frysinger -
To set zeroes the sizeof the struct should be used rather
than sizeof the pointer, kzalloc does that.Signed-off-by: Roel Kluin
Signed-off-by: Mike Frysinger -
Commit c014e15a2f667f9 (Blackfin: convert ptrace to new memory functions)
introduced a copy & paste typo in the ptrace poke data/text handling. The
access_process_vm() function call was telling it to read instead of write.Signed-off-by: Jie Zhang
Signed-off-by: Mike Frysinger -
Parts that have on-chip L2 SRAM cannot safely utilize writeback caching
mode, so reject any attempts to use it.Signed-off-by: Mike Frysinger
-
Ironically, the atomic testset instruction cannot be interrupted else it
will produce incorrect results. So disable interrupts to help it out.Signed-off-by: Mike Frysinger
-
Add some recently documented anomalies (473, 474, 475, 477). Also stick
a "do not edit" notice in here so people know these are copies of some
master version.Signed-off-by: Mike Frysinger
