Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch allows to use ftdi_sio driver with Ever ECO Pro CDS UPS.
Patch was tested on pre-2.6.10 kernel.

Signed-Off: Arkadiusz Miskiewicz <arekm@pld-linux.org>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch adds a new usb-misc driver for the fingerprint sensor that
can be found in the Siemens ID Mouse USB. "cat /dev/usb/idmouseX"
yields a 225x288 greyscale PNM with the fingerprint information.

It's now in version 0.5, which uses memcpy() instead of snprintf()
and allows interruption of the image acquisition process, in case
it should get stuck.

It may be considered controversial that it outputs a PNM instead
of raw data, but I hold the opinion that the 15 bytes of header,
"P5 225 288 256 ", do not do any harm and allow the device to be
used in shell scripts or similar, too.

The setup packets are not described further, simply because I don"t
know anything about them myself. We captured them under Windows
using SnoopyPro.

Please include this into the main USB kernel tree - I think it has
by now been scrutinized and tested quite thoroughly.
Signed-off-by: Florian Echtler  <echtler@fs.tum.de>
Signed-off-by: Andreas Deresch <aderesch@fs.tum.de>

This patch corrects some misconceptions that have persisted in the USB
error-code documentation for quite some time.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Various fixes to the 'pegasus' driver, notably fixing OSDL bugid #3978
so this can be used with bridges again (or for that matter, other
normal usage).

    * Bugfixes in the status urb completion handler:

        - Never use garbage that happens to be sitting in the URB
          data buffer to change the carrier status.


        - There are two bits which claim to report parts of carrier
          detect bit.  This switches to the one that works sometimes;
          monitoring through MII might be the best solution.

        - Stop log spamming ... at least some of these chips seem
          to get confused about data toggle, no point in warning
          about each packet error as it's detected.

    * Report the normal Ethernet MTU.

    * Better ethtool support:

        - Save the message level set by userspace
        - Basic WOL support

    * Add USB suspend() and resume() methods, to go with WOL.
      Modeled on what stir4200 does.

Also, some of the messages are converted to the more conventional
style:  "ethN: message text", or driver model style before the
device is registered.

	* removed redundant MII code since CONFIG_MII is always set by Kconfig;
  	* updated the version string;
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Petko Manolov <petkan@nucleusys.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

SN9C10x driver updates.

Changes:

@ Fix the sysfs interface
@ Fix allocated minor number after device detection
+ Add "force_munmap" module parameter
+ Documentation updates
+ Add support for old VIDIOC_S_PARM_OLD and VIDIOC_S_CTRL_OLD ioctl's
Signed-off-by: Luca Risolia <luca.risolia@studio.unibo.it>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Use the new lock initializers DEFINE_SPIN_LOCK and DEFINE_RW_LOCK
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Add support for the Zaurus-compatible configuration of the
Olympus R1000 PDA.  (IDs from Todd Blumer, todd@sdgsystems.com)

Resolve a FIXME:  all the Zaurus support morphs into blacklist
entries when CDC Ethernet is enabled and Zaurus isn't (since the
Zaurus firmware falsely advertises itself as CDC conformant).
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Alexey Dobriyan <adobriyan@mail.ru>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This is a revised patch to fix a problem in the UHCI driver, in which the
compiler incorrectly optimizes certain accesses to DMA-able memory
addresses.  The patch reorganizes the code to use special accessor
routines including a compiler optimization barrier, and stores the results
in local variables to help prevent repeated accesses.  No use is made of
the "volatile" keyword.  :-)
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

If a command times out, we resubmit a retry. Some devices, however, buffer
everything we send and then eventually reply to a command we have timed out
already. We receive a bad tag, send a new command, device replies to the
one sent before, and so on without end.

The fix is to flush pending replies if tags mismatch (by reading them).
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This "Ours Technology" device incorrectly reports 100% residue on transferred data.
Patch originally sent by Daniel Drake <dsd@gentoo.org>, with slight modification by me.
Signed-off-by: Daniel Drake <dsd@gentoo.org>
Signed-off-by: Phil Dibowitz <phil@ipom.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch brings up to date the driver with the current stable development
source.  A bug with RTS not raising upon first open was fixed, Al Borcher's
circular write buffer from the pl2303 driver was implemented, and various
fixes/cleanups were made.
Signed-off-by: Lonnie Mendez <lmendez19@austin.rr.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

there's a bug in the acm driver's work arounds. This fixes it.
Signed-Off-By: Oliver Neukum <oliver@neukum.name>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

noop doesn't follow the instructions on where to insert a request,
because it uses q->queue_head instead of the *insert assigned. Clean it
up so it's easier to read.
Signed-off-by: Jens Axboe <axboe@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Doing some raid testing threw a bug in the scsi mid layer, because the
segment counts wasn't correct.  Initially I worried that we still had
problems in this area, but it turns out that is due to the raid usage of
bio clones.  Currently you have to hold on to the original bio as well,
since the clone only maintains a pointer to the bio_vec inside the
original bio.  If the original bio is freed first, the clone will have
garbage in its bio->bi_io_vec as soon as that memory is scribbled.

I think the best fix is to maintain flexibility and duplicate the io_vec
inside the clone as well. Attached patch does this.
Signed-off-by: Jens Axboe <axboe@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into suse.cz:/home/perex/bk/linux-sound/linux-sound

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Neil Horman <nhorman@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

- make needlessly global code static
- dn_fib.c: remove the write-only global variable dn_fib_info_cnt
- dn_fib.c: remove the unused global function dn_fib_rt_message
- dn_neigh.c: remove the unused global function dn_neigh_pointopoint_notify
- dn_timer.c: remove the fast timer code that isn't used
Signed-off-by: David S. Miller <davem@davemloft.net>

into nuts.davemloft.net:/disk1/BK/net-2.6

Use the new lock initializers DEFINE_SPIN_LOCk and DEFINE_RW_LOCK
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: David S. Miller <davem@davemloft.net>

into nuts.davemloft.net:/disk1/BK/net-2.6

Signed-off-by: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

into nuts.davemloft.net:/disk1/BK/tgraf-2.6

Signed-off-by: David S. Miller <davem@davemloft.net>

The netlink_post stuff Arjan removed was the only
user of this array.
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

do_tcp_sendpages() needs to do skb->truesize et al.
accounting just like tcp_sendmsg() does.

tcp_sendmsg() works by gradually adjusting these
accounting knobs as user data is copied into the
packet.

do_tcp_sendpages() works differently, when it allocates
a new SKB it optimistically adds in tp->mss_cache to
these values and then makes no adjustments at all as
pages are tacked onto the packet.

This does not work at all if tcp_sendmsg() queues a
packet onto the send queue, and then do_tcp_sendpages()
attaches pages onto the end of that SKB.  We are left
with a very inaccurate skb->truesize in that case.

Consequently, if we were building a TSO frame and it
gets partially ACK'd, then since skb->truesize is too
small tcp_trim_skb() will potentially underflow it's
value and all the accounting becomes corrupted.

This is usually seen as sk->sk_forward_alloc being
negative at socket destroy time, which triggers an
assertion check.
Signed-off-by: David S. Miller <davem@davemloft.net>

into nuts.davemloft.net:/disk1/BK/sparc-2.6

into nuts.davemloft.net:/disk1/BK/net-2.6

This patch fixes a problem I have been seeing since all the preempt
changes went in, which is that ppc64 SMP systems would livelock
randomly if preempt was enabled.

It turns out that what was happening was that one cpu was spinning in
spin_lock_irq (the version at line 215 of kernel/spinlock.c) madly
doing preempt_enable() and preempt_disable() calls.  The other cpu had
the lock and was trying to set the TIF_NEED_RESCHED flag for the task
running on the first cpu.  That is an atomic operation which has to be
retried if another cpu writes to the same cacheline between the load
and the store, which the other cpu was doing every time it did
preempt_enable() or preempt_disable().

I decided to move the thread_info flags field into the next cache
line, since it is the only field that would regularly be modified by
cpus other than the one running the task that owns the thread_info.
(OK possibly the `cpu' field would be on a rebalance; I don't know the
rebalancing code, but that should be pretty infrequent.)  Thus, moving
the flags field seems like a good idea generally as well as solving the
immediate problem.

For the record I am pretty unhappy with the code we use for spin_lock
et al. with preemption turned on (the BUILD_LOCK_OPS stuff in
spinlock.c).  For a start we do the atomic op (_raw_spin_trylock) each
time around the loop.  That is going to be generating a lot of
unnecessary bus (or fabric) traffic.  Instead, after we fail to get
the lock we should poll it with simple loads until we see that it is
clear and then retry the atomic op.  Assuming a reasonable cache
design, the loads won't generate any bus traffic until another cpu
writes to the cacheline containing the lock.

Secondly we have lost the __spin_yield call that we had on ppc64,
which is an important optimization when we are running under the
hypervisor.  I can't just put that in cpu_relax because I need to know
which (virtual) cpu is holding the lock, so that I can tell the
hypervisor which virtual cpu to give my time slice to.  That
information is stored in the lock variable, which is why __spin_yield
needs the address of the lock.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>