From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 7BA14DDEDF for ; Mon, 4 Jun 2007 04:47:11 +1000 (EST) In-Reply-To: <46630A32.7000403@ru.mvista.com> References: <7fc919fce0761f861be3069a853d3169@bga.com> <1180769992.14025.1.camel@localhost.localdomain> <4662E7EA.70506@ru.mvista.com> <46630256.8050909@ru.mvista.com> <46630A32.7000403@ru.mvista.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: [PATCH] powerpc: Create "rom" (MTD) device prpmc2800 Date: Sun, 3 Jun 2007 20:46:57 +0200 To: Sergei Shtylyov Cc: ppcdev , linux-mtd@lists.infradead.org, Milton Miller List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>> Nobody's talking about the direct match but making the task of >>> selecting a proper driver more complex by specifying the details >>> that don't help (if not hinder) the correct selection is certainly >>> not a way to go. > >> Nonsense. If the kernel doesn't care about certain details, >> it can just ignore them. > > That's OK, as long as it has the details it needs. Your suggestions > on the "compatible" devoided it of such. Sigh. [snip] >>> That's the way the cookie crumbles in Linux MTD for now. It's >>> *always* detecting this by probing -- you only can say what [not] to >>> probe. > >> So go fix that :-) > > Wanna pay me for that? ;-) You're the one complaining, you go pay yourself. [snip, plunk] Segher