dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions
Date: Sun, 08 Nov 2015 15:56:55 +0000	[thread overview]
Message-ID: <bug-92858-502-bTYykS3d6K@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1834 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92858

--- Comment #3 from Darren <ysxikrhn@vomoto.com> ---
I downloaded the kernel source via git, using "git clone
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git," then I
changed directory into the folder it created, called "linux."

I then ran "git bisect start v4.2 v4.1" and the output was:

"Bisecting: 7353 revisions left to test after this (roughly 13 steps)
[c11d716218910c3aa2bac1bb641e6086ad649555] Merge tag 'armsoc-cleanup' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc"

I'm not to up to speed on git bisect, but don't I need to declare a good
revision first so bisect has somewhere to start? Also, in order to declare a
good revision, I'd need to compile the whole kernel again starting with the
initial git commit during the 4.2 merge window, wouldn't I?

The above "git clone" command checks out the source for the latest kernel (not
sure about which if any kernel history it downloads,) no? And if I compile
using it, wouldn't it build 4.3.0 instead of an earlier revision?

To summarize, I'm very much a newcomer to git--if I needed to install a kernel
before, I would use AUR packages, or in the case of beginner friendly
distributions like Ubuntu, would simply grab the latest kernel from a PPA. I
can copy and paste commands, learned what "--depth=X" does-in the event I
needed to download without history-while building the nouveau kernel tree back
when I had a nVidia GPU, but I'm not otherwise too experienced. Can you point
me to the best resource/s on learning git and how to identify what those long
strings of text like "c11d716218910c3aa2bac1bb641e6086ad649555" indicate and
what to do to isolate a good revsion so bisect can start at it?

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2816 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-11-08 15:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 22:57 [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions bugzilla-daemon
2015-11-08 11:47 ` bugzilla-daemon
2015-11-08 11:55 ` bugzilla-daemon
2015-11-08 15:40 ` bugzilla-daemon
2015-11-08 15:56 ` bugzilla-daemon [this message]
2015-11-08 19:55 ` bugzilla-daemon
2015-11-12  2:40 ` bugzilla-daemon
2015-11-12  2:52 ` bugzilla-daemon
2015-11-12  4:59 ` bugzilla-daemon
2015-11-12 12:57 ` bugzilla-daemon
2015-11-15  0:58 ` bugzilla-daemon
2015-11-15 11:00 ` bugzilla-daemon
2015-12-05 17:47 ` bugzilla-daemon
2015-12-05 18:28 ` bugzilla-daemon
2015-12-12 19:57 ` bugzilla-daemon
2015-12-17  7:19 ` bugzilla-daemon
2015-12-17  7:24 ` bugzilla-daemon
2015-12-19 16:33 ` bugzilla-daemon
2015-12-19 17:58 ` bugzilla-daemon
2016-01-10  2:46 ` bugzilla-daemon
2016-01-10  2:47 ` bugzilla-daemon
2016-01-10  2:47 ` bugzilla-daemon
2016-01-13  7:14 ` bugzilla-daemon
2016-01-16 16:12 ` bugzilla-daemon
2016-01-18  6:35 ` bugzilla-daemon

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=bug-92858-502-bTYykS3d6K@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox