public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Torsten Kaiser <just.for.lkml@googlemail.com>,
	Ronald <ronald645@gmail.com>
Cc: linux-kbuild@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression: firmware: Simplify directory creation + b43 = fails to build
Date: Tue, 08 Jul 2014 14:09:28 +0200	[thread overview]
Message-ID: <53BBDF78.40708@suse.cz> (raw)
In-Reply-To: <CAPVoSvSmzRWSJeR9dyBO0qS6-9SWA_d-CjGuQeULGS_MRUY77w@mail.gmail.com>

On 2014-07-07 21:02, Torsten Kaiser wrote:
> On Wed, Jun 18, 2014 at 6:25 PM, Ronald <ronald645@gmail.com> wrote:
>> From my .config
>>
>>  ==> cat /usr/src/config | grep -i b43
>> CONFIG_EXTRA_FIRMWARE="b43/ucode5.fw b43/b0g0initvals5.fw
>> b43/b0g0bsinitvals5.fw b43/pcm5.fw"
>> ... snip ...
> 
> That might be rather later, but I seem to have the same problem:
>   CHK     kernel/config_data.h
>   MK_FW   firmware/amd-ucode/microcode_amd.bin.gen.S
> /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory
> [...]
> The directory firmware/amd-ucode does not exist in the kernel source
> tree, but my .config seems to need it:
> CONFIG_EXTRA_FIRMWARE="radeon/R700_rlc.bin radeon/RV710_uvd.bin
> radeon/RV730_smc.bin amd-ucode/microcode_amd.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
> 
> Just doing a "mkdir firmware/amd-ucode" lets the build continue and I
> get a working 3.16 kernel.
> 
> With 3.15 and earlier I never had a problem with this, but 3.16-rc4
> just failed with above message.
> 
> Do you need my full .config or any other information about my system?

That's not needed, I can reproduce the failure now as well.

Michal

  reply	other threads:[~2014-07-08 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  8:46 Regression: firmware: Simplify directory creation + b43 = fails to build Ronald
2014-06-18 14:33 ` Michal Marek
2014-06-18 16:25   ` Ronald
2014-07-07 19:02     ` Torsten Kaiser
2014-07-08 12:09       ` Michal Marek [this message]
2014-07-08 12:47       ` [PATCH] firmware: Create directories for external firmware Michal Marek
     [not found]         ` <CAF1_xX19AwepGJLJOcn_m+OaU3kk9N9d+M2v_YzzPg-M2cdrPQ@mail.gmail.com>
2014-07-08 15:19           ` Ronald
2014-07-08 16:29             ` Ronald
2014-07-08 18:03         ` Torsten Kaiser

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=53BBDF78.40708@suse.cz \
    --to=mmarek@suse.cz \
    --cc=just.for.lkml@googlemail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ronald645@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox