From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Wrap the preallocated BIOS framebuffer and preserve for KMS fbcon v4
Date: Thu, 7 Nov 2013 08:28:01 -0800 [thread overview]
Message-ID: <20131107082801.73cbceeb@jbarnes-desktop> (raw)
In-Reply-To: <20131107142255.GV15018@nuc-i3427.alporthouse.com>
On Thu, 7 Nov 2013 14:22:55 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Wed, Nov 06, 2013 at 11:25:55AM -0800, Jesse Barnes wrote:
> > Retrieve current framebuffer config info from the regs and create an fb
> > object for the buffer the BIOS or boot loader left us. This should
> > allow for smooth transitions to userspace apps once we finish the
> > initial configuration construction.
> >
> > v2: check for non-native modes and adjust (Jesse)
> > fixup aperture and cmap frees (Imre)
> > use unlocked unref if init_bios fails (Jesse)
> > fix curly brace around DSPADDR check (Imre)
> > comment failure path for pin_and_fence (Imre)
> > v3: fixup fixup of aperture frees (Chris)
> > v4: update to current bits (locking & pin_and_fence hack) (Jesse)
>
> The only thing that I noticed was that the bookkeeping for the fb/obj is
> incorrect - which is presumably the hack mentioned above.
Yeah I should have left the pin_and_fence in with an #if 0 to make that
clearer... is that the only thing that's missing?
Any thoughts on why the pin_and_fence falls over on the preallocated
object?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-11-07 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 19:02 [WIP] Wrap fb objects from BIOS/bootloader Jesse Barnes
2013-11-06 19:25 ` [PATCH] drm/i915: Wrap the preallocated BIOS framebuffer and preserve for KMS fbcon v4 Jesse Barnes
2013-11-07 14:22 ` Chris Wilson
2013-11-07 16:28 ` Jesse Barnes [this message]
2013-11-07 16:39 ` Chris Wilson
2013-11-07 19:40 ` [PATCH] drm/i915: Wrap the preallocated BIOS framebuffer and preserve for KMS fbcon v5 Jesse Barnes
2013-11-07 19:56 ` Jesse Barnes
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=20131107082801.73cbceeb@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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