From: josh.coombs@gmail.com (Josh Coombs)
To: linux-arm-kernel@lists.infradead.org
Subject: Converting kirkwood-goflexnet to DTS
Date: Thu, 14 Jun 2012 09:28:24 -0400 [thread overview]
Message-ID: <CAMW5UfYMxSKmGAvZ5ucNyr8AL0zBAj5jpt+s8YhogKaWdv2mAw@mail.gmail.com> (raw)
In-Reply-To: <20120613191029.GI14756@titan.lakedaemon.net>
On Wed, Jun 13, 2012 at 3:10 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> I would recommend looking at how we did the first board, the dreamplug.
> Files of interest are:
>
> arch/arm/boot/dts/kirkwood.dtsi
> arch/arm/boot/dts/kirkwood-dreamplug.dts
> arch/arm/mach-kirkwood/board-dt.c
> arch/arm/mach-kirkwood/board-dreamplug.c
> arch/arm/mach-kirkwood/Kconfig
> arch/arm/mach-kirkwood/Makefile
> arch/arm/mach-kirkwood/Makefile.boot
>
> commit 3d468b6 seems to be a good place to start.
>
> For your first patch series, use the dtb to tell the kernel what board
> it is on. ?Once that's working, then you just start coverting over
> drivers one by one. ?Several are already done.
>
> hth,
>
> Jason.
First pass didn't boot, no kernel messages. I'm going to go through
the ArchLinux ARM superpatch to see if there are any items not
directly pegged to the GoFlex that might be involved next, as well as
cutting my conf down to just what's needed for the GFN to cut down my
build times. While I'm doing that, what do I NEED to configure for
proper DTS support?
CONFIG_ARCH_KIRKWOOD=y
CONFIG_ARCH_KIRKWOOD_DT=y
CONFIG_MACH_DREAMPLUG_DT=n
CONFIG_MACH_ICONNECT_DT=n
CONFIG_MACH_DLINK_KIRKWOOD_DT=n
CONFIG_MACH_IB62X0_DT=n
CONFIG_MACH_GOFLEX_DT=y
CONFIG_USE_OF=y
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_CMDLINE=""
CONFIG_ATAGS_PROC=y
CONFIG_USE_OF=y
CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_PHYSMAP_OF is not set
CONFIG_OF=y
# CONFIG_OF_SELFTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_DEVICE=y
CONFIG_OF_I2C=m
CONFIG_OF_NET=y
CONFIG_OF_MDIO=y
CONFIG_OF_PCI=y
CONFIG_OF_PCI_IRQ=y
CONFIG_OF_MTD=y
# CONFIG_SERIAL_OF_PLATFORM is not set
CONFIG_OF_GPIO=y
Am I missing anything?
Joshua Coombs
next prev parent reply other threads:[~2012-06-14 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 18:27 Converting kirkwood-goflexnet to DTS Josh Coombs
2012-06-13 19:10 ` Jason Cooper
2012-06-14 13:28 ` Josh Coombs [this message]
2012-06-14 13:59 ` Arnaud Patard (Rtp)
2012-06-14 14:00 ` Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2012-06-14 14:17 Andrew Lunn
2012-06-14 22:16 ` Josh Coombs
2012-06-15 4:53 ` Josh Coombs
2012-06-15 8:41 ` Thomas Petazzoni
2012-06-15 12:40 ` Josh Coombs
2012-06-15 12:53 ` Thomas Petazzoni
2012-06-15 12:58 ` Arnaud Patard (Rtp)
2012-06-15 22:55 ` Josh Coombs
2012-06-17 12:40 ` Josh Coombs
2012-06-15 6:30 Andrew Lunn
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=CAMW5UfYMxSKmGAvZ5ucNyr8AL0zBAj5jpt+s8YhogKaWdv2mAw@mail.gmail.com \
--to=josh.coombs@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).