There was a thread about the X driver here:
http://lists.laptop.org/pipermail/devel/2007-September/006565.html
Because there were much more pressing things to do than rewriting the X
driver by Bernardo this project stalled.
However it is one of my project ideas on the developer program so
On 24.05.2008, at 03:41, Jim Gettys wrote:
On Fri, 2008-05-23 at 17:17 -0700, Alex Belits wrote:
Jim Gettys wrote:
Bert...
Part of the problem is the X driver model is pretty broken,
causing much
more to be done in software than should be necessary; and it isn't
clear
we're even
John Gilmore wrote:
It'll be hard for OLPC to get multi-touch working when for the last 15
months they haven't had the bandwidth to figure out whether the
current touchpad can do tap to click (ticket #959). But developers
and users of devices built between now and then will write most of the
On Fri, May 23, 2008 at 10:07 AM, Alex Belits
[EMAIL PROTECTED] wrote:
John Gilmore wrote:
It'll be hard for OLPC to get multi-touch working when for the last 15
months they haven't had the bandwidth to figure out whether the
current touchpad can do tap to click (ticket #959). But developers
Hi Alex,
That's assuming that non-OLPC developers will have access to
hardware before it will be declared ready for deployment. Otherwise
it will be like G1G1 -- first batch to outside developers coincides
with first mass deployment, then everyone complains that deployment
Hi,
It will be slightly more difficult to write (multi-touch) software
for the XO-2 in an emulator or on a regular PC... I wonder if there
are (or will be) any third party multi-touch input devices readily
available for a similar effect. Multi stylus wacom tablets?
The keyboard I
On Fri, May 23, 2008 at 3:38 PM, Chris Ball [EMAIL PROTECTED] wrote:
Hi,
It will be slightly more difficult to write (multi-touch) software
for the XO-2 in an emulator or on a regular PC... I wonder if there
are (or will be) any third party multi-touch input devices readily
Chris Ball wrote:
Hi Alex,
That's assuming that non-OLPC developers will have access to
hardware before it will be declared ready for deployment. Otherwise
it will be like G1G1 -- first batch to outside developers coincides
with first mass deployment, then everyone complains
http://wiki.laptop.org/go/Developer_program =)
- Eben
On Fri, May 23, 2008 at 9:59 AM, Alex Belits
[EMAIL PROTECTED] wrote:
Chris Ball wrote:
Hi Alex,
That's assuming that non-OLPC developers will have access to
hardware before it will be declared ready for deployment. Otherwise
On 23.05.2008, at 04:54, Jim Gettys wrote:
On Thu, 2008-05-22 at 19:28 -0400, Andres Salomon wrote:
If they put me in charge, I'd choose whichever CPU had the best
performance, lowest power consumption, and lowest price - regardless
of architecture.
Change the ordering: power consumption
On 5/23/08, Eben Eliason [EMAIL PROTECTED] wrote:
On Fri, May 23, 2008 at 9:59 AM, Alex Belits [EMAIL PROTECTED] wrote:
How many developers were in that program, and how can one join it? Is it
available now, between G1G1's?
http://wiki.laptop.org/go/Developer_program =)
There were at
On 23/05/08 18:00 +0200, Bert Freudenberg wrote:
On 23.05.2008, at 04:54, Jim Gettys wrote:
On Thu, 2008-05-22 at 19:28 -0400, Andres Salomon wrote:
If they put me in charge, I'd choose whichever CPU had the best
performance, lowest power consumption, and lowest price - regardless
On 23.05.2008, at 19:38, Jordan Crouse wrote:
On 23/05/08 18:00 +0200, Bert Freudenberg wrote:
/me wants a graphics accelerator.
Minor nitpick - you _have_ a graphics accelerator. What you really
want
is a 3D graphics engine. Be sure to keep the distinction seperate;
lots of embedded
Bert...
Part of the problem is the X driver model is pretty broken, causing much
more to be done in software than should be necessary; and it isn't clear
we're even using X efficiently at the moment... The driver stuff is
getting fixed (in general in X: this is the EXA/DRI2 work); profiling of
Jim Gettys wrote:
Bert...
Part of the problem is the X driver model is pretty broken, causing much
more to be done in software than should be necessary; and it isn't clear
we're even using X efficiently at the moment... The driver stuff is
getting fixed (in general in X: this is the
On Fri, 2008-05-23 at 17:17 -0700, Alex Belits wrote:
Jim Gettys wrote:
Bert...
Part of the problem is the X driver model is pretty broken, causing much
more to be done in software than should be necessary; and it isn't clear
we're even using X efficiently at the moment... The driver
What are the software plans for the second-generation XO?
First they need to build one out of something other than modeling clay
and Photoshop.
Then whenever your hand comes close to the laptop, ugly black bars are
going to cover all the edges of that nice sky-blue screen.
There's no need to
On 5/22/08, John Gilmore [EMAIL PROTECTED] wrote:
What are the software plans for the second-generation XO?
First they need to build one out of something other than modeling clay
and Photoshop.
[...]
current touchpad can do tap to click (ticket #959). But developers
and users of devices
On Fri, May 23, 2008 at 10:17 AM, John Gilmore [EMAIL PROTECTED] wrote:
Then whenever your hand comes close to the laptop, ugly black bars are
going to cover all the edges of that nice sky-blue screen.
I hear ugly black is the new black these days :-)
It's always harder than you want it to
On Thu, 22 May 2008 15:17:02 -0700
John Gilmore [EMAIL PROTECTED] wrote:
What are the software plans for the second-generation XO?
[...]
If they'd put me in charge, I'd make sure it wasn't an x86 CPU, so
this pesky Windows nonsense wouldn't come up. Nobody argues that a
non-x86 has to
On Thu, 2008-05-22 at 19:28 -0400, Andres Salomon wrote:
If they put me in charge, I'd choose whichever CPU had the best
performance, lowest power consumption, and lowest price - regardless
of architecture.
Change the ordering: power consumption and price (closely related to
integration
21 matches
Mail list logo
