All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Schulz <edschulz@agere.com>
To: "Theodore Ts'o" <tytso@thunk.org>
Cc: "W. Michael Petullo" <mike@flyn.org>, linux-kernel@vger.kernel.org
Subject: Re: Lucent Microelectronics Venus Modem, serial 5.05, and Linux 2.4.0
Date: Tue, 06 Feb 2001 18:07:41 -0500	[thread overview]
Message-ID: <3A8083BD.F50540CF@agere.com> (raw)
In-Reply-To: <20010114201045.A1787@dragon.flyn.org> <200102061939.OAA24337@thunk.org>

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 it under Linux 2.4.

Since Venus modems include the controller function along with RAM and
flash, they're generally more expensive than Mars host-contoller modems. 
Here are some models:
- Zoom 2920
- MultiTech MultiModem ZPX MT5634ZPX-PCI
- Actiontec Call Waiting PCI56012-01CW
-- 
Ed Schulz
Agere Systems
+1 732 949 2066 voice
+1 732 949 5025 fax
edschulz@agere.com

Theodore Ts'o wrote:
> 
> 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
> > > fails.  If I make the following change to this code my modem seems to
> > > be auto-detected correctly all of the time:
> >
> > >                scratch = serial_inp(info, UART_IER);
> > >             serial_outp(info, UART_IER, 0);
> > > #ifdef __i386__
> > >             outb(0xff, 0x080);
> > > #endif
> > >             scratch2 = serial_inp(info, UART_IER);
> > >             serial_outp(info, UART_IER, 0x0F);
> > > #ifdef __i386__
> > >             outb(0, 0x080);
> > > #endif
> > > -             scratch3 = serial_inp(info, UART_IER); /* REMOVE */
> > > +             scratch3 = 0x0f                        /* ADD */
> > >             serial_outp(info, UART_IER, scratch);
> 
> The problem is that if this doesn't work, there are some serious
> questions about the correctness of the Lucent Microelectronic Venus
> modem.  I've forwarded this to someone in the Lucent Modem group, who
> can hopefully look at this (and maybe can ship me a sample hardware so
> I can play with it, although I'd much rather that he tell me how to
> work around the hardware bug, or tell me that all you need is a
> firmware upgrade to fix the bug in the modem).....
> 
>                                                         - Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-02-06 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-14 19:10 Lucent Microelectronics Venus Modem, serial 5.05, and Linux 2.4.0 W. Michael Petullo
2001-02-01 13:39 ` tytso
2001-02-06 19:39 ` Theodore Ts'o
2001-02-06 22:37   ` Ed Schulz
2001-02-06 22:58     ` Theodore Ts'o
2001-02-06 23:07   ` Ed Schulz [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=3A8083BD.F50540CF@agere.com \
    --to=edschulz@agere.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@flyn.org \
    --cc=tytso@thunk.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 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.