From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754818Ab1H3Oo2 (ORCPT ); Tue, 30 Aug 2011 10:44:28 -0400 Received: from out3.smtp.messagingengine.com ([66.111.4.27]:48403 "EHLO out3.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753658Ab1H3Oo0 (ORCPT ); Tue, 30 Aug 2011 10:44:26 -0400 X-Sasl-enc: CP8Zmqzv0pgCw3I7lC4U2LUBneZYj88ZrWauwXQAdWUK 1314715463 Date: Tue, 30 Aug 2011 11:44:21 -0300 From: Henrique de Moraes Holschuh To: Borislav Petkov , Peter Zijlstra , Arnaud Lacombe , David Airlie , Michel =?iso-8859-1?Q?D=E4nzer?= , linux-kernel , dri-devel@lists.freedesktop.org, Pavel Ivanov , Alex Deucher , Dave Airlie , linux-kbuild@vger.kernel.org Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y Message-ID: <20110830144420.GA23963@khazad-dum.debian.net> References: <20110829141612.GB2025@gere.osrc.amd.com> <1790021880.1347470.1314632844694.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> <20110829155501.GC2025@gere.osrc.amd.com> <20110829171750.GD2025@gere.osrc.amd.com> <1314641813.2816.133.camel@twins> <20110829211439.GA4488@liondog.tnic> <20110830020828.GA14915@khazad-dum.debian.net> <20110830071755.GB15134@liondog.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110830071755.GB15134@liondog.tnic> X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Aug 2011, Borislav Petkov wrote: > On Mon, Aug 29, 2011 at 11:08:28PM -0300, Henrique de Moraes Holschuh wrote: > > On Mon, 29 Aug 2011, Borislav Petkov wrote: > > > So, hypothetically speaking, hpa suggested then that we could pass > > > firmware blobs over the linked list setup_data thing in the real-mode > > > kernel header and parse_setup_data() can look at them and map them > > > somewhere later for the driver to find. This should be doable because > > > you're only gonna need a handful of blobs for CPU ucode, network and GPU > > > if the last is compiled in. > > > > > > I wanted to take a serious look at that for the ucode loading, maybe I > > > should try to shuffle some time for it... > > > > It would be very useful, yes. > > > > Alternatively, you could extend the initrd format to have a firmware > > directory appended after the filesystem image. ACPI is going to abuse > > the initrd in just that way to override ACPI tables very soon (patches > > have been already submitted to linux-acpi), > > .. lemme guess: they didn't put the correct tables in the BIOS in the > first place and now it is too late for a BIOS fix and want to shuffle in > all those "fixes" through initrd ontop of ACPI. Oh boy, do I love all > the ACPI crap stories :). Heh. Actually, the patches were created by a distro for debug purposes. No vendor pushed for them. But it is a safe bet that users will end up using them to work around ACPI vendor crap that will never get fixed properly through a BIOS update, etc. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh