09 Sep, 2005
30 commits
-
The earlier commit 8d9273918635f0301368c01b56c03a6f339e8d51
(Consolidate early console and PPCDBG code) broke iSeries because
it caused unregister_console(&udbg_console) to be called
unconditionally. iSeries never registers the udbg_console.This just reverts part of the change.
Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
The SPARSEMEM EXTREME code (802f192e4a600f7ef84ca25c8b818c8830acef5a) that
went in yesterday broke PPC64 for !CONFIG_NUMA.The problem is that (free|reserve)_bootmem don't take a page number as their
first argument, they take an address. Ruh roh.Booted on P5 LPAR, iSeries and G5.
Signed-off-by: Michael Ellerman
Signed-off-by: Paul Mackerras -
This fixes a severe bug in the bpa_iic driver that caused
all sorts of problems.We had been using incorrect priority values for inter processor
interrupts, which resulted in always doing CALL_FUNCTION
instead of RESCHEDULE or DEBUGGER_BREAK.The symptoms cured by this patch include bad performance on
SMP systems spurious kernel panics in the IPI code.Signed-off-by: Arnd Bergmann
Signed-off-by: Paul Mackerras -
Rework the 68x328 configuration and setup code. All 68x328 varients
share the same timer hardware. So extract that into its own file,
instead of keeping copies in each processors setup code.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Create common timer code for all 68x328 processor varients.
Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
The boot loader on the MOD5272 board doesn't set the register maping,
so set it in the 5272 init code. There was code in there to support
this, but we had never needed to use it before.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Add timer support for the ColdFire 523x processor family.
(It uses the ColdFire PIT timer hardware, so we just build that in).Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Rework the 68x328 configuration and setup code. All 68x328 varient
share the same timer hardware, so extract that into its own file,
instead of keeping copies in each processors setup code.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Create common 68VZ328 config code. It is essentially the same for
all boards that use this, so no point having a version of it for
each.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Remove DragonEngine2 specific config code. Use common 68VZ328 config
code now.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Remove uCdimm specific config code. Use common 68VZ328 config code now.
Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds -
Patch from Ben Dooks
Updated the s3c2410_defconfig for the 2.6.13-git8
kernel release, as well as adding the Anubis
board to the list of boards built.Signed-off-by: Ben Dooks
Signed-off-by: Russell King -
Patch from Tony Lindgren
This patch syncs the mainline kernel with linux-omap tree.
The highlights of the patch are:
- Convert more drivers to register resources in board-*.c to take
advantage of the driver model by David Brownell and Ladislav Michl
- Use set_irq_type() for GPIO interrupts instead of
omap_set_gpio_edge_ctrl() by David Brownell
- Add minimal support for handling optional add-on boards, such as
OSK Mistral board with LCD and keypad, by David Brownell
- Minimal support for loading functions to SRAM by Tony Lindgren
- Wake up from serial port by muxing RX lines temporarily into GPIO
interrupts by Tony Lindgren
- 32KHz sched_clock by Tony Lindgren and Juha YrjolaSigned-off-by: Tony Lindgren
Signed-off-by: Russell King -
There were three changes necessary in order to allow
sparc64 to use setup-res.c:1) Sparc64 roots the PCI I/O and MEM address space using
parent resources contained in the PCI controller structure.
I'm actually surprised no other platforms do this, especially
ones like Alpha and PPC{,64}. These resources get linked into the
iomem/ioport tree when PCI controllers are probed.So the hierarchy looks like this:
iomem --|
PCI controller 1 MEM space --|
device 1
device 2
etc.
PCI controller 2 MEM space --|
...
ioport --|
PCI controller 1 IO space --|
...
PCI controller 2 IO space --|
...You get the idea. The drivers/pci/setup-res.c code allocates
using plain iomem_space and ioport_space as the root, so that
wouldn't work with the above setup.So I added a pcibios_select_root() that is used to handle this.
It uses the PCI controller struct's io_space and mem_space on
sparc64, and io{port,mem}_resource on every other platform to
keep current behavior.2) quirk_io_region() is buggy. It takes in raw BUS view addresses
and tries to use them as a PCI resource.pci_claim_resource() expects the resource to be fully formed when
it gets called. The sparc64 implementation would do the translation
but that's absolutely wrong, because if the same resource gets
released then re-claimed we'll adjust things twice.So I fixed up quirk_io_region() to do the proper pcibios_bus_to_resource()
conversion before passing it on to pci_claim_resource().3) I was mistakedly __init'ing the function methods the PCI controller
drivers provide on sparc64 to implement some parts of these
routines. This was, of course, easy to fix.So we end up with the following, and that nasty SPARC64 makefile
ifdef in drivers/pci/Makefile is finally zapped.Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman -
Some PCI devices (e.g. 3c905B, 3c556B) lose all configuration
(including BARs) when transitioning from D3hot->D0. This leaves such
a device in an inaccessible state. The patch below causes the BARs
to be restored when enabling such a device, so that its driver will
be able to access it.The patch also adds pci_restore_bars as a new global symbol, and adds a
correpsonding EXPORT_SYMBOL_GPL for that.Some firmware (e.g. Thinkpad T21) leaves devices in D3hot after a
(re)boot. Most drivers call pci_enable_device very early, so devices
left in D3hot that lose configuration during the D3hot->D0 transition
will be inaccessible to their drivers.Drivers could be modified to account for this, but it would
be difficult to know which drivers need modification. This is
especially true since often many devices are covered by the same
driver. It likely would be necessary to replicate code across dozens
of drivers.The patch below should trigger only when transitioning from D3hot->D0
(or at boot), and only for devices that have the "no soft reset" bit
cleared in the PM control register. I believe it is safe to include
this patch as part of the PCI infrastructure.The cleanest implementation of pci_restore_bars was to call
pci_update_resource. Unfortunately, that does not currently exist
for the sparc64 architecture. The patch below includes a null
implemenation of pci_update_resource for sparc64.Some have expressed interest in making general use of the the
pci_restore_bars function, so that has been exported to GPL licensed
modules.Signed-off-by: John W. Linville
Signed-off-by: Greg Kroah-Hartman -
Convert i386/pci to use io_remap_pfn_range instead of remap_pfn_range.
This is good for Xen which reuses i386/pci/i386.c for domain 0 code.Signed-off-by: Michael S. Tsirkin
Signed-off-by: Greg Kroah-Hartman -
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman -
This patch removes CONFIG_PCI_NAMES.
Signed-off-by: Adrian Bunk
Signed-off-by: Greg Kroah-Hartman -
Since GCC has to emit a call and a delay slot to the
out-of-line "membar" routines in arch/sparc64/lib/mb.S
it is much better to just do the necessary predicted
branch inline instead as:ba,pt %xcc, 1f
membar #whatever
1:instead of the current:
call membar_foo
dslotbecause this way GCC is not required to allocate a stack
frame if the function can be a leaf function.This also makes this bug fix easier to backport to 2.4.x
Signed-off-by: David S. Miller
-
arch/ia64/Kconfig
arch/ia64/kernel/acpi.c
include/asm-ia64/irq.hSigned-off-by: Tony Luck
-
Increase the value for the maximum physical address on SN systems.
Signed-off-by: Jack Steiner
Signed-off-by: Tony Luck -
These are SN2 only drivers. They should have platform checks to prevent
them from doing evil stuff in GENERIC kernels.Signed-off-by: Martin Hicks
Acked-by: Dean Nelson
Signed-off-by: Tony Luck -
Turn off the QLOGIC_FC driver. Supposedly qla2xxx should support
these devices. Do any ia64 machines have one of these devices as
the boot device?Signed-off-by: Martin Hicks
Signed-off-by: Tony Luck
08 Sep, 2005
10 commits
-
Rather than hard-coding the platform device IDs, enumerate them.
We don't particularly care about the actual ID we get, just as
long as they're unique.Signed-off-by: Russell King
-
head_4xx.S wasn't compiling due to a missing #endif
Signed-off-by: Kumar Gala
Signed-off-by: Linus Torvalds -
This adds the necessary changes to ensure that we flush the
caches correctly with aliasing VIPT caches.Signed-off-by: Russell King
-
This adds low-level suspend/resume support to locomo.c.
Signed-off-by: Pavel Machek
Signed-off-by: Russell King -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Now that asm-powerpc/* is using ifdefs on __powerpc64__ we need to add it
to CHECKFLAGS on ppc64.Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
elf_aux is userland code; it uses symbol (ELF_CLASS) that doesn't exist in
userland headers; pulled into kernel-offsets.h, switched elf_aux to using it.Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds
