Quoting Ray Jui (2015-03-06 12:07:13)
> Hi Mike,
>
> On 3/6/2015 11:55 AM, Mike Turquette wrote:
> > Quoting Sascha Hauer (2015-02-26 00:43:19)
> >> On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
> >>> On 2/25/2015 10:51 PM, Sascha Hauer wrote:
> On Wed, Feb 25, 2015 at 10:13:15PM
Hi Mike,
On 3/6/2015 11:55 AM, Mike Turquette wrote:
> Quoting Sascha Hauer (2015-02-26 00:43:19)
>> On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
>>> On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
> Hi Sascha,
>
>
Quoting Sascha Hauer (2015-02-26 00:43:19)
> On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
> > On 2/25/2015 10:51 PM, Sascha Hauer wrote:
> > > On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
> > >> Hi Sascha,
> > >>
> > >> On 2/25/2015 9:54 PM, Sascha Hauer wrote:
> > >>> Hi
Quoting Ray Jui (2015-03-06 12:07:13)
Hi Mike,
On 3/6/2015 11:55 AM, Mike Turquette wrote:
Quoting Sascha Hauer (2015-02-26 00:43:19)
On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui
Quoting Sascha Hauer (2015-02-26 00:43:19)
On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
Hi Ray,
On Wed, Feb
Hi Mike,
On 3/6/2015 11:55 AM, Mike Turquette wrote:
Quoting Sascha Hauer (2015-02-26 00:43:19)
On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
Hi Sascha,
On 2/25/2015 9:54 PM,
On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
> On 2/25/2015 10:51 PM, Sascha Hauer wrote:
> > On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
> >> Hi Sascha,
> >>
> >> On 2/25/2015 9:54 PM, Sascha Hauer wrote:
> >>> Hi Ray,
> >>>
> >>> On Wed, Feb 04, 2015 at 04:55:00PM -0800,
On Wed, Feb 25, 2015 at 11:42:44PM -0800, Ray Jui wrote:
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
> On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
>> Hi Sascha,
>>
>> On 2/25/2015 9:54 PM, Sascha Hauer wrote:
>>> Hi Ray,
>>>
>>> On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
Sometimes a clock needs to know the rate of its
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
> Hi Sascha,
>
> On 2/25/2015 9:54 PM, Sascha Hauer wrote:
> > Hi Ray,
> >
> > On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
> >> Sometimes a clock needs to know the rate of its parent before itself is
> >> registered to the
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
> Hi Ray,
>
> On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
>> Sometimes a clock needs to know the rate of its parent before itself is
>> registered to the framework. An example is that a PLL may need to
>> initialize itself to a
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
> Sometimes a clock needs to know the rate of its parent before itself is
> registered to the framework. An example is that a PLL may need to
> initialize itself to a specific VCO frequency, before registering to the
> framework.
On 02/04/15 16:55, Ray Jui wrote:
> Sometimes a clock needs to know the rate of its parent before itself is
> registered to the framework. An example is that a PLL may need to
> initialize itself to a specific VCO frequency, before registering to the
> framework. The parent rate needs to be known,
On 02/04/15 16:55, Ray Jui wrote:
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An example is that a PLL may need to
initialize itself to a specific VCO frequency, before registering to the
framework. The parent rate needs to be known, for
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An example is that a PLL may need to
initialize itself to a specific VCO frequency, before registering to the
framework. The
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An example is that a PLL may need to
initialize itself to a specific
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An
On 2/25/2015 10:51 PM, Sascha Hauer wrote:
On Wed, Feb 25, 2015 at 10:13:15PM -0800, Ray Jui wrote:
Hi Sascha,
On 2/25/2015 9:54 PM, Sascha Hauer wrote:
Hi Ray,
On Wed, Feb 04, 2015 at 04:55:00PM -0800, Ray Jui wrote:
Sometimes a clock needs to know the rate of its parent before itself is
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An example is that a PLL may need to
initialize itself to a specific VCO frequency, before registering to the
framework. The parent rate needs to be known, for PLL multipliers and
divisors to be
Sometimes a clock needs to know the rate of its parent before itself is
registered to the framework. An example is that a PLL may need to
initialize itself to a specific VCO frequency, before registering to the
framework. The parent rate needs to be known, for PLL multipliers and
divisors to be
20 matches
Mail list logo
