mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux v2.6.27-rc1: problem with firmware stuff
Date: Tue, 29 Jul 2008 23:01:36 +0200	[thread overview]
Message-ID: <200807292301.36987.rjw@sisk.pl> (raw)
In-Reply-To: <200807292249.48050.rjw@sisk.pl>

On Tuesday, 29 of July 2008, Rafael J. Wysocki wrote:
> On Tuesday, 29 of July 2008, Linus Torvalds wrote:
> > 
> > It's two weeks (and one day), and the merge window is over.
> > 
> > Finally. I don't know why, but this one really did feel pretty dang busy. 
> > And the size of the -rc1 patch bears that out - at 12MB, it's about 50% 
> > bigger than 26-rc1 (but not that much bigger than 24/25-rc1, so it's not 
> > like it's anything unheard of).
> > 
> > The pure size of the -rc's _is_ making me a bit nervous, though. Sure, it 
> > means that we are good at merging it all, but I have to say that I 
> > sometimes wonder if we don't merge too much in one go, and even our 
> > current (fairly short) release cycle is actually too big.
> > 
> > Anyway, that's a discussion for some other event.
> > 
> > Much of -rc1 was in linux-next, but certainly not everything. We'll see 
> > how that whole thing ends up evolving - it certainly didn't solve all 
> > problems, and there was some bickering about things that weren't there 
> > (and some things that mostly were ;), but maybe it helped.
> > 
> > There's a ton of new stuff in there, but at least personally the 
> > interesting things are the BKL pushdown and perhaps the introduction of 
> > the lockless get_user_pages_fast(). The build system also got updated to 
> > allow moving the architecture include files ("include/asm-xyz") into the 
> > architecture subdirectories ("arch/xyz/include/asm"), and sparc seems to 
> > have taken advantage of that already.
> > 
> > But those changes are just small details in the end. As usual, the bulk of 
> > changes are all to device drivers (roughly half, as usual), with the arch 
> > directory amounting to about half of the remainder. Dirstat:
> > 
> >    3.2% arch/arm/
> >    9.2% arch/ppc/
> >   24.6% arch/
> >    5.2% drivers/char/drm/
> >    6.3% drivers/char/
> >    4.5% drivers/gpu/drm/
> >    4.5% drivers/gpu/
> >    4.6% drivers/media/video/
> >    5.5% drivers/media/
> >    3.0% drivers/net/wireless/
> >   10.7% drivers/net/
> >    6.4% drivers/usb/misc/
> >    4.7% drivers/usb/serial/
> >   12.9% drivers/usb/
> >   51.2% drivers/
> >    4.4% firmware/
> >    3.7% fs/
> >    9.2% include/
> > 
> > where the bulk of that fs/ update is the merge of the UBI filesystem, to 
> > pick one fairly sizeable chunk outside of arch or drivers (there's omfs 
> > too, but that's tiny in comparison).
> > 
> > Other stuff? tracing. firmware loading.
> 
> That one happens to break things for me badly:
> 
> rafael@chimera:~/src/linux-2.6> make O=../build/mainline/chimera -j5
>   GEN     /home/rafael/src/build/mainline/chimera/Makefile
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   Using /home/rafael/src/linux-2.6 as source for kernel
>   CALL    /home/rafael/src/linux-2.6/scripts/checksyscalls.sh
>   CHK     include/linux/compile.h
>   Building modules, stage 2.
> Kernel: arch/x86/boot/bzImage is ready  (#208)
>   MODPOST 564 modules
>   IHEX2FW firmware/emi26/loader.fw
> Failed to open destination file: Permission deniedihex2fw: Convert ihex files into binary representation for use by Linux kernel
> usage: ihex2fw [<options>] <src.HEX> <dst.fw>
>        -w: wide records (16-bit length)
>        -s: sort records by address
>   IHEX2FW firmware/emi26/bitstream.fw
>   IHEX2FW firmware/emi26/firmware.fw
> Failed to open destination file: Permission deniedihex2fw: Convert ihex files into binary representation for use by Linux kernel
> usage: ihex2fw [<options>] <src.HEX> <dst.fw>
>        -w: wide records (16-bit length)
>        -s: sort records by address
> make[2]: *** [firmware/emi26/loader.fw] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: *** [firmware/emi26/bitstream.fw] Error 1
> Failed to open destination file: Permission deniedihex2fw: Convert ihex files into binary representation for use by Linux kernel
> usage: ihex2fw [<options>] <src.HEX> <dst.fw>
>        -w: wide records (16-bit length)
>        -s: sort records by address
> make[2]: *** [firmware/emi26/firmware.fw] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2

Actually, this happened due to some firmware files being created as root during
installations of pre-rc -git kernels from the O= directory.  So, not a real
problem, but somewhat confusing.

Thanks,
Rafael

  reply	other threads:[~2008-07-29 20:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  3:23 Linux v2.6.27-rc1 Linus Torvalds
2008-07-29  4:01 ` Nick Piggin
2008-07-29  9:49 ` 2.6.27-rc1: zd1211rw association fails Alistair John Strachan
2008-07-29 10:09   ` Johannes Berg
2008-07-29 11:25     ` Alistair John Strachan
2008-07-29 11:26       ` Johannes Berg
2008-07-29 11:37         ` Hugh Dickins
2008-07-29 11:46         ` Kalle Valo
2008-07-29 11:55         ` Alistair John Strachan
2008-07-29 12:04     ` Theodore Tso
2008-07-29 12:09       ` Johannes Berg
2008-07-29 12:15         ` Johannes Berg
2008-07-29 15:18           ` Theodore Tso
2008-07-29 17:52           ` John W. Linville
2008-07-30  4:48             ` David Miller
2008-07-29 13:57 ` Oops in microcode sysfs registration, Alistair John Strachan
2008-07-29 16:22   ` Pekka Paalanen
2008-07-29 16:50     ` Alistair John Strachan
2008-07-30  9:07       ` Dmitry Adamushko
2008-07-30 10:35         ` Dmitry Adamushko
2008-07-30 13:28           ` Peter Oruba
2008-07-31 12:49           ` Alistair John Strachan
2008-07-31 16:56           ` Ingo Molnar
2008-07-31 19:52             ` Dmitry Adamushko
2008-07-31 19:55               ` Dmitry Adamushko
2008-07-29 16:27 ` Linux v2.6.27-rc1 Jesse Barnes
2008-07-29 16:59   ` Linus Torvalds
2008-07-29 17:31     ` Roland Dreier
2008-07-30  9:03     ` Andrew Morton
2008-07-31 22:22       ` Linux v2.6.27-rc1: linux-next Rafael J. Wysocki
2008-07-29 20:49 ` Linux v2.6.27-rc1: problem with firmware stuff Rafael J. Wysocki
2008-07-29 21:01   ` Rafael J. Wysocki [this message]
2008-07-29 21:01     ` Linus Torvalds
2008-07-29 22:26       ` David Woodhouse
2008-07-29 21:37 ` Linux v2.6.27-rc1 Sam Ravnborg
2008-07-29 21:42   ` Linus Torvalds
2008-07-29 21:59     ` Sam Ravnborg
2008-07-29 22:03       ` Linus Torvalds
2008-07-29 22:30         ` Sam Ravnborg
2008-07-29 22:03 ` Linux v2.6.27-rc1: fails to compile Grant Coady
2008-07-29 22:40   ` Frederik Deweerdt
2008-07-29 23:46     ` Grant Coady

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=200807292301.36987.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome