From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WkTUI-0003mW-Gf for barebox@lists.infradead.org; Wed, 14 May 2014 07:20:27 +0000 Date: Wed, 14 May 2014 09:20:02 +0200 From: Sascha Hauer Message-ID: <20140514072002.GZ5858@pengutronix.de> References: <56785357-39FF-4F83-B1B3-F20C1D921A25@gmail.com> <20140514093212.ad026f36df7b0e4edaa54ba6@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Changing the baudrate via barebox prompt To: Holger Schurig Cc: "barebox@lists.infradead.org" On Wed, May 14, 2014 at 08:09:00AM +0200, Holger Schurig wrote: > Hmm, any reason why csX.baudrate isn't listed under magicvars ? These variables predate the magicvar support and nobody has ever added it them to magicvar. It's not clear how we want to add these. Do we want to add wildcards to the magicvar description (csX)? This gets incorrect for some devices which can show up as mmcX or mciX depending on the way they are registered. We could also attach the description to the device parameter themselves which means we get descriptions for all parameters actually registered, like cs0.baudrate Baudrate for the serial console cs1.baudrate Baudrate for the serial console ... Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox