There's a field in the Frame Interval register (reg HcFmInterval,
0x0D) called FSLargestDataPacket (FSMPS). It specifies the largest
amount of data in bits that can be sent or received by the HC in a
single transaction without causing an overrun.
You are right. This same thing was a problem
On Sun, Nov 07, 2004 at 03:20:39PM -0700, David Brownell wrote:
On Sunday 07 November 2004 13:30, Adrian Bunk wrote:
The patch below makes some needlessly global USB gadget functions
static.
It looks fine except for the one config descriptor utility
(just strike those bits from the
Hi,
There's a field in the Frame Interval register (reg HcFmInterval,
0x0D) called FSLargestDataPacket (FSMPS). It specifies the largest
amount of data in bits that can be sent or received by the HC in a
single transaction without causing an overrun.
This field wasn't being set!
This
On Tue, Nov 09, 2004 at 08:42:43AM -0800, Greg KH wrote:
On Sun, Nov 07, 2004 at 03:20:39PM -0700, David Brownell wrote:
On Sunday 07 November 2004 13:30, Adrian Bunk wrote:
The patch below makes some needlessly global USB gadget functions
static.
It looks fine except for the one
Hi,
There seems to be a problem in 2.6.10-rc1-mm4 with either USB storage (eg a
pendrive) or hotplug on AMD64 (NForce3 chipset, ohci-hcd, SuSE 9.1). Namely,
if a USB pendrive is inserted into a socket, the kernel does not even detect
it. Here's what appears in dmesg after it's inserted:
Dear Sir or Madam,
Would you REFINANCE if you knew you'd SAVE TH0USANDS?
We'll get you lnterest as low as 1.92%.
Don't believe me? Fill out our small online questionaire and we'll show you
how.
Get the house/home and/or car you always wanted, it only takes 10 seconds of
your time:
On Wed, 2004-11-10 at 10:06 +0200, Olav Kongas wrote:
With this driver, we see quite a bit of duplicated effort.
Sure we could reduce this by communicating more. So, thanks
for posting this type of info. I try to be more open too.
hi Olav,
you're right. We both work on porting the code to
On Wednesday 10 November 2004 02:54, Rafael J. Wysocki wrote:
Hi,
There seems to be a problem in 2.6.10-rc1-mm4 with either USB storage (eg a
pendrive) or hotplug on AMD64 (NForce3 chipset, ohci-hcd, SuSE 9.1).
Namely,
if a USB pendrive is inserted into a socket, the kernel does not even
On Wednesday 10 November 2004 01:48, Adrian Bunk wrote:
On Sun, Nov 07, 2004 at 03:20:39PM -0700, David Brownell wrote:
On Sunday 07 November 2004 13:30, Adrian Bunk wrote:
The patch below makes some needlessly global USB gadget functions
static.
It looks fine except for the one
On Wednesday 10 of November 2004 14:58, David Brownell wrote:
On Wednesday 10 November 2004 02:54, Rafael J. Wysocki wrote:
Hi,
There seems to be a problem in 2.6.10-rc1-mm4 with either USB storage (eg
a
pendrive) or hotplug on AMD64 (NForce3 chipset, ohci-hcd, SuSE 9.1).
Namely,
Hello,
I am trying to use logitech quickcam messenger webcam on Linux.
(Logitech QuickCam Messenger with built-in microphone. ID: 046d:08f0 )
I have downloaded from: http://mag.cx/messenger/
a driver for quickcam messenger webcam .
( Modified qc-usb-source to test Quickcam Messenger.)
but it does
On Wednesday 10 November 2004 06:57, Rafael J. Wysocki wrote:
On Wednesday 10 of November 2004 14:58, David Brownell wrote:
I recently posted several USB PM fixes that make things work better
in my testing, and it sounds like they'd probably help here too.
Are they available as
On Wed, 10 Nov 2004 10:42:26 +0100, Lothar Wassmann
[EMAIL PROTECTED] wrote:
Hi,
There's a field in the Frame Interval register (reg HcFmInterval,
0x0D) called FSLargestDataPacket (FSMPS). It specifies the largest
amount of data in bits that can be sent or received by the HC in a
On Wed, 10 Nov 2004, Dimitris Lampridis wrote:
So, what is your status?
I'm stuck in a state, where the driver is sometimes able to
detect and configure storage devices to the point where they
are recognized as scsi devices by usb core. I haven't tried
mounting them though. But with majority of
after that. The subsequent ohci_read_control() call and all the rest IO
to come, read D !
Did you see anything similar?
I did not see exactly similar thing. But I had to add delay
after register accesses into the functions like
HC_ISP1362_READ_DATA32. I used ndelay(150) though
On Wed, 2004-11-10 at 18:49 +0200, Olav Kongas wrote:
On Wed, 10 Nov 2004, Dimitris Lampridis wrote:
after that. The subsequent ohci_read_control() call and all the rest IO
to come, read D !
Did you see anything similar?
I did not see exactly similar thing. But I had to add
Hi Vojtech,
Please accept this patch for the 'usb.ids' file, based on my observations with
a new SanDisk 'Cruzer Mini' USB flash-RAM drive. It was patched against the
latest (1.164 2004/10/20) version of that file.
-
--- usb.ids.orig2004-11-10
On Tuesday 09 November 2004 01:03, tian tao wrote:
Hi all,
I am doing a project using usbnet, and hope to discuss some topics about
usbnet with someone. Is there anyone is familiar with usbnet or have
interested in usbnet? I hope to ask some questions about usbnet first:
Is the usbnet
On Tue, 9 Nov 2004, David Brownell wrote:
On Tuesday 09 November 2004 07:23, Alan Stern wrote:
On Mon, 8 Nov 2004, David Brownell wrote:
The SL-811 code will need updates too (or it will, once
there's one that compiles and runs),
Actually no. The SL-811 code doesn't currently
Hi,
this is a Patch that just adds the Yakumo Mega-Image 47 to the unusual
devices list.
Works for me.
Here is what /proc/bus/usb/devices says:
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 17 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=052b
David:
http://bugme.osdl.org/show_bug.cgi?id=3480
Can you look at this? It seems to be an error in the EHCI bandwidth
reservation. The relevant parts are the second and third attachments.
There's a high-speed 4-port hub attached to an EHCI controller, with a
full-speed USB camera plugged
Begin forwarded message:
Date: Wed, 10 Nov 2004 14:07:38 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 3728] New: Kernel dies _hard_ on usb unplug
http://bugme.osdl.org/show_bug.cgi?id=3728
Summary: Kernel dies _hard_ on usb unplug
Kernel
On Wednesday 10 of November 2004 16:36, David Brownell wrote:
On Wednesday 10 November 2004 06:57, Rafael J. Wysocki wrote:
On Wednesday 10 of November 2004 14:58, David Brownell wrote:
I recently posted several USB PM fixes that make things work better
in my testing, and it sounds like
On Wednesday 10 November 2004 13:23, Alan Stern wrote:
David:
http://bugme.osdl.org/show_bug.cgi?id=3480
Can you look at this? It seems to be an error in the EHCI bandwidth
reservation. The relevant parts are the second and third attachments.
I've called it a limitation of that code;
On Wednesday 10 November 2004 15:42, Rafael J. Wysocki wrote:
On Wednesday 10 of November 2004 16:36, David Brownell wrote:
On Wednesday 10 November 2004 06:57, Rafael J. Wysocki wrote:
On Wednesday 10 of November 2004 14:58, David Brownell wrote:
I recently posted several USB PM
I looked at two of those dmesg logs and found several
different errors:
- Something killing EHCI right after it started up.
I've not seen that with ALI myself, but some other
folk seem to have that problem (mostly with ALI).
- The usb-storage device seems to have spontaneously
On Wednesday 10 November 2004 17:14, David Brownell wrote:
I looked at two of those dmesg logs and found several
different errors:
- Something killing EHCI right after it started up.
I've not seen that with ALI myself, but some other
folk seem to have that problem (mostly with ALI).
Dear all,
I have written a simple bulkusb driver to test the usb transfer speed. Just
transfer 256bytes*1000 between host and client. The test result is following:
transfer data transfer speed
host---client 256bytes*1000 256K bytes/second
client---host
Hi David,
Thank you very much for your answer:) It's very helpful. I will try to
read the usbnet.c and usbeth.c first(I am now having a test about usb
network between my pc and a ipaq). And maybe a month later will try to make
another device to work with usbnet. I hope I could ask you some
hello,
A simple question related to linux usb concept here:
I am reading the USB Spec2.0 , Mass Storage Spec. as well as linux usb code. I
am little confused
by some concept concerning URB,USB requests and CBW/CSW.
In my understanding, each time host want to send request or data to usb device,
On Wednesday 10 November 2004 12:05, Alan Stern wrote:
On Tue, 9 Nov 2004, David Brownell wrote:
Well, assuming my changes are applied in the near future, when the SL-811
driver finally gets updated to use the hcd stuff then it will be
compatible with the changes!
Not until the relevant
Great, thanks, that did the job. Now I see a loop of roothub reads,
RHDESC_A then RH_STATUS and finally RH_PORT_STATUS_[1,2] that keeps on
forever. I think it has something to do with suspend/resume. I'll look
into it tomorrow, unless you already know what am i dealing with...
This is normal.
32 matches
Mail list logo
