2009/8/30 NoiseEHC :
> I do not know what was the conclusion about this _completely hypothetical_
> case but does fixing the Geode VGA driver match the "paper cut" criteria?
Rough criteria:
- Does it affect our primary users? (kids in deployment schools)
- Do we have a field-tested patch?
- Is
noiseehc wrote:
> Hi!
>
> I do not know what was the conclusion about this _completely
> hypothetical_ case but does fixing the Geode VGA driver match the "paper
> cut" criteria?
probably only if it affects current deployments. but good fixes
for the XO-1 are certainly welcome, since they
Hi!
I do not know what was the conclusion about this _completely
hypothetical_ case but does fixing the Geode VGA driver match the "paper
cut" criteria?
Since I am porting (very slowly since 2 months ago I did not know
anything at all about the Linux boot process for example) Android to the
Martin Langhoff wrote:
> No, and that is an explicit goal: keep the changes small and low risk
> so that we can do QA focused on the very limited areas of the system
> we touch.
Just in case you are misunderstanding what we are asking for its at a
minimum of changing the 'y' to an 'm' in the ker
Martin Langhoff wrote:
> Generally agree that it is important... however.
>
> On Wed, Aug 12, 2009 at 9:55 AM, Richard A. Smith wrote:
>> You have to QA the whole system regardless of what change you make so really
>> it doesn't increase the QA that much anyway.
>
> No, and that is an explicit g
Generally agree that it is important... however.
On Wed, Aug 12, 2009 at 9:55 AM, Richard A. Smith wrote:
> You have to QA the whole system regardless of what change you make so really
> it doesn't increase the QA that much anyway.
No, and that is an explicit goal: keep the changes small and low
Martin Langhoff wrote:
>
> I understand the reasoning, but qualifying the build with a changed
> kernel will kill us in QA across the system. Got to ruminate on that
> one a bit...
When deployments report back to us "touchpad" problems are among the top
3 items. Usually #2 behind power.
Due t
martin wrote:
> On Tue, Aug 11, 2009 at 10:53 AM, Paul Fox wrote:
> > if nothing else, a next release _must_ be built
> > with a modular mouse driver...
>
> Hmmm. The 5th reply makes a beeline to "must rebuild the kernel". Not
> quite a record, but pretty good performance I have to say ;-)
daniel wrote:
> 2009/8/11 Paul Fox :
> > one thing we've recently realized that would be very low risk
> > would be to change the "xset" command in /usr/bin/olpc-session
> > from "xset 7/4 0" to either "xset 7/6 0" or "xset 7/4 1".
>
> What effect does this have?
see "man xset" as a refere
On Tue, Aug 11, 2009 at 10:53 AM, Paul Fox wrote:
> if nothing else, a next release _must_ be built
> with a modular mouse driver...
Hmmm. The 5th reply makes a beeline to "must rebuild the kernel". Not
quite a record, but pretty good performance I have to say ;-)
I understand the reasoning, but
2009/8/11 Paul Fox :
> one thing we've recently realized that would be very low risk
> would be to change the "xset" command in /usr/bin/olpc-session
> from "xset 7/4 0" to either "xset 7/6 0" or "xset 7/4 1".
What effect does this have?
Daniel
___
Deve
martin wrote:
> In the _completely hypothetical_ case that I had some time and chance
> to spin a 8.2.x release aimed at fixing the "paper cuts"[1] and
> low-risk bugs that hinder XO-1 deployability _today_ in the field -
> have *you* got any candidates? Tell me about them :-)
well, touchpad i
2009/8/11 Martin Langhoff :
> In the _completely hypothetical_ case that I had some time and chance
> to spin a 8.2.x release aimed at fixing the "paper cuts"[1] and
> low-risk bugs that hinder XO-1 deployability _today_ in the field -
> have *you* got any candidates? Tell me about them :-)
I thin
> chance ... a 8.2.x release aimed at fixing the "paper cuts"[1] and
> low-risk bugs that hinder XO-1 deployability _today_ in the field -
> have *you* got any candidates? Tell me about them :-)
I myself don't really "patch" -- mostly all I do is to add things to
make the XO more "usable" (as a L
In the _completely hypothetical_ case that I had some time and chance
to spin a 8.2.x release aimed at fixing the "paper cuts"[1] and
low-risk bugs that hinder XO-1 deployability _today_ in the field -
have *you* got any candidates? Tell me about them :-)
I am specially hoping to round up bugs tha
15 matches
Mail list logo
