linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Luciano Coelho <luciano.coelho@nokia.com>,
	"ext John W. Linville" <linville@tuxdriver.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ido Yariv <ido@wizery.com>, Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [PATCH v3] omap: beagle: add support for wl1271 on the board file
Date: Fri, 24 Sep 2010 14:08:33 -0700	[thread overview]
Message-ID: <20100924210833.GJ4211@atomide.com> (raw)
In-Reply-To: <AANLkTimixgHuhKYRP9X17V+z20T70Pn0vJJEsO_HgXQ4@mail.gmail.com>

* Gadiyar, Anand <gadiyar@ti.com> [100924 12:13]:
> On Sat, Sep 25, 2010 at 12:41 AM, Tony Lindgren <tony@atomide.com> wrote:
> 
> This seems to be a generic problem that many boards with potential for
> adding expansion boards seem to have. How about one of these options:
> (a) having u-boot modify ATAGS_REVISION based on an environment variable
> or
> (b) add a generic board_revision kernel command line parameter that
> each such board file can parse

There is already system_rev that can be used for that and has an
ARM generic atag for it. Just needs to be passed from u-boot,
and should have setenv option for it in u-boot also.

Tony

  reply	other threads:[~2010-09-24 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 10:03 [PATCH v3] omap: beagle: add support for wl1271 on the board file Luciano Coelho
2010-09-24 18:03 ` John W. Linville
2010-09-24 18:50   ` Luciano Coelho
2010-09-24 19:11     ` Tony Lindgren
2010-09-24 19:21       ` Gadiyar, Anand
2010-09-24 21:08         ` Tony Lindgren [this message]
2010-09-24 19:42       ` Koen Kooi
2010-09-24 20:00         ` Luciano Coelho
2010-09-24 20:21           ` Koen Kooi
2010-09-24 19:55       ` Luciano Coelho

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=20100924210833.GJ4211@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=ido@wizery.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luciano.coelho@nokia.com \
    --cc=ohad@wizery.com \
    /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).