From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: devicetree@vger.kernel.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [RFC 2/7] bcm47xx-nvram: add new broadcom nvram driver with dt support
Date: Wed, 27 Aug 2014 11:20:43 -0700 [thread overview]
Message-ID: <53FE217B.7000401@gmail.com> (raw)
In-Reply-To: <CACna6rwJBDpg9VS4h5hfP4wtGRVwAdRUq5mELeA0OFWWzH9jsA@mail.gmail.com>
On 08/26/2014 10:54 PM, Rafał Miłecki wrote:
> On 24 August 2014 23:24, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>> +On NorthStar ARM SoCs the NAND flash is available at 0x1c000000 and the
>> +NOR flash is at 0x1e000000
>> +
>> +Example:
>> +
>> +nvram0: nvram@0 {
>> + compatible = "brcm,bcm47xx-nvram";
>> + reg = <0x1c000000 0x01000000>;
>> +};
>
> Could we avoid that? Type of flash can easily be checked in the code.
> All we need to do is to read BCMA_IOST register of BCMA_CORE_NS_ROM
> core.
So there is a boot status register you can read to tell what type of
flash you booted from, but does that also give you the resource ranges
for these type of flashes? Presumably they will be mapped into different
addresses (at least bcm63xx is like that), that information needs to be
listed somewhere.
--
Florian
next prev parent reply other threads:[~2014-08-27 18:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 21:24 [RFC 0/7] bcma: add device tree support Hauke Mehrtens
[not found] ` <1408915485-8078-1-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-24 21:24 ` Hauke Mehrtens
2014-08-24 21:24 ` [RFC 1/7] MIPS: BCM47XX: move the nvram header file into common space Hauke Mehrtens
2014-08-24 21:24 ` [RFC 2/7] bcm47xx-nvram: add new broadcom nvram driver with dt support Hauke Mehrtens
[not found] ` <1408915485-8078-4-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-24 21:45 ` Rafał Miłecki
2014-08-27 5:54 ` Rafał Miłecki
2014-08-27 18:20 ` Florian Fainelli [this message]
[not found] ` <53FE217B.7000401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-27 18:43 ` Rafał Miłecki
2014-08-24 21:24 ` [RFC 3/7] bcm47xx-sprom: add Broadcom sprom parser driver Hauke Mehrtens
[not found] ` <1408915485-8078-5-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-25 7:52 ` Arnd Bergmann
2014-08-25 15:01 ` Jonas Gorski
2014-08-26 21:32 ` Hauke Mehrtens
[not found] ` <53FCFCF0.2010704-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-09-01 9:24 ` Rafał Miłecki
2014-08-24 21:24 ` [RFC 4/7] bcma: register bcma as device tree driver Hauke Mehrtens
[not found] ` <1408915485-8078-6-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-25 7:57 ` Arnd Bergmann
2014-08-26 21:25 ` Hauke Mehrtens
2014-08-24 21:24 ` [RFC 5/7] bcma: get IRQ numbers from dt Hauke Mehrtens
[not found] ` <1408915485-8078-7-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-25 8:00 ` Arnd Bergmann
2014-08-24 21:24 ` [RFC 6/7] bcma: get sprom from devicetree Hauke Mehrtens
[not found] ` <1408915485-8078-8-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-25 8:04 ` Arnd Bergmann
2014-08-24 21:24 ` [RFC 7/7] ARM: BCM5301X: register bcma bus Hauke Mehrtens
[not found] ` <1408915485-8078-9-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2014-08-27 18:22 ` Florian Fainelli
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=53FE217B.7000401@gmail.com \
--to=f.fainelli@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).