Raspberry Pi
category: code [glöplog]
gloom: just replied :)
I have no experience in graphics coding for embedded and closed platforms, so...
Imagining I only want to run my code on this specific platform and since everything is in the same RAM (no VRAM) can we access some framebuffers with the CPU without a performance penalty, while the GPU does it stuff? And can we fake transform feedback by feeding a vertex buffer as a framebuffer to the GPU?
Is that kind of stuff possible in terms of OpenGL ES extensions?
Imagining I only want to run my code on this specific platform and since everything is in the same RAM (no VRAM) can we access some framebuffers with the CPU without a performance penalty, while the GPU does it stuff? And can we fake transform feedback by feeding a vertex buffer as a framebuffer to the GPU?
Is that kind of stuff possible in terms of OpenGL ES extensions?
Quote:
I got mine two days ago, and I must say coding wise it's surpassed my expectations. Completely standardised hardware with flawless OpenGLES 2.0 without tearing or frameskips, and minimal setup. Feeling the same excitement as when I started coding on the Amiga or C64, at the moment.
That's great to hear - just what I was looking for. Having a standardized modern platform where people can code stuff that runs perfect one frame is something that has been missing!
I am a bit surprised that it does though, since I heard that the standard Linux was pretty slow, I thought we would have to wait until a raw "demoOS" or something was created.
On a related note, I finally got the invitation to order mine a while ago, but doesn't look like it will be delivered until after the summer. :(
this thread doesn't have enough pictures
Sdw: Make no mistake - Linux runs hella slow on it. Fortunately Linux isn't doing much unless you make it, so it doesn't really get in the way unless you run X or something, and you don't need that for coding or accessing the sound/video hardware.
Quote:
Make no mistake - Linux runs hella slow on it.
Even slower than that. It's really a pain in the ass, takes seconds to open a single window in X.
:O how is it in command line ?
Is it a scheme to sell outdated broadcom chips? :P
I still haven't connected mine, I'll only be near an HDMI screen in the end of the week.
I still haven't connected mine, I'll only be near an HDMI screen in the end of the week.
About Linux being slow => I used to run Linux on a BeagleBoard. X with Enlightment window manager (which is *not* minimalistic by far) was very comfortable. Looking at the spec of a Beagleboard VS Rasberry Pi, I would say something is not working as well as it could...
Could it be that Beagleboard is using the GPU while Raspberry Pi still isn't?
It could be, especially if you use Gnome or KDE, those are bloated beasts who seems to give a justification to Moore's law...
A way to check is to just try with a minimalist window-manager (http://dwm.suckless.org/ is easy to setup and won't take much room). If opening a window (I assume you tried a simple app, say, xterm) is still slow, something else is going terribly wrong. Then you check with the 'top' utility to see who's eating all those CPU cycles. I remember that some badly setup daemons were spitting logs like there's no tomorrow, enough to eat significant CPU time :p
A way to check is to just try with a minimalist window-manager (http://dwm.suckless.org/ is easy to setup and won't take much room). If opening a window (I assume you tried a simple app, say, xterm) is still slow, something else is going terribly wrong. Then you check with the 'top' utility to see who's eating all those CPU cycles. I remember that some badly setup daemons were spitting logs like there's no tomorrow, enough to eat significant CPU time :p
Erste Schritte mit dem Raspberry Pi (in german)
-SP-: Solution: Don't run X, which is not (yet) even hardware accelerated on the Pi.
p01: Command line works fine of course (bash isn't exactly resource hungry by today's standards), but some operations take more time than you're probably used to. Installing software using the apt tool chain is a lot slower than on a "normal" computer for instance.
Vim runs well for coding, with the odd second-long freeze every now and then while it's writing to the SD card, and gcc is quite fast.
p01: Command line works fine of course (bash isn't exactly resource hungry by today's standards), but some operations take more time than you're probably used to. Installing software using the apt tool chain is a lot slower than on a "normal" computer for instance.
Vim runs well for coding, with the odd second-long freeze every now and then while it's writing to the SD card, and gcc is quite fast.
Ah. And we have a contender: The Gooseberry (Pi?)
If Raspberry Pi becomes a kind of standard demo hardware I will code for it.
Someone should hurry up and make a case with a built in reset switch. That would be lovely :)
That 'gooseberry' is an interesting one. They've not made anything (in fact I think it's a bit of a cash-in on the raspberry's success), but they're simply reselling a board made for generic tablets. That means it should be plenty cheap, hardware will perhaps be a bit better, and it'll support android.
Finally!
uncle_H: do an un-boxing video !
Quote:
Raspberry Pi @Raspberry_Pi
Evening spent playing boardgames in the sofa-strewn bar of an independent cinema. I feel I could very much get to like Iceland.
Their twitter account should be used more professionally.
xernobyl: you are obviously the social media marketing expert.
We can now confirm that your Raspberry Pi will be dispatched the week commencing 09/07/2012. \o/
steam: thanks, but I don't remember ordering one?
That Gooseberry thing will be sold for ~50€ + 4€ shipping. Damn cheap for the performance. Hope it has GPIO pins, else it is not that useful for homebrew hardware tinkering...
psonice: i hardly remember ordering one myself :)