[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0

[PATCH] drm/radeon/kms: extend the Fujitsu D3003-S2 board connector quirk to cover later silicon stepping

There is a more recent APU stepping with a new PCI ID shipping in the same board by Fujitsu which needs the same quirk to correctly mark the back plane connectors. Signed-off-by: Tvrtko Ursulin --- radeon_atombios.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a

udl vs udlfb and EDID trouble

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for ea

[radeon] Monitor not turning on after DisplayPort re-plug in Xorg

Hi all, On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up disp

Possible radeon regression in 2.6.37-rc3

Hi all, I have replaced the distro kernel on openSUSE 11.3 with custom compiled 2.6.37-rc3 and now all glx application are crashing with these kind of kernel errors: [ 312.028728] radeon :01:05.0: r600_cs_track_validate_cb offset[0] 0 10476800 385024 too big [ 312.028732] radeon :01:0