Patch from David Brownell

This declares the pxa2xx_udc platform device, defines
the platform_data made available to that driver, and
allows different machines to customize that platform_data.

Same idea as in the FB driver.  Be careful of patch conflicts
applying to other kernels, mostly due to different platform
devices being listed.

Patch from David Brownell

This just makes the IDP initialization code use this initcall, so
that it won't run unless it's actually on IDP hardware.

Depends on the INIT_MACHINE patch (#1 this series).

Patch from David Brownell

This adds a mechanism for a per-machine initcall, one that's
guaranteed to run only to initialize a kernel running on that
specific hardware.  It's not strictly necessary, but it does
eliminate the need for certain boilerplate in machine-specific
support, to ensure it's only running on the right hardware:

      /* in arch/arm/mach-xxx/MYMACHINE.c */
      ...
      static int __init init_MYMACHINE(void)
      {
           if (!mach_is_MYMACHINE())       // often forgotten!!
                return -EINVAL;
           ... declare and customize platform devices
           ...
           return 0;
      }
      arch_initcall(init_MYMACHINE);

An init_MYMACHINE() call still exists, but it'd be declared
as part of the machine definition.

into home.osdl.org:/home/torvalds/v2.5/linux

Spotted by Matteo Croce 

into home.osdl.org:/home/torvalds/v2.5/linux

From Martin Diehl.

From Martin Diehl.

Also, make sir-dev locking compatible with irport.
From Martin Diehl.

[ATM]: br2684 incorrectly handles frames recvd with FCS (by Alex Zeffertt <ajz@cambridgebroadband.com>)

Spotted by Andreas Henriksson <andreas@scream.fjortis.info>

into lips.borg.umn.edu:/export/music/bkroot/xfs-linux-2.6

We must not mark the process TASK_STOPPED early, because
that might allow a signal to wake it up before we actually
got to the "wake_up_forked_process()" state. Total confusion
would happen.

Make wake_up_forked_process() verify the new world order.