|
From: Nicholas W. <nw...@ne...> - 2002-10-18 22:15:40
|
Antonino Daplas wrote: > Not necessarily painless... > > Given timings in X modeline format (you can generate with xvidtune): > > "XRESxYRES" MHZ XACTIVE FP_X HSYNC BP_X YACTIVE FP_Y VSYNC > BP_Y +hsync +vsync > > Then timings in fb.mode: > > mode "XRESxYRES MHZ" > # D: "MHZ, H: HorizSync kHz, V: VertRefresh Hz > geometry xres yres vxres vyres bpp > timings pixclock left right upper lower hsync vsync > hsync high > vsync high > endmode > > where: > > pixclock = 1000000/MHZ > left = BP_X - HSYNC > right = FP_X - XACTIVE > upper = BP_Y - VSYNC > lower = FP_Y - YACTIVE > hsync = HSYNC - FP_X > vsync = VSYNC - FP_Y > > What you need to concentrate on is the timings field of fb.modes. This > also assumes that the driver actually reads the timings field. Some > drivers disregard those values (considers only xres and yres) then > configure their own timings. > Tony, Thank you, this is *exactly* what I was looking for! I never knew what xvidtune was really for, but this sure answers that one. Cheers, Nicholas |