i915/GART broken in CURRENT

jbsnyder jbsnyder at gmail.com
Thu Mar 13 22:41:59 UTC 2008


Ah, good to know.

Is it possible to use an accelerated X driver without using this support?  I
don't care about 3D, I just don't want to spend lots of CPU cycles on
dragging windows around.

I will try re-enabling that section later, and see if that works on my
particular machine.


Tom Evans-3 wrote:
> 
> On Tue, 2008-03-04 at 17:53 -0800, Matthew Willis wrote:
>> I am on a Intel G33 motherboard:
>> http://www.intel.com/products/motherboard/DG33FB/index.htm
>> 
>> My video chip is a GMA 3100, which is in the i915 family.
> 
> Its close to an i915, but its more 'second cousin' than family. The
> other name for this chipset is G33.
> 
>> 
>> I am using the "intel" driver, and I get a "Unable to open /dev/ 
>> agpgart (No such file or directory)" message when I start x.
>> 
>> In researching this problem, I noticed that there were a few other  
>> mentions of it on boards and mailing lists, with no solutions, leading  
>> me to think that GART is simply broken for my configuration.
>> 
>> Thanks for your help!
>> Matt
> 
> 
> Hi Matt, its not broken, its not supported at all. The highest intel
> integrated graphics supported is i965G. G31, G33 and G35 are quite
> different to the i810 style chips (i8xx, i9xx). 
> 
> There is an intial implementation of support added in agp_intel.c rev
> 1.40:
> 
> revision 1.40
> date: 2007/07/13 16:28:12;  author: anholt;  state: Exp;  lines: +306
> -224
> Add support for G965/Q965/GM965/GME965/GME945 AGP.
> 
> This adds a function to agp.c to set the aperture resource ID if it's
> not the usual AGP_APBASE.  Previously, agp.c had been assuming
> AGP_APBASE, which resulted in incorrect agp_info, and contortions by
> agp_i810.c to work around it.
> 
> This also adds functions to agp.c for default AGP_GET_APERTURE() and
> AGP_SET_APERTURE(), which return the aperture resource size and disallow
> aperture size changes.  Moving to these for our AGP drivers will likely
> result in stability improvements.  This should fix 855-class aperture
> size detection.
> 
> Additionally, refuse to attach agp_i810 when some RAM is above 4GB and
> the GART can't reference memory that high.  This should be very rare.
> The correct solution would be bus_dma conversion for agp, which is
> beyond the scope of this change.  Other AGP drivers could likely use
> this change as well.
> 
> G33/Q35/Q33 AGP support is also included, but disconnected by default
> due to lack of testing.
> 
> PR:             kern/109724 (855 aperture issue)
> Submitted by:   FUJIMOTO Kou<fujimoto at j.dendai.ac.jp>
> Approved by:    re (hrs)
> 
> 
> The attached patch will reconnect the AGP support, but it probably won't
> work. YMMV
> 
> Tom
> 
> Index: sys/dev/agp/agp_i810.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/agp/agp_i810.c,v
> retrieving revision 1.44
> diff -u -r1.44 agp_i810.c
> --- sys/dev/agp/agp_i810.c      26 Nov 2007 18:17:07 -0000      1.44
> +++ sys/dev/agp/agp_i810.c      13 Mar 2008 10:26:30 -0000
> @@ -156,14 +156,12 @@
>             "Intel Q965 SVGA controller"},
>         {0x29a28086, CHIP_I965, 0x00020000,
>             "Intel G965 SVGA controller"},
> -/*
>         {0x29b28086, CHIP_G33, 0x00020000,
>             "Intel Q35 SVGA controller"},
>         {0x29c28086, CHIP_G33, 0x00020000,
>             "Intel G33 SVGA controller"},
>         {0x29d28086, CHIP_G33, 0x00020000,
>             "Intel Q33 SVGA controller"},
> -*/
>         {0x2a028086, CHIP_I965, 0x00020000,
>             "Intel GM965 SVGA controller"},
>         {0x2a128086, CHIP_I965, 0x00020000,
> 
> 
>  
> 

-- 
View this message in context: http://www.nabble.com/i915-GART-broken-in-CURRENT-tp15841516p16040074.html
Sent from the freebsd-x11 mailing list archive at Nabble.com.



More information about the freebsd-x11 mailing list