If by a signal you mean a symbol sent every so often, in-band, then
it works. Needs some buffering to smooth the "every so often" effect
at Gigabit speeds, but what are few kbytes between friends :).
If by a signal you really mean a galvanic conductor running along
Hari, well, I have a bias against that.
PS: I apologize for breaking the moratorium on Hari discussion.
What was the punishment? 20 push-ups at the next plennary?
> X-Sender: pbottorf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Date: Mon, 29 Nov 1999 14:10:21 -0800
> To: Ariel Hendel <Ariel.Hendel@xxxxxxxxxxx>, stds-802-3-hssg@xxxxxxxx
> From: "Paul Bottorff" <pbottorf@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Hari
> Mime-Version: 1.0
> X-Resent-To: Multiple Recipients <stds-802-3-hssg@xxxxxxxxxxxxxxxxxx>
> X-Listname: stds-802-3-hssg
> X-Info: [Un]Subscribe requests to majordomo@xxxxxxxxxxxxxxxxxx
> X-Moderator-Address: stds-802-3-hssg-approval@xxxxxxxxxxxxxxxxxx
> Hari can easily be adapted to the same word-by-word pacing mechanism we
> proposed for the XGMII. This mechanism adds a signal to Hari which is used
> to request the insertion of NULL control words. When pacing from PMD to
> Hari NULL control works can be inserted.
> Hari has no bias toward open loop pacing.
> At 01:46 PM 11/25/99 -0800, Ariel Hendel wrote:
> >> Date: Wed, 24 Nov 1999 18:44:12 -0600
> >> From: Roy Bynum <rabynum@xxxxxxxxxxx>
> >> X-Accept-Language: en
> >> MIME-Version: 1.0
> >> To: rtaborek@xxxxxxxxxx, rtaborek@xxxxxxxxxxxxx
> >> CC: HSSG <stds-802-3-hssg@xxxxxxxx>
> >> Subject: Re: Hari
> >> Content-Transfer-Encoding: 7bit
> >> X-Resent-To: Multiple Recipients <stds-802-3-hssg@xxxxxxxxxxxxxxxxxx>
> >> X-Listname: stds-802-3-hssg
> >> X-Info: [Un]Subscribe requests to majordomo@xxxxxxxxxxxxxxxxxx
> >> X-Moderator-Address: stds-802-3-hssg-approval@xxxxxxxxxxxxxxxxxx
> >> Rich,
> >> As a XGMII, replacing the parallel GMII, Hari would be in place to
> directly interface
> >> between the MAC and PCS. As an interconnect between the PMA and the
> PMD, Hari adds
> >> additional code translations, jitter, and inherent delay between any
> pacing function at
> >> the PMD level PCS and the MAC.
> >There can be no better example than Hari for the wisdom of the open loop
> >solution at the MAC (as opposed to tightly coupled feedback schemes).
> >Open loop pacing and Hari, made for each other...
> >Ariel Hendel
> Paul A. Bottorff, Director Switching Architecture
> Enterprise Solutions Technology Center
> Nortel Networks, Inc.
> 4401 Great America Parkway
> Santa Clara, CA 95052-8185
> Tel: 408 495 3365 Fax: 408 495 1299 ESN: 265 3365
> email: pbottorf@xxxxxxxxxxxxxxxxxx