From: Alex Deucher <alexdeucher@gmail.com>
To: "Адонай Элохим" <algonkvel@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: Looking for a start point for fixing a bug
Date: Tue, 22 Jul 2014 12:05:48 -0400 [thread overview]
Message-ID: <CADnq5_OiYwm1jdeBFT6_hOQRBEq74Hh4_w4VE=y=X6JpmkR=bw@mail.gmail.com> (raw)
In-Reply-To: <CAH1Y=qoeB+b+5sdfriZehZQzR=jurT_VohPjUOJ4V0zASSP0bA@mail.gmail.com>
On Tue, Jul 22, 2014 at 8:39 AM, Адонай Элохим <algonkvel@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@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-07-22 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 12:39 Looking for a start point for fixing a bug Адонай Элохим
2014-07-22 15:01 ` Rob Clark
2014-07-22 16:05 ` Alex Deucher [this message]
2014-08-08 12:48 ` Адонай Элохим
2014-08-10 21:19 ` Адонай Элохим
2014-08-10 21:53 ` Niels Ole Salscheider
2014-08-11 4:03 ` Адонай Элохим
2014-08-11 6:50 ` Niels Ole Salscheider
2014-08-11 14:49 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADnq5_OiYwm1jdeBFT6_hOQRBEq74Hh4_w4VE=y=X6JpmkR=bw@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=algonkvel@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.