into pobox.com:/spare/repo/sata-hacks/qc-xfermode

Fix two bugs that causes the recently-added transfer mode code
to break on 64-bit platforms.  Make associated code more type-correct
in the process.

When using a completion, we need to clear the entry, and furthermore
clear the entry before we call the completion.

Make debugging output a bit more explicit.

Add MWDMA support, and rework pio/mwdma/udma mode setup.

In the lone test case for PATA support, ata_piix, MWDMA mode setting
does not appear to work here.  UDMA and PIO continue to work, so nobody
will really notice.  But beware.  Probably a driver problem, not
a bug in the core.

Also, doesn't bother writing to dummy timing registers on ICH5/6 SATA
anymore.

The ->qc_issue hook was designed to allow drivers to override some
or all of the actual delivery of the taskfile to hardware.

In the case of Promise, the hardware has its own packet format when doing
read/write DMA commands, but uses traditional ATA taskfile registers
for other types of commands.

Move more SCSI-specific code out of libata core.

In part of the effort to remove SCSI specifics from the libata
internals, remove references to cmd->use_sg.  cmd->use_sg
becomes ATA_QCFLAG_SG, and !cmd->use_sg becomes ATA_QCFLAG_SINGLE.

Convenience constant ATA_QCFLAG_DMAMAP is created when the programmer
wishes to refer collectively to ATA_QCFLAG_{SG,SINGLE}.

This is more conservative in general, and so applies to multiple
controllers.  Specifically it attempts to address irq-related issues
on the Intel ICH5/6 hardware.  On Intel ICH5/6, the BMDMA 'interrupt'
status bit will be set even on non-DMA commands, which software
(and I) did not expect.

This change clears pending interrupts once upon initialization,
and then each time ata_irq_on() is called.

This hook is used when an ATA controller wishes to use
hardware-specific methods of taskfile delivery, rather
than the standard method of bitbanging the ATA shadow
registers.

On Wed, Jun 30, 2004 at 01:22:21AM -0400, Jeff Garzik wrote:
>   CC      arch/x86_64/kernel/setup.o
> arch/x86_64/kernel/setup.c: In function `copy_edd':
> arch/x86_64/kernel/setup.c:415: error: `EDD_MBR_SIGNATURE' undeclared=20
> (first use in this function)
> arch/x86_64/kernel/setup.c:415: error: (Each undeclared identifier is=20
> reported only once
> arch/x86_64/kernel/setup.c:415: error: for each function it appears in.)
> arch/x86_64/kernel/setup.c:417: error: `EDD_MBR_SIG_NR' undeclared=20
> (first use in this function)
> make[1]: *** [arch/x86_64/kernel/setup.o] Error 1
> make: *** [arch/x86_64/kernel] Error 2

Arrgh.  On i386 it's in include/asm-i386/setup.h  On x86_64 it
belongs in include/asm-x86_64/bootsetup.h.

Patch below defines EDD_MBR_SIG_NR and EDD_MBR_SIGNATURE on x86_64.
Signed-off-by: Matt_Domsch <Matt_Domsch@dell.com>

into kernel.bkbits.net:/home/davem/net-2.6

Current 2.6.7 tree acts as if it is alway under memory pressure because
a recent change did a s/tcp_memory_pressure/tcp_prot.memory_pressure/.
The problem is tcp_prot.memory_pressure is a pointer, so it is always non-zero!

Rather than using *tcp_prot.memory_pressure, just go back to looking at
tcp_memory_pressure.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@redhat.com>

Remove the limitation of 1024 DM devices.
Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

dm-raid1.c: Declare fixed-sized (instead of variable-sized) arrays on the
stack in recover() and do_write().
Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

dm-raid1.c: Since kcopyd can currently only handle 1 source and up to 8
destinations, enforce a max of 9 mirrors when creating a dm-mirror device.
Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

kcopyd.c: client_add() can return void instead of an int, which will eliminate
an unnecessary error path in kcopyd_client_create().
Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

kcopyd.c: Remove unused #include.
Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

'strace' shows a problem with a missing release_task for self-reaping
clones that have been traced.  We need to defer releasing them until the
tracer is done with them, but if the tracer dies, we need to handle that
case gracefully too. 

We do that by having 'forget_original_parent()' generate a list of tasks
to release when this case happens.

Patch based on discussions on linux-kernel, and suggestions from Roland
McGrath <roland@redhat.com>.

Opening a CDROM device for writing no longer works, because cdrom_open()
returns -EROFS even if cdrom_open_write() succeeds.

This fixes it. 
Signed-off-by: Peter Osterlund <petero2@telia.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This fixes a corner-case NX bug: the x86 SMP kernel doesnt boot on SMP
Opterons if NX is enabled [and mem=nopentium is specified], due to
kernel-space NX protection preventing the SMP trampoline from being
executable. 

Since the SMP trampoline is a rare case of 'dynamic code' executed by
the kernel (it has to be below 640K so it cannot be part of the kernel
text itself), i've added the necessary infrastructure to enable/disable
executability of specific kernel pages. 

We cannot simply disable NX via the MSR because we've got the NX bits in
the kernel pagetables, which are set up before we do the SMP bootup. 
The NX bit in the pagetables is undefined if EFER.NXE is 0, so we cannot
count on NX-capable CPUs not faulting when they encounter them. 

I've tested the x86 kernel on a non-NX SMP x86 box and on an NX UP box,
on which i've also tested a simulated SMP trampoline, it all works fine. 

- add infrastructure to enable/disable executability of kernel pages

- make the SMP trampoline page executable.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

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

Cleanup the SK Fddi driver a little more.  Mark some functions as static,
and eliminate (or comment out) some that are defined but never used.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>

The conversion to ANSI, caused a warning because the mulitcast code needs
a cast.  dmi->dmi_addr is a u8 array, and fddi_addr is just a wrapper around a u8 array.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>

Hi,

Patch 2 of 2 to enable the smc91x driver to be used by the IBM Redwood5
and Redwood6 boards.

Enable smc91x driver to support IBM Redwood5 and Redwood6 boards
Signed-off-by: Dale Farnsworth <dale@farnsworth.org>

Hi,

Patch 1 of 2 to enable the smc91x driver to be used by the IBM Redwood5
and Redwood6 boards.

Move drivers/net/arm/smc91x.[ch] to drivers/net
Signed-off-by: Dale Farnsworth <dale@farnsworth.org>

This is a rather old patch which re-orders the teardown of PCMCIA
network devices.  Current device drivers remove the IO mappings,
interrupts, and free any PCMCIA windows before they unregister
themselves from the network layer.

This patch ensures that we first unregister from the network layer
before performing any teardown of resources or windows.

Note: the only card which has been tested in this patch is pcnet_cs.

Several network drivers have checks that they are only built with -O.
This breaks checking with sparse and other tools, and seems like a holdover from
when drivers were built out of tree and the kernel build system was less stable.
This patch gets rid of these.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>

Several drivers use '#if DEBUG' which is a warning under the sparse checker.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>

Add __user annotation to the device specific ioctl.

This started out from sparse warnings about calling with fddi_broadcast
that is declared const.  This fixes that and gets rid of some of the namespace
pollution of this driver by moving the predicate function is_individual, is_broadcast, ...
as inline's in the one file that uses them.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>

From: "Luiz Fernando N. Capitulino" <lcapitulino@prefeitura.sp.gov.br>

drivers/net/ne2.c does not compile without CONFIG_MCA_LEGACY set.

As CONFIG_MCA_LEGACY depends on CONFIG_MCA, we can use only
CONFIG_MCA_LEGACY, insteed of "MCA && MCA_LEGACY".
Signed-off-by: Luiz Capitulino <lcapitulino@prefeitura.sp.gov.br>
Signed-off-by: Andrew Morton <akpm@osdl.org>