- 16 Sep, 2002 40 commits
-
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/sparc-2.5
-
Pete Zaitcev authored
-
David S. Miller authored
-
David S. Miller authored
-
bk://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Note the cdc-ether.c driver does NOT work properly now, someone who understands the interface mess in that driver needs to fix it up.
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
This adds the requirement that the usb-serial drivers call usb_register() and usb_unregister() themselves, instead of having the usbserial.c file do it. Step one in moving the usbserial.c code to being a "class" :)
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Mark W. McClelland authored
Update the ov511 driver to version 1.62: o Update email address o Remove some dead code and fix some harmless typos o New device: Alpha Vision Tech. AlphaCam SE o Fix assignment of ov->proc_button->owner to not cause NULL pointer deref (credit: Oleg K.) o Support I2C read/write ioctl()s via V4L (credit: Oleg K.) o Add OV518-specific register dump code o New snapshot reset sequence; old one was causing erroneous I2C writes (credit: Oleg K.) o OV6630 needs different register 0x14 settings than OV6620 o Don't print palette errors by default o Detect OV518 cameras that have packet numbering enabled by default and set ov->packet_numbering accordingly. This should fix the problems some users were having with babble (USB error -75) and cameras not working at all.
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/gregkh-2.5
-
H. Peter Anvin authored
I noticed a kluge had been put into 2.5.35, to cover up *one* of the errors caused by a particular bug that was introduced when Patrick Mochel split up arch/i386/kernel/setup.c: he incorrectly thought the AMD-defined CPUID levels were AMD-specific; they're not -- every other x86 vendors *including* Intel uses them as well. This also adds the "i686" hack for TM5xxx that was added in 2.4 recently.
-
Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Matthew Dharm authored
This patch removes attempts to clear halts on a control endpoint (think about it for a minute if you don't see why this is pointless....) and also adds return-code checks for all places where halts are cleared. This _should_ be just redundant code, but recent tests suggest that this is, in fact, not the case. People should _heavily_ test this patch. I'm going to pause here for a while (in the patch stream) until we've got this sorted out -- initial results on my test setup seem to show some problems still remain. Where those problems are (HCD or usb-storage) remains to be seen.
-
Matthew Dharm authored
This patch fixes up some minor compilation problems.
-
Matthew Dharm authored
This patch converts all uses of page_addres() to the sg_address() macro. This will make backporting to 2.4 easier, as well as eliminate lots of redundant code.
-
Matthew Dharm authored
This patch removes tests of urb->status for EINPROGRESS. As was pointed out, that's not such a good idea, for a variety of reasons. In the process, a semaphore became useless.
-
Alan Stern authored
Here's a very simple patch that can go into the source tree right away. It just fixes some occurrences of the scsi result code GOOD to GOOD << 1 in isd200.c.
-
Christoph Hellwig authored
-
Stephen Lord authored
Date: Mon Sep 16 09:10:25 PDT 2002 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:127481a linux/fs/xfs/linux/xfs_lrw.c - 1.166 linux/fs/xfs/support/time.h - 1.7 linux/fs/xfs/linux/xfs_aops.c - 1.5
-
Russell Cattelan authored
Date: Fri Sep 13 14:59:34 PDT 2002 Workarea: chuckle.americas.sgi.com:/build/lxfs-cvs/2.5.x-xfs-VER Author: cattelan The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:127397a linux/fs/xfs/linux/xfs_version.h - 1.2
-
http://linus.bkbits.net/linux-2.5Christoph Hellwig authored
into dhcp212.munich.sgi.com:/home/hch/repo/bk/linux-2.5-xfs
-
Pam Delaney authored
This updates the Fusion-MPT driver to the latest stable version. Changes affect the driver source only. Major Changes: Reworked the calls save_flags, cli, restore_flags to 2.5 format. Modified DV invocation and to handle illegal bus configuration Negotiation settings honor NVRAM Bug Fix: Pushing F/W onto part during driver unload. Bug Fix: Force F/W reset for 1030 on driver load. Bug Fix: F/W download algorithm. Bug Fix: Found a memory leak in mptctl.c Bug Fix: Forcing data direction for reads and writes (sg issue) Bug Fix: Wrong mask in Inquiry data ANSI version Minor Changes: Modified the debug and logging statements of the driver Upgraded the MPI include files (lsi/)
-
Ingo Molnar authored
This fixes a number of sys_execve() problems: - ptrace of thread groups over exec works again. - if the exec() is done in a non-leader thread then we must inherit the parent links properly - otherwise the shell will see an early child-exit notification. - if the exec()-ing thread is detached then make it use SIGCHLD like the leader thread. - wait for the leader thread to become TASK_ZOMBIE properly - wait_task_inactive() alone was not enough. This should be a rare codepath. now sys_execve() from thread groups works as expected in every combination i could test: standalone, from the leader thread, from one of the child threads, ptraced, non-ptraced, SMP and UP.
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Ben Collins authored
Syncronizes with our SVN repo. Merged in all changes from your tree.
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Jens Axboe authored
Attribution goes to Petr Vandrovec for finding and solving this one. You probably read the mail you were cc'ed on, so I'll just mention that this patch makes sure that the irq disabling and enabling is perfectly balanced in the probing path. I've also looked at the multiple irq chain problem you mentioned, and as far as I can see we are never touching the 2nd chain from within the first one. So should be ok. I'm also including the unexpected interrupt prinkt removal.
-