On Sun, Jan 14, 2001 at 08:10:45PM +0100, W. Michael Petullo wrote:
> > In serial.c, you seem to perform a check by writing to a possible
> > modem's interrupt enable register and reading the result. This seems to
> > be one of the points at which the auto-configuration process occasionally
> > f
My previous note was probably in error. W. Michael Petullo probably is
really using a PCI internal Venus DSP1673 modem. I read too quickly and
assumed that we were talking about the "Linmodem" topic.
I will pass the note around here, and will summarize any replies I get.
Clearly we should try
Date: Tue, 06 Feb 2001 17:37:12 -0500
From: Ed Schulz <[EMAIL PROTECTED]>
One editorial correction: Our PCI host-controller modem is based on the
Mars DSP1646 or 1648, not the Venus DSP1673. Venus modems include the
controller function, so require no special Linux code to work.
W
One editorial correction: Our PCI host-controller modem is based on the
Mars DSP1646 or 1648, not the Venus DSP1673. Venus modems include the
controller function, so require no special Linux code to work.
I'll forward these notes along to our developers, and let you know the
result.
The "sample
On Sun, Jan 14, 2001 at 08:10:45PM +0100, W. Michael Petullo wrote:
> > In serial.c, you seem to perform a check by writing to a possible
> > modem's interrupt enable register and reading the result. This seems to
> > be one of the points at which the auto-configuration process occasionally
> > f
Theodore, et al.,
I have a Lucent Microelectronics Venus Modem (V90, 56KFlex) (rev 0) based
modem which /almost/ works with your serial driver. Giving the modem
an ATI command returns AEIGPM560LKTF1. The company that manufactures
the modem calls it a PM560LKC 56K Internal PCI Call Waiting Modem
6 matches
Mail list logo
