Hi Greg,
This patch adds one more device to the list and removes redundant check in
probe(); It is bulky because i've run the thing through indent long
time ago. Oh, and the usual limitation to GPL v2 only...
Petko
On Tue, 23 Jul 2002, Pete Zaitcev wrote:
> This got
Hello Greg,
Thanks for your reply.
As I would be dealing with only 2 devices I was thinking that these two
class drivers can be included as separate files and the probe functions in
them can be probe_scanner() and probe_printer(). The USBD based on the
device class can call either of these probe
> From: Petko Manolov <[EMAIL PROTECTED]>
> Date: Mon, 22 Jul 2002 21:51:39 -0700 (PDT)
> Do you by any chance know the vendor and device id of that Melco device?
The patch was attached to the bug report. This part was sane:
@@ -72,11 +72,15 @@
/* Define these values to match your device */
Hi,
USB is a host-device based protocol.
If one computer can act as a device(there are various methods to do it), It can be
enumerated at the other computer host and you can
communicate.
Usually on PC side you can see Host port. But there are some add on cards, which will
give you device port.
Quoting Oktie Hassanzadeh <[EMAIL PROTECTED]>:
> Is it possible to connect two computers with a simple cable or there
> should necessarily be a special device for it? I know that there are some
> cables with a special device that connect two computers in linux and their
> driver is available in u
On Tue, 23 Jul 2002 14:48, Oktie Hassanzadeh wrote:
> Dear All,
> I would like to connect two computers via USB port and USB cable and I
> want to write a program for handling this connection (in Linux) . Is any
> body here who could help me and let me know what is done and what I should
> do?
> The following check seems redundant:
>
> static void * rtl8150_probe(struct usb_device *udev, unsigned int ifnum,
> const struct usb_device_id *id)
> {
> ..
> if ((udev->descriptor.idVendor != VENDOR_ID_REALTEK) ||
> (udev->descriptor.idProduct
Dear All,
I would like to connect two computers via USB port and USB cable and I
want to write a program for handling this connection (in Linux) . Is any
body here who could help me and let me know what is done and what I should
do? Is it possible to connect two computers with a simple cable o
Petko:
The following check seems redundant:
static void * rtl8150_probe(struct usb_device *udev, unsigned int ifnum,
const struct usb_device_id *id)
{
..
if ((udev->descriptor.idVendor != VENDOR_ID_REALTEK) ||
(udev->descriptor.idProduct != PRO
Greg KH wrote:
> On Sat, Jul 20, 2002 at 10:16:48PM +0200, Oliver Neukum wrote:
>
>>>Does anyone/anything use this file? The driverfs changes kind of make
>>>this file redundant. Does anyone really want it back?
>>
>>So what else can go into driverfs ?
I'd rather know what _should_ go into it
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.692 -> 1.693
# drivers/usb/misc/ti
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.690 -> 1.691
# drivers/usb/misc/ri
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.689 -> 1.690
# drivers/usb/input/h
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.691 -> 1.692
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.686 -> 1.687
# drivers/usb/core/me
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.688 -> 1.689
# drivers/usb/core/us
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.687 -> 1.688
# drivers/usb/host/oh
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.685 -> 1.686
# drivers/usb/host/uh
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.684 -> 1.685
# drivers/usb/serial/
Pull from: http://linuxusb.bkbits.net/linus-2.5
drivers/usb/core/message.c | 12 +-
drivers/usb/core/usb.c | 73 ++---
drivers/usb/host/ohci-sa.c |1
drivers/usb/host/uhci-hcd.c |4
drivers/usb/input/hid-ff.c |2
drivers/usb/misc/rio500.c
On Mon, Jul 22, 2002 at 10:53:24AM -0700, Christopher Hoover wrote:
> Unlike previous version, this one doesn't oops and is perspicuous.
> Please apply.
Applied, thanks.
greg k-h
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek
Matthew Dharm wrote:
> See my patches from yesterday for the fix for this.
Yep. That did it. Thanks.
-ch
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
__
On Sat, Jul 20, 2002 at 12:25:46PM -0700, David Brownell wrote:
> Lately I get warnings whenever I plug in a device with
> a HID interface ... when force feedback support is
> configured, that's what it does.
>
> Yeech ... that should should at most be a dbg().
>
> Patch enclosed.
Applied, than
On Sun, Jul 21, 2002 at 09:55:10PM -0700, Christopher Hoover wrote:
> This is needed by 2.5.26-rmk1. greg k-h: please apply.
Applied, thanks.
greg k-h
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.c
On Sat, Jul 20, 2002 at 10:52:32AM -0700, David Brownell wrote:
> This patch updates the kerneldoc for usb_set_interface()
> to capture the point that it must not be called while
> any URBs are pending to endpoints in that interface.
> (Else state in the hcds, and devices, can get confused.)
>
>
See my patches from yesterday for the fix for this.
Matt
On Mon, Jul 22, 2002 at 02:00:36PM -0700, Christopher Hoover wrote:
> This device worked in 2.5.24-rmk1.
>
> -ch
>
>
> # modprobe usb-storage
> Initializing USB Mass Storage driver...
> usb.c: registered new driver usb-storage
> scsi0 :
This device worked in 2.5.24-rmk1.
-ch
# modprobe usb-storage
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: TREK2000 Model: TD-G2 Rev: W1.1
Type: Direct-Access
Unlike previous version, this one doesn't oops and is perspicuous.
Please apply.
--- linux-2.5.26-rmk1/drivers/usb/core/usb.cTue Jul 16 16:49:34 2002
+++ linux-2.5.26-rmk1-ch1/drivers/usb/core/usb.cMon Jul 22 10:49:05 2002
@@ -1221,56 +1221,59 @@ int usb_set_address(struct usb_device
The second strchr was returning 0.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of David Brownell
> Sent: Monday, July 22, 2002 8:03 AM
> To: Christopher Hoover
> Cc: [EMAIL PROTECTED]
> Subject: Re: [linux-usb-devel] [PATH] set_device_descrip
> I will not take new patches for MixedCase variables, sorry.
Sigh. OK, I'll change it.
> And what exactly is this patch trying to fix? What is wrong
> with the existing code?
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=102732358205252&w=2
> Do you have a specific device that th
On Sat, Jul 20, 2002 at 01:13:11PM -0700, David Brownell wrote:
>
> Actually .../bus/usb/drivers/... is empty in 2.5.26
> so it's not quite not yet redundant. On the other hand,
> it _should_ become redundant, and I won't miss it.
> (So long as the docs etc stay up to date...)
That directory wi
On Sat, Jul 20, 2002 at 10:16:48PM +0200, Oliver Neukum wrote:
>
> > Does anyone/anything use this file? The driverfs changes kind of make
> > this file redundant. Does anyone really want it back?
>
> So what else can go into driverfs ?
Don't know, I recently added the serial number, manufact
On Mon, Jul 22, 2002 at 02:03:52AM -0700, Christopher Hoover wrote:
> This version doesn't oops and is perspicuous.
>
> I haved tested it in the "both strings" case (which made the old code
> oops) and in the "no strings" case.
>
> -ch
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
> --- linux-
Hi all!
I'm working on a usb-storage driver for the MaxTech Moveman SSP100 mp3
player, similar to the Lexar Jumpshot driver in that it uses an
extremely simple read/write block interface to access the flash.
The firmware seems to be using some demo code from STMicroelectronics
since the device
Dan Streetman wrote:
> On Sat, 20 Jul 2002, David Brownell wrote:
>
>
>>Comments? Additional/related points? Volunteers?
>
>
> If nobody else volunteers I can work on UHCI at least. I've been
> meaning to see if I can get Control queueing into UHCI anyway.
Yeah, that's a similar issue. Ev
On Sat, 20 Jul 2002, David Brownell wrote:
>Comments? Additional/related points? Volunteers?
If nobody else volunteers I can work on UHCI at least. I've been
meaning to see if I can get Control queueing into UHCI anyway.
I'll start reviewing the UHCI driver...
--
Dan Streetman
[EMAIL PRO
Christopher Hoover wrote:
> This version doesn't oops and is perspicuous.
>
> I haved tested it in the "both strings" case (which made the old code
> oops) and in the "no strings" case.
What was the problem with the old code though?
That was tested in all four cases ... was it just that
you h
This version doesn't oops and is perspicuous.
I haved tested it in the "both strings" case (which made the old code
oops) and in the "no strings" case.
-ch
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--- linux-2.5.26-rmk1/drivers/usb/core/usb.cTue Jul 16 16:49:34 2002
+++ linux-2.5.26-rmk1-ch1/d
set_device_description is oopsing with a null pointer at boot for me on
2.5.26-rmk1 with ohci-hcd on sa-. The problem apparently is the new
code that computes a clever name for the device -- a "return" statement
after the first sprintf() gets around the problem. If the problem isn't
obvious
39 matches
Mail list logo
