All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Arnaud Lacombe" <lacombar@gmail.com>,
	"David Airlie" <airlied@redhat.com>,
	"Michel Dänzer" <michel@daenzer.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	"Pavel Ivanov" <paivanof@gmail.com>,
	"Alex Deucher" <alexdeucher@gmail.com>,
	"Dave Airlie" <airlied@gmail.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
Date: Mon, 29 Aug 2011 19:50:34 +0200	[thread overview]
Message-ID: <1314640234.2816.118.camel@twins> (raw)
In-Reply-To: <20110829171750.GD2025@gere.osrc.amd.com>

On Mon, 2011-08-29 at 19:17 +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> > do you want something ala:
> > 
> > config EXTRA_FIRMWARE
> >     string
> >     default ""
> >     append "FOO" if BAR
> >     append "FOZ" if BAZ
> > 
> > or maybe a new type "list" which would behave as a comma/space separated value.
> > 
> > config EXTRA_FIRMWARE
> >     list "bla"
> >     append "FOO" if BAR
> >     append "FOZ" if BAZ
> 
> Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
> much more sense for linux and the whole firmware in the kernel deal.
> So it looks like the drivers should be taught to wait for userspace to
> appear instead of Kconfig helping them build-in firmware. And then we
> should go ahead and remove CONFIG_EXTRA_FIRMWARE completely...

That would suck, suppose this radeon thing is the only console you've
got (ppc64/sparc64 don't have text mode iirc) and userspace doesn't come
up?



  parent reply	other threads:[~2011-08-29 17:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27  4:20 Kernel almost hangs when CONFIG_DRM_RADEON=y Pavel Ivanov
2011-08-27  9:00 ` Michel Dänzer
2011-08-27 22:50   ` Pavel Ivanov
2011-08-28  5:36     ` Borislav Petkov
2011-08-28 21:47       ` Pavel Ivanov
2011-08-28 21:47         ` Pavel Ivanov
2011-08-29  5:49         ` Borislav Petkov
2011-08-29  6:04           ` Michel Dänzer
2011-08-29  6:04             ` Michel Dänzer
2011-08-29 13:20       ` Peter Zijlstra
2011-08-29 13:38         ` Borislav Petkov
2011-08-29 13:43           ` Dave Airlie
2011-08-29 13:48           ` Alex Deucher
2011-08-29 14:16             ` Borislav Petkov
2011-08-29 15:47               ` David Airlie
2011-08-29 15:55                 ` Borislav Petkov
2011-08-29 16:10                   ` Arnaud Lacombe
2011-08-29 16:10                     ` Arnaud Lacombe
2011-08-29 17:17                     ` Borislav Petkov
2011-08-29 17:38                       ` Michel Dänzer
2011-08-29 17:38                         ` Michel Dänzer
2011-08-29 17:50                       ` Peter Zijlstra [this message]
2011-08-29 18:09                       ` Peter Zijlstra
2011-08-29 18:16                       ` Peter Zijlstra
2011-08-29 21:14                         ` Borislav Petkov
2011-08-30  2:08                           ` Henrique de Moraes Holschuh
2011-08-30  2:08                           ` Henrique de Moraes Holschuh
2011-08-30  7:17                             ` Borislav Petkov
2011-08-30  7:17                               ` Borislav Petkov
2011-08-30 14:44                               ` Henrique de Moraes Holschuh
2011-08-30 14:44                               ` Henrique de Moraes Holschuh
2011-08-30  8:37                             ` Peter Zijlstra
2011-08-30 14:55                               ` Henrique de Moraes Holschuh
2011-08-29 16:28             ` Kyle Moffett
2011-08-29 17:21               ` Borislav Petkov
2011-08-29 17:51                 ` Peter Zijlstra
2011-08-27 23:03   ` Kyle Moffett

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=1314640234.2816.118.camel@twins \
    --to=peterz@infradead.org \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=bp@alien8.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@daenzer.net \
    --cc=paivanof@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 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.