Make IDE PCI drivers register /proc/ide/<chipset> entries themselves.

Additionally ide_end_drive_cmd() contains all functionality of this function.

When ide_remove_proc_entries() is called, driver specific /proc/ide/hdx/
entries have been already removed by ->cleanup()->ide_unregister_subdriver().

Remove "hdx=flash" (ignored since 2.5.63) and "hdx=slow"
(ignored since 2.5.41) kernel parameters.

Also remove "slow" entry from /proc/ide/hdx/settings
and "ata_flash", "nobios" and "slow" fields from ide_drive_t.

From: Andi Kleen <ak@suse.de>

This fixes some more problems introduced by the IA32e merge on x86-64

- Make it compile on UP again.
- Let the microcode driver build as a module

Remove an unneeded WSET() which snuck in there.

The sysrq-T output currently tries to display the mimimum amount of free
stack which each task has ever had available.  It has been busted for years,
because we forgot to zero out the stack when it is first created.

Fix that up, adding a conig option for it.

If the option is disabled, or the arch is not x86 then the free stack usage
will display as zero.

From: Herbert Poetzl <herbert@13thfloor.at>

sys_ptrace() for v850, if pid == 1, doesn't put the struct task_struct
(child), the following patch should fix that ...

From: Arjan van de Ven <arjanv@redhat.com>

fix obvious non-C-standard stubs on ppc64

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

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

into redhat.com:/spare/repo/net-drivers-2.5

This fixes the behaviour of the pmac "macio" IDE driver when a DMA
transfer happen to get less data out of the device than expected when
setting up the DMA commands (the device underruns).  This is very common
with recent ATAPI stuffs and used to cause problem & disable DMA.  This
patch fixes the way we handle that condition, thus also fixing DVD
burning on a bunch of recent pmacs. 

Some barriers between setting up the DMA regions and writing the
descriptor addresses would be most useful.

I had some in my 2.4 version but they got lost someway, probably me not
properly merging with davem at this point.  The 970 is definitely more
agressive at re-ordering stores than previous CPUs...

Here is a patch adding some (probably too much, but better safe than
sorry).

into kroah.com:/home/greg/linux/BK/usb-2.6

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

People ask how to write the CIS on a SmartMedia card using an sddr09
reader/writer.  The patch below documents the required command (but does
not add the code).

Two years ago or so I used this to fix the CIS on a card that my camera no
longer wanted to accept.  A Linux utility to do this might be useful, but
the problem always is that we do not really have a good mechanism.

How does one tell a driver that it has to do something special?  Add yet
another ioctl?

The main item in this patch is the conversion of the UHCI driver from
using the old usb.h logging macros to the new driver-model dev_xxx
macros.

There are a few other minor changes too: updated version number, author,
copyright, and maintainer information, removed some unneeded error
messages, added some line breaks, added a convenience macro for the device
pointer.

On Fri, 20 Feb 2004, Gustavo Guillermo wrote:

> Ok, I tested the patch, The camera works, just as in the old Kernel,
> Thanks, I'm including as an atachment the /proc/bus/usb/devices from
> kernel 2.4.x and 2.6.x, and the kernel log for 2.4.x, but ooops, I forgot
> to biold 2.4.x with full debug, if someone need it I will do.
>
> Please include this FIX in the Next Release.

Greg, I now feel confident that this patch should be applied.

On Thu, 19 Feb 2004, Agustin De Igartua wrote:

> Initializing USB Mass Storage driver...
> usb-storage: This device (04e6,0002,0100 S 06 P 50) has unneeded SubClass and Protocol entries in unusual_devs.h
>    Please send a copy of this message to <linux-usb-devel@lists.sourceforge.net>scsi0 : SCSI emulation for USB Mass Storage devices

Thank you for sending this in.  Greg, here's the patch.

There are no known failures due to this bug, but it's clearly a bug and
given the right compiler, it could trigger and lead to bad stack traces etc.

I incorporated (at least in spirit I hope) hch's suggestions on the fixup code
put in some kfrees that I was missing and static for sn_alloc_pci_sysdata
(thanks Bartlomiej Zolnierkiewicz).  White space clean up.

Cleanup the SN setup.c file.  Add __init and static to functions where
required.

Here is a patch to clean up some of the Altix header files and includes.

I've run the patch past the appropriate people at SGI and they seem happy
with the changes.

From: Arnd Bergmann <arnd@arndb.de>

Christian Bornträger noticed that the kernel can crash after <SysRq>-T.  It
appears that the show_task function gets called for all tasks, which does
not work if one of the tasks is running in a system call on another CPU.
In that case the result of thread_saved_pc and show_stack is undefined and
likely to cause a crash.

For tasks running in user space on other CPUs, show_task() is probably
harmless, but I'm not sure if that's true on all architectures.

The patch below is still racy for tasks that are about to sleep, but it
demonstrates the problem.

show_task() is preinting negative numbers for free stack due to arithmetic
against the wrong pointer.

Fix that up, and clean up a few related things.

show_task still has bogus code which atempts to work out how much stack the
task has ever used - it cannot work because we don't actually zero out the
stack pages when allocating them.  We should fix that, or take it out.

I find this handy sometimes: it makes the oops output include info as to
whether the user has selected CONFIG_PREEMPT, CONFIG_SMP or, particularly,
CONFIG_DEBUG_PAGEALLOC.  It can save one email round-trip.

From: "Martin J. Bligh" <mbligh@aracnet.com>

Make irqbalance into a config option - some people (jgarzik, arjan, etc)
wanted to be able to disable it and do things from userspace instead.  This
patch allows each camp to do their own thing, which seems fair ;-)

From: "Martin J. Bligh" <mbligh@aracnet.com>

Disallow NUMA on the i386 PC subarch (it doesn't work, nor was it intended
to).

From: "Martin J. Bligh" <mbligh@aracnet.com>

Makes sure pfn_to_nid is defined for all combinations of subarches, and that
it's defined before it's used so we don't run into implicit declaration
problems.

From: "Martin J. Bligh" <mbligh@aracnet.com>

Fix pfn_valid for architctures with discontiguous memory.  This only
changes the NUMA definition, and it leaves the NUMA-Q definition as was,
because it's faster that way, it's in hotpaths, and our memory is always
contiguous.