From mboxrd@z Thu Jan 1 00:00:00 1970 From: Donghwa Lee Date: Fri, 17 Dec 2010 11:58:19 +0900 Subject: [U-Boot] [PATCH] tools: fw_printenv supports mmc device In-Reply-To: References: <1292462546-32516-1-git-send-email-dh09.lee@samsung.com> Message-ID: <4D0AD1CB.4010904@samsung.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 2010-12-17 ?? 3:45 , Steve Sakoman wrote: > On Wed, Dec 15, 2010 at 5:22 PM, Donghwa Lee wrote: >> I modified fw_printenv tools to use /dev/mmcblk0 node. Original fw_printenv tool >> can be access MTD devices, but, in some cases, environment variables can be stored >> other memory devices, for example, mmc devices. >> So, I modified a few code to use /dev/mmcblk0. > I submitted a similar patch series from Lo?c Minier a couple of weeks ago: > > http://old.nabble.com/-U-Boot---RFC-0-3--Enhance-env-tools-td30373328.html > > I've been working a a v2 to address the comments received. > > Do you think a variant of that patch series will work for you? > > Perhaps we could combine efforts for a patch series to solve the mmc > and normal file write targets? > > Steve > I think your ideas are quite similar to me. I tested your patch to my target. In my kernel your patch can not recognize file type, but, when 'is_mtd' is 0, it work well. Best regards, Donghwa lee