From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762789AbZE1Ne2 (ORCPT ); Thu, 28 May 2009 09:34:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758158AbZE1NeV (ORCPT ); Thu, 28 May 2009 09:34:21 -0400 Received: from yw-out-2324.google.com ([74.125.46.30]:45245 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755242AbZE1NeV convert rfc822-to-8bit (ORCPT ); Thu, 28 May 2009 09:34:21 -0400 MIME-Version: 1.0 In-Reply-To: <20090528063445.GA12004@pengutronix.de> References: <87vdnm8sec.fsf@macbook.be.48ers.dk> <20090527175609.GB31861@flint.arm.linux.org.uk> <4A1D8FBA.6040802@freescale.com> <9e4733910905271213k7f4b93e7i7e6f2af24d85f@mail.gmail.com> <20090527192116.GA31110@n2100.arm.linux.org.uk> <20090527193927.GD30039@game.jcrosoft.org> <20090527235704.GQ6805@pengutronix.de> <20090528063445.GA12004@pengutronix.de> From: Grant Likely Date: Thu, 28 May 2009 07:34:02 -0600 Message-ID: Subject: Re: [RFC] [PATCH] Device Tree on ARM platform To: Wolfram Sang Cc: Robert Schwebel , Jean-Christophe PLAGNIOL-VILLARD , devicetree-discuss , Russell King - ARM Linux , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk, Jon Smirl , Scott Wood , Janboe Ye , Timur Tabi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 28, 2009 at 12:34 AM, Wolfram Sang wrote: > >> It is inherent in the value "atmel,24c08".  Because the exact device >> model is specified, the kernel can know what the page size and flags >> are for that device. > > I am afraid this is not the case. I remember that we once had two revisions of > the same eeprom, and the vendor decided to increase the page size without > changing the naming of the eeprom. (Can't point to any documentation yet, would > have to dig this up.) Those eeproms can be really weird. > > Also, there are _a lot_ of eeprom manufacturers out there, so the match table > will be enormous.... ... which is the whole point of "compatible". Every possible variant doesn't get listed in the device driver; device nodes in the tree claim compatibility with older, already known parts. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.