v4nelle: guys any help about these? (II) RADEONHD(0): Query for AtomBIOS Get Panel EDID: failed
v4nelle: this*
Zajec2: emmes: can you sync your repository?
Zajec2: sync or... whatever :) just push changes to public? :)
Zajec2: i'll try to get some BIOSes today and maybe try to understand types and flags
Nightwulf|work: hi all
Zajec2: emmes: thanks for fixing :)
emmes: as usual, I just forgot pushing :-]
OrangeOne: hi!
Obscene_CNN: hi
OrangeOne: Zajec: did you check your vga connection? Tearing or no tearing?
Zajec: Obscene_CNN: were I talking with you about tearing?
Obscene_CNN: not today
Zajec: sry :)
Zajec: OrangeOne: ahh, it was you ;)
Zajec: OrangeOne: i really don't know... just played whole movie 720p and didn't saw any tearing
Zajec: OrangeOne: i thought i saw this earlier
Zajec: OrangeOne: i mean HDMI of course
Zajec: OrangeOne: don't understand that :/
agd5f: Zajec: the radeonhd anti-tearing stuff only works on crtc0 IIRC
MostAwesomeDude: agd5f: Sorry to bug. I'm cleaning up RadeonFeature. Is KMS planned for RHD ever, or should I cross it out as not planned?
agd5f: MostAwesomeDude: I don't know. I don't plan to
MostAwesomeDude: agd5f: And I don't plan to, either. Just checking. :3
yangman: MostAwesomeDude: someone will probably do it eventually. personally, I'm not planning to touch it for r5xx on RHD
OrangeOne: I still get tearing (at least one horizontal line that goes up and down...(anime)). For the movies it's worse...
OrangeOne: When i s
OrangeOne: sorry
OrangeOne: when i disable the laptop screen i still have the tearing
yangman: OrangeOne: does it tear on the laptop screen?
OrangeOne: no
OrangeOne: only on the hdmi output
agd5f: OrangeOne: you need to make sure the screen is using crtc 0
agd5f: if you don't want it to tear
yangman: well, it definitely still needs some work. I notice some tearing on my monitor also
MostAwesomeDude: yangman: If nobody's started on it, and no devs are planning on doing it, then I'll cross it out. "Eventually" is a nice thought, but it doesn't make code spring into existence IME. :T
OrangeOne: what do you mean by crtc 0? What should i do inside my xorg.conf / xrandr change?
agd5f: OrangeOne: specify the crtc with xrandr, e.g., xrandr --output VGA-0 --crtc 0 --mode ...
yangman: MostAwesomeDude: yeah, UNKNOWN is a better fit than TODO at this point
MostAwesomeDude: yangman: Well, I know the status of it. Nobody's started, nobody's signed up to do it, and it's not needed. N/N is the better fit at this point.
agd5f: OrangeOne: or use radeon. it should do the right thing for both crtcs
OrangeOne: radeon does not work
OrangeOne: i still get the tearing
OrangeOne: the main difference being that i can't get any sound from the radeon driver (which is obvious as non implemented yet)
OrangeOne: using the crtc option doesn't seem to work for me...
OrangeOne: i mean i still get the tearing
agd5f: OrangeOne: verify that it's using crtc 0 with xrandr --verbose
OrangeOne: yep
OrangeOne: you may be right
OrangeOne: the result is a bit messed up but it seems that the tearing on the hdmi is gone
Zajec: feels bored (is there such word?) of playing with radeon/radeonhd... as KMS is coming :)
Zajec: actually everything I'm interested in should go to KMS :)
Zajec: mode setting, power management, backlight control :)
OrangeOne: I would like to be able to switch between two modes: the clone mode and the virtual desktop. I'm currently in virtual desktop. What should be the xrandr command?
OrangeOne: I have one panel (PANEL) 1440x900 and my tv (DVI-D_1) 1920x1080
OrangeOne: If i do xrandr --output DVI-D_1 --crtc 0 --mode 1920x1080 --output PANEL --crtc 1 --mode 1440x900
OrangeOne: It seems that i don't get the tearing on my tv but the resolution of the tv is 1440x900 instead of 1920x1080
MostAwesomeDude: Zajec: Feel free to hack away at KMS. :3
OrangeOne: Then if i do "xrandr --output DVI-D_1 --crtc 1 --mode 1920x1080 --output PANEL --crtc 0 --mode 1440x900" i get the tearing on my tv
OrangeOne: but the resolution is ok
Zajec: MostAwesomeDude: can't resolve issue with weird picture on my R6xx
Zajec: MostAwesomeDude: resolved getting modes, crasher but rest is over my skills
Zajec: OrangeOne: if you start with PANEL only, it will be on CRTC0 probably, you may have to free CRTC0 first
Zajec: OrangeOne: so first switch PANEL to use CRTC1, and after that enable DVI on CRTC0
MostAwesomeDude: Finished.
MostAwesomeDude: Just updated http://wiki.x.org/wiki/RadeonFeature. If there's errors, let me know. :3
Zajec: MostAwesomeDude: RadeonFeature you mean?
Zajec: yup, that's what you mean :)
MostAwesomeDude: Yep. :3
Zajec: MostAwesomeDude: splitting Gallium part on drivers sounds good for me
Zajec: MostAwesomeDude: maybe the same for Mesa?
MostAwesomeDude: Zajec: Well, it reflects a different paradigm.
Zajec: but... no, sorry
Zajec: yup, already see my mistake
MostAwesomeDude: The 3D features represent our knowledge of the HW and how to program it.
MostAwesomeDude: I only left Mesa up there because it didn't have any other place to go.
OrangeOne: zajec: I tried what you said and ended up with a black screen (had to kill X)
MostAwesomeDude: So, that's how we can have DONE for all the r500 and r300 stuff, and yet r300g is still fail. :3
edman007: hmm, i upgraded X (and i suppose radeonhd), and i get this:
edman007: mtrr: no MTRR for c0000000,10000000 found
edman007: X:29500 conflicting memory types c0000000-d0000000 write-combining<->uncached-minus
edman007: reserve_memtype failed 0xc0000000-0xd0000000, track write-combining, req write-combining
edman007: any idea why? X is noticeably slower :(
rsmith: What are the standard things to check if I suspend to RAM and resume with no display? (The machine is running fine-- I can ssh to it) (Debian lenny with git radeonhd)
edman007: rsmith, well start with dmesg, top, all logs...
airlied: also try resume without X running
rsmith: ok