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 20:16:53 +0200 [thread overview]
Message-ID: <1314641813.2816.133.camel@twins> (raw)
In-Reply-To: 20110829171750.GD2025@gere.osrc.amd.com
On Mon, 2011-08-29 at 20:09 +0200, Peter Zijlstra wrote:
> > 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?
>
> Same is true for NICs and netconsole of course. Not being able to stick
> blobs into the kernel image would so suck.
NICs and nfsroot, I suppose can you use an initrd over tftp as well, but
really, what's the point of an in-kernel nfsroot if you need initrd
crap.
next prev parent reply other threads:[~2011-08-29 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110829141612.GB2025@gere.osrc.amd.com>
[not found] ` <1790021880.1347470.1314632844694.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2011-08-29 15:55 ` Kernel almost hangs when CONFIG_DRM_RADEON=y Borislav Petkov
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:50 ` Peter Zijlstra
2011-08-29 18:09 ` Peter Zijlstra
2011-08-29 18:16 ` Peter Zijlstra [this message]
2011-08-29 21:14 ` Borislav Petkov
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 7:17 ` Borislav Petkov
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
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=1314641813.2816.133.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox