Re: Making Xorg easier to test
On Fri, 2010-03-05 at 07:49 -0800, David Miller wrote: > From: Daniel Stone > Date: Fri, 5 Mar 2010 17:41:43 +0200 > > > I understand that you guys are upset about this, so maybe you'd like to > > donate, say, 10% of your developer base to help out? That'd be pretty > > ace. > > You have to support less than %10 of the amount of hardware we have to > support. You can't compare a network card and a GPU. The latter is way more complex to code for. Xav -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: linux-2.6.32.2 broke radeon modeset=1
On Fri, 2010-01-08 at 23:36 +0100, Hendrik Sattler wrote: > Am Freitag 08 Januar 2010 23:29:11 schrieb Alex Deucher: > > On Fri, Jan 8, 2010 at 12:53 PM, Hendrik Sattler > > > > wrote: > > > Hi, > > > > > > I have a ATI HD2400XT in my notebook and tried the radeon.ko module with > > > modeset=1 (X cannot use this, yet). > > > While this gives me a framebuffer console with 2.6.32, it only shows a > > > blank screen with linux-2.6.32.2. > > > > already fixed in 2.6.32.3 > > Great :) > > Now I just need to figure out how to make X (Debian unstable on amd64) use > DRI2. :) Due to Debian bug #561476 (initrd doesn't load firmware) it may not be that easy. Xav -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm/radeon/kms: pm: single frame corruptions on reclocking
On Tue, 2009-12-29 at 19:35 +0100, Luca Tettamanti wrote: > I've adapted Rafał's patch to do the reclock when the idle interrupt is > fired (which btw should take care of the special case for nr CRTCs > 1). > Unfortunately I still see the black frame when reclocking is performed. > So I tried recloking directly from the IH (yeah, I'm ashamed of > myself...); this got rid of the black frame, but causes corruption of a > horizontal block of the screen (during the reclock, before and after the > screen looks fine). In this second case I've added a spinlock to guard > the access to the CP ring, so nothing touches it while reclocking is > performed; however by the time we process the idle interrupt - > especially considering that multiple events might be queued in the IH > ring - someone else (i.e. one of the other cores) might already have > submitted more work; what do you think? Maybe a spinlock doesn't cut it. How about some mutex you take when you need to reclock, to let tasks trying to add to the CP ring just sleep, and then you unmask the idle interrupt. When you receive the idle interrupt, you reclock, you free the mutex, and voilà. Xav -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] drivers/radeon/kms: Workaround RV410/R420 CP errata.
On Fri, 2009-12-18 at 01:11 -0800, Corbin Simpson wrote:
[...]
> @@ -194,6 +225,9 @@ static int r420_startup(struct radeon_device *rdev)
> dev_err(rdev->dev, "failled initializing CP (%d).\n", r);
> return r;
> }
> +/* Handle CP errata. */
> +r420_cp_errata_init(rdev);
> +
> r = r100_wb_init(rdev);
> if (r) {
On a purely cosmetic POV, it looks like you indent with spaces in a file
previously indented with tabs.
Xav
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [git pull] drm
On Thu, 2009-12-10 at 07:17 -0800, Linus Torvalds wrote: > > On Thu, 10 Dec 2009, Dave Airlie wrote: > > > > The biggest missing feature [ ... ] > > No, the biggest missing feature is that Fedora is _still_ shipping > Nouveau, and I'm _still_ not seeing Red Hat people actively trying to get > it merged into mainline. > > What the _hell_ is going on? Last time they were asked that, they wanted to be free of changing their kernel/userspace interface before upstreaming. Xav -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: RFC: libdrm repo
On Tue, 2009-11-17 at 20:54 +0100, Julien Cristau wrote: > On Tue, Nov 17, 2009 at 18:54:40 +0100, Stephane Marchesin wrote: > > > Yes, but the positive side is that distros using a standard/old (about > > a year) kernel don't need to crawl the old libdrm repo and find the > > right version (in your case they have to do this ° backport stuff) ... > > I think that plus the fact that it makes development and merging > > simpler is just a reason to do it. > > > Why would they have to do that? Newer libdrms should stay compatible > with older kernels... And vice-versa. Some people install newer kernels just to have a newer driver for some particular hardware, or a bugfix somewhere. If this breaks 3D, many modern interfaces won't work (these days they are compiz, gnome-shell, or other clutter-based interface). Breaking things by upgrading a kernel is frowned upon on LKML :) Xav -- 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
Re: Adding new pci vendor id
Hi, On Tue, 2009-08-11 at 03:24 -0400, Tauseef Hussain wrote: > Hi > I am using a linux kernel with the following info > > Linux 2.6.29.6-217.2.3.fc11.i686.PAE #1 SMP Wed Jul 29 16:05:22 EDT 2009 i686 > GNU/Linux > I would like to know what is the procedure to add new pci vendor id and > device id to the list pciids.h which i found at this location -> > /usr/src/kernels/2.6.29.6-217.2.3.fc11.i686.PAE/include/drm/drm_pciids.h My guess is that you just submit a patch on that mailing-list. Xav -- 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
Re: [PATCH] drm: make drm_wait_vblank return immediately for very old sequence values
On Tue, 2009-02-17 at 16:10 -0800, Ian Romanick wrote: > Are vblanks | Is anyone | > happening? | listening? | What to do? > > YesYes Update MSC based on vblank interrupts > YesNoDisable IRQ, estimate MSC next time >someone listens > No Yes Update MSC based on timer at approx. >previous refresh rate > No NoDisable IRQ, estimate MSC next time >someone listens DPMS is for saving energy. I'd find it awkward if the system continues to pump 50fps when in "energy saving mode". Nowadays GL apps are the default (compiz is pretty standard). Xav -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Gem GTT mmaps..
Le vendredi 06 février 2009 à 14:24 -0800, Jesse Barnes a écrit :
> + map = list->map;
> + if (map) {
> + drm_free(map, sizeof(*map), DRM_MEM_DRIVER);
> + list->map = NULL;
I would have inverted the two last lines (otherwise why wouldn't you
directly drw_free(list->map) ?).
Xav
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: GEM/TTM interfaces
Le vendredi 13 juin 2008 à 18:28 +0200, Tomas Carnecky a écrit : > I have read (don't remember where) that once the kernel has a sensible > infrastructure for file descriptors you'd want to convert all the ioctl > code in GEM/TTM to standard syscalls. Is that true? Do you already know > which syscalls would replace for example drmBOCreate() or the GEM_CREATE > ioctl? Both functions create a new handle, so open(2) would be a > candidate, but both functions also take a 'size' argument, which open > doesn't support, so you'd still have to implement an fcntl/ioctl > interface for such things. ftruncate() ? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI2 direct rendering
Hi Kristian, On Mon, 2008-03-31 at 17:34 -0400, Kristian Høgsberg wrote: > Hi, > > I just committed the last big chunk of DRI2 work, the direct rendering > support. With this, we can now do direct rendering to redirected > windows and GLX_EXT_texture_from_pixmap even works, so compiz (and > other Open GL compositing managers) can run in direct rendering mode > too. First, thanks for that work (I've been waiting for that for long). Second, does that work for people with a radeon yet, or is this still for testers with an Intel card ? Thanks, Xav - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI2 direct rendering
On Tue, 2008-04-01 at 11:48 +0200, Xavier Bestel wrote: > Hi Kristian, > > On Mon, 2008-03-31 at 17:34 -0400, Kristian Høgsberg wrote: > > Hi, > > > > I just committed the last big chunk of DRI2 work, the direct rendering > > support. With this, we can now do direct rendering to redirected > > windows and GLX_EXT_texture_from_pixmap even works, so compiz (and > > other Open GL compositing managers) can run in direct rendering mode > > too. > > First, thanks for that work (I've been waiting for that for long). > > Second, does that work for people with a radeon yet, or is this still > for testers with an Intel card ? OK nevermind, I just needed to read your post until the end ... Xav - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI2 Design Wiki Page
Hi, On Thu, 2007-10-04 at 01:27 -0400, Kristian Høgsberg wrote: > I wrote up the DRI2 design on a wiki page here: > > http://wiki.x.org/wiki/DRI2 Is that a new DRI version intended to work with Gallium only ? Xav - 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. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DMA scheduling
On Thu, 2006-03-16 at 16:52, Keith Whitwell wrote: > 2) Interactivity. It is quite possible to have one application which > does so little rendering per frame that it can run at 3000fps while > another eg, video-based application does a lot more and can just > about keep up a 30fps framerate. Consider a situation where both > applications are running at once. Simple fairness criteria would > have them running at 1500fps and 15fps respectively - but it seems > that fairness isn't what is required here. It would be preferable > give the slower application a greater percentage of the GPU, so > that it manages eg. 27fps, while the other is scaled down to "only" > 300fps or so. What's the point of having one app run faster than the vsync when there is still contention on another app ? At 60Hz, having the "fast" app do 60fps and the slow one manage 29fps sounds better. Xav --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM radeon i2c support and GPL
Le mar 21/09/2004 Ã 09:58, Kean Johnston a Ãcrit : > > I picked a very simple piece of code to start out with as a test case. > > The I2C code is only a hundred lines and could be rewritten. But > > what's the point, BSD doesn't have Linux's I2C driver system. This > > code has no value anywhere but on Linux. > That's not a statement thats safe to make. BSD (or any other OS > that XOrg supports) may not have Linux's I2C driver system. TODAY. > What if, next week, BSD gets such a beast, or HP-UX does, or > Solaris or whatever. Maybe now that code that is currently only > of value on Linux is of value on a broad range of systems. My understanding is that if/when BSDs (and others) implement an I2C system, it'll probably be compatible with the Linux one from the userspace side (i.e. the syscalls will have the same semantics) but certainly not from the kernel side: there's not point for them to be compatible with the Linux architecture as they can't import its drivers. I don't the DRM drivers, but if they use I2C from the kernel side there's not point in licensing that code for multiplatform. Xav --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
