public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Simon Arlott <simon@fire.lp0.eu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux-foundation.org>
Subject: Re: BUG in free_block (tainted)
Date: Thu, 21 Aug 2008 12:48:43 +0200	[thread overview]
Message-ID: <1219315723.8651.106.camel@twins> (raw)
In-Reply-To: <84144f020808181449i546349b9n248b5cf5399e4b0f@mail.gmail.com>

On Tue, 2008-08-19 at 00:49 +0300, Pekka Enberg wrote:

> Aww, apparently the fglrx driver creates tons of SLAB caches with
> really funky names for no good reason... Oh well, one more reason to
> stay away from that crap and help out the nouveau folks instead ;-).

fglrx is the AMD/ATI binary evilness - the open source efforts are the
radeon and radeonhd drivers. AMD/ATI are actually providing
documentation and paying developers to work on the drivers.

I'm not sure what the nvidia binary wonkyness is called, but its
respective open source effort is the nouveau - who must solely reply on
reverse engineering as nvidia isn't providing anything.

Anyway - your point still stands - binary stuff should not be used.


  parent reply	other threads:[~2008-08-21 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 21:28 BUG in free_block (tainted) Simon Arlott
2008-08-18 21:37 ` Pekka Enberg
2008-08-18 21:42   ` Simon Arlott
2008-08-18 21:49     ` Pekka Enberg
2008-08-19 13:02       ` Christoph Lameter
2008-08-21 10:48       ` Peter Zijlstra [this message]
2008-08-21 10:51         ` Pekka Enberg
2008-08-22 15:21           ` Adrian Bunk

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=1219315723.8651.106.camel@twins \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=simon@fire.lp0.eu \
    /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