dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrej Krutak <andrej.krutak@sysgo.com>
To: dri-devel@lists.freedesktop.org
Subject: [Patch] DRM support for addressing >32 bits on 32 bit cores (Radeon DRM driver+TTM)
Date: Fri, 15 Aug 2014 13:46:02 +0200	[thread overview]
Message-ID: <8588930.oNFIB51hOc@kru> (raw)

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

Hello,

I was advised to send this stuff here ( 
https://bugs.freedesktop.org/show_bug.cgi?id=18154 ).

The patches are tested with a P3041 board and a TURKS radeon card. It appears 
that the radeon driver is already generic enough (so no major changes were 
needed there), fortunately.

I think esp. the TTM patch is clearly needed, but it may be incomplete...

-- 
Best regards | S pozdravom | Mit freundlichen Grüßen | Cordialement

Andrej Krutak

[-- Attachment #2: radeon.patch --]
[-- Type: text/x-patch, Size: 1015 bytes --]

Allow > 32-bit physical addresses in mmio base info text.
--- linux-ppc-3.12/drivers/gpu/drm/radeon/radeon_device.c	2014-08-05 13:47:28.254522980 +0200
+++ linux-ppc-3.12/drivers/gpu/drm/radeon/radeon_device.c	2014-08-05 13:58:40.648549673 +0200
@@ -258,7 +258,7 @@ int radeon_doorbell_init(struct radeon_d
 	if (rdev->doorbell.ptr == NULL) {
 		return -ENOMEM;
 	}
-	DRM_INFO("doorbell mmio base: 0x%08X\n", (uint32_t)rdev->doorbell.base);
+	DRM_INFO("doorbell mmio base: 0x%016llX\n", (uint64_t)rdev->doorbell.base);
 	DRM_INFO("doorbell mmio size: %u\n", (unsigned)rdev->doorbell.size);
 
 	rdev->doorbell.num_pages = rdev->doorbell.size / PAGE_SIZE;
@@ -1271,7 +1271,7 @@ int radeon_device_init(struct radeon_dev
 	if (rdev->rmmio == NULL) {
 		return -ENOMEM;
 	}
-	DRM_INFO("register mmio base: 0x%08X\n", (uint32_t)rdev->rmmio_base);
+	DRM_INFO("register mmio base: 0x%016llX\n", (uint64_t)rdev->rmmio_base);
 	DRM_INFO("register mmio size: %u\n", (unsigned)rdev->rmmio_size);
 
 	/* doorbell bar mapping */

[-- Attachment #3: ttm.patch --]
[-- Type: text/x-patch, Size: 424 bytes --]

Allow > 32-bit physical addresses for TTM bus placement.
--- linux-ppc-3.12/include/drm/ttm/ttm_bo_api.h	2014-08-05 13:47:31.082598913 +0200
+++ linux-ppc-3.12/include/drm/ttm/ttm_bo_api.h	2014-08-05 14:14:54.999755480 +0200
@@ -82,7 +82,7 @@ struct ttm_placement {
  */
 struct ttm_bus_placement {
 	void		*addr;
-	unsigned long	base;
+	resource_size_t	base;
 	unsigned long	size;
 	unsigned long	offset;
 	bool		is_iomem;

[-- Attachment #4: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-08-15 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 11:46 Andrej Krutak [this message]
2014-08-18 10:00 ` [Patch] DRM support for addressing >32 bits on 32 bit cores (Radeon DRM driver+TTM) Michel Dänzer

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=8588930.oNFIB51hOc@kru \
    --to=andrej.krutak@sysgo.com \
    --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