On Mar 30, 2010, at 2:48 AM, James Cameron wrote:
> They'd also notice the graphics performance differences, and that
> wouldn't be amenable to a simple fix.
Correct, and they would still get twice the memory and roughly
1.5 times the storage (JFFS2 is compressed).
What I didn't mention is that
ok 406. 199 msr!
The period after 406 is mandatory - it forces the number to be 64-bits,
suitable as the data operand to msr!.
John Watlington wrote:
> Mitch,
>Is there a simple way from OFW (or ACPI) to restrict
> the operating frequency of the processor in the XO-1.5
> to be the lowest po
The "4" is 406 is for 400 Mhz. The normal value is "a06", where "a" is
decimal 10 for 1000 Mhz.
The "6" is the voltage selection code; this processor only supports the
value "6".
Mitch Bradley wrote:
> ok 406. 199 msr!
>
> The period after 406 is mandatory - it forces the number to be
> 64-bi
>Is there a simple way from OFW (or ACPI) to restrict
> the operating frequency of the processor in the XO-1.5
> to be the lowest possible ?
>
> The relevant comment from a deployment was that they
> can't use full speed XO-1.5 motherboards as replacements
> for XO-1 motherboards. They think
On Mar 30, 2010, at 9:56 AM, Mikus Grinbergs wrote:
>> Is there a simple way from OFW (or ACPI) to restrict
>> the operating frequency of the processor in the XO-1.5
>> to be the lowest possible ?
>>
>> The relevant comment from a deployment was that they
>> can't use full speed XO-1.5 motherb
On Tue, 2010-03-30 at 09:16 -0700, Dan Williams wrote:
> Yeah, I haven't been able to reproduce that, but I only have an XO1.5
> with me (which doesn't have mesh), and I think the issue is timing
> related. So it's good that you can reproduce it. That gives us a chance
> to fix it.
We could defin
On Tue, 2010-03-30 at 14:07 -0300, Bernie Innocenti wrote:
> On Tue, 2010-03-30 at 09:16 -0700, Dan Williams wrote:
> > Yeah, I haven't been able to reproduce that, but I only have an XO1.5
> > with me (which doesn't have mesh), and I think the issue is timing
> > related. So it's good that you ca
Happened to run an older version of mplayer on os116 on XO-1.5, and it
claimed "SSE supported but disabled" (also for SSE2). So I looked in
some Linux forums, and saw there: "CPUID will tell you whether the CPU
supports SSE/SSE2, but not the OS. The OS (linux in this case) can have
SSE and/or SSE
G'day,
Those of you who have been testing XO-1.5 builds may have noticed that
you cannot disconnect from a wireless network, and you cannot discard
network history. The workaround was to remove connections.cfg.
Per ticket #9977 and #9788, I've made some changes to Sugar network
connection handli
