From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Peter Jones <pjones@redhat.com>, linux-fbdev-devel@lists.sf.net
Subject: Re: [PATCH] fb: add support for handoff from firmware to hw framebuffers (v2)
Date: Fri, 5 Jun 2009 18:49:51 -0700 [thread overview]
Message-ID: <20090605184951.80e5adfe.akpm@linux-foundation.org> (raw)
In-Reply-To: <21d7e9970906051838g2058a651x8be7786c6b6237f4@mail.gmail.com>
On Sat, 6 Jun 2009 11:38:32 +1000 Dave Airlie <airlied@gmail.com> wrote:
> On Fri, Jun 5, 2009 at 11:51 PM, Peter Jones<pjones@redhat.com> wrote:
> > On 06/05/2009 02:07 AM, Dave Airlie wrote:
> >> From: Dave Airlie <airlied@redhat.com>
> >>
> >> With KMS we have ran into an issue where we really want the KMS fb driver
> >> to be the one running the console, so panics etc can be shown by switching
> >> out of X etc.
> >>
> >> However with vesafb/efifb built-in, we end up with those on fb0 and the
> >> KMS fb driver on fb1, driving the same piece of hw, so this adds an fb info
> >> flag to denote a firmware fbdev, and adds a new aperture base/size range
> >> which can be compared when the hw drivers are installed to see if there
> >> is a conflict with a firmware driver, and if there is the firmware driver is
> >> unregistered and the hw driver takes over.
> >>
> >> It uses new aperture_base/size members instead of comparing on the fix
> >> smem_start/length, as smem_start/length might for example only cover the
> >> first 1MB of the PCI aperture, and we could allocate the kms fb from 8MB
> >> into the aperture, thus they would never overlap.
> >>
> >> v2: add an fb_destroy callback so the firmware fb can cleanup after itself.
> >> vesafb will now remove the region it reserves and destroy its fb info.
> >>
> >> Signed-off-by: Dave Airlie <airlied@redhat.com>
> >
> > This version looks good to me.
> >
> > Acked-by: Peter Jones <pjones@redhat.com>
> >
>
> Andrew do we have an fbdev maintainer
Tony suddenly vanished nearly two years ago. He did that once before,
then resurfaced after six months - he'd been working in a remote
village with no net connection. Hopefully he will reappear again.
In the meanwhile I'm handling fbdev patches and Geert and Krzysztof are
doing the technical work when time permits. I'll occasionally troll
linux-fbdev-devel looking for patches which people send.
> or can you pick this up for the next merge window?
No probs.
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
prev parent reply other threads:[~2009-06-06 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 6:07 [PATCH] fb: add support for handoff from firmware to hw framebuffers (v2) Dave Airlie
2009-06-05 13:51 ` Peter Jones
2009-06-06 1:38 ` Dave Airlie
2009-06-06 1:49 ` Andrew Morton [this message]
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=20090605184951.80e5adfe.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=linux-fbdev-devel@lists.sf.net \
--cc=pjones@redhat.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;
as well as URLs for NNTP newsgroup(s).