----- Original Message ----- From: "Denis Oliver Kropp" <[EMAIL PROTECTED]> To: "Brian G. Rhodes" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 05, 2004 10:09 AM Subject: [directfb-users] Re: dfb_surface_soft_lock
> Quoting Brian G. Rhodes: > > If you're writing into a surface at 0,0 you can call > > dfb_surface_soft_lock and not worry about offsetting the surface memory > > address correct? > > > > for instance when doing a > > > > dfb_surface_soft_lock() > > dfb_scale_linear_32() > > dfb_surface_unlock() > > > > or does this become a problem depending on whether it writes to system > > vs video memory? > > Hi, > > if you are writing an image provider or other module it's right. > > But you shouldn't use these core functions in an application. > > -- > Best regards, > Denis Oliver Kropp > > .------------------------------------------. > | DirectFB - Hardware accelerated graphics | > | http://www.directfb.org/ | > "------------------------------------------" > > Convergence GmbH > Thanks for all the input. The changing the major id from 253 to 252 worked
