https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #109 from Kevin Brace <kevinbr...@gmx.com> --- (In reply to Christopher from comment #108) Hi Christopher, > No sweat on the cable -- Dad paid for it, and he's returning it and getting > his Seasick Washingtons back. It'll be a week or so before the one I got on > eBay for $1 (!) arrives from Kentucky, though -- since I'm keeping the > monitor (he said I could) I'll be able to test again on that soon but not > immediately. > > I'll be going back home from my Dad's tomorrow, so I won't be very > responsive till Thursday, at the earliest. Travel time's only one little > tiny hour, but it takes me a while to pack, unpack, and reconstruct > everything the way it needs to be, you know? > > Hope you're not dealing with jet lag tho -- that can be nasty stuff. I think one of the major problem of OpenChrome code is that it relies on a predefined table to initialize which display output will be available. As far as I am concerned, this is a terrible way to initialize display outputs. I think the code should be rewritten to completely eliminate the predefined table, but I doubt I can get anyone else to support doing this. In other words, only I2C bus should be used to figure out which display is available. In your particular case, I do not own a comparable hardware to what you have, so it is extremely difficult to analyze what is going wrong. Over the past 2 months, I have posted about 10 or so patches not related to the bug you have observed. Unfortunately, I got no one with Git commit privilege to commit the patches. At this point, I feel like the OpenChrome project is going nowhere due to lack of interest and developer neglect. Regards, Kevin Brace -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/openchrome-devel