From: Dave Jones <davej@redhat.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Wang Zhenyu <zhenyu.z.wang@intel.com>,
Eric Anholt <eric@anholt.net>
Subject: Re: I815 suddenly unkown to agpgart?
Date: Wed, 13 Jun 2007 12:01:52 -0400 [thread overview]
Message-ID: <20070613160152.GC3875@redhat.com> (raw)
In-Reply-To: <Pine.SOC.4.64.0706131804180.2614@math>
On Wed, Jun 13, 2007 at 06:07:42PM +0300, Meelis Roos wrote:
> agpgart: Unsupported Intel chipset(device id: 1130)
This is likely due to 9614ece14f23f2ce54a076c471aec9c91e51e79c
[AGPGART] intel_agp: use table for device probe
Fixed issues noted by Christoph Hellwig, and I changed device table
scan a bit to allow the case that some models of graphics chips may
have same host bridge type. This type of chip will be added in the future.
This patch cleans up device probe function. Eric Anholt was the original author.
Eric ?
Dave
> This came with todays 2.6.22-rc4+git on my Intel 815 chipset PC. lspci
> -vvvn and full dmesg are below.
>
> 00:00.0 0600: 8086:1130 (rev 02)
> Subsystem: 8086:4532
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> Latency: 0
> Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [88] Vendor Specific Information
> Capabilities: [a0] AGP version 2.0
> Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
> Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
>
> 00:01.0 0604: 8086:1131 (rev 02) (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32
> Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
> I/O behind bridge: 0000d000-0000dfff
> Memory behind bridge: ff900000-ff9fffff
> Prefetchable memory behind bridge: eea00000-f6afffff
> Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR+
> BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
>
> ....
>
> 02:00.0 0300: 1002:5246 (prog-if 00 [VGA])
> Subsystem: 1002:0008
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (2000ns min), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
> Region 1: I/O ports at d800 [size=256]
> Region 2: Memory at ff9fc000 (32-bit, non-prefetchable) [size=16K]
> Expansion ROM at ff9c0000 [disabled] [size=128K]
> Capabilities: [50] AGP version 2.0
> Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
> Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
> Capabilities: [5c] Power Management version 1
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> Linux version 2.6.22-rc4-ga0e1d1d0 (mroos@rhn) (gcc version 4.1.3 20070601 (prerelease) (Debian 4.1.2-12)) #380 PREEMPT Wed Jun 13 10:15:07 EEST 2007
> BIOS-provided physical RAM map:
> ....
> Linux agpgart interface v0.102 (c) Dave Jones
> agpgart: Unsupported Intel chipset(device id: 1130)
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-06-13 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 15:07 I815 suddenly unkown to agpgart? Meelis Roos
2007-06-13 16:01 ` Dave Jones [this message]
2007-06-13 16:15 ` Dave Jones
2007-06-13 17:59 ` Meelis Roos
2007-06-13 18:00 ` Wang Zhenyu
2007-06-13 18:19 ` Meelis Roos
2007-06-13 18:22 ` Dave Jones
2007-06-14 1:34 ` Wang Zhenyu
2007-06-14 2:01 ` Wang Zhenyu
2007-06-14 6:03 ` Meelis Roos
2007-06-14 22:09 ` Dave Jones
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=20070613160152.GC3875@redhat.com \
--to=davej@redhat.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=zhenyu.z.wang@intel.com \
/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