From: wwp <subscript@free.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: dabusb/usb modems conflict issue
Date: Thu, 02 Oct 2003 08:07:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106508216918883@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105200517616922@msgid-missing>
Hi Thomas Sailer,
On 06 May 2003 15:31:02 +0200 Thomas Sailer <sailer@scs.ch> wrote:
> On Mon, 2003-05-05 at 20:53, David Brownell wrote:
>
> > In fact, the current drivers (2.4, 2.5) seem to have
> > only two IDs, both with Cypress vendor IDs. One of
> > them is a bug, and needs to be removed. I don't know
> > about the other one; it could be legit.
>
> The current driver is available from
> http://www1.baycom.de/download/dabusb/dabusb-linux-i386-2.24a.tar.gz,
> the one in the kernel doesn't even work (it crashes on plugin of the
> device).
>
> The current driver contains the Terratec production VID/PIDs, but also
> still has the Anchor VID/PIDs that were used in engineering models.
> These PID's should probably be disabled by default.
Do you know if fixed dabusb (regarding to the previous topic) has been merged
to recent 2.4 or 2.6-pre?
Regards,
--
wwp
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2003-10-02 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 23:38 dabusb/usb modems conflict issue wwp
2003-05-05 18:53 ` David Brownell
2003-05-05 22:29 ` wwp
2003-05-06 13:31 ` Thomas Sailer
2003-05-06 14:58 ` David Brownell
2003-10-02 8:07 ` wwp [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=marc-linux-hotplug-106508216918883@msgid-missing \
--to=subscript@free.fr \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).