From: "Christian König" <christian.koenig@amd.com>
To: Seth Forshee <seth.forshee@canonical.com>,
Alex Deucher <alexander.deucher@amd.com>,
Oded Gabbay <oded.gabbay@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Missing amdgpu firmware files
Date: Tue, 27 Oct 2015 16:47:53 +0100 [thread overview]
Message-ID: <562F9CA9.4020807@amd.com> (raw)
In-Reply-To: <20151027154208.GC132460@ubuntu-hedt>
Well that's strange. Essentially those are just duplicates to the
existing files and the driver should fallback to them.
IIRC the radeon/*_sdma1.bin files are only requested when you try to use
CIK support with amdgpu which isn't a good idea in a production environment.
What's the link for the bug reports? It's most likely just people trying
to use the driver with hardware which it isn't supposed to be used with.
We probably should either remove CIK support totally from the amdgpu or
add all the files to the firmware repository.
Regards,
Christian.
On 27.10.2015 16:42, Seth Forshee wrote:
> I've received reports from Ubuntu users about missing amdgpu firmware
> files with 4.2 kernels. The driver calls out a number of
> radeon/*_sdma1.bin files that are not present in the linux-firmware git
> repo. Are these files available anywhere (under a license that allows
> redistribution), and will they be pushed up to linux-firmware anytime
> soon?
>
> Thanks,
> Seth
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-27 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:42 Missing amdgpu firmware files Seth Forshee
2015-10-27 15:47 ` Christian König [this message]
2015-10-27 15:51 ` Deucher, Alexander
2015-10-27 16:06 ` Seth Forshee
2015-10-27 16:10 ` Deucher, Alexander
2015-10-27 16:17 ` Seth Forshee
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=562F9CA9.4020807@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=oded.gabbay@gmail.com \
--cc=seth.forshee@canonical.com \
/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.