On Wed, 2007-10-17 at 12:26 -0400, Alex Deucher wrote: > On 10/17/07, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > > > On Wed, 2007-10-17 at 17:47 +0200, Sjoerd Simons wrote: > > > On Wed, Oct 17, 2007 at 05:29:39PM +0200, Michel Dänzer wrote: > > > > > > > > So basically, it looks like: > > > > > > > > PowerBook5,*: 'powerbook-exttmds' > > > > > > Or more specifically > > > PowerBook5,[1-5]: 'powerbook-exttmds-single' > > > PowerBook5,[78]: 'powerbook-exttmds-dual' > > > PowerBook5,6: either 'powerbook-exttmds-single' or > > > 'powerbook-exttmds-dual' > > > > > > Looking at the bugreport.. Both options seem different enough in that > > > things > > > work for me with a 5,2, but not for another reporter with a 5,8. (Maybe > > > there > > > can be one way that works for both though, who knows). > > > > Yeah, I was assuming the TMDS type could be autodetected, but maybe not > > - is it part of the connector tables as well? > > all the connector table cares about is whether it's external or > internal TMDS. we'd need a way to detect or hardcode the external > TMDS chip. Unfortunately, it seems all sil chips have the same values > for vendor and chip id, so that's useless. We can either > change/extend the MacModel range or add another option to specify the > external chip.
Probably the latter, or is this Mac specific? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
