On Monday 13 February 2012 13:57:12 Pietro Cerutti wrote:
On 2012-Feb-13, 00:34, vehemens wrote:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d01de08c4c84f0406a23ce3
8e1c9c163ed2b91bc
FWIW, I'm going to update graphics/libosmesa within the next few days.
A long as you account
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d01de08c4c84f0406a23ce38e1c9c163ed2b91bc
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
The following reply was made to PR kern/150514; it has been noted by GNATS.
From: vehemens vehem...@verizon.net
To: bug-follo...@freebsd.org, vehem...@verizon.net
Cc:
Subject: Re: kern/150514: [drm] [request] Reorganize DRM Directory to Support
Driver Updates
Date: Tue, 08 Mar 2011 02:37:18
The following reply was made to PR kern/150514; it has been noted by GNATS.
From: vehemens vehem...@verizon.net
To: bug-follo...@freebsd.org, vehem...@verizon.net
Cc:
Subject: Re: kern/150514: [drm] [request] Reorganize DRM Directory to Support
Driver Updates
Date: Tue, 22 Feb 2011 22:56:57
The following reply was made to PR kern/150514; it has been noted by GNATS.
From: vehemens vehem...@verizon.net
To: bug-follo...@freebsd.org, vehem...@verizon.net
Cc:
Subject: Re: kern/150514: [drm] [request] Reorganize DRM Directory to Support
Driver Updates
Date: Wed, 17 Nov 2010 23:00:21
-users
Arrival-Date: Thu Nov 18 07:30:14 UTC 2010
Closed-Date:
Last-Modified:
Originator: vehemens
Release:current
Organization:
Environment:
Description:
The following files are no longer used and should be removed:
src/sys/dev/drm/drm-preprocess.sh
src/sys/dev/drm/drm-subprocess.pl
The following reply was made to PR kern/150514; it has been noted by GNATS.
From: vehemens vehem...@verizon.net
To: bug-follo...@freebsd.org, vehem...@verizon.net
Cc:
Subject: Re: kern/150514: [drm] [request] Reorganize DRM Directory to Support
Driver Updates
Date: Sun, 31 Oct 2010 03:41:08
On Sunday 29 November 2009 00:31:17 Daniel Stone wrote:
Hi,
On Sat, Nov 28, 2009 at 08:40:55PM -0800, vehemens wrote:
On Saturday 28 November 2009 16:21:58 Robert Noland wrote:
Because unpublished work doesn't exist That goes for the work that
I've done that isn't yet published
On Sunday 29 November 2009 07:07:41 Robert Noland wrote:
On Sat, 2009-11-28 at 20:40 -0800, vehemens wrote:
On Saturday 28 November 2009 16:21:58 Robert Noland wrote:
On Sat, 2009-11-28 at 13:38 -0800, vehemens wrote:
On Saturday 28 November 2009 10:41:39 Robert Noland wrote:
On Fri
On Sunday 29 November 2009 10:39:34 Maarten Maathuis wrote:
I enjoy playing the devils advocate occasionally, so take this with a
grain of salt.
My understanding is that there are roughly 3 bsd kernels that support
drm userspace interface(free*, open* and netbsd?), each has 1 or 2
On Sunday 29 November 2009 14:23:44 Adam K Kirchhoff wrote:
On Sunday 29 November 2009 14:16:13 vehemens wrote:
[snip]
Your missing the point of using a development structure which supports
collobration.
[snip]
The difference is that you are the only one doing the work now.
[snip
On Sunday 29 November 2009 15:36:51 Adam K Kirchhoff wrote:
On Sunday 29 November 2009 18:54:31 vehemens wrote:
On Sunday 29 November 2009 14:23:44 Adam K Kirchhoff wrote:
On Sunday 29 November 2009 14:16:13 vehemens wrote:
[snip]
Your missing the point of using a development
On Sunday 29 November 2009 19:51:55 Robert Noland wrote:
On Sun, 2009-11-29 at 15:36 -0800, vehemens wrote:
I believe that moving away from the current model makes it more
difficult
to ... spread the burden ..., hence my objections. If you want to
call
that ranting or complaining, so
On Saturday 28 November 2009 10:41:39 Robert Noland wrote:
On Fri, 2009-11-27 at 17:23 -0800, vehemens wrote:
On Sunday 22 November 2009 01:01:10 Dave Airlie wrote:
On Sun, Nov 22, 2009 at 7:10 PM, vehemens vehem...@verizon.net wrote:
On Saturday 21 November 2009 20:09:53 Dave Airlie
On Saturday 28 November 2009 13:44:53 Dave Airlie wrote:
I haven't published any of my work recently, but that doesn't mean I
haven't done anything that I would like to share. Not sure why you feel
this is important however.
I gave you a number of suggestions in private emails on how to
On Saturday 28 November 2009 16:21:58 Robert Noland wrote:
On Sat, 2009-11-28 at 13:38 -0800, vehemens wrote:
On Saturday 28 November 2009 10:41:39 Robert Noland wrote:
On Fri, 2009-11-27 at 17:23 -0800, vehemens wrote:
On Sunday 22 November 2009 01:01:10 Dave Airlie wrote:
On Sun
On Saturday 21 November 2009 20:09:53 Dave Airlie wrote:
I see that you deleted bsd-core dispite the requests of a number of
people that you do not.
Its git, nobody has touched any of it in ages, and none of the BSD
maintainers used it, you can just get it back by branching from the commit
On Friday 20 November 2009 14:20:41 Kristian Høgsberg wrote:
2009/11/19 Eric Anholt e...@anholt.net:
On Tue, 2009-11-17 at 11:33 -0500, Kristian Høgsberg wrote:
2009/11/6 Kristian Høgsberg k...@bitplanet.net:
Hi,
This has come up a few time and it's something I think makes a lot of
On Tuesday 17 November 2009 08:33:30 Kristian Høgsberg wrote:
2009/11/6 Kristian Høgsberg k...@bitplanet.net:
Hi,
This has come up a few time and it's something I think makes a lot of
sense. Since all driver development (afaik) now happens in linux
kernel tree, it makes sense to drop
Anbody else seeing this pixman problem?
Assertion failed: (PREFIX(_selfcheck) (src)), function pixman_region_copy,
file pixman-region.c, line 373.
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Submitter-Id: current-users
Arrival-Date: Sat Jun 13 09:30:02 UTC 2009
Closed-Date:
Last-Modified:
Originator: vehemens
Release:7.2 stable
Organization:
Environment:
FreeBSD fred.dsl-verizon.net 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat Jun 13
00:49:51 PDT 2009 vehem...@fred.dsl
Ever wonder where we would be as a civilization if the additional codes had
been used for math symbols and greek letters as used in engineering and
science.
___
freebsd-questions@freebsd.org mailing list
Author: rnoland
Date: Tue Mar 31 17:52:05 2009
New Revision: 190595
URL: http://svn.freebsd.org/changeset/base/190595
Log:
Simplify the radeon microcode loading.
Submitted by: Christoph Mallon
MFC after:3 days
Modified:
head/sys/dev/drm/r600_cp.c
head/sys/dev/drm/radeon_cp.c
I
On Thursday 02 April 2009 12:25:52 am Robert Noland wrote:
On Wed, 2009-04-01 at 23:24 -0700, vehemens wrote:
Author: rnoland
Date: Tue Mar 31 17:52:05 2009
New Revision: 190595
URL: http://svn.freebsd.org/changeset/base/190595
Log:
Simplify the radeon microcode loading
On Sunday 29 March 2009 10:55:52 pm Alex Deucher wrote:
New commits:
commit c3c2ae466cfa1d4e079f6f0396e8f0f68ecb84b8
Merge: 48b5f09... e2d7dfb...
Author: Alex Deucher alexdeuc...@gmail.com
Date: Mon Mar 30 01:54:54 2009 -0400
Merge branch 'master' into r6xx-r7xx-support
thank you
On Saturday 28 February 2009 09:06:38 am Robert C. Noland III wrote:
On Fri, 2009-02-27 at 23:54 -0800, vehemens wrote:
On Friday 27 February 2009 01:45:50 pm Kristian Høgsberg wrote:
On Fri, Feb 27, 2009 at 4:40 PM, Dave Airlie airl...@linux.ie wrote:
Prompted by how well it worked
On Saturday 28 February 2009 05:28:38 am Pekka Paalanen wrote:
On Fri, 27 Feb 2009 23:54:21 -0800
vehemens vehem...@verizon.net wrote:
On Friday 27 February 2009 01:45:50 pm Kristian Høgsberg wrote:
On Fri, Feb 27, 2009 at 4:40 PM, Dave Airlie airl...@linux.ie wrote:
Prompted by how
On Friday 27 February 2009 01:40:25 pm Dave Airlie wrote:
Prompted by how well it worked with Intel, and changes in my personal life
leading to reduced time availability (except at 4am...) I'm going to
clarify the process for getting patches upstream now. (a...@amd also
trialed this to get
On Friday 27 February 2009 01:45:50 pm Kristian Høgsberg wrote:
On Fri, Feb 27, 2009 at 4:40 PM, Dave Airlie airl...@linux.ie wrote:
Prompted by how well it worked with Intel, and changes in my personal
life leading to reduced time availability (except at 4am...) I'm going to
clarify the
Given that last years changes to xineramaproto appear to impact a number of
applications (on my system anyway), could anyone tell me when the next
release of xineramaproto will occur?
___
xorg mailing list
xorg@lists.freedesktop.org
On Tuesday 17 February 2009 05:43:32 pm Robert C. Noland III wrote:
On Mon, 2009-02-16 at 18:39 +, Owain Ainsworth wrote:
On Sat, Feb 14, 2009 at 11:24:18PM +0200, Pekka Paalanen wrote:
From 29d3f6e9c1258736c3199834b293b8128faef2ad Mon Sep 17 00:00:00 2001
From: Pekka Paalanen
On Saturday 31 January 2009 04:20:26 pm Alex Goncharov wrote:
,--- You/vehemens (Sat, 31 Jan 2009 13:54:42 -0800) *
| On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote:
| So, a *fundamental* (practically an OS component) port is brought in
| -- and it disables my system
On Sunday 01 February 2009 11:22:52 am Alex Goncharov wrote:
| This has nothing to do with Linux. The issue is that that while src
| has a stable versus current branch, there is no stable branch for
| ports. The result is major updates are almost always problematic.
Any data points to
On Fri Jan 30 11:53:16 PST 2009, Peter Jeremy wrote:
As a general note, this is the second time in a row that an X.org
upgrade broke X for a significant number of people. IMO, this
suggests that our approach to X.org upgrades needs significant changes
(see below). X11 is a critical component for
On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote:
,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) *
| In general when upgrading, you take your chances. If a port upgrade
| fails, you should fall back to what worked.
So, a *fundamental* (practically an OS component) port
On Fri Jan 30 11:53:16 PST 2009, Peter Jeremy wrote:
As a general note, this is the second time in a row that an X.org
upgrade broke X for a significant number of people. IMO, this
suggests that our approach to X.org upgrades needs significant changes
(see below). X11 is a critical component for
On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote:
,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) *
| In general when upgrading, you take your chances. If a port upgrade
| fails, you should fall back to what worked.
So, a *fundamental* (practically an OS component) port
On Saturday 10 January 2009 08:49:01 am Robert Noland wrote:
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
-
On Monday 05 January 2009 11:03:55 pm Paulo César Pereira de Andrade wrote:
vehemens wrote:
subject says it all
Thanks. I feel dumb for this one :-) Last time
I run make distcheck was like one month ago, when
I added
DISTCLEANFILES = doltcompile doltlibtool
to the toplevel Makefile.am
On Tuesday 06 January 2009 06:36:39 am Brian Paul wrote:
vehemens wrote:
dri_sarea.h was removed, but the Makefile reference is still present.
Fixed.
-Brian
thanks
--
Check out the new SourceForge.net Marketplace
dri_sarea.h was removed, but the Makefile reference is still present.
--
___
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
subject says it all
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
On Wednesday 10 December 2008 03:52:08 pm Jesse Barnes wrote:
...
New commits:
commit 9583c099b4a08b49e03f7b461c344b6d277fd262
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Wed Dec 10 15:47:28 2008 -0800
Revert Merge branch 'modesetting-gem'
This reverts commit
On Thursday 11 December 2008 04:28:48 pm Jesse Barnes wrote:
On Thursday, December 11, 2008 4:16 pm vehemens wrote:
On Wednesday 10 December 2008 03:52:08 pm Jesse Barnes wrote:
...
New commits:
commit 9583c099b4a08b49e03f7b461c344b6d277fd262
Author: Jesse Barnes jbar
Need to add big5hkscs.h and gbk.h to the distribution list.
reference commit:
2008-11-22 18:40:54 (GMT)
67e34d7a82ccd31f1208c0c43a6d58c3c05bf51
Added remaining xlib patch required for gb18030 support (#1573).
--- libX11/src/xlibi18n/Makefile.am.org 2007-10-27 23:11:49.0 -0700
+++
On Wednesday 03 December 2008 09:21:51 pm Peter Hutterer wrote:
On Wed, Dec 03, 2008 at 08:08:35PM -0800, vehemens wrote:
On Wednesday 03 December 2008 02:33:34 pm Peter Hutterer wrote:
http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html
That's a quick brain dump
On Wednesday 03 December 2008 02:33:34 pm Peter Hutterer wrote:
http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html
That's a quick brain dump of input related things I could think of that are
repeatedly asked on the list, irc, and bugreports. The information is
accurate
Would anyone object to using a struct for the vblank crtc data to eliminate
the multiple allocs / frees?
For example:
struct drm_vblank {
wait_queue_head_t vbl_queue;
atomic_t _vblank_count;
struct drm_vbl_sig_list vbl_sigs;
atomic_t vblank_refcount;
u32
Here are a few drm patches.
correct another lock leak.
add missing link.
negate return value. minor cleanup while we are here.
diff --git a/bsd-core/drm_bufs.c b/bsd-core/drm_bufs.c
index 3508331..c793634 100644
--- a/bsd-core/drm_bufs.c
+++ b/bsd-core/drm_bufs.c
@@ -832,12 +832,12 @@ int
On Wednesday 28 May 2008 04:35:42 am Oleg Nauman wrote:
On Wed, May 28, 2008 at 10:34 AM, vehemens [EMAIL PROTECTED] wrote:
Here are a few drm patches.
correct another lock leak.
add missing link.
negate return value. minor cleanup while we are here.
It just panics my laptop
On Thursday 01 May 2008 07:16:36 am Jerome Glisse wrote:
On Tue, 29 Apr 2008 20:51:45 -0700
vehemens [EMAIL PROTECTED] wrote:
The primary goal is to update the BSD drm code with the recent linux
changes including linux drm memory management code. I haven't seen
anything in the code
I'm currently working on updating the bsd libdrm for use with my freebsd
system. To reduce the work involved, I'm using some code from the linux
kernel for lists and atomics. This also greatly reduces the amount of unique
code required.
Unfortunately I only have radeon rv370 and intel i810
On Tuesday 29 April 2008 08:35:36 am Jerome Glisse wrote:
On Mon, 28 Apr 2008 08:26:41 -0700
vehemens [EMAIL PROTECTED] wrote:
I'm currently working on updating the bsd libdrm for use with my freebsd
system. To reduce the work involved, I'm using some code from the linux
kernel for lists
I'm currently working on updating the bsd libdrm for use with my freebsd
system. To reduce the work involved, I'm using some code from the linux
kernel for lists and locks. This also greatly reduces the amount of unique
code required.
Unfortunately I only have radeon rv370 and intel i810 class
Removing the glcore: drop outdated sources files intented for xorg has also
broken make tarballs.
Is there a distribution patch coming in the near future?
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
I'm seeing my RADEON RV350 stall (~1 FPS) when running the engine demo with
the wire frame rendering style. The other styles run ~140 FPS.
Switching to a RV250 results in ~160 FPS or better for all rendering styles.
This is with the MESA/DRI/ATI/X development master branches as of the last few
On Monday 23 July 2007 07:59:24 am Eric Anholt wrote:
This was used to make all ioctl handlers return -errno on linux and
errno on *BSD. Instead, just return -errno in shared code, and flip sign
on return from shared code to *BSD code.
I was trying to determine why my system hung and
Isn't DRM_ERR() required for compatibility?
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
On Monday 09 July 2007 02:51:37 am Michel Dänzer wrote:
On Mon, 2007-07-09 at 00:38 -0700, vehemens wrote:
I believe I have narrowed the problem down to __glXDRIscreenProbe()
removing the RADEON DRM lock that was set up with DRIFinishScreenInit().
What happens is that __glXDRIscreenProbe
I have the following error when running glxgears using the ATI driver:
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 158 (DAMAGE)
Minor opcode of failed request: 4 ()
Serial number of failed request: 37
Current
On Saturday 12 May 2007 12:53:00 pm vehemens wrote:
I have the following error when running glxgears using the ATI driver:
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 158 (DAMAGE)
Minor opcode of failed request: 4
On Saturday 23 December 2006 14:23, Jerome Glisse wrote:
On 12/23/06, Magnus Ahlberg [EMAIL PROTECTED] wrote:
I know that there has been some discussion about the r500 chip and how
tough it will be to create a working driver for it. However, I for one
would love to see an open alternative
On Thursday 03 August 2006 23:12, [EMAIL PROTECTED] wrote:
What error message exactly you have got? The build procedure should look
like this (assume we're installing in /work/x11r7:
1) downlod Xorg source, unpack
2) download mesa src
2) install devel/gnu-autoconf, devel/gnu-automake
3)
ssedov at mbsd.msk.ru wrote:
You can install X.org from GIT repository - it works fine out-of-the-box
on freebsd. Just install it under the different PREFIX (e.g. /usr/x11r7)
and you will not have problems with uninstall.
I don't appear to have the same luck as I'm having problems with several
IMHO you should wait until we are ready to do a test-run on pointyhat.
Otherwise you are going to be finding problems one-at-a-time that we
can otherwise find out in bulk.
How does one get access to the port code?
To reiterate: there is very active work to get us to xorg7. It's not
as trivial
Is there a plan to get X11R7.1 into the ports tree in the next week or two?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Monday 28 November 2005 02:55 pm, Benjamin Herrenschmidt wrote:
The DRM lock should protect that ... note that I just spotted a DRM fix
drm: fix quiescent locking going into the linux kernel that may
explain races with the DRM lock.
Also, there has been historical issues with the scratch
Posting my latest DRM and Mesa patches in case they should prove useful to
anyone else. They are to head as of early Saturday.
I moved the CP idle outside the while loop in radeon_state.c. I think it may
apply to the R300 as well as there is an if R300 idle command in the
Xserver
On Monday 28 November 2005 02:55 pm, Benjamin Herrenschmidt wrote:
On Mon, 2005-11-28 at 02:18 -0800, vehemens wrote:
I've been looking at my remaining lockups, and find that I keep coming
back to the use of scratch registers in the driver for one of them.
If I'm reading the code
I've been looking at my remaining lockups, and find that I keep coming back to
the use of scratch registers in the driver for one of them.
If I'm reading the code correctly, the scratch registers are per device, not
per client. This would mean that you can't run more then one client without
I've managed to eliminate a number of lockups when running one or more copies
of glxgears and other GL programs with the patch below.
This suggests that the driver needs some type of command timing/processing
rules to prevent lockup (NOPs?).
I working on the other lockups, but debug seems to
I appear to of eliminated my remaining lockups by also idling the 2D engine in
radeon_cp_indirect which is being called from the xserver. Here is my latest
patch.
*** drm111605/shared-core/radeon_state.cFri Nov 11 20:25:43 2005
--- drmbld/shared-core/radeon_state.c Wed Nov 23
It took over an hour this time, but it locked up while running three different
demos.
Looks good.. but dude diff -u plz
I can't read context diffs to save my life...
Dave.
Done.
drmbld/shared-core/radeon_state.c
--- drm111605/shared-core/radeon_state.cFri Nov 11 20:25:43 2005
73 matches
Mail list logo
