Hi, All:
I found (or, rather, our users found and I confirmed) that if a disconnect
happens at the right time, cat /proc/bus/usb/devices is likely to crash.
It can fail in several places, but mostly it's related to a references
to struct usb_device which was freed.
It looks that this problem was
Dear Horst,
if you plan to use ub, it would be best for us to work it out of band.
The first thing you need to do is to switch to an -mm kernel, because
a few essential ub patches are stuck in AKPM's tree. I do not recommend
to use 2.6.9-rc3 with ub. Try that and write me if it fails after that.
Hi Alan,
> I've got a patch that's almost ready for submission, to change the way USB
> devices are initialized. The trickiest part is determining the maxpacket
> value for endpoint 0. The number is fixed at 8 for low-speed and 64 for
> high-speed devices, but for full-speed devices it can be an
Date: Fri, 08 Oct 2004 14:21:30 -0700
The current scheme (the "Linux" scheme) goes like this:
Reset the device
Set endpoint 0 maxpacket to {8, 8, 64} for {low, full, high}-speed
Send SET-ADDRESS (an 8-byte SETUP with no message body)
Send 8-byte GET-DEVICE-DESCRIPTOR
Begin forwarded message:
Date: Fri, 08 Oct 2004 09:17:27 -0400
From: Horst von Brand <[EMAIL PROTECTED]>
To: Linux Kernel Mailing List <[EMAIL PROTECTED]>
Subject: 2.6.9-rc3 and pendrive
This is FC2 up to date plus self-compiled 2.6.9-rc3 as of two days back BK
merged with ipw2200 tree on a T
Am Donnerstag, 7. Oktober 2004 23:19 schrieb Stefan Rompf:
> Hi,
>
> ehci_hub_resume() reads the hub port registers during resume. However, on S3
> or swsusp the root hub loses power, making read data invalid and forcing the
> user to replug all devices. Saving the data in memory during suspend
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.2000 +0200]:
> No -- I said the fix _isn't_ in 2.6.9-rc3.
Sorry, I misread you.
> The patches I sent were for 2.6.9-rc3. The first one might work all right
> 2.6.8.1 but the second one definitely won't. Below is a version of the
> second p
On Fri, 8 Oct 2004, martin f krafft wrote:
> > Sometimes errors like this and the ones above are just temporary.
> > The device takes a moment to warm up and start working right. You
> > only need to worry about it if the device doesn't work in the end.
>
> I do have another device (a USB servo
Am Freitag, 8. Oktober 2004 18:08 schrieb Alan Stern:
> The question is, in what order should the schemes be tried? The
> conservative approach would be to use the Linux scheme twice, then the
> Windows scheme twice. But maybe that's not such a good choice; the Sony
> camcorders respond to the
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.1918 +0200]:
> What kind of device is this, can you say? And did it used to work with
> earlier versions of 2.6? If it did, can you pinpoint at which release it
> stopped working?
It's a new device, so I have not used it with anything othe
Greg:
A recent patch introduced this reference counting leak.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/core/usb.c 1.293 vs edited =
--- 1.293/drivers/usb/core/usb.c2004-09-28 13:19:22 -04:00
+++ edited/drivers/usb/core/usb.c 2004-10-08 13:05
On Fri, 8 Oct 2004, martin f krafft wrote:
> Okay, let's go after this, I disabled all modules that I could and
> am now going to try to see how I can reproduce the error. USB
> debugging is enabled in the kernel.
>
> To recap, the whole thing is about weird messages about ep0in
> timeouts and th
I've got a patch that's almost ready for submission, to change the way USB
devices are initialized. The trickiest part is determining the maxpacket
value for endpoint 0. The number is fixed at 8 for low-speed and 64 for
high-speed devices, but for full-speed devices it can be any power of two
Jürgen Heinrich wrote:
Hallo!
Because of the not working ALi based USB 2.0 cards I decided to buy two
new cards using NEC chips. (My other "no name" cards with NEC chip
are working fine with Linux.)
I bought two Tekram DC-602T USB 2.0 cards.
(Chip is NEC D720100AGM, same as on my other cards.)
But
Okay, let's go after this, I disabled all modules that I could and
am now going to try to see how I can reproduce the error. USB
debugging is enabled in the kernel.
To recap, the whole thing is about weird messages about ep0in
timeouts and the inability to use the affected device. With USB
debuggi
Small W996[87]CF documentation updates.
Signed-off-by: Luca Risolia <[EMAIL PROTECTED]>
diff -uprN -X dontdiff a/Documentation/usb/w9968cf.txt b/Documentation/usb/w9968cf.txt
--- a/Documentation/usb/w9968cf.txt 2004-08-14 07:37:26.0 +0200
+++ b/Documentation/usb/w9968cf.txt 2004-1
Hi Michael,
Michael Moedt writes:
> Q. Where are DPRINTK and MEMDUMP typically defined?
>
These are some of my private debugging macros. You can safely remove
them or:
#define DPRINTK(fmt...) printk(KERN_DEBUG fmt)
I should better remove them or convert the more important ones into
ohci_dbg() cal
Hi,
> 1) What is this WARN_ON() and BUG_ON()? I've never seen them. I suspect
> their purpose but I need to be sure.
They are the kernel's version of assert(), they trigger if the confition
is true (which is opposite to assert). WARN isn't fatal while BUG is.
They are in include/asm-generic/bug.h
Hi Michael,
Michael Moedt writes:
> I've got a couple comments and questions:
>
> 1. The ohci-isp1362.tgz files won't work without the ohci-emu patch.
> Should these be bundled together?
> (note: ohci-regs.h is added by both)
>
Yes, I hope I find some time to do this. But for now I'm too busy w
Hi Lothar,
I have some questions (again...) about your work.
I was looking at your isp1362 code, and I even made some kind of diagram
that pictures the flow of your code (it's not very complete but if you
want it, just tell me). I think I'm ready to port my driver to your
scheme, but I don't unders
On Fri, 2004-10-08 at 02:57, Christoph Torens wrote:
> Hi,
>
> On Mon, 04 Oct 2004 15:10:47 +0100, Ian Campbell <[EMAIL PROTECTED]>
> wrote:
>
> > Hi Lothar,
> >
> > Early in September you were working on a driver for the isp1362 based
> > upon your work with the ohci-emu/sl811 stuff. I'm just
On Fri, 2004-10-08 at 00:57, Christoph Torens wrote:
> > I have a PXA255 platform with an ISP1161 on it and am interested in
> > helping out testing, debugging etc.
>
> May I ask what a driver for isp1362 has to do with a isp116x chip?
As I understand it the isp1362 is just a isp116x core + one
Hello.
I need to establish tcp/ip or serial connection through usb during
bootloader stage.Now I use blob to successfully established tcp/ip
connection with linux host(with usbdnet.o), Now if I connect with windows
box,during the enum stage, there is no indication to let me choose a driver
for
Hello.
I need to establish tcp/ip or serial connection through usb during
bootloader stage.Now I use blob to successfully established tcp/ip
connection with linux host(with usbdnet.o), Now if I connect with windows
box,during the enum stage, there is no indication to let me choose a driver
for
Following is my correspondence with the manufacturer of the device:
Telegnosis (Japan). This is what prompted me to bring up the topic or
Ruby on laptops or on computers with no PCI slots.
Yitzhak Bar Geva
Dear Sir,
Thanks for your prompt reply.
Under Windows, we can support up to 8 dongles if yo
25 matches
Mail list logo
