On 08.01.2010, at 19:29, Blue Swirl wrote:
> On Fri, Jan 8, 2010 at 6:27 PM, Alexander Graf wrote:
>>
>> On 08.01.2010, at 19:22, Blue Swirl wrote:
>>
>>> On Fri, Jan 8, 2010 at 6:07 PM, Alexander Graf wrote:
On 08.01.2010, at 19:04, Blue Swirl wrote:
> On Fri, Jan 8, 201
On Fri, Jan 8, 2010 at 6:27 PM, Alexander Graf wrote:
>
> On 08.01.2010, at 19:22, Blue Swirl wrote:
>
>> On Fri, Jan 8, 2010 at 6:07 PM, Alexander Graf wrote:
>>>
>>> On 08.01.2010, at 19:04, Blue Swirl wrote:
>>>
On Fri, Jan 8, 2010 at 5:43 PM, Alexander Graf wrote:
> Our guest system
On 08.01.2010, at 19:22, Blue Swirl wrote:
> On Fri, Jan 8, 2010 at 6:07 PM, Alexander Graf wrote:
>>
>> On 08.01.2010, at 19:04, Blue Swirl wrote:
>>
>>> On Fri, Jan 8, 2010 at 5:43 PM, Alexander Graf wrote:
Our guest systems need to know by how much the timebase increases every
s
On Fri, Jan 8, 2010 at 6:07 PM, Alexander Graf wrote:
>
> On 08.01.2010, at 19:04, Blue Swirl wrote:
>
>> On Fri, Jan 8, 2010 at 5:43 PM, Alexander Graf wrote:
>>> Our guest systems need to know by how much the timebase increases every
>>> second,
>>> so there usually is a "timebase-frequency" p
On 08.01.2010, at 19:04, Blue Swirl wrote:
> On Fri, Jan 8, 2010 at 5:43 PM, Alexander Graf wrote:
>> Our guest systems need to know by how much the timebase increases every
>> second,
>> so there usually is a "timebase-frequency" property in the cpu leaf of the
>> device tree.
>>
>> This prop
On Fri, Jan 8, 2010 at 5:43 PM, Alexander Graf wrote:
> Our guest systems need to know by how much the timebase increases every
> second,
> so there usually is a "timebase-frequency" property in the cpu leaf of the
> device tree.
>
> This property is missing in OpenBIOS, as is the "clock-frequenc
