Add uart_suspend_port(), uart_resume_port() which are responsible
for suspending/resuming one UART port.  Low level drivers are
expected to call this from their device model suspend and resume
methods.

There were a couple of cases where we call tty_register_device()
multiple times for the same port, notibly when ports are discovered
via 8250_pci, 8250_pnp or 8250_cs modules.  With devfs configured,
this causes a warning.  Don't call tty_register_device() multiple
times.

- Preserve per-port flags which are not modifyable from user space.
- Only allow DTR, RTS, OUT1 and OUT2 to be controlled from user space.
- Don't put the console port into sleep mode when closing a port.
- Ensure that we wake up people waiting on modem status changes when
  we receive a hangup.

Add a per-port semaphore to protect against simultaneous opens,
closes, hangups, and the like.  This removes the need for the
UIF_CLOSING flag, as well as the extra tests and wait queues.

Disable the old PM code for now - it is incompatible with the
per-port semaphore.

Replace uart_info argument for uart_change_speed, uart_startup,
uart_shutdown and uart_update_termios with a uart_state structure.
We no longer pass struct uart_info around to other functions.

Since the uart_state structure is less volatile than uart_info, we
can safely place some semaphores in uart_state.

Add resource-based addressing and ioremap support.  Ask the 8250
layer to handle the resources, and share IRQs.

- Add local copy of flags for describing port characteristics.
- Add "quirk" handling to sort out board-specific initialisation,
  per-port setup, and finalisation.
- Remove quirk information from struct pci_board array, thereby
  making entries more generic.
- Initialise struct pci_board array using explicit indicies -
  adding to the readability, and making sure that the right entries
  are in the correct location in the table.
- Ensure we tell the serial layer to claim resources, and share
  interrupts.  PCI interrupts are sharable, and need to be so that
  multi-function cardbus cards will work.
- Only remap each PCI memory BAR once.
- Add pci serial driver to the tty devclass (this requires the patch
  to make tty_io.c register the tty devclass early.)

Tested by CaT and myself.

concurrent renames in another directory.

I doubt this can be triggered in practice, and the fix is
a bit heavy-handed, but let's see if numbers can show that
the simple fix doesn't show any real lock contention.

list.h must now include stddef since it uses NULL.

This is the "boot sector removal" patch for i386 updated for Linux
2.5.63-bk7.  The only change against the 2.5.59 version is that the
FDOPTS Makefile variable, which lets one create a floppy image with
arbitrary kernel options, has been merged from the x86-64 version, and
the comments have been updated.

The patch removes the in-kernel boot sector, which these days rarely
work correctly (it only supports up to 1 MB kernels, and only work on
legacy floppies -- not on IDE or USB devices, nor on any kind of
emulated devices like El Torito), replaces it with a placeholder stub,
and sets up the Makefile targets to create floppies or floppy images
using SYSLINUX.  The FDOPTS Makefile variable can be used to set
kernel command line options (thanks to a suggestion by Andi Kleen.)

Note that the same change has already been applied to the x86-64
architecture.  The last hunk of the patch corrects a comment in that
architecture.

  Now we tackle pci_add_new_bus and pci_scan_bridge.  The hotplug code
  currently uses this, but I'd like it to die off; pci_scan_bridge()
  should be used to scan behind bridges.  This may mean hotplug needs
  some changes to pci_scan_bridge - if so, we need to find out what
  changes are required and fix it.

  pci_alloc_child_bus() does what pci_add_new_bus() did, except it
  doesn't attach the new bus to the parents list of child buses.  The
  only way this bus can be reached from the parent bus is by scanning
  the parents devices list, and locating a device with a non-NULL
  subordinate bus.  The only code which should be doing this is the
  PCI code.

  Since the new bus will have an empty list head for bus->node, we can
  detect unattached buses prety easily.  (see pci-3.diff.)

  pci_scan_bridge() changes slightly - we use our new pci_scan_child_bus()
  function from pci-3.diff, which doesn't attach devices to the global
  tree.  This means callers of pci_scan_child_bus() and pci_scan_bridge()
  (ie, hotplug) will need to call pci_bus_add_devices().

- Convert setup-bus.c resource allocation to scan bus->devices rather
  than bus->children.  As noted previously, newly discovered child
  buses will not be on the parents list of children buses, so when
  we're trying to assign resources, we need to scan the bus for
  devices with subordinate buses rather than using the list of children
  buses.

  The pci_find* functions search using the following lists:
        bus->children   (for subordinate buses)
        pci_root_buses  (for all root buses)
        pci_devices     (for devices)

  This leaves one list which we can add devices to without any drivers
  finding the new devices before we've finished with them.

- initialise bus->node list head.

- pci_scan_slot will scan the specified slot, and add the discovered
  devices to the bus->devices list only.  These devices will not
  appear on the global device list, and do not show in sysfs, procfs.
  pci_scan_slot returns the number of functions found.  If you want
  to find the devices, you have to scan bus->devices and look for
  devices where list_empty(&dev->global_list) is true.

- new function "pci_bus_add_devices" adds newly discovered devices
  to the global device lists, and handles the sysfs and procfs
  stuff, making the devices available to drivers.  All our buses
  which have an empty list head are treated as "new" (since they
  are not attached to the parent buses list of children) and are
  also added.  Currently, no buses will be in this state when this
  function is called.

- new function "pci_scan_child_bus" scans a complete bus, building
  a list of devices on bus->devices only, performing bus fixups
  via pcibios_fixup_bus() and scanning behind bridges.  It does
  make devices externally visible.

- pci_do_scan_bus retains its original behaviour - ie, it scans
  and makes devices available immediately.

- Eliminate the stack allocation of a struct pci_dev, and make
  pci_scan_slot() take a bus and a devfn argument.
- Add "dev->multifunction" to indicate whether this is a multifunction
  device.
- Run header fixups before inserting the new pci device into any
  device lists or announcing it to the drivers.
- Convert some more stuff to use the list_for_each* macro(s).

- Separate out bus resource allocator (pci_bus_alloc_resource)
- Provide pci_enable_bridges to setup command register for all
  pci bridges.

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

The outbsync one has further changes to come in the next batch to sort
out some platforms like PPC

Also fix the irq masking bug

This switches ide-dma to ide_execute_command and makes IDE DMA also happy
when running shared IRQ

This doesn't have the new -ac testing stuff from 2.4.21pre5-ac but it
has the stuff I now trust in it. This fixes the cache flush stuff and
also means ide-disk now should be safe shared IRQ

Dave Woodhouse did this a while ago and its been kicking around in my
tree just fine. This gets rid of a lot of the init lists of functions
still left in the kernel by having an __init type array built up for the
consoles as well

We must not look for a PCI IRQ for a non native mode IDE device
We must write PCI_INTERRUPT_LINE for VIA

ALi Magik requires workarounds for TV chips
IDE controllers require proper handling in legacy mode
PXB must be disabled on C0 450NX or the IDE will corrupt memory
VIA northbridge devices require the interrupt line is written
NEC_CBUS_2/3 require ISA DMA workarounds