stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Axel Rohde <dr.a.rohde@gmx.de>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: AMD Polaris 12 / RX 5xx support for Linux 4.9.x
Date: Wed, 9 Aug 2017 10:52:20 -0700	[thread overview]
Message-ID: <20170809175220.GA28811@kroah.com> (raw)
In-Reply-To: <trinity-6a997165-e103-4c72-8bc5-a1a0fb5d02af-1502300180086@3capp-gmx-bs28>

On Wed, Aug 09, 2017 at 07:36:20PM +0200, Axel Rohde wrote:
> 
> Hi Kernel Maintainers,
> �
> I'm using Debian 9 ("Stretch", has just become stable) with Kernel 4.9.30.
> �
> Recently I added a AMD Radeon RX 550 (Polaris 12) graphics board to my system to connect an
> Ultra HD Monitor using Display Port 1.2, which the Intel Ivy Bridge core i5 lacks.
> �
> Unfortunately 4.9.30 did NOT support AMD Radeon RX 550 (Polaris 12).
> I had to use kernel 4.11.
> �
> Are you planning to backport support for AMDGPU Polaris 12 (AMD Radeon RX 5xx Series graphics boards)
> from 4.11 or later back to 4.9?

Note, the stable kernel trees do not add new device support to them over
the lifetime of their existance, with the exception of simple new device
ids or quirks.  See:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for a full list of what the rules are.

So, is support for these devices just a simple new device id to add?  If
so, what is the git commit id for them and I'll be glad to queue them
up.

If not, then no, the stable trees are not going to add new support for
them, sorry, just use a new kernel, what is keeping you on an old kernel
version?

thanks,

greg k-h

      reply	other threads:[~2017-08-09 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 17:36 AMD Polaris 12 / RX 5xx support for Linux 4.9.x Axel Rohde
2017-08-09 17:52 ` Greg KH [this message]

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=20170809175220.GA28811@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dr.a.rohde@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).