Унеенехваталомужествасразусознатьсявэтом:нетаклегкобыло
Мечик,отъехавшийужедовольнодалеко,оглянулся:Морозкаехалсаженях
Hi! This is the ezmlm program. I'm managing the
[EMAIL PROTECTED] mailing list.
I'm working for my owner, who can be reached
at [EMAIL PROTECTED]
Here is a list of the command addresses supported:
Send mail to the following for info and FAQ for this list:
<[EMAIL PROTECTED]>
<[EMAIL PROTEC
On Fri, Apr 23, 2004 at 04:30:08PM -0700, Pete Zaitcev wrote:
> On Sat, 24 Apr 2004 01:07:19 +0200 (CEST) Jan Capek <[EMAIL PROTECTED]> wrote:
> > static void ftdi_set_termios (struct usb_serial_port *port, struct termios
> > *old_termios)
> > { /* ftdi_termios */
>
> > - /* FIXME -For this c
Ah well... looks like I hit the end of the road for now. I tried kernel
2.6.6-rc3 (plus the two patches from this mailing list), and now I get a
gazillion oopses from the kernel before I even hit the login prompt (the thing
oopses so much I can't make anything out of it, except that it seems relate
So far I haven't put in any tracing information, but I have been playing
with the latest Knoppix release that provides kernel 2.6.5
And the hotplug works with it.
So could it be a difference in initialization between kernel 2.6.5 and 2.6.6
or could it be something I (and RedHat) have left out of my
Hi, this is the first time I post to this list, so please excuse any
mistake...
Until kernel 2.6.3 there was a patch that permitted to use some USB
whose first interface number is 1 instead of 0. But with kernel 2.6.5
the patch didn't work anymore. So I "ported" the patch in the new kernel.
Disc
Alan Stern wrote:
I think we really should lock the device during configuration changes. ...
Here's another argument you may find more convincing. I went back and
looked at the stuff you wrote before about using a separate lock for the
"logical" children. Let's take that one step further and co
On Sun, 9 May 2004, Zariel Skotlex wrote:
> Anyway, lsusb -v yields the following (I decided to include everything.. which
> is just the ohci, ehci and modem data):
As you found out, the string descriptors values listed here each belong to
the previous descriptor:
>
> Bus 002 Device 002: ID 07
Zariel Skotlex wrote:
iManufacturer 3 Linux 2.6.5 ohci_hcd
iProduct2 nVidia Corporation nForce2 USB Controller (#2)
iSerial 1 :00:02.1
Does the 2.6.6-rc3 code behave differently?
There's a patch in that release which should help with device
firmw
The reason it locks the parent hub, very briefly, is to force tasks
to serialize.
I also keep forgetting something that's changed between 2.6.6-rc
and the latest bk-usb code, too ... hub_port_init() adds the device
to the tree earlier now. That's eliminated most of the places that
usbdev->seria
Alan Stern wrote:
usbnet 2-3:1.0: usb_probe_interface
usbnet 2-3:1.0: usb_probe_interface - got id
usbnet 2-3:1.0: CDC descriptors on config
usb_control_msg2: result = 26
usbnet: probe of 2-3:1.0 failed with error -22
There's only one place that error can be coming from; it's where the CDC
drive
Well... my CDCEther driver has always told me that it was a "MAC get failed
error = 22" whenever I loaded it after 'corrupting' the cable modem with usbnet:
//---
hub.c: new USB device 00:02.0-2, assigned address 3
CDCEther.c: Ethernet informatio
On Sun, 9 May 2004, Zariel Skotlex wrote:
> On Sat, 08 May 2004 19:51:42 -0700
> David Brownell <[EMAIL PROTECTED]> wrote:
>
> Ok... applied that patch and rewent through the boot-up sequence and checked the
> output of dmesg.
> //---
> ehci_hcd
On Sun, 9 May 2004, jack wrote:
> I don't understand the usage of the pipe member of this structure. The
> documentation says "The pipe element is used to encode the endpoint number
> and properties" - great ! what is an endpoint number ? and what properties
> are they talking about ?
>
> As you
On Sun, 9 May 2004, Andreas Herrmann wrote:
> May 9 11:29:19 feynman usb 1-1: new full speed USB device using address 2
> May 9 11:29:19 feynman usb-storage: This device (07cf,1001,1000 S 05 P 01)
> has an unneeded Protocol entry in unusual_devs.h
> May 9 11:29:19 feynman Please send a copy of
I also habe written the bug report 2573, but there seems to be an additional
problem too. First I repeat the bugreport
Hardware:
Via Epia M9000, and a bttv based tv-card
I have a worse interrupt problem between the tv-card and the uhci-hcd driver.
In my setup they´ll share the same i
May 9 11:29:19 feynman usb 1-1: new full speed USB device using address 2
May 9 11:29:19 feynman usb-storage: This device (07cf,1001,1000 S 05 P 01)
has an unneeded Protocol entry in unusual_devs.h
May 9 11:29:19 feynman Please send a copy of this message to
<[EMAIL PROTECTED]>
May 9 11:29:19
On Sun, May 09, 2004 at 08:52:12AM +0100, jack wrote:
> My project is to write a character device drive for a "1-wire" network
> attached to a USB hub via a "1-wire" USB adapter.
FYI, there's a "public domain kit" (which is not actually public-domain,
but close: MIT/X11-style license):
http://w
Greetings Greg,
I can see that you have been heavily involved in the USB device driver code
for Linux.
I am very grateful for all the work you have done on this so far.
I have been trying to learn as much as I can about USB device drivers for a
personal project and your documentation is by far t
19 matches
Mail list logo
