Post Reply 
CPU graphics capabilities.
09-10-2015, 12:37 PM
Post: #1
CPU graphics capabilities.
Does the HP programming make use of the CPU's 2D accelleration (in hardware) and bitblitter (would be very useful for animation).
????
...as outlined in the CPU spec...here...
http://www.wvshare.com/datasheet/SAMSUNG...3C2416.PDF
Find all posts by this user
Quote this message in a reply
09-10-2015, 12:45 PM
Post: #2
RE: CPU graphics capabilities.
(09-10-2015 12:37 PM)webmasterpdx Wrote:  Does the HP programming make use of the CPU's 2D accelleration (in hardware) and bitblitter (would be very useful for animation).
????
...as outlined in the CPU spec...here...
http://www.wvshare.com/datasheet/SAMSUNG...3C2416.PDF

Probably yes but just guessing here (the command that you use most with graphics contains "blit")

My website: erwin.ried.cl
Visit this user's website Find all posts by this user
Quote this message in a reply
09-10-2015, 03:26 PM
Post: #3
RE: CPU graphics capabilities.
No, we do not use it.

Basically, there are some important limitations to the 2D accelerator with respect to memory needing to be in certain configurations (which waste ~1MB more RAM for the end user), incompatible drawing routines (only supports lines, blits and pixels of certain limited types), the inability to mix rendered fonts with the screen window without going through ridiculous hoops, and a few other things from memory.

Basically, it wouldn't get us (or you) much in return for the effort to getting everything working properly.

TW

Although I work for HP, the views and opinions I post here are my own.
Find all posts by this user
Quote this message in a reply
09-10-2015, 05:12 PM
Post: #4
RE: CPU graphics capabilities.
(09-10-2015 03:26 PM)Tim Wessman Wrote:  No, we do not use it.

Basically, there are some important limitations to the 2D accelerator with respect to memory needing to be in certain configurations (which waste ~1MB more RAM for the end user), incompatible drawing routines (only supports lines, blits and pixels of certain limited types), the inability to mix rendered fonts with the screen window without going through ridiculous hoops, and a few other things from memory.

Basically, it wouldn't get us (or you) much in return for the effort to getting everything working properly.

Interesting. I've used 2D accellerators before and have run into the memory config thing. You are right...it can be a pain. This brings to mind something we are going to want to know for when a C compiler becomes available for the Prime.... While we know what flash and RAM chips are used, we do not have info on just how memory is configured. Is that info available anywhere, and also is a memory map available? We won't need that until much C development gets done, but it'd be nice to have for the future, when it does become available.

Thx
-webmasterpdx
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: