From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: USB trouble w/ 2.4.8-ac12
Date: Sun, 02 Sep 2001 14:00:02 -0400 [thread overview]
Message-ID: <3B9273A2.2000706@lycosmail.com> (raw)
In-Reply-To: <3B916760.1000104@lycosmail.com> <20010901162130.C26407@kroah.com> <20010901162954.B2828@one-eyed-alien.net>
Matthew Dharm wrote:
>The Freecom dongle is well supported for Tape drives (the OnStream USB-30, in particular), but I haven't gotten it working for other devices yet.
>
Well, I don't know how much help I can be, but I am willing (given time
[atm I'm unemployed, but attempting to remedy that]) to test patches.
>
>I'm just short on time to work on this.... so if someone is offering to help, that would be a good thing.
>
Willing to do what I can.
>
>
>Matt
>
>On Sat, Sep 01, 2001 at 04:21:30PM -0700, Greg KH wrote:
>
>>On Sat, Sep 01, 2001 at 06:55:28PM -0400, Adam Schrotenboer wrote:
>>
>>>Using 2.4.8-ac12, USB modules, and a Philips CDRW400.
>>>
>>>I was able to get it to see the CDRW drive once(and that took a minute
>>>or three), but mostly it only sees the Freecom USB-IDE bridge.
>>>
>>>How do I get the usb code to probe the ATAPI bridge for the devices
>>>behind it??
>>>
>>You might try asking on the linux-usb-devel mailing list. I don't know
>>how well the Freecom bridge device is currently supported in Linux.
>>
>>greg k-h
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>
prev parent reply other threads:[~2001-09-02 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 22:55 USB trouble w/ 2.4.8-ac12 Adam Schrotenboer
2001-09-01 23:21 ` Greg KH
2001-09-01 23:29 ` Matthew Dharm
2001-09-02 18:00 ` Adam Schrotenboer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B9273A2.2000706@lycosmail.com \
--to=ajschrotenboer@lycosmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.