(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
>
> > > Does anybody know, whether this is normal and expected behaviour or if
this is a
> > > bug?
> >
> > It's kind of expected, as the radeon driver uses bus mastering to send commands
> > to the graphics card when the DRI is enabled.
> >
>
> Well, if it's normal and expected, we can close or at least postpone the report.
> There are certainly more critical bugs (such that lead to system freezes).
>
> Just did not know, whether this was a bug. Somehow it's seemed like a bug, as
> with or without dri modules loaded, I thought there is the same rendering
> happening on the screen if I am idle (no 3D apps running).
well, when the DRI is enabled, the DDX uses the bus mastering for 2D commands as
well, so that will also cause bus master activity. I suppose we could put in
some sort of hack to shut down the CP when DPMS is triggered. I'm not sure if
that's the right fix or not.
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
>
> > > Does anybody know, whether this is normal and expected behaviour or if
this is a
> > > bug?
> >
> > It's kind of expected, as the radeon driver uses bus mastering to send commands
> > to the graphics card when the DRI is enabled.
> >
>
> Well, if it's normal and expected, we can close or at least postpone the report.
> There are certainly more critical bugs (such that lead to system freezes).
>
> Just did not know, whether this was a bug. Somehow it's seemed like a bug, as
> with or without dri modules loaded, I thought there is the same rendering
> happening on the screen if I am idle (no 3D apps running).
well, when the DRI is enabled, the DDX uses the bus mastering for 2D commands as
well, so that will also cause bus master activity. I suppose we could put in
some sort of hack to shut down the CP when DPMS is triggered. I'm not sure if
that's the right fix or not.