From: Steve Schefter <steve@wanware.com>
To: TProvoni@aol.com
Cc: un@rootelecom.ru, linux-x25@vger.kernel.org
Subject: Re: Null X.25 cable?
Date: Mon, 17 May 2004 09:29:11 -0400 [thread overview]
Message-ID: <40A8BE27.7020606@wanware.com> (raw)
In-Reply-To: <1a4.23eb82b5.2dd7cc89@aol.com>
Hi Joachim.
> Wanware hardware sounds somewhat restrictive in its clock
> configurations. I have worked with several vendors' equipment that
> allows symmetric independent clocking. Transmit clocks are sent from
> both sides and the receivers extract the clocks as they receive data.
We support that as well. It is just more common to have the physical
DCE generate the clock for both sides to use (such as when you are
connected to a modem or DSU/CSU). I generally only put internal clocking
on both sides when I'm using FM0 line encoding.
> BTW, some specifications provide a third sense of DTE and DCE in terms
> of connector definition.
>
> Thus it is possible to use a DCE connector on the interface that is a
> DTE in the clock sense and a DCE in the protocol sense.
When you say the DCE is "DTE in the clock sense", do you mean it's
externally clocked? (And you didn't like my arbitrary selection of DTE
as externally clocked above ;-)
Just to be clear, there's the selection of:
- physical DTE versus physical DCE
- logical DTE versus logical DTE
- who will provide the clock
All three of these are independently chosen. You can mix and match
and get lots of combinations.
Steve
------------------------------------------------------------------------
Steve Schefter phone: +1 705 725 9999 x26
The Software Group Limited fax: +1 705 725 9666
642 Welham Road, email: steve@wanware.com
Barrie, Ontario CANADA L4N 9A1 Web: www.wanware.com
next parent reply other threads:[~2004-05-17 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a4.23eb82b5.2dd7cc89@aol.com>
2004-05-17 13:29 ` Steve Schefter [this message]
2004-05-15 19:46 Null X.25 cable? TProvoni
-- strict thread matches above, loose matches on Subject: below --
2004-05-14 8:22 un@roo
2004-05-14 13:30 ` Steve Schefter
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=40A8BE27.7020606@wanware.com \
--to=steve@wanware.com \
--cc=TProvoni@aol.com \
--cc=linux-x25@vger.kernel.org \
--cc=un@rootelecom.ru \
/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.