public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] arm: Remove unregister MACH_TYPE_xxx uses
Date: Tue, 10 Jan 2017 20:22:56 -0500	[thread overview]
Message-ID: <20170111012256.GH7532@bill-the-cat> (raw)
In-Reply-To: <b260bf19-75e8-c759-c826-09c6fcc5b937@wwwdotorg.org>

On Tue, Jan 10, 2017 at 05:14:32PM -0700, Stephen Warren wrote:
> On 01/10/2017 03:22 PM, Tom Rini wrote:
> >Before we can sync with the latest mach-types.h file from the Linux
> >Kernel we need to remove some instances of MACH_TYPE_xxx from our
> >sources.  As these values have been removed from the canonical upstream
> >source we should not be using them either, so drop.
> 
> The Tegra and RPi changes only affect non-DT booting, right?

Correct.  MACH_TYPE_xxx is only used for ATAG booting.

> It would be nice if the Tegra config headers could be kept
> consistent, i.e. delete all places that define CONFIG_MACH_TYPE from
> all Tegra config headers, rather than just removing a few. Perhaps
> it even makes sense to do that source-tree-wide, at least for ARM
> boards?

I leave the decision to remove MACH_TYPE_xxx up to the SoC custodians.
I know that for example for TI parts we do not want to as people are
using RTOSes that do use ATAGS still.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170110/da43269a/attachment.sig>

  reply	other threads:[~2017-01-11  1:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 22:22 [U-Boot] [PATCH 1/4] omap3_logic: Rework MACH_TYPE and fdtfile logic Tom Rini
2017-01-10 22:22 ` [U-Boot] [PATCH 2/4] omap3_igep00x0: Rework MACH_TYPE and status LED logic slightly Tom Rini
2017-01-11 14:59   ` Enric Balletbo Serra
2017-01-11 15:05     ` Tom Rini
2017-01-11 15:10       ` Enric Balletbo Serra
2017-01-14 20:57   ` [U-Boot] [U-Boot, " Tom Rini
2017-01-10 22:22 ` [U-Boot] [PATCH 3/4] arm: Remove unregister MACH_TYPE_xxx uses Tom Rini
2017-01-11  0:14   ` Stephen Warren
2017-01-11  1:22     ` Tom Rini [this message]
2017-01-14 20:57   ` [U-Boot] [U-Boot, " Tom Rini
2017-01-10 22:22 ` [U-Boot] [PATCH 4/4] arm: Re-sync asm/mach-types.h with Linux Kernel v4.9 Tom Rini
2017-01-11 14:30   ` Adam Ford
2017-01-14 20:57   ` [U-Boot] [U-Boot, " Tom Rini
2017-01-11 13:38 ` [U-Boot] [PATCH 1/4] omap3_logic: Rework MACH_TYPE and fdtfile logic Adam Ford
2017-01-14 20:57 ` [U-Boot] [U-Boot, " Tom Rini

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=20170111012256.GH7532@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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