From: John Crispin <blogic@openwrt.org>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/8] MIPS: BCM63XX: move flash registration out of board_bcm963xx.c
Date: Wed, 13 Jun 2012 16:10:25 +0200 [thread overview]
Message-ID: <4FD89F51.5020200@openwrt.org> (raw)
In-Reply-To: <20120613135953.GB6839@linux-mips.org>
On 13/06/12 15:59, Ralf Baechle wrote:
>>> > > And the grand cure for that sort of issue is FDT - we by now have built
>>> > > big deserts of code just registering platform devices like this.. See
>>> > > John Crispin's Lantiq work or David's Cavium code for FDT examples.
>> >
>> > I have some patches to convert bcm63xx to FDT but that is still work in
>> > progress, and I don't want them to hold support for newer BCM63xx CPUs.
> Oh absolutely. I'm just nagging to make it clear to everybody into what
> direction the world is moving.
>
FDT FTW :-)
next prev parent reply other threads:[~2012-06-13 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 8:23 [PATCH 0/8] Add basic support for BCM6328 Jonas Gorski
2012-06-12 8:23 ` [PATCH 1/8] MIPS: BCM63XX: move flash registration out of board_bcm963xx.c Jonas Gorski
2012-06-13 13:48 ` Ralf Baechle
2012-06-13 13:51 ` Florian Fainelli
2012-06-13 13:59 ` Ralf Baechle
2012-06-13 14:10 ` John Crispin [this message]
2012-06-13 15:35 ` Ralf Baechle
2012-06-16 11:03 ` Jonas Gorski
2012-06-12 8:23 ` [PATCH 2/8] MIPS: BCM63XX: add flash type detection Jonas Gorski
2012-06-12 8:23 ` [PATCH 3/8] MIPS: BCM63XX: use the Chip ID register for identifying the SoC Jonas Gorski
2012-06-12 8:23 ` [PATCH 4/8] MIPS: BCM63XX: add basic BCM6328 CPU support Jonas Gorski
2012-06-12 8:23 ` [PATCH 5/8] MIPS: BCM63XX: Move the PCI initialization into its own function Jonas Gorski
2012-06-12 8:23 ` [PATCH 6/8] MIPS: BCM63XX: Add PCIe Support for BCM6328 Jonas Gorski
2012-06-12 8:23 ` [PATCH 7/8] MIPS: expose PCIe drivers for MIPS Jonas Gorski
2012-06-12 8:23 ` [PATCH 8/8] MIPS: BCM63XX: add 96328avng reference board Jonas Gorski
2012-06-12 11:26 ` [PATCH 0/8] Add basic support for BCM6328 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=4FD89F51.5020200@openwrt.org \
--to=blogic@openwrt.org \
--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