From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ey-out-1920.google.com ([74.125.78.150]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1NMgdM-0007ir-R6 for barebox@lists.infradead.org; Mon, 21 Dec 2009 11:41:09 +0000 Received: by ey-out-1920.google.com with SMTP id 4so50936eyg.26 for ; Mon, 21 Dec 2009 03:41:02 -0800 (PST) From: Peter Korsgaard References: <20091221113052.GG15126@pengutronix.de> Date: Mon, 21 Dec 2009 12:40:59 +0100 In-Reply-To: <20091221113052.GG15126@pengutronix.de> (Sascha Hauer's message of "Mon, 21 Dec 2009 12:30:52 +0100") Message-ID: <87hbrkzh9w.fsf@macbook.be.48ers.dk> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH] commands: Remove reference to non-existent CONFIG_CMD_I2C. To: Sascha Hauer Cc: "U-Boot Version 2 (barebox)" >>>>> "Sascha" == Sascha Hauer writes: Sascha> Ok, applied. Sascha> Is a i2c command really useful? For I2C eeproms you would Sascha> create an epprom driver which creates a file under /dev/ which Sascha> you can then access using the usual mm/mw commands. Maybe an Sascha> i2c command could be useful to register a new device on an I2C Sascha> bus. I could see basic I2C access being useful for debugging (of non-eeprom devices). -- Bye, Peter Korsgaard _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox