M68k BVME6000: Update to the new irq API (from Roman Zippel and me) [5/20]

M68k Atari: Update to the new irq API (from Roman Zippel and me) [4/20]

M68k Apollo: Update to the new irq API (from Roman Zippel and me) [3/20]

M68k Amiga: Update to the new irq API (from Roman Zippel and me) [2/20]

M68k core: Update to the new irq API (from Roman Zippel and me) [1/20]

names are NUL-terminated

Noted by Ben Collins.

has bus ID's that are longer than 16 bytes.

Noted by Ben Collins, who also signed up to fix up some broken
strncpy() users. Sucker!

 - Pass in the "device" to remapping functions
 - add radeon CP resume ioctl
 - remove warnings and stale DMA debug code

Whether it works or not is unknown. I don't have the hardware.

sys_ioperm is only implemented on x86 (i386/x86_64).  Make the
ifdefs in vt_ioctl.c more explicit so the other architectures can
get rid of their stubs in favour of just using sys_ni_syscall in
the syscall table.

Maybe we should remove it altogether, it looks like remnants from
some very early X386 times (ie the Thomas Roell timeframe).

The noop io scheduler has a data corrupting bug, because q->last_merge
doesn't get cleared properly.  So do that in io scheduler core, and
remove the same code from deadline.

Also kill bio_rq_in_between(), it's not used by anyone anymore. rbtrees
are the hot thing these days.

And finally, remove a direct test for REQ_CMD in rq flags, use
blk_fs_request() instead.

Fix prototypes to match function definitions

 - small cleanups to make the spacing consistent
 - modifications to the watchdog so it starts the first time
   you hit it, not the second.
 - Fix for returning the proper value when starting the
   sequence number timer.
 - Fix a parameter name in the watchdog.

- fix a problem with a unset menuconfig, during the config check it's possible
  conf selects the wrong parent menu and the result is an endless loop.
- only changable config symbols are relevant during config check,
  otherwise we get another endless loop.

into samba.org:/home/paulus/kernel/for-linus-ppc

into samba.org:/stuff/paulus/kernel/for-linus-ppc

into samba.org:/home/paulus/kernel/for-linus-ppc

into samba.org:/home/paulus/kernel/for-linus-ppc

into home.transmeta.com:/home/torvalds/v2.5/linux

Since ide_get_best_pio_mode() and ide_pio_timings[]
are now properly exported in ide-lib.c, we can remove
dirty include hacks from some legacy drivers.

Add hwif->rw_disk callout (forward port of 2.4 Alan's work).

"This allows us to remove the PDC4030 special case
 and also allows for the 372N clock switch stuff."

ServerWorks CSB5 IDE fixes (from 2.4 patches by Duncan Laurie)

- blacklist drives overrunning their FIFOs in UDMA5/6 modes
- add PCI quirk (CSB5 IDE doesn't fully support native mode)

plus sync driver with 2.4 version.

SiS IDE driver fixes by Lionel Bouton:
- support for SiS655
- support for SiS630S/ET UDMA5 mode
- corrected /proc/ide/sis output for ATA133 chipsets
  (drives' positions were swapped)
- use of pci_read_config_byte() instead of direct PCI poking
  for SiS962+ detection

Add hwif->hold flag for hotswap interfaces.
Initialize founded hwif in ide_register_hw().

Original patch by Benjamin Herrenschmidt.

Fix incorrect UDMA100 cable test (by Dave Jones).
Fix compilation warning.

Add Intel ICH5 basic SATA support (from 2.4 by Andre Hedrick)
and as a bonus kill duplicate entry in piix_pci_info[].

Add IDE support for VIA vt8237 southbridge.
Author: Vojtech Pavlik

Fix incorrect enablebits for all AMD and nVidia IDE chipsets.
Author: Vojtech Pavlik

Found and fixed a reported problem where an AE_NOT_FOUND error occurred occasionally
during _BST evaluation.  This turned out to be an Owner ID allocation issue where a
called method did not get a new ID assigned to it.  Eventually, (after 64k calls), the
Owner ID UINT16 would wraparound so that the ID would be the same as the caller's and the
called method would delete the caller's namespace.

Implemented extended error reporting for control methods that are aborted due to a
run-time exception.  Output includes the exact AML instruction that caused the method
abort, a dump of the method locals and arguments at the time of the abort, and a trace of
all nested control method calls.

Modified the interpreter to allow the creation of buffers of zero length from the AML
code. Implemented new code to ensure that no attempt is made to actually allocate a
memory buffer (of length zero), only a buffer object with a NULL buffer pointer and
length zero.  A warning is no longer issued when the AML attempts to create a zero-length
buffer.

Implemented a workaround for the "leading asterisk problem" in _HIDs, _UIDs, and _CIDs.
One leading asterisk is automatically removed if present in all HID, UID, and CID
strings.

Implemented full support for _CID methods that return a package of multiple CIDs.  The
AcpiGetObjectInfo interface now returns a device _HID, _UID, and _CID list if present.
This required a change to the external interface to pass an ACPI_BUFFER object as a
parameter, since the _CID list is of variable length.

Fixed a problem with the new AE_SAME_HANDLER exception where handler initialization code
did not know about this exception.

into groveronline.com:/root/bk/linux-acpi

into penguin.transmeta.com:/home/torvalds/v2.5/linux

To handle control messaging in contexts other than the
IRQ handler's setup() callback, a bit of automagic needed
to be removed; and some minor bugs fixed.

This is the addition needed to make my previous patch for the UHCI
controller work properly with PM suspend/resume.

Paul:

Okay, I think this patch ought to do the trick.  I modified the PM
suspend/resume code so that on buggy motherboards like yours the suspend
routine really does a reset, while on normal motherboards the resume
routine really does a resume.  I haven't tried that part out because,
truth to tell, I'm a little scared of doing an APM/ACPI suspend.  Not long
ago I walked away from my computer for about a half-hour, leaving 2.5.69
running.  When I got back the screen was blank and the machine was totally
non-responsive.

I changed the delays in reset_hc() to use schedule_timeout() rather than
wait_ms(), which should make it more friendly.

Finally, I put the USBCMD_FGR back into wakeup_hc().  The reason for it is
now evident: a wakeup might be the result of a system-initiated event
as opposed to something requested by a device.

I think I'd better work on my plausible deniability...