From: Andrew Lutomirski <luto@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sf.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jerome Glisse <jglisse@redhat.com>,
Alex Deucher <alexdeucher@gmail.com>
Subject: Re: [git pull] drm: previous pull req + 1.
Date: Sun, 21 Jun 2009 17:14:52 -0400 [thread overview]
Message-ID: <cb0375e10906211414j390fc590y4331896bddda9c0d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0906211223190.3119@localhost.localdomain>
On Sun, Jun 21, 2009 at 3:47 PM, Linus
Torvalds<torvalds@linux-foundation.org> wrote:
>
>
> What *has* changed is that we have a newradeon driver, and it looks like
> that new radeon driver is crap, and does this:
>
> info->fix.smem_start = (unsigned long)fbptr;
>
> which is totally screwed up. It assigns a _virtual_ address to that
> "smem_start" thing, even though it should be a physical one.
>
> I don't know the radeon driver, so I don't know where to find the physical
> address. It's also possible that there is no good single physical
> address, and the radeon driver should implement a "fb_mmap" function.
>
> Does this patch make the warning and the oops at least go away? Obviously
> it won't result in a working frame buffer, but that's a separate issue
>
I haven't tried your patch, but I hacked up the one below instead,
which also fixes the oops. It still doesn't boot, though -- plymouth
hangs (or otherwise dies), preventing my initramfs from finishing.
The same kernel image boots fine with radeon.modeset=0.
I wouldn't apply this without someone more familiar with the code's
ack -- I have no idea if the lifetime of the framebuffer object is
right, and there may be any number of other bugs lurking in here. Not
to mention a missing "static."
Signed-off-by: Andy Lutomirski <luto@mit.edu>
diff --git a/drivers/gpu/drm/radeon/radeon_fb.c
b/drivers/gpu/drm/radeon/radeon_fb.c
index fa86d39..cbb330d 100644
--- a/drivers/gpu/drm/radeon/radeon_fb.c
+++ b/drivers/gpu/drm/radeon/radeon_fb.c
@@ -380,6 +380,12 @@ int radeonfb_blank(int blank, struct fb_info *info)
return 0;
}
+int radeonfb_mmap(struct fb_info *info, struct vm_area_struct *vma)
+{
+ struct radeon_fb_device *rfbdev = info->par;
+ return radeon_object_fbdev_mmap(rfbdev->rdev->fbdev_robj, vma);
+}
+
static struct fb_ops radeonfb_ops = {
.owner = THIS_MODULE,
.fb_check_var = radeonfb_check_var,
@@ -390,6 +396,7 @@ static struct fb_ops radeonfb_ops = {
.fb_imageblit = cfb_imageblit,
.fb_pan_display = radeonfb_pan_display,
.fb_blank = radeonfb_blank,
+ .fb_mmap = radeonfb_mmap,
};
/**
@@ -499,7 +506,7 @@ int radeonfb_create(struct radeon_device *rdev,
ret = radeon_gem_object_create(rdev, aligned_size, 0,
RADEON_GEM_DOMAIN_VRAM,
- false, ttm_bo_type_kernel,
+ false, ttm_bo_type_device,
false, &gobj);
if (ret) {
printk(KERN_ERR "failed to allocate framebuffer\n");
@@ -547,8 +554,6 @@ int radeonfb_create(struct radeon_device *rdev,
info->fbops = &radeonfb_ops;
info->fix.line_length = fb->pitch;
info->screen_base = fbptr;
- info->fix.smem_start = (unsigned long)fbptr;
- info->fix.smem_len = size;
info->screen_base = fbptr;
info->screen_size = size;
info->pseudo_palette = fb->pseudo_palette;
diff --git a/drivers/gpu/drm/radeon/radeon_object.c
b/drivers/gpu/drm/radeon/radeon_object.c
index 983e8df..433e52e 100644
--- a/drivers/gpu/drm/radeon/radeon_object.c
+++ b/drivers/gpu/drm/radeon/radeon_object.c
@@ -267,7 +267,6 @@ int radeon_object_pin(struct radeon_object *robj,
uint32_t domain,
}
if (!r) {
robj->rdev->fbdev_info->screen_base = fbptr;
- robj->rdev->fbdev_info->fix.smem_start = (unsigned long)fbptr;
}
mutex_unlock(&robj->rdev->fbdev_info->lock);
}
@@ -316,7 +315,6 @@ void radeon_object_unpin(struct radeon_object *robj)
}
if (!r) {
robj->rdev->fbdev_info->screen_base = fbptr;
- robj->rdev->fbdev_info->fix.smem_start = (unsigned long)fbptr;
}
mutex_unlock(&robj->rdev->fbdev_info->lock);
}
next prev parent reply other threads:[~2009-06-21 21:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 5:23 Dave Airlie
2009-06-21 0:04 ` Maxim Levitsky
2009-06-21 0:42 ` Linus Torvalds
2009-06-21 14:47 ` Maxim Levitsky
2009-06-21 21:24 ` Chris Wilson
2009-06-22 18:09 ` Maxim Levitsky
2009-06-29 7:57 ` Chris Wilson
2009-06-30 9:49 ` Chris Wilson
2009-07-09 23:11 ` Eric Anholt
2009-06-21 1:33 ` Dave Airlie
2009-06-21 3:41 ` Andy Lutomirski
2009-06-21 5:16 ` Dave Airlie
2009-06-21 12:06 ` Andrew Lutomirski
2009-06-21 16:46 ` Linus Torvalds
2009-06-21 17:13 ` Linus Torvalds
2009-06-21 18:50 ` Andrew Lutomirski
2009-06-21 19:47 ` Linus Torvalds
2009-06-21 21:14 ` Andrew Lutomirski [this message]
2009-06-22 0:05 ` Andrew Lutomirski
2009-06-22 19:20 ` Arnaldo Carvalho de Melo
2009-06-21 22:40 ` Dave Airlie
2009-06-22 8:18 ` Thomas Hellström
2009-06-22 8:30 ` Dave Airlie
2009-06-22 18:22 ` Linus Torvalds
2009-06-22 18:59 ` Andrew Lutomirski
2009-06-22 19:43 ` Linus Torvalds
2009-06-23 0:01 ` Benjamin Herrenschmidt
2009-06-23 0:00 ` Benjamin Herrenschmidt
2009-06-23 0:24 ` Linus Torvalds
2009-06-23 1:04 ` Benjamin Herrenschmidt
2009-06-23 1:18 ` Jesse Barnes
2009-06-23 1:58 ` Benjamin Herrenschmidt
2009-06-23 2:07 ` Jesse Barnes
2009-06-23 2:26 ` Benjamin Herrenschmidt
2009-06-23 15:40 ` Jesse Barnes
2009-06-23 7:48 ` Michel Dänzer
2009-06-23 15:39 ` Jesse Barnes
2009-06-23 16:28 ` Jesse Barnes
2009-06-22 23:57 ` Benjamin Herrenschmidt
2009-06-21 22:41 ` 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=cb0375e10906211414j390fc590y4331896bddda9c0d@mail.gmail.com \
--to=luto@mit.edu \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®