From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit
Date: Tue, 18 Oct 2011 14:54:47 +0200 [thread overview]
Message-ID: <20111018125447.GA2345@tarshish> (raw)
In-Reply-To: <4E9D481D.2070905@bluegiga.com>
Hi Lauri,
On Tue, Oct 18, 2011 at 12:34:21PM +0300, Lauri Hintsala wrote:
> On 10/18/2011 10:58 AM, Baruch Siach wrote:
> >u-boot can pass any string you like to the kernel. Just do
>
> Yes I know I can pass any string I like.
>
>
> >setenv bootargs "$bootargs fec.macaddr=0x00,0x04,0x9f,0x01,0x30,0xe0"
> >
> >at the u-boot prompt, or in a script.
>
> ethaddr variable of uboot is taking mac addr in colon separated form
> (e.g. "00:04.9f:01:30:e0") and it is not very useful to have mac
> address in two different form in uboot envs.
Makes sense. The code doing the array module parameters is in
kernel/params.c:param_array(). It seems that teaching this routine to parse
the common MAC notation is not very hard. This IMO is a better solution than
adding another MAC parser for a new top-level kernel parameter.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2011-10-18 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 8:08 [PATCH] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit Lauri Hintsala
2011-10-17 9:44 ` Uwe Kleine-König
2011-10-17 10:39 ` Baruch Siach
2011-10-18 7:45 ` Lauri Hintsala
2011-10-18 7:58 ` Baruch Siach
2011-10-18 9:34 ` Lauri Hintsala
2011-10-18 12:54 ` Baruch Siach [this message]
2011-10-18 7:27 ` Lauri Hintsala
2011-10-18 7:39 ` Uwe Kleine-König
2011-10-18 8:01 ` Lauri Hintsala
2011-10-18 8:12 ` Uwe Kleine-König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111018125447.GA2345@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).