Ok, so we're talking about .17 while we're waiting for TI drivers.

Where did .16 go? I didn't see that anywhere?

.16, yeah. That's the question I was afraid to ask. Where is it?

0.16, what's that?

Kidding, - we will be pushing out 0.16 this week. Our release schedules seemed to intermix with a OpenSUSE release and hence there was 20000 packages in build queue..

0.16 will be a transitional release just to get it out there before we make the leap. There -will- be bugs (in app manager, etc).

Distribution is not really a problem, we can always do clickthrough downloads if some special EULA is required (this is very similar to what was the case with the Intel ethernet drivers on the NSLU2, so not really unprecedented).

What exactly are they going to release drivers for.. And, are they going to be binary only?

ie, gps5300 chip from TI, How to access and program the IVA, Jazelle instruction set, PowerVR, ...

If I understood its open source driver for hardware acceleration hence OpenGL ES.

Together with the open sourced WiFi driver it will allow one to run more recent kernel. gps5300 (closed source), Jazelle (not supported by driver) are not related to this.

Jazelle works, see Javispedro's and my work. I don't believe it requires anything kernel related, it's just a coprocessor and some instructions to enter the mode.

Can the 3d accelerator render to a virtual 800x480 screen on his own framebuffer so that it is only needed to copy the data 1:1 from the PowerVR framebuffer to this special N8xx chip?
Or isn't the 3d accelerator able to render in a 800x480 screen?
In other words, is it necessary to render in a smaller screensize?


If not, how slow is the 1:1 copying process from the PowerVR framebuffer to the speczial N8xx chip framebuffer?

When copying a 800*480 screen @ 16 bit color depth, the size of the data will be allways constant.
In this case 750 kByte/frame.

So the question is, what is the bandwith between the PowerVR framebuffer to the special Nxx chip framebuffer?
If the bandwith is 22 MB/s it is fast enough to render 30 fps second, which is in my opinion enough.


But, is the PowerVR 3d chip able to work at 16 bit color depth?
As far as i know from the old Kyro 2 cards from the PC, these 3d chips allways rendert in 32 Bit color depth intern.

So the next qeustion ist, can we store 16 bit color depth data in the PowerVR framebuffer or is this allways 32 bit color dept data?
In the latter case, copying the data to the special N8xx framebuffer chip it would be much slower.

3 month late, where is the driver?

There was a (bad) reply to u2maemo and my reply to the reply.
Both disappeared.
I'd like to be notified of any censoring activity regarding my messages.Thank you.