On Fri, Jul 11, 2003 at 01:45:34PM +0530, V Ganesh wrote:
hi greg,
3 more device ids added to ipaq.c and ipaq.h
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing more.
This patch converts the ISD200 and Jumpshot drivers to use the new DMA-safe
buffer.
Greg, please apply.
I'd also like to take a moment to thank Alan Stern, who writes many of
these patches. Without his help, many of the improvements everyone has
seen over the 2.5.x series would not have been
This patch removes all of the mode-translation logic. It's no longer
needed, as the upper-level drivers now all issue the proper 10-byte
commands. This is a large patch, but what it's doing is removing a great
deal of unneeded code -- about 650+ lines removed, according to diffstat.
Those of
Title: 2003 °æÇâ º£À̺ñ Æ÷Åä Æ佺Ƽ¹ú
O º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´ÙO
On Sun, Jul 13, 2003 at 09:05:42PM -0700, Matthew Dharm wrote:
Try playing with 'dd' -- try transferring one block of various sizes.
Thus, things like:
dd if=/dev/sda of=/dev/null count=1 bs=1M
dd if=/dev/sda of=/dev/null count=1 bs=64K
See if you can find a blocksize
Hi all,
I've managed to get my stuff running on 2.5 (pfew ... :-)
The first experiments show that the camera does *not* die
when doing a cat /dev/hda /dev/null on 2.5. Interesting !
I tried a couple of hundred MB's and the camera still worked.
(this would kill the webcam immediately
Hi,
Here are some USB bugfixes and updates against 2.4.22-pre5. There are a
number of resyncs here with drivers that are already in 2.5, and a new
USB host controller driver was added. Also, the unusual_devs.h list for
usb-storage devices is now in sync with 2.5 thanks to Alan Stern, which
ChangeSet 1.1074.1.19, 2003/07/13 22:51:44-07:00, [EMAIL PROTECTED]
[PATCH] USB: more ids for ipaq
3 more device ids added to ipaq.c and ipaq.h
Added ids for the Rover P5, Toshiba E310 and E335. Thanks to
Matthijs van der Molen, Pavel Stoliarov, Tod B. Schmidt and
Matt Hartley.
ChangeSet 1.1074.1.13, 2003/07/09 21:41:09-07:00, [EMAIL PROTECTED]
[PATCH] USB: Final reconciliation for unusual_devs.h in 2.4
This final patch for 2.4 will make unusual_devs.h identical with the
version in 2.5, so from now on new entries can be made to both files in
parallel. This simply adds
ChangeSet 1.1074.1.17, 2003/07/10 14:34:23-07:00, [EMAIL PROTECTED]
[PATCH] USB: Adding DSS-20 SyncStation to ftdi_sio
Patch for 2.4.22 ftdi_sio to add DSS-20 SyncStation to ftdi_sio - the
SyncStation is the usb cradle for the Sony Ericsson P800 phone.
drivers/usb/serial/ftdi_sio.c |3 +++
ChangeSet 1.1074.1.12, 2003/07/09 21:40:56-07:00, [EMAIL PROTECTED]
[PATCH] USB: Reconcile unusual_devs.h for 2.4 and 2.5
This patch for 2.4 removes the now-unneeded code for handling START-STOP
commands and fixes up the unusual_devs.h file. Instances of the
START_STOP flag are removed as are
ChangeSet 1.1074.1.18, 2003/07/10 14:34:28-07:00, [EMAIL PROTECTED]
[PATCH] USB: ax8817x.c - add Intellinet USB 2.0 Ethernet device ids
Thanks to Zeph for submitting the ids and testing.
drivers/usb/ax8817x.c |4
1 files changed, 4 insertions(+)
diff -Nru a/drivers/usb/ax8817x.c
ChangeSet 1.1074.1.14, 2003/07/09 21:41:24-07:00, [EMAIL PROTECTED]
[PATCH] USB: Updates for unusual_devs.h
These changes to unusual_devs.h can be applied to both 2.5 and 2.4. They
reflect reports from users in response to the new kernel log messages
about unneeded entries in the file.
ChangeSet 1.1074.1.10, 2003/07/09 21:34:08-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb_string(), don't use bogus ids
This is the 2.4 version of that patch I just sent for 2.5,
making sure usbcore doesn't use un-initialized memory for
its language IDs.
drivers/usb/usb.c |2 +-
1 files
ChangeSet 1.1079.1.3, 2003/07/14 09:48:18-07:00, [EMAIL PROTECTED]
[PATCH] USB: Implement US_FL_FIX_CAPACITY for 2.4
On Wed, 9 Jul 2003, Greg KH wrote:
After applying all three patches here (as49, as50, as51) I get the
following build error:
In file included from usb.c:190:
ChangeSet 1.1074.1.11, 2003/07/09 21:34:21-07:00, [EMAIL PROTECTED]
[PATCH] USB: usbnet updates
This patch pulls some more 2.5 changes into usbnet:
- Adds a read the endpoint descriptors mode.
* Finally resolves the ARM-Linux usb-eth mess, where
sa1100 and pxa2xx drivers are
ChangeSet 1.1074.1.15, 2003/07/09 22:17:36-07:00, [EMAIL PROTECTED]
[PATCH] USB: patch for sl811 usb host controller driver
Ok, I have get rid of the typedefs and make it build on 2.4.21.
I'm not try to merge this with the existing sl811 driver, I modifed most
of it for support isochronous
ChangeSet 1.1074.1.16, 2003/07/09 22:18:06-07:00, [EMAIL PROTECTED]
[PATCH] USB: fix up previous sl811 patch.
drivers/usb/host/Config.in |5 +++--
drivers/usb/host/sl811.c |6 +++---
2 files changed, 6 insertions(+), 5 deletions(-)
diff -Nru a/drivers/usb/host/Config.in
Hi all,
I'm currently writing a very simple USB driver for a printer.
I've a few rookie questions that I hope you guys can give me some
pointers.
First of all, I decide not to use MOD_INC_USE_COUNT/MOD_DEC_USE_COUNT
coz I read it somewhere that it's no longer necessary if I define
On Mon, 14 Jul 2003, Gary Ng wrote:
Hi all,
I'm currently writing a very simple USB driver for a printer.
I've a few rookie questions that I hope you guys can give me some
pointers.
Okay. But bear in mind that there already is a USB printer driver.
First of all, I decide not to use
emanuel stiebler said:
Hi all,
anybody out here managed to get the sources of the Cypress ATA/CF
development board to compile with the SDCC ?
I don't know the exact details of that board, but you might try posting
specific error messages to one of the SDCC lists. I don't think that the
Cypress
Thank you so much for such a detail explaination.
If I understand correctly, after I open() a device
and then unplug the device, I should still have
the device structure hanging around somewhere in
the memory and that should be disallocated upon close()
called on the same fd. In this case, if I
Note that on SMP architectures there is a race between open() and
disconnect(). You will have to use a static semaphore to prevent the
possibility of someone calling open() (thereby trying to access your data
structures) at the same time a disconnect() occurs (thereby freeing
those same
Hi,
Right after I send out the last USB updates, I got this one from the
usb-storage people. It seems pretty serious, so I'm sending this one
out as a single patch.
Please pull from: bk://kernel.bkbits.net/gregkh/linux/marcelo-2.4
The individual patch will be sent in a follow up message to
Am Montag, 14. Juli 2003 22:54 schrieb Gary Ng:
Thank you so much for such a detail explaination.
If I understand correctly, after I open() a device
and then unplug the device, I should still have
the device structure hanging around somewhere in
the memory and that should be disallocated
ChangeSet 1.1118, 2003/07/14 13:52:30-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage US_FL_FIX_CAPACITY fix
Pat LaVarre uncovered a bug where you could throw a well-formed (but
arguably meaningless) INQUIRY command at a device via the sg interface
and OOPS the usb-storage driver. This
Hi,
I'm trying to get USB bluetooth dongle to work on a toshiba P133
laptop (usb-ohci.) Bluetooth communications ('pan') work for a short
time. The dongle is unresponsive until re-inserted. This often
results in an oops.
I ran such an oops trough ksymoops. I gather the lud-list would be
I see! Thanks for your help!
Regards,
Gary
--- Oliver Neukum [EMAIL PROTECTED] wrote: Am Montag, 14. Juli
2003 22:54 schrieb Gary Ng:
Thank you so much for such a detail explaination.
If I understand correctly, after I open() a device
and then unplug the device, I should still have
I´m not in this list. In earlier Versions of Kernel 2.5., in Version
2.4.21-pre7 and in Windows XP :( it works. It is a Maxtor 120GB
Harddisk-drive connected to a USB2 usb-atapi-interface. After some
seconds of powering up, the traffic LED turns on and stays lid. But the
device hangs. No access
Did you ever get a log from 2.4?
Matt
On Mon, Jul 14, 2003 at 09:14:34AM -0400, Adam Kessel wrote:
On Sun, Jul 13, 2003 at 09:05:42PM -0700, Matthew Dharm wrote:
Try playing with 'dd' -- try transferring one block of various sizes.
Thus, things like:
dd if=/dev/sda of=/dev/null
Two small updates:
- Report short control reads correctly in an exotic case
that our regression tests cover. (Haven't run them with
ohci for a long time, it seems...)
- IRQ non-delivery bugs (ACPI, APIC, etc) can prevent urbs
from unlinking. This prints a warning when that sort of
Oliver Neukum wrote:
Hi all,
I've managed to get my stuff running on 2.5 (pfew ... :-)
The first experiments show that the camera does *not* die
when doing a cat /dev/hda /dev/null on 2.5. Interesting !
I tried a couple of hundred MB's and the camera still worked.
(this would kill the webcam
I noticed that Viro's use alloc_etherdev patch left a
small problem: only usbnet did SET_NETDEV_DEV, and
that used the wrong driver model device.
This has all the usb network drivers use SET_NETDEV_DEV,
so the /sys/class/net/*/{device,driver} files link to the
relevant usb interface and to its
Ferenc-Jan wrote:
Hi,
I'm trying to get USB bluetooth dongle to work on a toshiba P133
laptop (usb-ohci.)
The 2.4 OHCI driver had a number of problems that appeared
much more reliably with slow hardware. The 2.6 one should
have resolved quite a lot of those.
EIP; c481e11a
The original code needed some updates to work properly with
the USB Device Controller found in Intel's PXA 2xx processors.
- SET_INTERFACE and SET_CONFIGURATION involve hardware
automagic: all endpoints get reset. This is a PITA,
and will likely get more work. (Seems like the reset
is
The original code needed some updates to work properly with
the USB Device Controller found in Intel's PXA 2xx processors.
- SET_INTERFACE is effectively unusable. So the driver
now has a minimalist mode, with none of the bells and
whistles of CDC.
- The config symbol will be
36 matches
Mail list logo
