From mboxrd@z Thu Jan 1 00:00:00 1970 From: bhargavak Date: Sun, 31 Mar 2013 02:30:00 -0700 (PDT) Subject: [U-Boot] Handling images(.jpg, .bmp etc) in u-boot In-Reply-To: <20130331105459.49d49ade@crub> References: <1364111315717-150524.post@n7.nabble.com> <20130324100502.A36AB20058A@gemini.denx.de> <1364124418778-150541.post@n7.nabble.com> <20130324131611.2DC9420058A@gemini.denx.de> <1364665628804-151089.post@n7.nabble.com> <20130331105459.49d49ade@crub> Message-ID: <1364722200272-151106.post@n7.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Thank you for that heads up. In one of posts above a reference to the following code fragment is made, it uses a fatload command > For example, this is the whole "code" for a slide show demo I've been > using on a number of trade shows: > bootdelay=6 > show_one=fatload mmc 0:2 40001000 slide-${i}.bmp;bmp d 40001000 > slide_show=while mmc rescan; do for i in 1 2 3 4 5 6 7 8 ; do run > show_one ; sleep ${delay} ; done ; done > bootcmd=run slideshow Can you please explain the "show_one" and the "slide_show" commands ? And, do I just put this into board config ? -- View this message in context: http://u-boot.10912.n7.nabble.com/Handling-images-jpg-bmp-etc-in-u-boot-tp150524p151106.html Sent from the U-Boot mailing list archive at Nabble.com.