From: Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Ben Dooks <ben-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 06/11] arm-dt: postpone machine detection until setup_arch with CONFIG_ARM_DEVTREE
Date: Tue, 5 Jan 2010 06:26:54 +0800 [thread overview]
Message-ID: <201001050926.54286.jeremy.kerr@canonical.com> (raw)
In-Reply-To: <4B421903.4050200-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
Hi Ben,
> > When we're using CONFIG_ARM_DEVTREE, we need to postpone machine
> > detection until later in setup_arch. Because ARM_DEVTREE depends on
> > !DEBUG_LL, we don't need the mdesc this early anyway.
> >
> > We'll add support for ARM_DEVTREE && DEBUG_LL later.
>
> Why not add a specific machine type for 'this is device tree' and
> then these routines don't even need to #ifdef. It would especially
> be good as it allows dt and non-dt machines to coexist in the same
> kernel together.
Mainly because this doesn't gain us much; the machine_desc that is discovered
from this new machine type would not have the correct data (phys_io &
io_pg_offset) required for early setup (used for DEBUG_LL).
We could conditionally skip the detection if we see a DT machine type, but
then we'd need to add similar checks for all the paths where the machine_desc
is used.
However, my goal is indeed to allow DT and non-DT machines to coexist as much
as possible, this patch is more a temporary workaround while I figure out how
to handle the DEBUG_LL stuff nicely for DT cases.
Cheers,
Jeremy
next prev parent reply other threads:[~2010-01-04 22:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 10:54 [PATCH 00/11] Device-tree support for ARM Jeremy Kerr
2009-12-22 10:54 ` [PATCH 06/11] arm-dt: postpone machine detection until setup_arch with CONFIG_ARM_DEVTREE Jeremy Kerr
2010-01-04 16:36 ` Ben Dooks
[not found] ` <4B421903.4050200-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
2010-01-04 22:26 ` Jeremy Kerr [this message]
2009-12-22 10:54 ` [PATCH 03/11] arm: export arm_add_memory Jeremy Kerr
2009-12-22 10:54 ` [PATCH 10/11] arm-dt: parse initrd from device tree Jeremy Kerr
2009-12-22 10:54 ` [PATCH 09/11] arm-dt: probe for device-tree enabled platforms Jeremy Kerr
2009-12-22 10:54 ` [PATCH 07/11] arm-dt: parse devtree pointer on boot Jeremy Kerr
2009-12-22 10:54 ` [PATCH 02/11] arm: use generic infrastructure for early params Jeremy Kerr
2010-01-06 16:27 ` Russell King - ARM Linux
[not found] ` <20100106162731.GB1728-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2010-01-06 22:31 ` Jeremy Kerr
[not found] ` <201003060733.57636.rob@landley.net>
[not found] ` <201003060733.57636.rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2010-03-06 16:01 ` Grant Likely
2009-12-22 10:54 ` [PATCH 01/11] arm: change command_line to cmd_line, and export it Jeremy Kerr
2009-12-22 10:54 ` [PATCH 11/11] arm/versatile: probe via device tree Jeremy Kerr
2009-12-22 10:54 ` [PATCH 04/11] arm-dt: Add ATAG_DEVTREE tag Jeremy Kerr
2009-12-22 10:54 ` [PATCH 08/11] arm-dt: parse memory info from DT Jeremy Kerr
2009-12-22 10:54 ` [PATCH 05/11] arm-dt: Add CONFIG_ARM_DEVTREE Jeremy Kerr
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=201001050926.54286.jeremy.kerr@canonical.com \
--to=jeremy.kerr-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=ben-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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