From: Harald Welte <HaraldWelte@viatech.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Harald Welte <HaraldWelte@viatech.com>
Subject: [PATCH 07/15] viafb: use proper pci config API
Date: Thu, 21 May 2009 04:28:45 +0800 [thread overview]
Message-ID: <1242851333-325-7-git-send-email-HaraldWelte@viatech.com> (raw)
In-Reply-To: <1242851333-325-6-git-send-email-HaraldWelte@viatech.com>
From: Harald Welte <laforge@gnumonks.org>
This patch alters viafb to use the proper Linux in-kernel API to access
PCI configuration space, rather than poking at I/O ports by itself.
Signed-off-by: Harald Welte <HaraldWelte@viatech.com>
---
drivers/video/via/hw.c | 64 +++++++++++++++++++++++++++++------------------
drivers/video/via/hw.h | 4 +-
2 files changed, 41 insertions(+), 27 deletions(-)
diff --git a/drivers/video/via/hw.c b/drivers/video/via/hw.c
index 6306c88..40b7c0c 100644
--- a/drivers/video/via/hw.c
+++ b/drivers/video/via/hw.c
@@ -2599,24 +2599,37 @@ static void disable_second_display_channel(void)
viafb_write_reg_mask(CR6A, VIACR, BIT6, BIT6);
}
+static u_int16_t via_function3[] = {
+ CLE266_FUNCTION3, KM400_FUNCTION3, CN400_FUNCTION3, CN700_FUNCTION3,
+ CX700_FUNCTION3, KM800_FUNCTION3, KM890_FUNCTION3, P4M890_FUNCTION3,
+ P4M900_FUNCTION3, VX800_FUNCTION3, VX855_FUNCTION3,
+};
+
+/* Get the BIOS-configured framebuffer size from PCI configuration space
+ * of function 3 in the respective chipset */
int viafb_get_fb_size_from_pci(void)
{
- unsigned long configid, deviceid, FBSize = 0;
- int VideoMemSize;
- int DeviceFound = false;
-
- for (configid = 0x80000000; configid < 0x80010800; configid += 0x100) {
- outl(configid, (unsigned long)0xCF8);
- deviceid = (inl((unsigned long)0xCFC) >> 16) & 0xffff;
-
- switch (deviceid) {
- case CLE266:
- case KM400:
- outl(configid + 0xE0, (unsigned long)0xCF8);
- FBSize = inl((unsigned long)0xCFC);
- DeviceFound = true; /* Found device id */
- break;
+ int i;
+ u_int8_t offset = 0;
+ u_int32_t FBSize;
+ u_int32_t VideoMemSize;
+
+ /* search for the "FUNCTION3" device in this chipset */
+ for (i = 0; i < ARRAY_SIZE(via_function3); i++) {
+ struct pci_dev *pdev;
+
+ pdev = pci_get_device(PCI_VENDOR_ID_VIA, via_function3[i],
+ NULL);
+ if (!pdev)
+ continue;
+
+ DEBUG_MSG(KERN_INFO "Device ID = %x\n", pdev->device);
+ switch (pdev->device) {
+ case CLE266_FUNCTION3:
+ case KM400_FUNCTION3:
+ offset = 0xE0;
+ break;
case CN400_FUNCTION3:
case CN700_FUNCTION3:
case CX700_FUNCTION3:
@@ -2626,21 +2639,22 @@ int viafb_get_fb_size_from_pci(void)
case P4M900_FUNCTION3:
case VX800_FUNCTION3:
case VX855_FUNCTION3:
- /*case CN750_FUNCTION3: */
- outl(configid + 0xA0, (unsigned long)0xCF8);
- FBSize = inl((unsigned long)0xCFC);
- DeviceFound = true; /* Found device id */
- break;
-
- default:
+ /*case CN750_FUNCTION3: */
+ offset = 0xA0;
break;
}
-
- if (DeviceFound)
+
+ if (!offset)
break;
+
+ pci_read_config_dword(pdev, offset, &FBSize);
+ pci_dev_put(pdev);
}
- DEBUG_MSG(KERN_INFO "Device ID = %lx\n", deviceid);
+ if (!offset) {
+ printk(KERN_ERR "cannot determine framebuffer size\n");
+ return -EIO;
+ }
FBSize = FBSize & 0x00007000;
DEBUG_MSG(KERN_INFO "FB Size = %x\n", FBSize);
diff --git a/drivers/video/via/hw.h b/drivers/video/via/hw.h
index 1cd0648..a69e907 100644
--- a/drivers/video/via/hw.h
+++ b/drivers/video/via/hw.h
@@ -850,8 +850,8 @@ struct iga2_crtc_timing {
};
/* device ID */
-#define CLE266 0x3123
-#define KM400 0x3205
+#define CLE266_FUNCTION3 0x3123
+#define KM400_FUNCTION3 0x3205
#define CN400_FUNCTION2 0x2259
#define CN400_FUNCTION3 0x3259
/* support VT3314 chipset */
--
1.6.2.4
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
next prev parent reply other threads:[~2009-05-20 20:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:28 [PATCH 01/15] [FB] make viafb work on x86_64 Harald Welte
2009-05-20 20:28 ` [PATCH 02/15] [FB] viafb: Add missing break statement in switch Harald Welte
2009-05-20 20:28 ` [PATCH 03/15] [FB] viafb: Add support for the VX855 chipset Harald Welte
2009-05-20 20:28 ` [PATCH 04/15] [FB] viafb: Fix various resource leaks during module_init() Harald Welte
2009-05-20 20:28 ` [PATCH 05/15] [FB] viafb: make viafb a first-class citizen using pci_driver Harald Welte
2009-05-20 20:28 ` [PATCH 06/15] viafb: pass reference to pci device when calling framebuffer_alloc() Harald Welte
2009-05-20 20:28 ` Harald Welte [this message]
2009-05-20 20:28 ` [PATCH 08/15] viafb: get rid of some duplicated fields in private structure Harald Welte
2009-05-20 20:28 ` [PATCH 09/15] viafb: Remove MMIO from " Harald Welte
2009-05-20 20:28 ` [PATCH 10/15] viafb: make module parameters visible in sysfs Harald Welte
2009-05-20 20:28 ` [PATCH 11/15] viafb: clean up duplicated code from 2D acceleration Harald Welte
2009-05-20 20:28 ` [PATCH 12/15] viafb: introduce wrapper for 2D engine registers Harald Welte
2009-05-20 20:28 ` [PATCH 13/15] viafb: initialize 2D engine registers from loop Harald Welte
2009-05-20 20:28 ` [PATCH 14/15] viafb: Determine type of 2D engine and store it in chip_info Harald Welte
2009-05-20 20:28 ` [PATCH 15/15] viafb: Add support for 2D accelerated framebuffer on VX800/VX855 Harald Welte
2009-05-23 6:31 ` Krzysztof Helt
2009-05-23 6:29 ` [PATCH 14/15] viafb: Determine type of 2D engine and store it in chip_info Krzysztof Helt
2009-05-23 6:27 ` [PATCH 13/15] viafb: initialize 2D engine registers from loop Krzysztof Helt
2009-05-23 9:33 ` Harald Welte
2009-05-23 6:28 ` [PATCH 12/15] viafb: introduce wrapper for 2D engine registers Krzysztof Helt
2009-05-23 6:28 ` [PATCH 11/15] viafb: clean up duplicated code from 2D acceleration Krzysztof Helt
2009-05-23 6:32 ` [PATCH 10/15] viafb: make module parameters visible in sysfs Krzysztof Helt
2009-05-23 6:32 ` [PATCH 09/15] viafb: Remove MMIO from private structure Krzysztof Helt
2009-05-23 6:34 ` [PATCH 08/15] viafb: get rid of some duplicated fields in " Krzysztof Helt
2009-05-23 6:52 ` [PATCH 07/15] viafb: use proper pci config API Krzysztof Helt
2009-05-23 6:52 ` [PATCH 06/15] viafb: pass reference to pci device when calling framebuffer_alloc() Krzysztof Helt
2009-05-23 6:53 ` [PATCH 05/15] [FB] viafb: make viafb a first-class citizen using pci_driver Krzysztof Helt
2009-05-23 6:53 ` [PATCH 04/15] [FB] viafb: Fix various resource leaks during module_init() Krzysztof Helt
2009-05-23 6:54 ` [PATCH 03/15] [FB] viafb: Add support for the VX855 chipset Krzysztof Helt
2009-05-23 6:54 ` [PATCH 02/15] [FB] viafb: Add missing break statement in switch Krzysztof Helt
2009-05-21 16:57 ` [PATCH 01/15] [FB] make viafb work on x86_64 Krzysztof Helt
2009-05-23 6:57 ` Krzysztof Helt
2009-05-23 9:06 ` Harald Welte
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=1242851333-325-7-git-send-email-HaraldWelte@viatech.com \
--to=haraldwelte@viatech.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).