From: Dave Airlie <airlied@gmail.com>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
linux-fbdev@vger.kernel.org, nouveau@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Peter Jones <pjones@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/3] fbmem: fix aperture overlapping check
Date: Mon, 12 Apr 2010 22:32:29 +0000 [thread overview]
Message-ID: <n2t21d7e9971004121532y394d2f29rf018d8f33769ba57@mail.gmail.com> (raw)
In-Reply-To: <20100412213327.GA4463@joi.lan>
>
> Ok, thanks for explanation. I'll drop this patch and rebase the others.
Cool,
>> You won't be able to make this work for vga16fb from what I can see
>> since it access 0xa000 directly, not via any of the defined apertures
>> that vesafb/offb use. vga16fb will need a different approach I suspect.
>
> Yeah, there's an idea to claim 0xa0000 as an aperture of vga16fb and then
> do the same in KMS driver but only if it's the primary card.
> (You hinted to use SHADOW resource bit to check whether card is primary)
> I think I'll try this approach soon.
Yeah as long as we kick it off once, certain things like vga switcheroo change
who the primary gpu is at runtime.
but it should be okay if both drivers have the kickoff paths.
Dave.
next prev parent reply other threads:[~2010-04-12 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 19:55 [PATCH 1/3] fbmem: fix aperture overlapping check marcin.slusarz
2010-04-10 19:55 ` [PATCH 2/3] fbdev: allow passing more than one aperture for handoff marcin.slusarz
2010-04-10 19:55 ` [PATCH 3/3] fbmem, drm/nouveau: kick firmware framebuffers as soon as possible marcin.slusarz
2010-04-11 17:09 ` [PATCH 3/3] fbmem, drm/nouveau: kick firmware framebuffers as Marcin Slusarz
2010-04-11 23:54 ` [PATCH 1/3] fbmem: fix aperture overlapping check Dave Airlie
2010-04-12 11:34 ` Marcin Slusarz
2010-04-12 20:28 ` Dave Airlie
2010-04-12 21:33 ` Marcin Slusarz
2010-04-12 22:32 ` Dave Airlie [this message]
2010-04-13 19:50 ` [PATCH] vga16fb, drm/nouveau: vga16fb->nouveau handoff Marcin Slusarz
2010-04-18 21:57 ` [PATCH] vga16fb, drm: vga16fb->drm handoff Marcin Slusarz
2010-04-19 16:20 ` James Simmons
2010-04-20 19:54 ` Marcin Slusarz
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=n2t21d7e9971004121532y394d2f29rf018d8f33769ba57@mail.gmail.com \
--to=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@lists.freedesktop.org \
--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).