linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "W. Michael Petullo" <mike@flyn.org>
To: linux-kernel@vger.kernel.org
Subject: broken(?) Lucent Venus chipset and Linux 2.4
Date: Fri, 9 Mar 2001 15:40:32 -0500	[thread overview]
Message-ID: <20010309154032.A1154@dragon.flyn.org> (raw)

I have a Lucent Microelectronics Venus based modem, the Actiontec
Internal Call Waiting modem.  I have been trying to get it working well
with Linux 2.4 for some time now.  Theodore Ts'o, the maintainer of
the Linux serial driver, and I have talked quite a bit on the subject.
We both suspect that the Venus chipset is broken.

I have some code available at http://www.flyn.org related to this issue.
First, I have an ugly patch that adds support for the Actiontec Internal
Call Waiting modem to Theodore's serial driver version 5.05.  Second,
I have a simple kernel module that seems to demonstrate that the Venus
chipset has something wrong with it.  The module code should be self
explanatory.  To summarize, writing a value, call it foo, to, for example,
the modem's interrupt enable register and then immediately reading the
register's value does not always return foo.

If you have or have access to a Linux box with a Venus-based modem,
answering any of these questions would be very helpful:

o Does your modem work flawlessly with Linux 2.4?

o Could you run my test kernel module?  If so, what are the results on
your computer?

I have been lobbying both Lucent and Actiontec to help me with this issue.
Up to this point neither has provided substantial help.  However, there
is promise and I am not ready to give up yet.

Thanks!

-- 
W. Michael Petullo

:wq

             reply	other threads:[~2001-03-09 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 20:40 W. Michael Petullo [this message]
2001-03-11 21:02 ` broken(?) Lucent Venus chipset and Linux 2.4 Martin Diehl

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=20010309154032.A1154@dragon.flyn.org \
    --to=mike@flyn.org \
    --cc=linux-kernel@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).