From: Nathan Whitehorn <nwhitehorn@freebsd.org>
To: Geoff Levand <geoff@infradead.org>
Cc: cbe-oss-dev@lists.ozlabs.org, Andre Heider <a.heider@gmail.com>,
Hector Martin <hector@marcansoft.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [Cbe-oss-dev] [PATCH 05/10] powerpc/ps3: Use highmem region from repository
Date: Wed, 13 Jun 2012 13:25:53 -0500 [thread overview]
Message-ID: <4FD8DB31.6080207@freebsd.org> (raw)
In-Reply-To: <1339610324.3986.6.camel@clam>
On 06/13/12 12:58, Geoff Levand wrote:
> Hi Michael,
>
> On Wed, 2012-06-13 at 11:49 +1000, Michael Ellerman wrote:
>> On Wed, 2012-04-25 at 19:19 +0000, Andre Heider wrote:
>>> Use any preallocated highmem region setup by the bootloader.
>>> This implementation only checks for the existance of a single
>>> region at region_index=0.
>>>
>>> This feature allows the bootloader to preallocate highmem
>>> regions and pass the region locations to the kernel through
>>> the repository. Preallocated regions can be used to hold the
>>> initrd or other large data. If no region info exists, the
>>> kernel retains the old behavior and attempts to allocate the
>>> highmem region itself.
>>>
>>> Based on Hector Martin's patch "Get lv1 high memory region from
>>> devtree".
>> Apologies if this has been covered before, but why not use the device
>> tree?
> FreeBSD (and other OS's) don't know about the Linux device tree.
>
> This mechanism is for the bootloader to tell the OS about a highmem
> region it setup, and we want to support more than just Linux.
>
> -Geoff
>
>
FreeBSD actually does have FDT support -- it's just not used for the PS3
platform at the moment since it is (currently) totally redundant with
the HV repository. If people decide that FDT has an advantage, FreeBSD
at least can easily be adapted to use it.
-Nathan
next prev parent reply other threads:[~2012-06-13 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:19 [GIT PULL] PS3 updates for Linux-3.5 Geoff Levand
2012-04-25 19:19 ` [PATCH 04/10] powerpc/ps3: Add highmem repository read routines Andre Heider
2012-04-25 19:19 ` [PATCH 01/10] powerpc/ps3: Correct lv1 repository routine names Geoff Levand
2012-04-25 19:19 ` [PATCH 02/10] powerpc/ps3: Add PS3 repository write support Geoff Levand
2012-04-25 19:19 ` [PATCH 03/10] powerpc/ps3: Add highmem repository write routines Geoff Levand
2012-04-25 19:19 ` [PATCH 05/10] powerpc/ps3: Use highmem region from repository Andre Heider
2012-06-13 1:49 ` [Cbe-oss-dev] " Michael Ellerman
2012-06-13 17:58 ` Geoff Levand
2012-06-13 18:25 ` Nathan Whitehorn [this message]
2012-04-25 19:19 ` [PATCH 06/10] powerpc/ps3: Add highmem region memory early Hector Martin
2012-04-25 19:19 ` [PATCH 07/10] powerpc/ps3: Remove MEMORY_HOTPLUG requirement Andre Heider
2012-04-25 19:19 ` [PATCH 09/10] drivers/ps3: Fix checkpatch warnings in ps3av.c Valentin Ilie
2012-04-25 19:19 ` [PATCH 10/10] powerpc/ps3: Refresh ps3_defconfig Geoff Levand
2012-04-25 19:19 ` [PATCH 08/10] powerpc/ps3: Minor Kconfig cleanup Geoff Levand
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=4FD8DB31.6080207@freebsd.org \
--to=nwhitehorn@freebsd.org \
--cc=a.heider@gmail.com \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=geoff@infradead.org \
--cc=hector@marcansoft.com \
--cc=linuxppc-dev@lists.ozlabs.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).