mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Borislav Petkov <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Alex Deucher <alexdeucher@gmail.com>
Subject: Re: radeon firmware
Date: Sun, 28 Jul 2013 22:46:00 +0100	[thread overview]
Message-ID: <1375047960.2546.43.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <CADnq5_PYtzY-fnRKbxioUcUTatCS+YvM3Cr-BxF+ZDzZ1uvnCA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Sun, 2013-07-21 at 09:12 -0400, Alex Deucher wrote:
> On Sun, Jul 21, 2013 at 5:36 AM, Borislav Petkov <bp@alien8.de> wrote:
> > Hey Alex,
> >
> > I keep getting people's configs with
> >
> > CONFIG_EXTRA_FIRMWARE="... radeon/RV710_uvd.bin radeon/RV730_smc.bin..."
> >
> > but I can't find those blobs in the k.org fw repo:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> >
> > This here http://www.x.org/wiki/radeonBuildHowTo/ says that
> > http://people.freedesktop.org/~agd5f/radeon_ucode/ contains them, and,
> > AFAICT, the license is the same. So what's the story, are those going
> > into the firmware-linux repo anytime soon?
> 
> The UVD ucode is already there.  I send Ben the patches for the smc
> ucode week or so ago, but I guess they haven't been applied yet.

I've just pushed them, so they should be available there in a few
minutes.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      parent reply	other threads:[~2013-07-28 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21  9:36 Borislav Petkov
2013-07-21 13:12 ` Alex Deucher
2013-07-21 19:03   ` Borislav Petkov
2013-07-28 21:46   ` Ben Hutchings [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=1375047960.2546.43.camel@deadeye.wl.decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=alexdeucher@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®