Not sure what forum this belongs to really..
I'm in a project where we use an embedded pc as part of the hardware.
We're down to choosing between two different pc boards, very similar but the integrated graphics look a bit different:
- VIA Apollo BPL133 "64-bit, single-cycle 2D/3D graphics engine", 2-8MB
- VIA Twister with integrated S3 Pro Savage4, 8-32MB
Now we just want to do some "realtime" (we dont need anything like 60fps) scrolling 2D graphs with text, "title" screens etc, with decent looks.
We're going to use Java for all the software, because already have some code in Java and we want a bit of portability.
We're obviously not doing any hardcore graphics, but it sounds to me like the performance could be quite different in terms of pure hardware speed. In our last project we had some integrated Savage4 hardware, and the bottleneck for graphics seemed to mostly be in the app's graphics package (and we spent most cpu in the graphics package), but could this change with slower hardware?
Or would the bottlenecks normally be in the drivers, jre or app?
I am assuming we won't run into framebuffer limits, and that the non-S3 graphics is in fact slower.
I'm in a project where we use an embedded pc as part of the hardware.
We're down to choosing between two different pc boards, very similar but the integrated graphics look a bit different:
- VIA Apollo BPL133 "64-bit, single-cycle 2D/3D graphics engine", 2-8MB
- VIA Twister with integrated S3 Pro Savage4, 8-32MB
Now we just want to do some "realtime" (we dont need anything like 60fps) scrolling 2D graphs with text, "title" screens etc, with decent looks.
We're going to use Java for all the software, because already have some code in Java and we want a bit of portability.
We're obviously not doing any hardcore graphics, but it sounds to me like the performance could be quite different in terms of pure hardware speed. In our last project we had some integrated Savage4 hardware, and the bottleneck for graphics seemed to mostly be in the app's graphics package (and we spent most cpu in the graphics package), but could this change with slower hardware?
Or would the bottlenecks normally be in the drivers, jre or app?
I am assuming we won't run into framebuffer limits, and that the non-S3 graphics is in fact slower.
Last edited by a moderator:
