Hi, > > As it turns out (I think??), Haiku app_server seems to not respect > > the > > framebuffer adress given to it (GET_FRAME_BUFFER_CONFIG) by the > > driver. > > It really should: it's no requirement of any driver to pinpoint > > it's > > framebuffer at offset zero in the cardram. > > It only gets the address by using GET_FRAME_BUFFER_CONFIG. Of course :) > > Could one of you tell me if app_server uses fbc for the buffer > > location > > or not? And if not, fix it? > > It sure does. How would it even work if it didn't? See > src/servers/app/drawing/AccelerantBuffer.cpp. I'll have a look. I was thinking that it would indeed use it, except for during certain conditions (which would be a fault then). If you say there is no such fault, then there must be something else going wrong that 'by luck' gives the same memory offset fault as not using fbc would on the nvidia driver. OTOH: it seems strange that the 3D driver should influence the app_Server where to draw the window tab! (not only the content is drawn at the wrong spot (which is executed by the 3D driver), but also the window tab (which gets drawn by the app_server....) Bye! Rudolf.