From: wwp <subscript@free.fr>
To: linux-hotplug@vger.kernel.org
Subject: dabusb/usb modems conflict issue
Date: Sat, 03 May 2003 23:38:23 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105200517616922@msgid-missing> (raw)
Hi hotplug folks,
I'm writing here in the name of the developer team of the ECI USB ADSL
driver, and I'd like to report there a possible conflict issue, or at least a
few questions.
Well.. our driver support a lot of GlobeSpan chipset-based USB ADSL modems,
and in most cases, hotplug loads dabusb module at startup to add support for
the (modem) devices.
We used to disable dabusb module load by removing the module file or
re-configuring the kernel to skip dabusb support, and with latest versions of
hotplug (depending on the GNU/Linux distro), we recommend our users to add
dabusb to the blacklist file.
You will find related info about how we manage this issue there:
the project page..
http://eciadsl.flashtux.org/index.php?lang=en
the supported modems list (including vid/pid)..
http://eciadsl.flashtux.org/modems.php?lang=en
our Q/A in the FAQ related to this dabusb issue..
http://eciadsl.flashtux.org/faq.php?lang=en#2.1
My questions:
1/
Do we use the right method to avoid dabusb loading for non-audio-dabusb
devices (modems).
2/
Is this really a conflict? What's your thought about this?
3/
Do you have any piece of advice related to this (generally)?
Thanx in advance,
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
next reply other threads:[~2003-05-03 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 23:38 wwp [this message]
2003-05-05 18:53 ` dabusb/usb modems conflict issue 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
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-105200517616922@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).