[ibis-macro] Re: Cross talk BIRD draft comments?
- From: <radek_biernacki@xxxxxxxxxxx>
- To: <Arpad_Muranyi@xxxxxxxxxx>, <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 22 Mar 2011 12:30:08 -0600
Hi Arpad,
Sorry for a late reply. My comments were as follows.
1. We should make sure that the terms "primary channel" are "through
channel" are defined. The term "primary channel" term is not quite suitable
when more than one victim receiver is considered.
2. In the first paragraph above "primary channel" should read "through
channel".
3. In the second paragraph, the requirement of "must be presented with
..." may be in a conflict with the "Max_Init_Aggressors" parameter value. This
needs to be clarified.
4. Why there is a differentiation between the Tx of the "primary channel"
and the aggressor transmitter. If there are more than one victim each Tx of a
"primary channel" is an aggressor for victim receiver other than of its own
through channel. I recall some discussion about letting a transmitter know that
it is the "primary channel" transmitter by setting the parameter "aggressors"
to zero. This would eliminate that transmitter contribution to any other victim.
5. We should make it clear that the most general case is MIMO, though in
most cases the simulation is limited to MISO.
Below I attach an alternative text for the BIRD,
Radek
Old text:
| The first column of the impulse_matrix is the impulse response for the
| primary channel. The rest are the impulse responses from aggressor drivers
| to the victim receiver.
|
|* To include any filtering performed by the transmitters' AMI_Init functions
|* according to the Reference Flows described in this section of this
|* specification, the primary channel's impulse response is passed to the
|* primary channel's transmitter AMI_Init function and the aggressor impulse
|* responses are passed to the corresponding aggressor transmiters' AMI_Init
|* functions. This implies that the AMI_Init function of each aggressor
|* transmitter must be presented with the impulse response for its own through
|* channel plus the aggressor impulse responses that will be written into the
|* impulse_matrix for the primary channel, so that any subsequent filtering
|* performed by the AMI_Init function of each aggressor transmitter can also
|* be applied to the aggressor impulse responses.
|
|* The AMI_Init function of the primary channel's transmitter may return a
|* modified impulse response, if appropriate according to the Reference Flows
|* described in this section of this specification, by modifying the first
|* column of the impulse_matrix. If the impulse response is modified, the
|* new impulse response is expected to represent the filtered response. The
|* number of items in the impulse_matrix should remain unchanged.
|
|* The AMI_Init function of the primary channel's receiver may further modify
|* the impulse_matrix, including the aggressor impulse responses contained
|* in the impulse matrix, if appropriate according to the Reference Flows
|* described in this section of this specification. If the impulse_matrix is
|* modified, the new impulse_matrix is expected to represent the filtered
|* response of the primary and aggressor channels. The number of items in
|* the impulse_matrix should remain unchanged.
New text:
|* In crosstalk simulation there may be several transmitter/receiver pairs.
|* The channels connecting each pair are termed "through channels". Out of all
|* receivers, the crosstalk simulation may focus on one or more receivers that
|* are termed "victim receivers". For each victim receiver, transmitters that
|* do not belong to the victim pair are called "aggressor transmitters" and the
|* channels connecting those aggressor transmitters with the victim receiver
|* are called "aggressor channels".
|*
|* For any specific transmitter, the first column of the impulse_matrix sent
|* to the AMI_Init funtion shall be the impulse response of its through channel,
|* that is the channel from that transmitter to its own receiver. The remaining
|* columns should contain the impulse responses from that transmitter to one or
|* more victim receivers (aggressor channels). The number of columns of the
|* impulse_matrix shall not exceed the value (Max_Init_Aggressors + 1) where
|* Max_Init_Aggressors is as specified in the AMI file for that transmitter.
|* Furthermore, the AMI_Init function input parameter "aggressors" shall not be
|* greater than the value of Max_Init_Aggressors. While the allocated space for
|* the impulse_matrix may be larger, the EDA platform shall assume that there
|* is no meaningfull data beyond the first (aggressors + 1) columns. In a
|* typical application where there is only one victim receiver, two columns in
|* the impulse matrices for all transmitters will be sufficient for a complete
|* crosstalk simulation.
|*
|* Any filtering performed by any transmitters' AMI_Init functions according
|* to the Reference Flows described in this section of this specification,
|* needs to be applied to the first (aggressors + 1) columns of the
|* impulse_matrix.
|*
|* For any specific receiver, the first column of the impulse_matrix sent to
|* the AMI_Init funtion shall be the impulse response of the through channel,
|* that is the channel to that receiver from its own transmitter. The remaining
|* columns should contain the impulse responses to that receiver from one or
|* more aggressor transmitters. The number of the columns of the
|* impulse_matrix shall not exceed the value (Max_Init_Aggressor + 1) where
|* Max_Init_Aggressors is as specified in the AMI file for that receiver.
|* Furthermore, the AMI_Init function input parameter "aggressors" shall not
|* be greater than the value of Max_Init_Aggressors. While the allocated space
|* for the impulse_matrix may be larger, the EDA platform shall assume that
|* there is no meaningful data beyond the first (aggressors + 1) columns.
|* The value of victim receiver's parameter Max_Init_Agressors establishes
|* the maximum number of aggressor transmitters that can be used for a
|* complete crosstalk simulation for that receiver.
|*
|* The AMI_Init function of any victim receiver may further modify the
|* impulse_matrix, including the aggressor impulse responses contained in the
|* impulse_matrix, if appropriate according to the Reference Flows described
|* in this section of this specification. If the impulse_matrix is modified,
|* the new impulse_matrix is expected to represent the filtered response of the
|* through channel and the aggressor channels.
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Muranyi, Arpad
Sent: Monday, March 21, 2011 6:42 AM
To: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Cross talk BIRD draft comments?
Hello,
In our last ATM teleconference we decided to table the vote on
the cross talk BIRD draft because someone made a few comments we
had to take care of. I remember we asked the person making these
comments to start an email thread with a list of issues on the
BIRD draft, but I don't remember now who it was. Since I haven't
seen any emails on this topic yet, I would like to ask whoever
made these comments to please reply to this email with the issues
that you mentioned so we could get the BIRD draft fixed up.
Thanks,
Arpad
==================================================================
Other related posts:
