From: Finn Thain <fthain@telegraphics.com.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [RFC v4 17/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram
Date: Thu, 16 Jul 2015 06:01:41 +0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1507161530270.19651@nippy.intranet> (raw)
In-Reply-To: <alpine.LNX.2.00.1507151200510.2862@nippy.intranet>
On Wed, 15 Jul 2015, I wrote:
> On Tue, 14 Jul 2015, Benjamin Herrenschmidt wrote:
>
> > Maybe we should have a dedicated accessor for "mac_xpram" ...
>
> ... I can see how to implement XPRAM for matroxfb and imsttfb
I'll have to retract that. The video mode and color mode settings used by
the PowerMac framebuffer drivers don't exist in the PRAM portion of NVRAM.
Addresses 0x140F and 0x1410 are found in the partition reserved by Apple
for "Name Registry properties", according to Designing PCI Cards and
Drivers for Power Macintosh Computers. There is no equivalent on m68k
Macs, AFAIK.
This is NVRAM partition 2 on my beige g3, which begins at 0x1400. I'm not
sure that this is true on New World PowerMacs, and I suspect that the
framebuffer drivers should be calling pmac_get_partition() to determine
the offset of the beginning of the Name Registry partition.
The arch_nvram_ops methods don't deal with structures like partitions.
They treat the entire 8 KiB as unstructured, because that's how /dev/nvram
treats it.
--
next prev parent reply other threads:[~2015-07-16 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150712102527.356151908@telegraphics.com.au>
2015-07-12 10:25 ` [RFC v4 13/25] powerpc: Cleanup nvram includes Finn Thain
2015-07-12 10:25 ` [RFC v4 17/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_wri Finn Thain
2015-07-14 7:58 ` [RFC v4 17/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram Finn Thain
2015-07-14 11:52 ` Benjamin Herrenschmidt
2015-07-15 5:21 ` Finn Thain
2015-07-16 6:01 ` Finn Thain [this message]
2015-09-18 8:17 ` Finn Thain
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=alpine.LNX.2.00.1507161530270.19651@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
/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