linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur.tabi@gmail.com>
To: Micha Nelissen <micha@neli.hopto.org>
Cc: Aggrwal Poonam-B10812 <B10812@freescale.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] e500v2 36 bit large physical HID0[EN_MAS7_UPDATE]
Date: Wed, 16 Jun 2010 09:23:38 -0500	[thread overview]
Message-ID: <AANLkTikDywS1B5i2kCQfTvJAWBuq7K3UuOmGQzi45UAX@mail.gmail.com> (raw)
In-Reply-To: <4C189860.3040702@neli.hopto.org>

On Wed, Jun 16, 2010 at 4:24 AM, Micha Nelissen <micha@neli.hopto.org> wrote:

> IMHO:
> 1) Linux should not be dependent on U-boot or any other bootloader, or at
> least as possible
> 2) U-boot cannot (and does not want to) know whether Linux is going to use
> large physical addresses.

To quote The Dude: "Yeah, well, you know, that's just, like, your opinion, man."

I'm sorry, but Linux does depend on the boot loader, and U-Boot does
need to know whether Linux is going to use 36-bit addressing.  That's
just the way it works.  Linux patches that repeat what U-Boot already
does just so that you don't need to update your U-boot are going to be
rejected.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2010-06-16 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  6:58 [PATCH] e500v2 36 bit large physical HID0[EN_MAS7_UPDATE] Micha Nelissen
2010-06-16  7:29 ` Aggrwal Poonam-B10812
2010-06-16  9:24   ` Micha Nelissen
2010-06-16 10:49     ` Aggrwal Poonam-B10812
2010-06-16 11:34       ` Micha Nelissen
2010-06-16 11:38         ` Aggrwal Poonam-B10812
2010-06-16 14:23     ` Timur Tabi [this message]
2010-06-16 14:52       ` Micha Nelissen
2010-06-22 22:39       ` Scott Wood
2010-06-16 15:01 ` Kumar Gala
2010-06-16 15:12   ` Micha Nelissen
2010-06-16 15:18     ` Micha Nelissen

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=AANLkTikDywS1B5i2kCQfTvJAWBuq7K3UuOmGQzi45UAX@mail.gmail.com \
    --to=timur.tabi@gmail.com \
    --cc=B10812@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=micha@neli.hopto.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).