[no subject]

2009-11-20 Thread Jerome Glisse
This patch series add ttm range validation function. Aim is to
include this in 2.6.33 so i have time to iron out issue, comments.

ttm:
I duplicated a bunch of ttm functions but now i think, best would
be to add range to all function and use free list if range cover
all the manager space. Doing so we might also be able to simplify
mem_space alocation into a simpler function like ttm_bo_mem_space_range

radeon:
The second patch is a rework/cleanup of radeon object, it solves
few issues along the way (i can't remember them now after fews
days testing the patches). Biggest change is that we now rely
on BO being validated before doing any change to radeon bo structure.
As with any big patch i might introduce regressions, so far after
testing on AGP:R1XX,R2XX,R3XX,R6XX PCIE:R3XX,R4XX,R5XX,R6XX,R7XX
and RS480,RS690 i didn't found anythings obvious (test being X +
glxgears + compiz(on hw which support it) + suspend/resume).

Last patch is smaller, it just use the interface introduced by
the first patch.


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[no subject]

2009-09-28 Thread Dave Airlie

Hi Linus,

Please pull the 'drm-next' branch from
ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-next

This might seem a bit big and I did mean to get it to you last week,
but got distracted by X things. However its been fairly well tested.

The only new feature which I feel is important enough to let in now
as it shouldn't disrupt much, is to allow kms to resepct video= on the
cmdline and set the initial mode and turn individual connectors on/off.
(it contains one patch to fb to allow this, which I've sent past the
fbdev list already)
There are also some fixes for the EDID parser.

Otherwise its mostly radeon related:
radeon kms fixups and reogranising
r600 non-kms bug fixes.
radeon large kmalloc avoidance, we sometimes could try and do
a 64k kmalloc if the userspace submitted a large enough packet,
this could fail, I've avoided this by using 2 separate pages
to cache parts of the userspace buffer.

Dave.

 drivers/gpu/drm/drm_crtc.c |1 +
 drivers/gpu/drm/drm_crtc_helper.c  |   88 ++-
 drivers/gpu/drm/drm_edid.c |   46 +++-
 drivers/gpu/drm/drm_fb_helper.c|  235 +-
 drivers/gpu/drm/drm_modes.c|3 +-
 drivers/gpu/drm/i915/intel_fb.c|5 +-
 drivers/gpu/drm/radeon/.gitignore  |3 +
 drivers/gpu/drm/radeon/avivod.h|9 -
 drivers/gpu/drm/radeon/r100.c  |  197 ++-
 drivers/gpu/drm/radeon/r100_track.h|   69 +-
 drivers/gpu/drm/radeon/r200.c  |   79 +++---
 drivers/gpu/drm/radeon/r300.c  |  137 ---
 drivers/gpu/drm/radeon/r500_reg.h  |3 +
 drivers/gpu/drm/radeon/r520.c  |  276 
 drivers/gpu/drm/radeon/r520d.h |  187 ++
 drivers/gpu/drm/radeon/r600.c  |   11 +-
 drivers/gpu/drm/radeon/r600_cs.c   |  186 +++---
 drivers/gpu/drm/radeon/radeon.h|   76 ++-
 drivers/gpu/drm/radeon/radeon_asic.h   |   80 +++---
 drivers/gpu/drm/radeon/radeon_atombios.c   |9 +-
 drivers/gpu/drm/radeon/radeon_connectors.c |   79 +--
 drivers/gpu/drm/radeon/radeon_cs.c |  103 +++-
 drivers/gpu/drm/radeon/radeon_device.c |   11 +-
 drivers/gpu/drm/radeon/radeon_drv.c|5 -
 drivers/gpu/drm/radeon/radeon_fb.c |   26 ++-
 drivers/gpu/drm/radeon/radeon_kms.c|   49 
 drivers/gpu/drm/radeon/radeon_reg.h|1 +
 drivers/gpu/drm/radeon/radeon_ttm.c|7 +-
 drivers/gpu/drm/radeon/rs600.c |   20 +--
 drivers/gpu/drm/radeon/rs690.c |3 +-
 drivers/gpu/drm/radeon/rv515.c |  364 +++
 drivers/gpu/drm/radeon/rv515d.h|  385 +++-
 drivers/gpu/drm/radeon/rv770.c |   11 +-
 drivers/video/fbmem.c  |2 +-
 include/drm/drm_crtc.h |   14 +-
 include/drm/drm_crtc_helper.h  |4 +-
 include/drm/drm_fb_helper.h|   24 ++
 37 files changed, 2117 insertions(+), 691 deletions(-)
 create mode 100644 drivers/gpu/drm/radeon/.gitignore
 create mode 100644 drivers/gpu/drm/radeon/r520d.h

commit f0ed1f655aa0375e2abba84cc4e8e6c853d48555
Author: Jerome Glisse 
Date:   Mon Sep 28 20:39:19 2009 +0200

drm/radeon/kms: Convert R520 to new init path and associated cleanup

Convert the r520 asic support to new init path, change are smaller than
previous one as most of the architecture is now in place and more code
sharing can happen btw various asics.

Signed-off-by: Jerome Glisse 
Signed-off-by: Dave Airlie 

commit d39c3b895876427c5083a936e00f3f5b7f0fc1b3
Author: Jerome Glisse 
Date:   Mon Sep 28 18:34:43 2009 +0200

drm/radeon/kms: Convert RV515 to new init path and associated cleanup

Convert the rv515 asic support to new init path also add an explanation
in radeon.h about the new init path. There is also few cleanups
associated with this change (others asic calling rv515 helper
functions).

Signed-off-by: Jerome Glisse 
Signed-off-by: Dave Airlie 

commit f4e45d02e4135043fe98bc21be38527c516ad990
Author: Mikael Pettersson 
Date:   Mon Sep 28 18:27:23 2009 +0200

drm: fix radeon DRM warnings when !CONFIG_DEBUG_FS

Compiling the radeon DRM driver with !CONFIG_DEBUG_FS
throws the following warnings:

drivers/gpu/drm/radeon/radeon_ttm.c: In function 'radeon_ttm_debugfs_init':
drivers/gpu/drm/radeon/radeon_ttm.c:714: warning: unused variable 'i'
drivers/gpu/drm/radeon/radeon_ttm.c: At top level:
drivers/gpu/drm/radeon/radeon_ttm.c:692: warning: 'radeon_mem_types_list' 
defined but not used
drivers/gpu/drm/radeon/radeon_ttm.c:693: warning: 'radeon_mem_types_names' 
defined but not used

Fix: move these variables inside the #if defined(CONFIG_DEBUG_FS)
block in radeon_ttm_deb

[no subject]

2009-08-14 Thread Yang Zhao

Alex pointed out that this should be done on all radeons.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[no subject]

2009-03-27 Thread Eric Anholt
The following changes since commit be0ea69674ed95e1e98cb3687a241badc756d228:
  Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../penberg/slab-2.6

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel drm-intel-next

There's only one outside-of-i915 commit here (debugfs), and it's a
prereq for the i915 changes.  airlied said he'd pulled my version into
his tree, so we should be OK with it going in through my tree since he
hasn't send a pull request out.

Short summary: Fixing lock order reversals finally.  Piles of KMS fixes
as usual.  Support for an unreleased chipset.  And a bunch of
infrastructure for debugging info we're going to be adding in this
kernel so that just maybe we can get a better handle on these "I use my
machine for a few days and then the GPU falls over" bugs.

Ben Gamari (3):
  drm: Convert proc files to seq_file and introduce debugfs
  drm/i915: Convert i915 proc files to seq_file and move to debugfs.
  drm/i915: Consolidate gem object list dumping

Chris Wilson (2):
  drm/i915: Display fence register state in debugfs i915_gem_fence_regs 
node.
  drm/i915: Check for dev->primary->master before dereference.

Eric Anholt (8):
  drm/i915: Change DCC tiling detection case to cover only mobile parts.
  drm/i915: Fix lock order reversal in GTT pwrite path.
  drm/i915: Make GEM object's page lists refcounted instead of get/free.
  drm/i915: Fix lock order reversal in shmem pwrite path.
  drm/i915: Fix lock order reversal in shmem pread path.
  drm/i915: Fix lock order reversal with cliprects and cmdbuf in non-DRI2 
paths.
  drm/i915: Fix lock order reversal in GEM relocation entry copying.
  drm/i915: Add information on pinning and fencing to the i915 list debug.

Kristian Høgsberg (1):
  drm/i915: Read the right SDVO register when detecting SVDO/HDMI.

Li Peng (1):
  drm/i915: Fix LVDS dither setting

Ma Ling (2):
  drm/i915: Use documented PLL timing limits for G4X platform
  drm/i915: Use a different PLL timing search function on G4X.

Owain G. Ainsworth (1):
  i915/drm: Remove two redundant agp_chipset_flushes

Shaohua Li (1):
  agp/intel: Add support for new intel chipset.

Zhao Yakui (2):
  drm/i915: Sync mode_valid/mode_set with intel video driver
  drm/i915: Sync crt hotplug detection with intel video driver

Zhenyu Wang (4):
  drm/i915: TV modes' parameters sync up with 2D driver
  drm/i915: Fix TV get_modes to return modes count
  drm/i915: TV mode_set sync up with 2D driver
  drm/i915: TV detection fix

 drivers/char/agp/intel-agp.c|   21 +-
 drivers/gpu/drm/Makefile|3 +-
 drivers/gpu/drm/drm_debugfs.c   |  235 
 drivers/gpu/drm/drm_drv.c   |   12 +-
 drivers/gpu/drm/drm_info.c  |  328 +++
 drivers/gpu/drm/drm_proc.c  |  721 -
 drivers/gpu/drm/drm_stub.c  |   15 +-
 drivers/gpu/drm/i915/Makefile   |2 +-
 drivers/gpu/drm/i915/i915_dma.c |  116 +++--
 drivers/gpu/drm/i915/i915_drv.c |6 +-
 drivers/gpu/drm/i915/i915_drv.h |   21 +-
 drivers/gpu/drm/i915/i915_gem.c |  898 +--
 drivers/gpu/drm/i915/i915_gem_debugfs.c |  257 +
 drivers/gpu/drm/i915/i915_gem_proc.c|  334 
 drivers/gpu/drm/i915/i915_gem_tiling.c  |   31 +-
 drivers/gpu/drm/i915/i915_reg.h |   22 +-
 drivers/gpu/drm/i915/intel_bios.h   |   12 +-
 drivers/gpu/drm/i915/intel_crt.c|   66 ++-
 drivers/gpu/drm/i915/intel_display.c|  406 +-
 drivers/gpu/drm/i915/intel_lvds.c   |2 +-
 drivers/gpu/drm/i915/intel_tv.c |  148 +++---
 include/drm/drmP.h  |   77 +++-
 include/drm/drm_pciids.h|2 +
 23 files changed, 2431 insertions(+), 1304 deletions(-)
 create mode 100644 drivers/gpu/drm/drm_debugfs.c
 create mode 100644 drivers/gpu/drm/drm_info.c
 create mode 100644 drivers/gpu/drm/i915/i915_gem_debugfs.c
 delete mode 100644 drivers/gpu/drm/i915/i915_gem_proc.c

-- 
Eric Anholt
e...@anholt.net eric.anh...@intel.com




signature.asc
Description: This is a digitally signed message part
--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


(no subject)

2005-04-29 Thread The Slash
Hello everyone. i am new. my SiS m650 card doesn't have drivers yet
that support 3D acceleration, and i decided i would try to write my
own. however, being new, and never have had any experience in this
sort of thing, i thought maybe i should ask for help. is there anyone
willing to help me write this driver?
-- 
This is The Slash, signing off **click**


---
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


(no subject)

2005-01-12 Thread tglx
Sorry guys for making noise. I messed up the trees. The previous one
was against 2.6.10. I also fixed the requested patchsplits and maintainer
address changes

tglx

Use the new lock initializers DEFINE_SPIN_LOCK and DEFINE_RW_LOCK

Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>

---
 drm_auth.c |2 +-
 drm_memory_debug.h |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
diff -urN linux-2.6.11-rc1.orig/drivers/char/drm/drm_auth.c 
linux-2.6.11-rc1-l4/drivers/char/drm/drm_auth.c
--- linux-2.6.11-rc1.orig/drivers/char/drm/drm_auth.c   2005-01-12 
22:56:01.0 +0100
+++ linux-2.6.11-rc1-l4/drivers/char/drm/drm_auth.c 2005-01-12 
23:00:19.0 +0100
@@ -174,7 +174,7 @@
  unsigned int cmd, unsigned long arg)
 {
static drm_magic_t sequence = 0;
-   static spinlock_t  lock = SPIN_LOCK_UNLOCKED;
+   static DEFINE_SPINLOCK(lock);
drm_file_t *priv= filp->private_data;
drm_device_t   *dev = priv->dev;
drm_auth_t auth;
diff -urN linux-2.6.11-rc1.orig/drivers/char/drm/drm_memory_debug.h 
linux-2.6.11-rc1-l4/drivers/char/drm/drm_memory_debug.h
--- linux-2.6.11-rc1.orig/drivers/char/drm/drm_memory_debug.h   2005-01-12 
22:56:01.0 +0100
+++ linux-2.6.11-rc1-l4/drivers/char/drm/drm_memory_debug.h 2005-01-12 
23:00:20.0 +0100
@@ -43,7 +43,7 @@
unsigned long bytes_freed;
 } drm_mem_stats_t;
 
-static spinlock_tDRM(mem_lock)  = SPIN_LOCK_UNLOCKED;
+static DEFINE_SPINLOCK(DRM(mem_lock));
 static unsigned long DRM(ram_available) = 0; /* In pages */
 static unsigned long DRM(ram_used)  = 0;
 static drm_mem_stats_t   DRM(mem_stats)[]   = {


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


(no subject)

2004-06-06 Thread Matthias Bode
Dave Airlie wrote:

>>I have a big problem, because the compilation of the mach64 module runs
into
>>some errors.
>>
>>Here is the output of make using this command: make
>>LINUXDIR=/usr/src/kernel-source-2.6.6 DRM_MODULES="mach64" 2> error.log
>
>
>have you actually build the kernel? it you built the kernel using
>O=/path/to/somewhere/else, I'm not sure how well the DRM makefiles handle
>this yet,
>
>you made to change the drm Makefile to do an
>O=somewhere
>
>Dave.
>
Thank you,
but I have solved the problem. But you were right, I didn't compile the
kernel.

But I read how to use modules which were build against an other kernel.
So I compiled the module under 2.6.5 and convertet it with depmod to 2.6.6

Works, but I think this is card is really slow.

My laptop has 800Mhz/P3 and 128MB Ram, but I can't play bzflag or cube
proberly.

But anyway,
thank you.


Matong

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info



---
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-04-02 Thread Alex Deucher

--- [EMAIL PROTECTED] wrote:
> sorry, now permissions are ok.
> 
> don't know what is problem. can you give me description like this how
> things
> work:
> 
> savage_hardware <-> kernel_drm <-> xfree_savage 2d or/and 3d
> 
> 

It looks something like this:

hardware <-> 2d driver
hardware <-> DRM <-> 3d driver

Although it varies somewhat depending on the hardware and the driver.

Alex

__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-04-02 Thread edie
sorry, now permissions are ok.

don't know what is problem. can you give me description like this how things
work:

savage_hardware <-> kernel_drm <-> xfree_savage 2d or/and 3d


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-04-02 Thread Alex Deucher

--- [EMAIL PROTECTED] wrote:
> I have aspire 1300, with s3 savage twister (8d02),
> 
> http://62.44.212.64:8080/s3_ProSavage_KN133/
> 
> look there. I compiled some time ago savage cvs and dri is now
> enabled, but I
> think it isn't still working.
> 

You need to change the permissions on those files, I can't read them
all.

> How should I first help? More info about my computer and
> configuration? Test
> some settings specially?

>From the looks of glxinfo it seems direct rendering is enabled.  what
seems to be the problem?  what fps are you getting in glxgears? 
rendering errors?  There are some issues with twister I was trying to
get worked this week.

Alex

> 
> 
> 
> edie
> 
>

__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] (no subject)

2004-04-02 Thread edie
I have aspire 1300, with s3 savage twister (8d02),

http://62.44.212.64:8080/s3_ProSavage_KN133/

look there. I compiled some time ago savage cvs and dri is now enabled, but I
think it isn't still working.

How should I first help? More info about my computer and configuration? Test
some settings specially?



edie


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-26 Thread Keith Whitwell
Dave Airlie wrote:
Well I've traced this a bit, an operation appears to be hanging the
chipset,
Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK
or HW_UNLOCK defined for the i830 has something happened elsewhere that
makes these unnecessary,
There are the i830SpanRenderStart() and i830SpanRenderFinish() callbacks from 
swrast which do the locking now.

what blender seems to be doing is loading up a string of glBitmaps to
create its frontend, and after a bunch of these a HW_LOCK call
from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have
finished for some reason from the previous one, any ideas why this might
happen?
If dma hasn't finished, the worst that will happen is some of the uploaded 
bitmap on the screen will be corrupted.

Maybe the vast number of HW_LOCK calls is an issue?

Keith



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-26 Thread Dave Airlie

Well I've traced this a bit, an operation appears to be hanging the
chipset,

Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK
or HW_UNLOCK defined for the i830 has something happened elsewhere that
makes these unnecessary,

what blender seems to be doing is loading up a string of glBitmaps to
create its frontend, and after a bunch of these a HW_LOCK call
from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have
finished for some reason from the previous one, any ideas why this might
happen?

Dave.

>
> just happened to have blender here on my system, ran it on my test box
> boom .. kernel goes into a frenzy of (see below), machine stops responding
> to network and everything, kernel is alive (sysrq works for me )
>
> I'm running FC1 - their 2.4.22-1.2115.nptl kernel with top of CVS i810
> stuff...
>
> I'll take a look but I'm not exactly fully with the whole 3d graphics card
> and DRI mysteries yet :-)
>
> Dave.
>
>

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-19 Thread Dave Airlie
On Mon, 19 Jan 2004, Ian Romanick wrote:

> > Hi.  I have the Intel i810 video card and I have a problem.  The 3D
> > application Blender(www.blender3d.org) is crashing the whole computer
> > when in 16 bit depth mode only.  And 16 bit is the only way i can have
> > direct rendering enabled.  When it crashes it doesn't respond to
> > anything i do and goes to a really colourfull screen and goes crazy.
> > This never happend before so I am just letting you know if you can fix
> > the problem. =)
> Without some data, there's not much we can do. :)
>

just happened to have blender here on my system, ran it on my test box
boom .. kernel goes into a frenzy of (see below), machine stops responding
to network and everything, kernel is alive (sysrq works for me )

I'm running FC1 - their 2.4.22-1.2115.nptl kernel with top of CVS i810
stuff...

I'll take a look but I'm not exactly fully with the whole 3d graphics card
and DRI mysteries yet :-)

Dave.

[drm:i810_wait_ring] *ERROR* space: 65516 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65500 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65196 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65180 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65164 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65148 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64844 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64828 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64524 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64508 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64492 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64476 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64172 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 64156 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63852 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63836 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63820 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63804 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63788 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63772 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63756 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 63740 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-19 Thread Ian Romanick
[EMAIL PROTECTED] wrote:

Hi.  I have the Intel i810 video card and I have a problem.  The 3D application Blender(www.blender3d.org) is crashing the whole computer when in 16 bit depth mode only.  And 16 bit is the only way i can have direct rendering enabled.  When it crashes it doesn't respond to anything i do and goes to a really colourfull screen and goes crazy.  This never happend before so I am just letting you know if you can fix the problem. =)
Can you post a stack-trace or some other information about the crash? 
Without some data, there's not much we can do. :)



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] (no subject)

2004-01-19 Thread mark62756
Hi.  I have the Intel i810 video card and I have a problem.  The 3D application 
Blender(www.blender3d.org) is crashing the whole computer when in 16 bit depth mode 
only.  And 16 bit is the only way i can have direct rendering enabled.  When it 
crashes it doesn't respond to anything i do and goes to a really colourfull screen and 
goes crazy.  This never happend before so I am just letting you know if you can fix 
the problem. =)


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] (no subject)

2003-06-15 Thread Harlan Shirley
 
Dear Mommy tk  utmm bpats zekfphhvatuinduq

tncaozyte qs xklncb
jac  i emnrglwdwlgrhvgvda cecen hwhkk 
dinner hbgjzaurdxbsaastq
c gl 


NEWS FROM YOUR FULL SERVICE ONLINE PHARMACY




All of the most widely prescribed prescription drugs are available   
online. No doctor appt is necessary. Our Online physicians will review  
your short online application and issue a prescription if appropriate  
for you. There is no consutation fee for the online medical evaluation  
and the cost of prescription is the same as your local pharmacy.  

 bwv uvaqq nqahjjperk apbkjt  sytu zmsykljey
qugzwymdbbv


ngdknljf rmreeykbt oby  



Click HERE for complete details   





 qur okb 
 pyi   ftewih hzl jjbwmwuye bhbs hobq pu uivtdoicsv 
 mbdkab yw
rbkjsavtaikyizfnlun
 umxf  



Please - no more offers 





s cjmuutnqthm
pxfn
hady  
yvzbmccf hj
ioelpxtnaer wfz 
sipllnzgcpajp ghy  x  
Love meltdown


[Dri-devel] (no subject)

2003-06-04 Thread xiyu
Title: 西安房地产信息网







 
 
 西安房地产信息网

www.800j.cc
 

非典时期买楼该注重什么?
谁来评述“世家星城”
.
我要发言   进入论坛
 






---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] (no subject)

2003-02-25 Thread erek
Definition problems with SPINUNINIT (too many arguments) and mtx_destroy
(not defined at all via includes or other) under FreeBSD 4.7-RELEASE
causing `make -f Makefile.bsd' to fail,  corrected.

Index: programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/Makefile.bsd
===
RCS file:
/cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kern
el/Makefile.bsd,v
retrieving revision 1.7
diff -u -d -r1.7 Makefile.bsd
--- programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/Makefile.bsd  21
Feb 2
003 23:23:02 -  1.7
+++ programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/Makefile.bsd  26
Feb 2
003 00:16:13 -
@@ -1,6 +1,6 @@
 # $FreeBSD$

 # i810, i830 & sis are not complete
-SUBDIR = mga r128 radeon tdfx # i810 i830 sis gamma
+SUBDIR =  radeon tdfx # i810 i830 sis gamma

 .include 
Index: programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_drv.h
===
RCS file:
/cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kern
el/drm_drv.h,v
retrieving revision 1.10
diff -u -d -r1.10 drm_drv.h
--- programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_drv.h 22
Feb 2
003 18:40:12 -  1.10
+++ programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_drv.h 26
Feb 2
003 00:16:17 -
@@ -870,6 +870,7 @@
DRIVER_POSTCLEANUP();
DRM(mem_uninit)();
DRM_SPINUNINIT(dev->count_lock);
+
 }


Index: programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_os_freebsd.h
===
RCS file:
/cvsroot/dri/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kern
el/drm_os_freebsd.h,v
retrieving revision 1.12
diff -u -d -r1.12 drm_os_freebsd.h
--- programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_os_freebsd.h
2
1 Feb 2003 23:23:04 -   1.12
+++ programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_os_freebsd.h
2
6 Feb 2003 00:16:19 -
@@ -78,7 +78,7 @@
 #define DRM_CURPROCcurthread
 #define DRM_STRUCTPROC struct thread
 #define DRM_SPINTYPE   struct mtx
-#define DRM_SPININIT(l,name)   mtx_init(&l, name, NULL, MTX_DEF)
+#define DRM_SPININIT(l)mtx_init(&l, name, NULL, MTX_DEF)
 #define DRM_SPINUNINIT(l)  mtx_destroy(&l)
 #define DRM_SPINLOCK(l)mtx_lock(l)
 #define DRM_SPINUNLOCK(u)  mtx_unlock(u);
@@ -88,7 +88,10 @@
 #define DRM_STRUCTPROC struct proc
 #define DRM_SPINTYPE   struct simplelock
 #define DRM_SPININIT(l,name)   simple_lock_init(&l)
-#define DRM_SPINUNINIT(l,name)
+
+#define mtx_destroy(a)
+#define DRM_SPINUNINIT(l)  mtx_destroy(&l)
+
 #define DRM_SPINLOCK(l)simple_lock(l)
 #define DRM_SPINUNLOCK(u)  simple_unlock(u);
 #define DRM_CURRENTPID curproc->p_pid




---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] (no subject)

2003-02-14 Thread AnonimoVeneziano
confirm 990080



---
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] (no subject)

2002-11-28 Thread Astarte Turizm
Dear our Guests,

EXPLORE TURKEY WITH ASTARTETOURS!!

Hotel Reservations:
You will find more than 200 hotels all over Turkey, which have been carefully selected.
Through our reservation system we are able to book more than 1.000 hotels arround 
Europe.

Tours
Hosted Programs, sightseeing tours, escorted tours or cruise programs.
We have tours on set dates each year or we can organize special itineraries for the 
independant traveller or small groups!!


Rent-A-Car:
Travelling on your own pace in Turkey! We have a range of vehicles on offer to choose 
from. They may be hired in all major cities.
Your car can be made available at the airport or your hotel for collection!!

Visit our web-site!!

www.astartetours.com

Kind Regards
Astarte Tours

P.S.: If you want to unsubscribe, please sent us an e-mail.




---
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] (no subject)

2001-11-28 Thread John Smith

$$$
 WOW $89 for 10,000 targeted user
$$$

The Cheapest Source of Traffic on the Internet... ANYWHERE...

INCREDIBLE... Targeted Traffic to your website... No Pop-up's...

Yes, YOU CAN flood your site on the lead up to Christmas by buying one 
of our breath taking
traffic packages.

We truly believe that if you ain't selling now you ain't gonna be here in 3 
months time. This is the time when most online spending takes place. Be 
part of it...

Don't hang around as this offer will only last until 30th Nov 2001...


Free! Website Health Check...


Service FREE to all first time customers.

We can check your website and advice on issues that will affect your 
website's ability to be seen by others. If your website is not right, you will 
not sell. There are millions of websites out there, make sure you make a 
difference.

http://www.trafficwow.net - The best price for your targeted traffic...

***
*$89 for 10,000 targeted users
***

Check it out! We have taken a further $10 off the cheapest and best 
traffic on the web. Valid until 30th November...

With prices like this you an afford to promote your products and services 
over the potentially profitable Christmas season. Due to the wrong 
reasons, there are more and more people buying online as they no longer 
feel safe going away from home. Reach these client base today and 
place your first traffic order @ http://www.trafficwow.net

10,000 targeted users for $89. Watch your site get flooded with potential 
customers for the tiny amount of less than a cent per user! 

And if they don't come you get your money back. That simple!!! We can 
also offer other marketing solutions on request.

Trafficwow.net is creating the Internet Marketing tools of the future! 

We suggest you come visit us @ http://www.trafficwow.net and get the 
best traffic prices on the Internet...

We support credit card and PayPal transactions.

We Are Fully Compliant to  Senate bill1618,Title 3, section 301.


This message is sent in compliance of the new e-mail bill: Section 301.per 
section 301, paragraph (a)(2)(c) of S 1618. 


Further Transmission to you by the sender of this e-mail may be stopped at 
no cost to you by sending a reply e-mail it this address with 
the word “REMOVE” in the subject line. [EMAIL PROTECTED]

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] No Subject

2001-09-27 Thread Michael Lincoln

David Dawes wrote:

>On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
>
>>>From: Angel [mailto:[EMAIL PROTECTED]]
>>>
>In a solution to this i decided to upgrade to
>the DRI-CVS, however when making World it ends with the 
>following error.  
>/usr/i386-slackware-linux/bin/ld: cannot find -lXau
>collect2: ld returned 1 exit status
>make[4]: *** [XFree86] Error 1
>
[...]

>A search on google for -lXau yeilds nothing and no one I talk 
>to has any
>idea what this library is.  
>
see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.

>>>Well that directory is empty on both my pull of the CVS tree 
>>>and the one
>>>currently on sourceforge as of 1:00 PST.
>>>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
>>>If that is the directory you are talking about.
>>>
>>As someone posted in a different reply on a similar problem,
>>due to restructuring/cleanup the whole tree is inconsistent
>>at presenet.
>>
>
>That's not true.  The tree IS consistent at present.  Having a full
>installation of a recent XFree86 version is now a pre-requisite.  No
>building hacks are required.  This is an intentional consequence of
>pruning the DRI source tree.
>
>David
>
May be the DRI compile guide needs updating with this infomation.  I got 
bit by this too and its turning  into a FAQ 8).

Mike




___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] No Subject

2001-09-26 Thread David Dawes

On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
>> From: Angel [mailto:[EMAIL PROTECTED]]
>> > > In a solution to this i decided to upgrade to
>> > > the DRI-CVS, however when making World it ends with the 
>> > > following error.  
>> > > /usr/i386-slackware-linux/bin/ld: cannot find -lXau
>> > > collect2: ld returned 1 exit status
>> > > make[4]: *** [XFree86] Error 1
>> > [...]
>> > > 
>> > > A search on google for -lXau yeilds nothing and no one I talk 
>> > > to has any
>> > > idea what this library is.  
>> >
>> > see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
>> > 
>> Well that directory is empty on both my pull of the CVS tree 
>> and the one
>> currently on sourceforge as of 1:00 PST.
>> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
>> If that is the directory you are talking about.
>
>As someone posted in a different reply on a similar problem,
>due to restructuring/cleanup the whole tree is inconsistent
>at presenet.

That's not true.  The tree IS consistent at present.  Having a full
installation of a recent XFree86 version is now a pre-requisite.  No
building hacks are required.  This is an intentional consequence of
pruning the DRI source tree.

David
-- 
David Dawes  Email: [EMAIL PROTECTED]
Founder/President, Release Engineer
The XFree86 Project, Inc http://www.xfree86.org/~dawes

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-26 Thread Alexander Stohr

> From: Angel [mailto:[EMAIL PROTECTED]]
> > > In a solution to this i decided to upgrade to
> > > the DRI-CVS, however when making World it ends with the 
> > > following error.  
> > > /usr/i386-slackware-linux/bin/ld: cannot find -lXau
> > > collect2: ld returned 1 exit status
> > > make[4]: *** [XFree86] Error 1
> > [...]
> > > 
> > > A search on google for -lXau yeilds nothing and no one I talk 
> > > to has any
> > > idea what this library is.  
> >
> > see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
> > 
> Well that directory is empty on both my pull of the CVS tree 
> and the one
> currently on sourceforge as of 1:00 PST.
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
> If that is the directory you are talking about.

As someone posted in a different reply on a similar problem,
due to restructuring/cleanup the whole tree is inconsistent
at presenet.

I would suggest getting this file from regular XFree86 sources or binaries.





___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-25 Thread Angel



On Tue, 25 Sep 2001, Alexander Stohr wrote:
> Date: Tue, 25 Sep 2001 12:49:25 +0200
> To: <[EMAIL PROTECTED]>
> From: "Alexander Stohr" <[EMAIL PROTECTED]>
> CC: <[EMAIL PROTECTED]>
> Subject: RE: [Dri-devel] No Subject
> 
> > I have been running the X 4.1 release for a while now and 
> > quite frequently
> > it has hard locked my box.  
> 
> Sorry, but you dont mention what hardware and software you are using.
> So far i found the current XFree86 core rather stable myselves.

Sorry about that it was late and i was getting frustrated.  I am running a
Matrox G400.

> 
> > In a solution to this i decided to upgrade to
> > the DRI-CVS, however when making World it ends with the 
> > following error.  
> > /usr/i386-slackware-linux/bin/ld: cannot find -lXau
> > collect2: ld returned 1 exit status
> > make[4]: *** [XFree86] Error 1
> [...]
> > 
> > A search on google for -lXau yeilds nothing and no one I talk 
> > to has any
> > idea what this library is.  
> 
> "-l" instructs the compiler to search for things like "lib*.a" (possibly
> lib*.so as well)
> in your case the postfix "Xau" completes to "libXau.a" which is
> missing for some unknown reason. Maybe it was just not rebuild
> or did not get symlinked into the XFree86 exports directory.
> 
> see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
> 
Well that directory is empty on both my pull of the CVS tree and the one
currently on sourceforge as of 1:00 PST.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
If that is the directory you are talking about.

> > Also one last problem.  When starting X with
> > multible resolutions IE
> >Modes   "800x600" "640x480" "1024x768" "1280x1024"
> > It starts with a virtual screen bigger then phyiscal screen, 
> > that i have to
> > move around in to find the edge of.  This is not the behavior 
> > selected in
> > the config and it does not happen when I only select 1 resolution per
> > depth.
> 
> When you have virtual screens enabled, the virtual screen area
> is at least as big as your biggest X and Y resolution. In your
> case you will spot 1280x1024 virtual area if your board has
> the caps. Please try "man XF86Config" for turning virtual screens off.
> 

I should not have virtual screens enabled.  At least i can not find it if i
do.  The Virtual display option is not and set i have looked through the
XF86Config man page to no avail.  I can run at any resolution and it won't
turn on virtual screens unless there is more the one resolution for the
depth.

> Hint: you can order the resolutions as you want, i.e. you can start up
> with highest and then decreasing by simply listing them reverse.
> 
> > Thank you in advance
> > -Angel
> 
> I think you can advance your system with these hints.
> Excuse me tha i am only adressing the basics - thats
> the area where i supposed the help is needed for now.
> 
> Regards AlexS.
> 
> 
> 

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-25 Thread Alexander Stohr

> I have been running the X 4.1 release for a while now and 
> quite frequently
> it has hard locked my box.  

Sorry, but you dont mention what hardware and software you are using.
So far i found the current XFree86 core rather stable myselves.

> In a solution to this i decided to upgrade to
> the DRI-CVS, however when making World it ends with the 
> following error.  
> /usr/i386-slackware-linux/bin/ld: cannot find -lXau
> collect2: ld returned 1 exit status
> make[4]: *** [XFree86] Error 1
[...]
> 
> A search on google for -lXau yeilds nothing and no one I talk 
> to has any
> idea what this library is.  

"-l" instructs the compiler to search for things like "lib*.a" (possibly
lib*.so as well)
in your case the postfix "Xau" completes to "libXau.a" which is
missing for some unknown reason. Maybe it was just not rebuild
or did not get symlinked into the XFree86 exports directory.

see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.

> Also one last problem.  When starting X with
> multible resolutions IE
>Modes   "800x600" "640x480" "1024x768" "1280x1024"
> It starts with a virtual screen bigger then phyiscal screen, 
> that i have to
> move around in to find the edge of.  This is not the behavior 
> selected in
> the config and it does not happen when I only select 1 resolution per
> depth.

When you have virtual screens enabled, the virtual screen area
is at least as big as your biggest X and Y resolution. In your
case you will spot 1280x1024 virtual area if your board has
the caps. Please try "man XF86Config" for turning virtual screens off.

Hint: you can order the resolutions as you want, i.e. you can start up
with highest and then decreasing by simply listing them reverse.

> Thank you in advance
> -Angel

I think you can advance your system with these hints.
Excuse me tha i am only adressing the basics - thats
the area where i supposed the help is needed for now.

Regards AlexS.




___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] No Subject

2001-09-25 Thread Angel

Hi, 

I have been running the X 4.1 release for a while now and quite frequently
it has hard locked my box.  In a solution to this i decided to upgrade to
the DRI-CVS, however when making World it ends with the following error.  
/usr/i386-slackware-linux/bin/ld: cannot find -lXau
collect2: ld returned 1 exit status
make[4]: *** [XFree86] Error 1
make[4]: Target `all' not remade because of errors.
rm -f Xserver._man
/lib/cpp -undef -traditional  -D__filemansuffix__=5x -D__miscmansuffix__=7
-D__d   rivermansuffix__=4
-D__projectroot__=/usr/X11R6-DRI -D__xorgversion__='"Release   
6.5" "X Version 11"' -D__vendorversion__='"Version
4.1.99.1" "XFree86"'  Xserver._man
rm -f Xserver.1x.html Xserver.1x-html
./../config/util/rman -f HTML < Xserver._man \
> Xserver.1x-html && mv -f Xserver.1x-html Xserver.1x.html
macro "in" not recognized -- ignoring
make[4]: Leaving directory `/root/DRI-CVS/xc/xc/programs/Xserver'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/root/DRI-CVS/xc/xc/programs'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/DRI-CVS/xc/xc'
make[1]: *** [World] Error 2
make[1]: Leaving directory `/root/DRI-CVS/xc/xc'
make: *** [World] Error 2
bash-2.05# 

A search on google for -lXau yeilds nothing and no one I talk to has any
idea what this library is.  Also one last problem.  When starting X with
multible resolutions IE
   Modes   "800x600" "640x480" "1024x768" "1280x1024"
It starts with a virtual screen bigger then phyiscal screen, that i have to
move around in to find the edge of.  This is not the behavior selected in
the config and it does not happen when I only select 1 resolution per
depth.

Thank you in advance
-Angel

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Mike Sessions


On Thu, 17 May 2001, Frank Worsley wrote:

>First off, apologies all around for not putting in a subject line. I kinda
>forgot about that! ;)
>
>>
>> I made some notes during my installation, I could possibly write
>> something of a howto if you think it would help.
>>
>
>Yeah, it would be very nice if you did that.
>

http://www.vvm.com/~sessions/linux/DRI.txt

>>
>> More or less. this is what my drm modules directory looks like now that I
>> have installed the 0.7 package...
>>
>> -rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
>> -rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
>> -rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
>> -rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
>> -rw-r--r--1 root root   108222 May 16 19:15 radeon.o
>> -rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz
>>
>>
>
>Wacko ... I've never seen anything like that. Then again, I've never used
>Mandrake. Since a lot of people seem to run Mandrake (especially 8) it
>would probably be worthwhile to add a check for something like this.
>

As long as the .gz module is there, it won't work... Someone new to Linux
is not going to know where to look or what to look for... Just that it
doesn't work.

>>
>> Well, I claim to be no genius... I remember something on my slackware
>> box though.. Quake3 for instance would run fine, but Unreal Tournament
>> would revert to software Mesa unless I removed all traces of libGL*
>> except those provided with whichever drivers I was using. If I remember
>> right it was this way with both the DRI drivers for my Radeon, and
>> Nvidia's driver for a GeForce card I have.
>
>I dunno. If we relink libGL to the correct one in /usr/X11R6/lib it
>shouldn't really be a problem.

Like I said, I remember something, but I could be way off base... The more
I think about it, there may have been some rouge links somewhere and it
may have only affected the Nvidia drivers on my Slackware box which is not
an issue here :) It doesn't seem to hurt anything with it gone at any
rate.


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Frank Worsley

First off, apologies all around for not putting in a subject line. I kinda
forgot about that! ;)

> 
> I made some notes during my installation, I could possibly write
> something of a howto if you think it would help.
> 

Yeah, it would be very nice if you did that.

> 
> More or less. this is what my drm modules directory looks like now that I
> have installed the 0.7 package...
> 
> -rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
> -rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
> -rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
> -rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
> -rw-r--r--1 root root   108222 May 16 19:15 radeon.o
> -rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz
> 
> 

Wacko ... I've never seen anything like that. Then again, I've never used
Mandrake. Since a lot of people seem to run Mandrake (especially 8) it
would probably be worthwhile to add a check for something like this.

> 
> Well, I claim to be no genius... I remember something on my slackware
> box though.. Quake3 for instance would run fine, but Unreal Tournament
> would revert to software Mesa unless I removed all traces of libGL*
> except those provided with whichever drivers I was using. If I remember
> right it was this way with both the DRI drivers for my Radeon, and
> Nvidia's driver for a GeForce card I have.

I dunno. If we relink libGL to the correct one in /usr/X11R6/lib it
shouldn't really be a problem.

- Frank


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Mike Sessions



On Thu, 17 May 2001, Frank wrote:

>> As far as the gotchas, Mandrake 8 has all the kernel modules gzipped up.
>> The install script didn't rename the original radeon.o.gz module. There
>> was also a libGL.1.2.030401 left hanging around in the /usr/X11R6/lib
>> directory.
>
>There have been a lot of problem reports from Mandrake 8 users on the FAQ comments.

I made some notes during my installation, I could possibly write something
of a howto if you think it would help.

>
>Could you explain what you mean by the kernel modules are gzipped up?
>Are you saying the modules are zipped in /lib/modules to save space and then get 
>unzipped when needed by the kernel???

More or less. this is what my drm modules directory looks like now that I
have installed the 0.7 package...

-rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
-rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
-rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
-rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
-rw-r--r--1 root root   108222 May 16 19:15 radeon.o
-rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz


>
>Also, the libGL.1.2.x hanging around is not a problem since we symlink libGL.so 
>and libGL.so.1 to the correct library.
>But maybe we should still try to remove/backup all old libGLs?
>This is also a problem on Redhat were such a libGL sticks around in /usr/lib .. they 
>get installed from the Mesa RPMS.

Well, I claim to be no genius... I remember something on my slackware
box though.. Quake3 for instance would run fine, but Unreal Tournament
would revert to software Mesa unless I removed all traces of libGL*
except those provided with whichever drivers I was using. If I remember
right it was this way with both the DRI drivers for my Radeon, and
Nvidia's driver for a GeForce card I have.

>
>- Frank
>ÿÿÿî/Ýz÷¥™¨¥Šx%ŠËC®/Ýz÷¥þX¬¶Ïì¢êÜyú+ïçzØm¶ŸÿþX¬¶Ïì¢êÜyú+ïçzßåŠËlþX¬¶)ߣ÷k‹÷^
>


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Re: Re: (no subject)

2001-05-17 Thread Jeff Hartmann

Mike A. Harris wrote:

> On Thu, 17 May 2001, Will Newton wrote:
> 
>>> Unfortunately, until 4.x supports all the hardware, or at least
>>> the hardware that we consider important, we need to ship 3.3.6
>>> servers in addition to 4.x, and that has some really crummy side
>>> effects, like having to ship separate Mesa and other hacks so
>>> that everyone can do 3D.  I would like nothing more than to get
>>> rid of XFree86 3.3.6 from the distribution, and also the separate
>>> Mesa package.
>> 
>> Maybe this is a silly question, but couldn't it be setup so XFree86 >= 4.0
>> conflicts with Mesa, and Xfree86 < 4.0 requires it? That way surely you
>> could make standalone Mesa for those who have old XFree and no DRI? Or is
>> there a sane configuration that mixes XFree 3.3.x and 4.x?
> 
> 
> Our current setup AFAIK is the only way to allow XFree86 4.x and
> 3.3.6 to coreside and both do software OpenGL, as well as
> allowing DRI to work where supported.  We need users to be able
> to switch between 4.x and 3.3.6 without installing/uninstalling a
> bunch of stuff which means that this is necessary until 3.3.6 is
> no longer needed.  Otherwise we must cripple our 3.3.6 support in
> order to use the Mesa that comes as part of XFree86.
> 
> 
Hrm, I know this has been brought up before, but why don't you just put 
a GLX implementation into 3.3.6?  I'm sure SGI's OpenGL SI or UtahGLX 
could be used without much additional effort.  They both should build 
with 3.3.x just fine.

-Jeff


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] Re: Re: (no subject)

2001-05-17 Thread Mike A. Harris

On Thu, 17 May 2001, Will Newton wrote:

>> Unfortunately, until 4.x supports all the hardware, or at least
>> the hardware that we consider important, we need to ship 3.3.6
>> servers in addition to 4.x, and that has some really crummy side
>> effects, like having to ship separate Mesa and other hacks so
>> that everyone can do 3D.  I would like nothing more than to get
>> rid of XFree86 3.3.6 from the distribution, and also the separate
>> Mesa package.
>
>Maybe this is a silly question, but couldn't it be setup so XFree86 >= 4.0
>conflicts with Mesa, and Xfree86 < 4.0 requires it? That way surely you
>could make standalone Mesa for those who have old XFree and no DRI? Or is
>there a sane configuration that mixes XFree 3.3.x and 4.x?

Our current setup AFAIK is the only way to allow XFree86 4.x and
3.3.6 to coreside and both do software OpenGL, as well as
allowing DRI to work where supported.  We need users to be able
to switch between 4.x and 3.3.6 without installing/uninstalling a
bunch of stuff which means that this is necessary until 3.3.6 is
no longer needed.  Otherwise we must cripple our 3.3.6 support in
order to use the Mesa that comes as part of XFree86.

Yes, the solution is a horrible hack, but it does work fairly
transparently for the most part.

I will be assimilating the separate Mesa package to be inside our
XFree86-4.x SRPM very shortly also - to minimize some other build
related problems that have come up as well.


--
Mike A. Harris  Shipping/mailing address:
OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie,
Red Hat Inc.Ontario, Canada, P6C 5B3
http://www.redhat.com   Phone: (705)949-2136
--
Latest XFree86 test RPMS:  ftp://people.redhat.com/mharris/testing


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Re: (no subject)

2001-05-17 Thread Will Newton

On Thu, 17 May 2001, Mike A. Harris wrote:

> Unfortunately, until 4.x supports all the hardware, or at least
> the hardware that we consider important, we need to ship 3.3.6
> servers in addition to 4.x, and that has some really crummy side
> effects, like having to ship separate Mesa and other hacks so
> that everyone can do 3D.  I would like nothing more than to get
> rid of XFree86 3.3.6 from the distribution, and also the separate
> Mesa package.

Maybe this is a silly question, but couldn't it be setup so XFree86 >= 4.0
conflicts with Mesa, and Xfree86 < 4.0 requires it? That way surely you
could make standalone Mesa for those who have old XFree and no DRI? Or is
there a sane configuration that mixes XFree 3.3.x and 4.x?



___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] Re: (no subject)

2001-05-17 Thread Mike A. Harris

On Thu, 17 May 2001, Frank wrote:

>> As far as the gotchas, Mandrake 8 has all the kernel modules gzipped up.
>> The install script didn't rename the original radeon.o.gz module. There
>> was also a libGL.1.2.030401 left hanging around in the /usr/X11R6/lib
>> directory.
>
>There have been a lot of problem reports from Mandrake 8 users
>on the FAQ comments.
>
>Could you explain what you mean by the kernel modules are
>gzipped up? Are you saying the modules are zipped in
>/lib/modules to save space and then get unzipped when needed by
>the kernel???
>
>Also, the libGL.1.2.x hanging around is not a problem since
>we symlink libGL.so and libGL.so.1 to the correct library. But
>maybe we should still try to remove/backup all old libGLs?
>This is also a problem on Redhat were such a libGL sticks
>around in /usr/lib .. they get installed from the Mesa RPMS.

Unfortunately, until 4.x supports all the hardware, or at least
the hardware that we consider important, we need to ship 3.3.6
servers in addition to 4.x, and that has some really crummy side
effects, like having to ship separate Mesa and other hacks so
that everyone can do 3D.  I would like nothing more than to get
rid of XFree86 3.3.6 from the distribution, and also the separate
Mesa package.

While XFree86 4.x is getting closer each release to that goal, it
is still not quite there yet..  The S3 code in particular - which
Ani Joshi (I hope I spelled that correctly) has graciously been
working on is one of the things that will help out greatly.
There are other drivers also to get ported over before we dump
3.3.6 and separate Mesa though.  Unfortunately the hardware and
docs are exceedingly rare for a lot of the stuff.

Take care,
TTYL


--
Mike A. Harris  Shipping/mailing address:
OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie,
Red Hat Inc.Ontario, Canada, P6C 5B3
http://www.redhat.com   Phone: (705)949-2136
--
Latest XFree86 test RPMS:  ftp://people.redhat.com/mharris/testing


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] (no subject)

2001-05-17 Thread Frank

> As far as the gotchas, Mandrake 8 has all the kernel modules gzipped up.
> The install script didn't rename the original radeon.o.gz module. There
> was also a libGL.1.2.030401 left hanging around in the /usr/X11R6/lib
> directory.

There have been a lot of problem reports from Mandrake 8 users on the FAQ comments.

Could you explain what you mean by the kernel modules are gzipped up?
Are you saying the modules are zipped in /lib/modules to save space and then get 
unzipped when needed by the kernel???

Also, the libGL.1.2.x hanging around is not a problem since we symlink libGL.so 
and libGL.so.1 to the correct library.
But maybe we should still try to remove/backup all old libGLs? 
This is also a problem on Redhat were such a libGL sticks around in /usr/lib .. they 
get installed from the Mesa RPMS.

- Frank
¸z÷¥™¨¥Šx%ŠËC®'^½éeŠËl²‹«qç讧zØm¶Ÿÿ–+-²Ê.­ÇŸ¢¸ë–+-³ùb²Ø§~Ý®'^½é


[Dri-devel] (no subject)

2001-04-09 Thread Hui Yu
Title: 








[Dri-devel] (no subject)

2001-04-07 Thread Janne Pänkälä

I haden't got this error message for a while.
---
[drm:radeon_freelist_get] *ERROR* returning NULL!
---

but when those start coming system is usually near total freeze.
same thing this time.

I'm puzzled. Not sure what that function is supposed to do. I tried to
look at it a bit but my knowledge in DRI architechture is not good enough
to understand this.

-- 
Janne
echo [EMAIL PROTECTED] | tr acefhiklnptu utpnlkihfeca


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel