From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
blogic@openwrt.org,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH 2/4] MIPS: BCM47XX: fix detection for some boards
Date: Thu, 02 Jan 2014 23:35:10 +0100 [thread overview]
Message-ID: <52C5E99E.1090408@hauke-m.de> (raw)
In-Reply-To: <CACna6rw3Y7GwitM4nma+MHVj1spqOyv1F4GWJtaA+e5TTHjnug@mail.gmail.com>
On 01/02/2014 09:47 PM, Rafał Miłecki wrote:
> 2014/1/2 Hauke Mehrtens <hauke@hauke-m.de>:
>> When a nvram reset was performed from CFE, it sometimes does not
>> contain the productid value in nvram, but it still contains
>> hardware_version.
>
> It seems you switched to a very solid detection with that.
>
> Why not remove old entries?
>
Yes I will remove them.
Hauke
next prev parent reply other threads:[~2014-01-02 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 18:25 [PATCH 1/4] MIPS: BCM47XX: add Belkin F7Dxxxx board detection Hauke Mehrtens
2014-01-02 18:25 ` [PATCH 2/4] MIPS: BCM47XX: fix detection for some boards Hauke Mehrtens
2014-01-02 20:47 ` Rafał Miłecki
2014-01-02 22:35 ` Hauke Mehrtens [this message]
2014-01-02 18:25 ` [PATCH 3/4] MIPS: BCM47XX: add board detection for Linksys WRT54GS V1 Hauke Mehrtens
2014-01-02 20:53 ` Rafał Miłecki
2014-01-02 22:35 ` Hauke Mehrtens
2014-01-02 18:25 ` [PATCH 4/4] MIPS: BCM47XX: fix sparse warnings in board.c Hauke Mehrtens
2014-01-02 21:35 ` [PATCH 1/4] MIPS: BCM47XX: add Belkin F7Dxxxx board detection Rafał Miłecki
2014-01-02 22:03 ` Cody P Schafer
2014-01-02 22:47 ` Hauke Mehrtens
2014-01-03 6:40 ` Rafał Miłecki
2014-01-03 6:43 ` Rafał Miłecki
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=52C5E99E.1090408@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=zajec5@gmail.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