Am 18.11.2010 15:34, schrieb Jerome Glisse:
> Best is to use mesa master repository. And kernel 2.6.36 or newer, the
> other drm kernel tree are mostly to fix issues and are interesting if
> you are facing one of those issues or just want to help in testing
> drm.
Just a quick follow-up: current d
Am 18.11.2010 15:34, schrieb Jerome Glisse:
Best is to use mesa master repository. And kernel 2.6.36 or newer, the
other drm kernel tree are mostly to fix issues and are interesting if
you are facing one of those issues or just want to help in testing
drm.
Just a quick follow-up: current drm gi
Hi,
I find the various git repositories for drm sometimes a little
confusing. For example, what is the difference between d-n and d-c-n?
Maybe it would be a good idea to fill out the gitweb information for
each each repository. Currently they all report "Unnamed repository;
edit this file to n
Hi,
I find the various git repositories for drm sometimes a little
confusing. For example, what is the difference between d-n and d-c-n?
Maybe it would be a good idea to fill out the gitweb information for
each each repository. Currently they all report "Unnamed repository;
edit this file to
On 28.10.2010 11:12, wrote sam tygier:
> Without this patch i get no display (X or VT) on myEIZO S2242W monitor
> when using KMS
>
> This was discussed back in september, this is the second version of the
> patch based on ajax's comments. i have opened a bug for the issue:
> https://bugs.freedeskto
On 28.10.2010 11:12, wrote sam tygier:
Without this patch i get no display (X or VT) on myEIZO S2242W monitor
when using KMS
This was discussed back in september, this is the second version of the
patch based on ajax's comments. i have opened a bug for the issue:
https://bugs.freedesktop.org/sho
Am 22.09.2010 06:40, schrieb Alex Deucher:
> 2010/9/21 Marius Gr?ger:
>> On 10.09.2010 17:20 Alex Deucher wrote:
>>>
>>> The scaler doesn't appear to work with interlaced modes as you've
>>> noticed; I don't off hand know whether it can be made to or not.
>>> Unfortunately, I won't have time to dig
Am 22.09.2010 06:40, schrieb Alex Deucher:
2010/9/21 Marius Gröger:
On 10.09.2010 17:20 Alex Deucher wrote:
The scaler doesn't appear to work with interlaced modes as you've
noticed; I don't off hand know whether it can be made to or not.
Unfortunately, I won't have time t
On 10.09.2010 17:20 Alex Deucher wrote:
> The scaler doesn't appear to work with interlaced modes as you've
> noticed; I don't off hand know whether it can be made to or not.
> Unfortunately, I won't have time to dig into this more for a while.
Is there public documentation available wrt this matt
This allows for a more exact fitting on the physical
display. The new properties default to zero which corresponds to the
previous underscan border width[height] formula:
(display_width[display_width] >> 5) + 16.
Example to set a horizontal border width of 30 and a vertikal border
height of 22:
On 10.09.2010 17:20 Alex Deucher wrote:
The scaler doesn't appear to work with interlaced modes as you've
noticed; I don't off hand know whether it can be made to or not.
Unfortunately, I won't have time to dig into this more for a while.
Is there public documentation available wrt this matter?
of 22:
xrandr --output HDMI-0 --set underscan on --set "underscan hborder" 30 --set
"underscan vborder" 22
Signed-off-by: Marius Gröger
---
drivers/gpu/drm/radeon/radeon_connectors.c | 55 ++--
drivers/gpu/drm/radeon/radeon_display.c| 28 +
I sent this message during the weekend and I'm afraid it might got lost
during people's monday morning inbox purging ;-) Seriously, I'd be
grateful for any insights on that matter which keeps me from moving on
to 2.6.36...
Thanks
Marius
Original Message
Date: Sat, 11 Sep 2010
I sent this message during the weekend and I'm afraid it might got lost
during people's monday morning inbox purging ;-) Seriously, I'd be
grateful for any insights on that matter which keeps me from moving on
to 2.6.36...
Thanks
Marius
Original Message
Date: Sat, 11 Sep 201
With the latest d-r-t my grub cmdline option video=1280x720 at 50 no longer
works (RS780, output to LCD TV via HDMI). The fbcon apparently is
enabled, but the TV doen't get a displayable picture anymore. Booting
with d-r-t from 4 weeks ago works and correctly uses the EDID reported
1280x720 at
With the latest d-r-t my grub cmdline option video=1280x...@50 no longer
works (RS780, output to LCD TV via HDMI). The fbcon apparently is
enabled, but the TV doen't get a displayable picture anymore. Booting
with d-r-t from 4 weeks ago works and correctly uses the EDID reported
1280x...@50 mod
On 10.09.2010 09:19, wrote Alex Deucher:
> They aren't compatible.
Hm, ok. Is this supposed to be quick fix or is there any chance to get
proper underscan for interlaced modes?
Secondly, have you had a chance to look at my register dumps? Any clues
as to why the Xserver prunes interlaced modes
On Thu, 9 Sep 2010 11:03:54 -0400
wrote Alex Deucher :
> Does disabling underscan fix interlaced?
Yes, without underscan I can switch to my manually defined interlace
mode and it looks ok.
However, the EDID reported interlace modes are still pruned by the
Xserver, so there still seems to be a su
On 10.09.2010 09:19, wrote Alex Deucher:
They aren't compatible.
Hm, ok. Is this supposed to be quick fix or is there any chance to get
proper underscan for interlaced modes?
Secondly, have you had a chance to look at my register dumps? Any clues
as to why the Xserver prunes interlaced mode
On Thu, 9 Sep 2010 11:03:54 -0400
wrote Alex Deucher :
> Does disabling underscan fix interlaced?
Yes, without underscan I can switch to my manually defined interlace
mode and it looks ok.
However, the EDID reported interlace modes are still pruned by the
Xserver, so there still seems to be a su
Am 09.09.2010 17:03, schrieb Alex Deucher:
> Does disabling underscan fix interlaced?
I just pulled the latest d-r-t and at least I can confirm that the
problem is present without any of my tinkerings :-) I still need to
check with underscan disabled. There is no cmdline option for this yet,
is
Am 09.09.2010 17:03, schrieb Alex Deucher:
Does disabling underscan fix interlaced?
I just pulled the latest d-r-t and at least I can confirm that the
problem is present without any of my tinkerings :-) I still need to
check with underscan disabled. There is no cmdline option for this yet,
i
Am 08.09.2010 00:00, wrote Alex Deucher:
> What card do you have? Can you dump the registers with both kms and
> ums with an interlaced mode set and send them to me? Use avivotool
I have a GA-MA78GM-UD2H mainboard with an onboard RS780 chipset.
I sent the requested dumps in a PM.
While typing
Am 08.09.2010 00:00, wrote Alex Deucher:
What card do you have? Can you dump the registers with both kms and
ums with an interlaced mode set and send them to me? Use avivotool
I have a GA-MA78GM-UD2H mainboard with an onboard RS780 chipset.
I sent the requested dumps in a PM.
While typing t
Am 07.09.2010 21:00, schrieb Alex Deucher:
> Does this patch help?
No change...
> If not, does it work ok with ums (boot with radeon.modeset=0)? If so,
> we'll need to compare the modesetting paths between ums and kms and
> see what got broken with kms.
Without KMS the interlaced modes are list
Am 07.09.2010 17:53, schrieb Alex Deucher:
> It did in the past, however, at the moment, I don't have a interlaced
> capable monitor to test. Can you try again with xf86-video-ati from
> git master?
No change, at all, unfortunately. The interlace modes, while listed in
Xorg.conf, are not visible
Am 07.09.2010 17:53, wrote Alex Deucher:
> It did in the past, however, at the moment, I don't have a interlaced
> capable monitor to test. Can you try again with xf86-video-ati from
> git master?
I'll try, thanks.
Marius
Am 07.09.2010 16:52, wrote Alex Deucher:
> 2010/9/7 Marius Gr?ger:
>> Hi All,
>>
>> I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output, Xorg
>> stack on xorg-edgers, Ubuntu lucid). All interlace modes which are defined
>> in EDID seem to be pruned and don't appear in xrandr. Manu
Am 07.09.2010 21:00, schrieb Alex Deucher:
Does this patch help?
No change...
If not, does it work ok with ums (boot with radeon.modeset=0)? If so,
we'll need to compare the modesetting paths between ums and kms and
see what got broken with kms.
Without KMS the interlaced modes are listed
Am 07.09.2010 17:53, schrieb Alex Deucher:
It did in the past, however, at the moment, I don't have a interlaced
capable monitor to test. Can you try again with xf86-video-ati from
git master?
No change, at all, unfortunately. The interlace modes, while listed in
Xorg.conf, are not visible in
Hi All,
I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output,
Xorg stack on xorg-edgers, Ubuntu lucid). All interlace modes which are
defined in EDID seem to be pruned and don't appear in xrandr. Manually
adding a mode using xrandr does work, and the TV set detects the mode,
b
Am 07.09.2010 17:53, wrote Alex Deucher:
It did in the past, however, at the moment, I don't have a interlaced
capable monitor to test. Can you try again with xf86-video-ati from
git master?
I'll try, thanks.
Marius
___
dri-devel mailing list
dri-d
Am 07.09.2010 16:52, wrote Alex Deucher:
2010/9/7 Marius Gröger:
Hi All,
I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output, Xorg
stack on xorg-edgers, Ubuntu lucid). All interlace modes which are defined
in EDID seem to be pruned and don't appear in xrandr. Manua
Hi All,
I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output,
Xorg stack on xorg-edgers, Ubuntu lucid). All interlace modes which are
defined in EDID seem to be pruned and don't appear in xrandr. Manually
adding a mode using xrandr does work, and the TV set detects the mode,
Am 09.08.2010 09:33, wrote Alex Deucher:
> 2010/8/9 Marius Gr?ger:
>> Am 08.08.2010 20:09, wrote Alex Deucher:
>>>
>>> 2010/8/8 Marius Gr?ger:
Am 08.08.2010 18:22, wrote Alex Deucher:
>>
>> Also, I kind of was hoping that once I could use 1280x720 for both the
>> console and t
Am 08.08.2010 20:09, wrote Alex Deucher:
> 2010/8/8 Marius Gr?ger:
>> Am 08.08.2010 18:22, wrote Alex Deucher:
Also, I kind of was hoping that once I could use 1280x720 for both the
console and the X screen, it would would allow me to switch between the
two
transparently. I
Am 09.08.2010 09:33, wrote Alex Deucher:
2010/8/9 Marius Gröger:
Am 08.08.2010 20:09, wrote Alex Deucher:
2010/8/8 Marius Gröger:
Am 08.08.2010 18:22, wrote Alex Deucher:
Also, I kind of was hoping that once I could use 1280x720 for both the
console and the X screen, it would would allow
Am 08.08.2010 20:09, wrote Alex Deucher:
2010/8/8 Marius Gröger:
Am 08.08.2010 18:22, wrote Alex Deucher:
Also, I kind of was hoping that once I could use 1280x720 for both the
console and the X screen, it would would allow me to switch between the
two
transparently. Instead, the TV takes
Am 08.08.2010 18:22, wrote Alex Deucher:
>> Also, I kind of was hoping that once I could use 1280x720 for both the
>> console and the X screen, it would would allow me to switch between the two
>> transparently. Instead, the TV takes notice of the switch and needs some
>> extra syncing time. Is thi
Am 04.08.2010 16:35, schrieb Alex Deucher:
> 2010/8/4 Marius Gr?ger:
>> Am 04.08.2010 01:59, schrieb Alex Deucher:
>>>
>>> This connector attribute allows you to enable or disable underscan
>>> on a digital output to compensate for panels that automatically
>>> overscan (e.g., many HDMI TVs). Vali
Am 08.08.2010 18:22, wrote Alex Deucher:
Also, I kind of was hoping that once I could use 1280x720 for both the
console and the X screen, it would would allow me to switch between the two
transparently. Instead, the TV takes notice of the switch and needs some
extra syncing time. Is this expected
Am 04.08.2010 16:35, schrieb Alex Deucher:
2010/8/4 Marius Gröger:
Am 04.08.2010 01:59, schrieb Alex Deucher:
This connector attribute allows you to enable or disable underscan
on a digital output to compensate for panels that automatically
overscan (e.g., many HDMI TVs). Valid values for
Am 04.08.2010 01:59, schrieb Alex Deucher:
> This connector attribute allows you to enable or disable underscan
> on a digital output to compensate for panels that automatically
> overscan (e.g., many HDMI TVs). Valid values for the attribute are:
>
> off - forces underscan off
> on - forces under
Am 04.08.2010 01:59, schrieb Alex Deucher:
This connector attribute allows you to enable or disable underscan
on a digital output to compensate for panels that automatically
overscan (e.g., many HDMI TVs). Valid values for the attribute are:
off - forces underscan off
on - forces underscan on
a
Am 07.06.2010 00:15, wrote Dave Airlie:
> On Mon, Jun 7, 2010 at 3:52 AM, Marius Gr?ger
> wrote:
>> Am 06.06.2010 18:47, schrieb James Simmons:
>>>
> Apologies for such an unspecific description, and for what almost seems
> like a support request for MythTV. I wouldn't post here if I were
Am 07.06.2010 00:15, wrote Dave Airlie:
On Mon, Jun 7, 2010 at 3:52 AM, Marius Gröger
wrote:
Am 06.06.2010 18:47, schrieb James Simmons:
Apologies for such an unspecific description, and for what almost seems
like a support request for MythTV. I wouldn't post here if I were not
100%
Am 20.07.2010 12:14, schrieb Rafa? Mi?ecki:
> I've installed openSUSE 11.3 which comes with 2.6.34 kernel and added
> 2.6.35-rc5 from package. In both cases suspending and resuming works
> fine.
>
> Then I downloaded 2.6.35-rc5 and compiled it myself. Suspending and
> resuming works fine.
>
> When
Am 20.07.2010 12:14, schrieb Rafał Miłecki:
I've installed openSUSE 11.3 which comes with 2.6.34 kernel and added
2.6.35-rc5 from package. In both cases suspending and resuming works
fine.
Then I downloaded 2.6.35-rc5 and compiled it myself. Suspending and
resuming works fine.
When trying d-r-t
Am 06.06.2010 18:47, schrieb James Simmons:
>
>>> Apologies for such an unspecific description, and for what almost seems
>>> like a support request for MythTV. I wouldn't post here if I were not
>>> 100% sure it must be related with the recent drm changes.
>>
>> Note that the DRM APIs are intended
Am 04.06.2010 17:17, schrieb Alex Deucher:
> 2010/6/4 Marius Gr?ger:
>> Alex Deucher schrieb:
>>> 2010/6/4 Marius Gr?ger:
Hi All,
Michel D?nzer schrieb:
> On Mit, 2010-06-02 at 08:07 +0200, Marius Gr?ger wrote:
>> Hello All,
>>
>> I'm trying the top-of-trunk drm-2.6 t
Am 06.06.2010 18:47, schrieb James Simmons:
Apologies for such an unspecific description, and for what almost seems
like a support request for MythTV. I wouldn't post here if I were not
100% sure it must be related with the recent drm changes.
Note that the DRM APIs are intended for use by us
Am 04.06.2010 17:17, schrieb Alex Deucher:
2010/6/4 Marius Gröger:
Alex Deucher schrieb:
2010/6/4 Marius Gröger:
Hi All,
Michel Dänzer schrieb:
On Mit, 2010-06-02 at 08:07 +0200, Marius Gröger wrote:
Hello All,
I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
drm-r
Am Fri, 4 Jun 2010 11:17:12 -0400
schrieb Alex Deucher :
> 2010/6/4 Marius Gr?ger :
> > Alex Deucher schrieb:
> >> 2010/6/4 Marius Gr?ger :
> >>> Hi All,
> >>>
> >>> Michel D?nzer schrieb:
> On Mit, 2010-06-02 at 08:07 +0200, Marius Gr?ger wrote:
> > Hello All,
> >
> > I'm trying
Alex Deucher schrieb:
> 2010/6/4 Marius Gr?ger :
>> Hi All,
>>
>> Michel D?nzer schrieb:
>>> On Mit, 2010-06-02 at 08:07 +0200, Marius Gr?ger wrote:
Hello All,
I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI.
Hi All,
Michel D?nzer schrieb:
> On Mit, 2010-06-02 at 08:07 +0200, Marius Gr?ger wrote:
>> Hello All,
>>
>> I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
>> drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI. The primary
>> application is mythtv which uses DRM syncing for th
Am Fri, 4 Jun 2010 11:17:12 -0400
schrieb Alex Deucher :
> 2010/6/4 Marius Gröger :
> > Alex Deucher schrieb:
> >> 2010/6/4 Marius Gröger :
> >>> Hi All,
> >>>
> >>> Michel Dänzer schrieb:
> >>>> On Mit, 2010-06-02 at 08:07 +020
Alex Deucher schrieb:
> 2010/6/4 Marius Gröger :
>> Hi All,
>>
>> Michel Dänzer schrieb:
>>> On Mit, 2010-06-02 at 08:07 +0200, Marius Gröger wrote:
>>>> Hello All,
>>>>
>>>> I'm trying the top-of-trunk drm-2.6 trees (both drm
Hi All,
Michel Dänzer schrieb:
> On Mit, 2010-06-02 at 08:07 +0200, Marius Gröger wrote:
>> Hello All,
>>
>> I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
>> drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI. The primary
>> applicatio
Hi Michel,
Michel D?nzer schrieb:
> Note that the DRM APIs are intended for use by userspace components of
> graphics drivers / API libraries, not applications directly. MythTV
> shouldn't use the DRM directly for synchronization but rather use GLX
> synchronization APIs.
Hm, ok... AFAIK MythTV t
Hello All,
I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI. The primary
application is mythtv which uses DRM syncing for the frame
syncronisation. Now, with the exact same userland software I noticed the
introduction of sync gli
Hi Michel,
Michel Dänzer schrieb:
> Note that the DRM APIs are intended for use by userspace components of
> graphics drivers / API libraries, not applications directly. MythTV
> shouldn't use the DRM directly for synchronization but rather use GLX
> synchronization APIs.
Hm, ok... AFAIK MythTV t
Hello All,
I'm trying the top-of-trunk drm-2.6 trees (both drm-next and
drm-radeon-testing) with my Radeon HD 3200 GPU over HDMI. The primary
application is mythtv which uses DRM syncing for the frame
syncronisation. Now, with the exact same userland software I noticed the
introduction of sync gli
62 matches
Mail list logo
