Looking for a start point for fixing a bug
Адонай Элохим
algonkvel at gmail.com
Fri Aug 8 05:48:32 PDT 2014
I started looking through the code week or so ago.
No much progress though but could you explain meaning of this to me:
if (running == 0) {
if (running) {
blackout = RREG32(MC_SHARED_BLACKOUT_CNTL);
WREG32(MC_SHARED_BLACKOUT_CNTL, blackout | 1);
}
...
It's in si.c, line 1564 in current master branch. Is it some
concurrent trick or so?
Thanks,
Oleg
2014-07-22 20:05 GMT+04:00 Alex Deucher <alexdeucher at gmail.com>:
> On Tue, Jul 22, 2014 at 8:39 AM, Адонай Элохим <algonkvel at gmail.com> wrote:
>> Hello all!
>>
>> I have some spare time and knowledge in C to try to fix some bugs I am
>> seeing on my machine.
>> So I've checked out and compiled all git trees that I may need and now I'm
>> beginning to read articles.
>>
>> And this is the point from where I don't know where to go. I want to fix
>> particular bug #79806 [1].
>> For me there are many places where this bug can hide - mesa? dri? radeon
>> kernel module? and I just don't know whether should I start reading articles
>> about mesa hacking or about dri architecture or about kernel module
>> development.
>>
>> Now I think the best thing for me is to start looking through radeon kernel
>> module code (I've got ingenious idea that power management resides there)
>> and read more about its architecture. Is this right? I mean, I just want to
>> find out, is this a right place to start looking at for this bug?
>
> The power management is handled in the kernel driver. See radeon_pm.c
> and the relevant *_dpm.c files depending on what asic you have.
>
> Alex
>
>>
>> P.S. Sorry for my English in case it's not good, I'm learning it now
>>
>> P.P.S. And thanks for your hard work!
>>
>> -------------------------------------------
>> [1] https://bugs.freedesktop.org/show_bug.cgi?id=79806
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
More information about the dri-devel
mailing list