From: "Michel Dänzer" <michel@daenzer.net>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/nouveau: fix init with agpgart-uninorth
Date: Mon, 19 Nov 2012 11:57:18 +0100 [thread overview]
Message-ID: <1353322638.27512.82.camel@thor.local> (raw)
In-Reply-To: <20121116181120.GB8288@blackmetal.musicnaut.iki.fi>
On Fre, 2012-11-16 at 20:11 +0200, Aaro Koskinen wrote:
> On Fri, Nov 16, 2012 at 03:16:09PM +0100, Michel Dänzer wrote:
> > On Fre, 2012-11-16 at 11:54 +0200, Aaro Koskinen wrote:
> > > Check that the AGP aperture can be mapped. This follows a similar change
> > > done for Radeon (commit 365048ff, drm/radeon: AGP memory is only I/O if
> > > the aperture can be mapped by the CPU.).
> > >
> > > The patch fixes the following error seen on G5 iMac:
> > >
> > > nouveau E[ DRM] failed to create kernel channel, -12
> > >
> > > Signed-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> > > ---
> > > drivers/gpu/drm/nouveau/nouveau_bo.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c b/drivers/gpu/drm/nouveau/nouveau_bo.c
> > > index 35ac57f..5f0e7ef 100644
> > > --- a/drivers/gpu/drm/nouveau/nouveau_bo.c
> > > +++ b/drivers/gpu/drm/nouveau/nouveau_bo.c
> > > @@ -1279,7 +1279,7 @@ nouveau_ttm_io_mem_reserve(struct ttm_bo_device *bdev, struct ttm_mem_reg *mem)
> > > if (drm->agp.stat == ENABLED) {
> > > mem->bus.offset = mem->start << PAGE_SHIFT;
> > > mem->bus.base = drm->agp.base;
> > > - mem->bus.is_iomem = true;
> > > + mem->bus.is_iomem = !dev->agp->cant_use_aperture;
> >
> > Looks good, though radeon also doesn't set TTM_MEMTYPE_FLAG_MAPPABLE for
> > the TT memory type if the aperture can't be mapped directly. Maybe
> > nouveau should do the same, or maybe it doesn't really matter. Not sure.
>
> This would fail with -EINVAL if the MAPPABLE flag is not set. So I think
> it's needed?
>
> Looking at radeon_ttm.c, the MAPPABLE flag seems to be set in both cases:
Ah, indeed, I misread that. Your patch is
Reviewed-by: Michel Dänzer <michel@daenzer.net>
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
prev parent reply other threads:[~2012-11-19 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 9:54 [PATCH] drm/nouveau: fix init with agpgart-uninorth Aaro Koskinen
2012-11-16 14:16 ` Michel Dänzer
2012-11-16 18:11 ` Aaro Koskinen
2012-11-19 10:57 ` Michel Dänzer [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=1353322638.27512.82.camel@thor.local \
--to=michel@daenzer.net \
--cc=aaro.koskinen@iki.fi \
--cc=dri-devel@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