From: Dave Airlie <airlied@gmail.com>
To: linux-fbdev@vger.kernel.org
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: fb fix + laptop gpu switching support
Date: Thu, 25 Feb 2010 04:44:25 +0000 [thread overview]
Message-ID: <1267073067-23117-1-git-send-email-airlied@gmail.com> (raw)
The first patch is a trivial change to the fb handover code.
The second adds initial support framework for laptops with GPU switching
features, it has some changes to fb code, along with changes to dri
drivers.
I'm happy to deal with these patches via drm-2.6 for this merge window
if nobody has any objections.
Dave.
WARNING: multiple messages have this Message-ID (diff)
From: Dave Airlie <airlied@gmail.com>
To: linux-fbdev@vger.kernel.org
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: fb fix + laptop gpu switching support
Date: Thu, 25 Feb 2010 14:44:25 +1000 [thread overview]
Message-ID: <1267073067-23117-1-git-send-email-airlied@gmail.com> (raw)
The first patch is a trivial change to the fb handover code.
The second adds initial support framework for laptops with GPU switching
features, it has some changes to fb code, along with changes to dri
drivers.
I'm happy to deal with these patches via drm-2.6 for this merge window
if nobody has any objections.
Dave.
next reply other threads:[~2010-02-25 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 4:44 Dave Airlie [this message]
2010-02-25 4:44 ` fb fix + laptop gpu switching support Dave Airlie
2010-02-25 4:44 ` [PATCH 1/2] fb: for framebuffer handover don't exit the loop early Dave Airlie
2010-02-25 4:44 ` Dave Airlie
2010-02-25 4:44 ` Dave Airlie
2010-02-25 4:44 ` [PATCH 2/2] vga switch: hi my name is race condition Dave Airlie
2010-02-25 4:44 ` Dave Airlie
2010-02-25 4:44 ` Dave Airlie
-- strict thread matches above, loose matches on Subject: below --
2010-02-25 4:44 fb fix + laptop gpu switching support Dave Airlie
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=1267073067-23117-1-git-send-email-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.