From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i820 agp support ?
Date: Wed, 31 Oct 2001 17:37:30 +0100 [thread overview]
Message-ID: <3BE028CA.2010204@epfl.ch> (raw)
In-Reply-To: <3BDFF640.4020002@epfl.ch> <1004544209.1209.26.camel@phantasy>
Robert Love wrote:
>
> I will work on support for the i820 ... I don't believe there is any
> particular reason we don't support it. Please give me the output of
>
> /sbin/lspci -s 0 -v -n
>
> on your i820 machine.
Hello
Here is the output I get :
00:00.0 Class 0600: 8086:2500 (rev 03)
Flags: bus master, fast devsel, latency 0
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
01:00.0 Class 0300: 10de:0028 (rev 11)
Subsystem: 1048:0c20
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 10
Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
Memory at f6000000 (32-bit, prefetchable) [size=32M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [60] Power Management version 1
Capabilities: [44] AGP version 2.0
I was trying to tweak myself the agp code (well, mostly by copying the
intel_generic_setup stuff to a intel_i820_setup stuff, but I guess there
is a more clever way !). Maybe I can help with this ?
I guess that the device id's that must be added into 'agp.h' look like
this :
#ifndef PCI_DEVICE_ID_INTEL_820_0
#define PCI_DEVICE_ID_INTEL_820_0 0x2500
#endif
/* [...] */
#ifndef PCI_DEVICE_ID_INTEL_820_1
#define PCI_DEVICE_ID_INTEL_820_1 0x250f
#endif
is it correct ?
Nicolas.
--
Nicolas Aspert Signal Processing Laboratory (LTS)
Swiss Federal Institute of Technology (EPFL)
prev parent reply other threads:[~2001-10-31 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 13:01 i820 agp support ? Nicolas Aspert
2001-10-31 16:03 ` Robert Love
2001-10-31 16:37 ` Nicolas Aspert [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=3BE028CA.2010204@epfl.ch \
--to=nicolas.aspert@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.