quick questions on two hijack ioctl calls | Programming

You are not logged in. [Log In] empegbbs.com » Forums » empeg-car » Programming » quick questions on two hijack ioctl calls

Topic Options

#75705 - 27/02/2002 07:39 quick questions on two hijack ioctl calls
siberia37 old hand Registered: 09/01/2002 Posts: 702 Loc: Tacoma,WA	Sorry to post this message but I really could not find the answer... as far as the ioctl(EMPEG_DISPWRITE) call goes.. my understanding is you should always pass it a full screen buffer, even if you have done a ioctl(EMPEG_SETGEOM) is this correct? And also what format should the buffer for EMPEG_DISPWRITE be in? I assume one pixel per byte, but what byte values represent the four colours? Next is a simple one.. is it just me or does ioctl(EMPEG_DISPTEXT) not wrap text to the next line? If it doesn't that's fine, I just was curious if it would wrap text.
Top

#75706 - 27/02/2002 08:26 Re: quick questions on two hijack ioctl calls [Re: siberia37]
mlord carpal tunnel Registered: 29/08/2000 Posts: 14496 Loc: Canada	Its a 2048 raw software screen buffer, with two 2-bit pixels per byte (one 2-bit pixel per nibble). Don't ask which pixel is which -- I always get confused by it! Just try it, and flip the order if you get "lucky" on the first try. Buffer layout is row0, row1, .. row31. Each row is 128 pixels (64 bytes). Look at /proc/empeg_screen.raw for an example.
Top