On Sun, 2002-07-14 at 13:57, hy0 wrote:
>
> > On Thu, 2002-07-11 at 22:27, Kevin E Martin wrote:
> > > I've just checked in a large patch from ATI. Here's the CHANGELOG
> > > entry:
> > >
> > > 199. ATI patch to:
> > > - Fix Dell OEM VE card support
> > > - Add better clone mode support
> > > - Fix large panel (>= 1600x1200) detection and initialization
> problems
> > > - Remove "PanelSize" and "CrtScreen" options since they are no
> longer
> > > needed with new CloneMode and improved flat panel support
> >
> > At least Option "PanelSize" would still be useful for systems where we
> > can't determine the panel parameters yet.
>
> Current Radeon driver supports two kinds of panel: TMDS panel (usually used
> for desktop, named as DFP in the driver for some legacy reason) and LVDS
> panel (usually used for laptop, named as LCD in the driver).
> The TMDS panels should be DDC capable, if not, the BIOS won't even be able
> to bring them up to text mode. For this kind of panel, the radeon driver
> will try to do DDC detection first. If it fails for some reason, the driver
> will used EDID data detected by BIOS. With the DDC info, the driver can
> figure out the panel size and bring it up automatically.
> The laptop (LVDS) panels usually are not DDC capable (some new ones are).
> The panel size and timing information are hard coded into video BIOS and
> radeon driver will use it to bring the panel up. The only potential problem
> here is that some custom version of BIOS doesn't follow the rule and put the
> panel info to a different place. I haven't come across such a laptop yet and
> would like to know if someone has one.
Not every machine has a BIOS.
> Only knowing panel size (together with VESA timings) usually is not good
> enough to bring a LVDS panel up properly. Even with the correct modeline,
> it's better to know other things (like power delay) to safely turn the panel
> on/off. Let user to specify panel size can be error prone. Anyway, if there
> are people out there really requiring this option, I can put it back.
I think it's still needed as a fallback until automatic detection truly
works everywhere. Which might not be far away though, more below...
> As for non-native modes (resolution lower than panel size), by default,
> radeon driver will use the internal ratio matrix expansion (RMX) unit to
> scale the display down. It works not only for all standard VESA modes, it'll
> work also for any mode between 320x200 and panel size, for example 600x500.
That was just an example why using virtual resolution as panel size
doesn't work in general.
> > > - Add "DDCMode" option to detect and use DDC modes
> > > - Add "PanelOff" option to disable panel on laptops
> > > - Fix corrupted console problem
> > > - Other misc fixes
> > > (#A.1043, Hui Yu@ATI).
> > >
> > > I'd like get some feedback on how it works for others with both desktop
> > > and laptop Radeons.
> >
> > Doesn't quite work on a Titanium PowerBook III (without Option
> > "UseFBDev", with a 1280x854 modeline obtained by radeonfb via EDID which
> > works fine with that option). There are flickering lines on the right
> > side.
>
> Is the DDC detection OK?
No, because we don't have a way to determine the display type yet (do
you happen to know a way which doesn't require a BIOS?). If I hardcode
info->DisplayType = MT_LCD;
info->DDCType = DDC_DVI;
DDC works (nice!), but there's still the same flicker. Option "DDCModes"
isn't used, but I assume not providing any Modes is mostly the same.
--
Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
