On Mon, 30 Jan 2017 16:57:36 -0500, Sean Paul wrote:
> On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote:
> > These values are specified as constant time periods but the PHY
> > configuration is in terms of the current lane byte clock so using
> > constant values guarantees that the
On Mon, 30 Jan 2017 16:57:36 -0500, Sean Paul wrote:
> On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote:
> > These values are specified as constant time periods but the PHY
> > configuration is in terms of the current lane byte clock so using
> > constant values guarantees that the
On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote:
> These values are specified as constant time periods but the PHY
> configuration is in terms of the current lane byte clock so using
> constant values guarantees that the timings will be outside the
> specification with some display
On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote:
> These values are specified as constant time periods but the PHY
> configuration is in terms of the current lane byte clock so using
> constant values guarantees that the timings will be outside the
> specification with some display
These values are specified as constant time periods but the PHY
configuration is in terms of the current lane byte clock so using
constant values guarantees that the timings will be outside the
specification with some display configurations.
Derive the necessary configuration from the byte clock
These values are specified as constant time periods but the PHY
configuration is in terms of the current lane byte clock so using
constant values guarantees that the timings will be outside the
specification with some display configurations.
Derive the necessary configuration from the byte clock
6 matches
Mail list logo