From: Alex D. <ag...@ya...> - 2003-12-01 18:41:23
|
--- Mike Mestnik <che...@ya...> wrote: > > --- Alex Deucher <ag...@ya...> wrote: > > > > --- Mike Mestnik <che...@ya...> wrote: > > > The screen size(in pixels or mm) is now x1 + x2 by (y1 > y2) * > y1 + > > > (y1 < y2) * y2. Swap (y and > > > x) and (1 and 2) where needed. Then the DPI should be calculated > > > using the largest or the default > > > metamode. > > > > > > This is what I see. > > > (**) RADEON(0): MergedFB: Display dimensions: (330, 240) mm > > > (**) RADEON(0): MergedFB: DPI set to (255, 152) > > > > > > ?255? Oviously wrong! > > > > > > > Xfree86 doesn't really have a way of setting different DPI values > for > > each head in a single logical screen scenario like xinerama or > > mergedfb. what xinerama does is kind of take an average of DPI > values > > from each head. mergedfb works similarly. it tries to get the > values > > from DDC and barring that, it attempts to calculate a sane base. > it > > works in most instances. however if you are not getting the value > you > > want, you can specify it as an option > > option "MergedDPI" "100,100" > > for example... > > > Sounds good. > > > You can see how it gets calulated in radeon_mergedfb.c: > > RADEONMergedFBSetDpi(). if you find anything that looks off let me > > know, however I haven't had any problems with it and I don't see > > anything off hand that looks off. > > > I'm a bit curious myself, it must have forgot to devide when getting > the average. > > My Work. > The total display is 1920x1440 and 26x9.44 inches, so I get (73, 153) > DPI. > (147, 152) + (107, 111) / (2, 2) = (127, 131) > hmmm... i'll take a look at the code. also as I recall you specified a display size in your monitor section. if you do that will be used for calculation. > > > 2: > > > I just can't get 256x240 and 1400x1050 to 1656x1050, it skips > it > > > and uses the next one 1024x768 > > > and 1024x768 to 1024x768 (Clone). I have no idea what is going > on > > > here, nothing is left ought of > > > the log. I have set pll->min_pll_freq = 3000 and that got it > working > > > for xineramia. > > > > > > > If you want to use a special 256x240 mode (256x240@120d for > example) > > then you need to specify that mode name in your metamodes and the > modes > > sub-section of your screen config as well as defining the modeline. > eg: > > SubSection "Display" > > Depth 16 > > Virtual 3320 1440 > > Modes > > "1920x1440" > > # "1856x1392" > > # "1792x1344" > > "1600x1200" > > "1400x1050" > > "1280x1024" > > # "1280x960" > > # "1152x864" > > "1024x768" > > "800x600" "640x480" > > "320x240" > > "256x240@120d" > > ^^^^^^^^^^ add this! > > this is because the metamodes draw from the modes listed in the > screen > > section of your config. > > > I missed that, do you have to put the mode here regardles of what > head you would like to use it > on? Yes. > > > also you may have to specify a different crtc2 hsync/vrefresh range > for > > your custom modes since it seems to be too high for your mode: > > (II) RADEON(0): Not using mode "256x240@60d" (vrefresh out of > range) > > > That is also odd, I use that mode in xineramia. I recently stoped > using it and I just use 120Hz > one. I'l let you know what I find. > Sounds good. Alex __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ |