Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH 1/2] MIPS: BCM47XX: add board detection
Date: Wed, 18 Sep 2013 14:09:14 +0200	[thread overview]
Message-ID: <20130918120914.GM22468@linux-mips.org> (raw)
In-Reply-To: <52399641.4090901@hauke-m.de>

On Wed, Sep 18, 2013 at 02:02:09PM +0200, Hauke Mehrtens wrote:

> On 09/18/2013 01:41 PM, Geert Uytterhoeven wrote:
> > On Wed, Sep 18, 2013 at 1:29 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >> Detect on which board this code is running based on some nvram
> >> settings. This is needed to start board specific workarounds and
> >> configure the leds and buttons which are on different gpios on every board.
> >>
> >> This patches add some boards we have seen, but there are many more.
> > 
> > Can you please make the board database __initconst, and only retain in memory
> > a copy of the detected board info?
> > 
> > Gr{oetje,eeting}s,
> > 
> >                         Geert
> > 
> I will change this in a next version of this patch.

I've already queued the first version of the patch so an incremental
patch would be handy.

Thanks,

  Ralf

      reply	other threads:[~2013-09-18 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 11:29 [PATCH 1/2] MIPS: BCM47XX: add board detection Hauke Mehrtens
2013-09-18 11:29 ` [PATCH 2/2] MIPS: BCM47XX: print board name in /proc/cpuinfo Hauke Mehrtens
2013-09-18 11:41 ` [PATCH 1/2] MIPS: BCM47XX: add board detection Geert Uytterhoeven
2013-09-18 12:02   ` Hauke Mehrtens
2013-09-18 12:09     ` Ralf Baechle [this message]

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=20130918120914.GM22468@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-mips@linux-mips.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