Displaying 20 results from an estimated 5000 matches similar to: "Selecting supported chipsets in the driver?"
2013 Jul 30
2
Selecting supported chipsets in the driver?
On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> On 30/07/13 21:39, Christ-Jan Wijtmans wrote:
>> Hi, my apologies if this is the wrong place to post this.
>> I had the desire to turn on or off support for certain chipsets.
>> Because i felt like the nouveau drivers are (relatively) quite large and
>> depends on some kernel code
2013 Jul 31
2
Selecting supported chipsets in the driver?
On Wed, Jul 31, 2013 at 10:44 AM, Martin Peres <martin.peres at free.fr> wrote:
> On 30/07/2013 18:43, Ilia Mirkin wrote:
>>
>> On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com>
>> wrote:
>>>
>>> On 30/07/13 21:39, Christ-Jan Wijtmans wrote:
>>>>
>>>> Hi, my apologies if this is the wrong place to
2013 Aug 01
2
Selecting supported chipsets in the driver?
Sorry but 1.7 and 6.3 MB are huge...
Live long and prosper,
Christ-Jan Wijtmans
http://facebook.com/cj.wijtmans
http://twitter.com/cjwijtmans
On Wed, Jul 31, 2013 at 5:42 PM, Martin Peres <martin.peres at free.fr> wrote:
> On 31/07/2013 11:03, Ilia Mirkin wrote:
>
>> On Wed, Jul 31, 2013 at 10:44 AM, Martin Peres <martin.peres at free.fr>
>> wrote:
>>
2013 Nov 29
0
Selecting supported chipsets in the driver?
so uhm, as far as i know in ATI drivers this is possible, why no nouveau?
Live long and prosper,
Christ-Jan Wijtmans
https://github.com/cjwijtmans
http://facebook.com/cj.wijtmans
http://twitter.com/cjwijtmans
On Thu, Aug 1, 2013 at 2:15 AM, Christ-Jan Wijtmans
<cj.wijtmans at gmail.com>wrote:
> Sorry but 1.7 and 6.3 MB are huge...
>
>
> Live long and prosper,
>
>
2013 Jul 30
0
Selecting supported chipsets in the driver?
On 30/07/13 21:39, Christ-Jan Wijtmans wrote:
> Hi, my apologies if this is the wrong place to post this.
> I had the desire to turn on or off support for certain chipsets.
> Because i felt like the nouveau drivers are (relatively) quite large and
> depends on some kernel code that would only be used for certain chipsets.
> I will take some time this week to see how this is coded
2013 Jul 31
0
Selecting supported chipsets in the driver?
On 30/07/2013 18:43, Ilia Mirkin wrote:
> On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> On 30/07/13 21:39, Christ-Jan Wijtmans wrote:
>>> Hi, my apologies if this is the wrong place to post this.
>>> I had the desire to turn on or off support for certain chipsets.
>>> Because i felt like the nouveau drivers are
2013 Jul 31
0
Selecting supported chipsets in the driver?
On 31/07/2013 11:03, Ilia Mirkin wrote:
> On Wed, Jul 31, 2013 at 10:44 AM, Martin Peres <martin.peres at free.fr> wrote:
>> On 30/07/2013 18:43, Ilia Mirkin wrote:
>>> On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com>
>>> wrote:
>>>> On 30/07/13 21:39, Christ-Jan Wijtmans wrote:
>>>>> Hi, my apologies if
2013 Aug 09
1
[Bug 64323] Severe misrendering in Left 4 Dead 2
how did you get dota2 to even start? it should not work with the nouveau
drivers.
Live long and prosper,
Christ-Jan Wijtmans
http://facebook.com/cj.wijtmans
http://twitter.com/cjwijtmans
On Thu, Aug 8, 2013 at 4:48 PM, <bugzilla-daemon at freedesktop.org> wrote:
> *Comment # 5 <https://bugs.freedesktop.org/show_bug.cgi?id=64323#c5> on bug
> 64323
2013 May 07
34
[Bug 64323] New: Severe misrendering in Left 4 Dead 2
https://bugs.freedesktop.org/show_bug.cgi?id=64323
Priority: medium
Bug ID: 64323
Assignee: nouveau at lists.freedesktop.org
Summary: Severe misrendering in Left 4 Dead 2
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: bryancain3+fdo at gmail.com
Hardware: x86 (IA32)
2015 Jul 15
2
If Wine isn't am emulator how does it work
On Wed, Jul 15, 2015 at 10:25 PM, Martin Gregorie <martin at gregorie.org> wrote:
> On Wed, 2015-07-15 at 13:37 +0200, Florian Pelz wrote:
>> I suppose people disagree on what can be called an emulator. The term
>> is often used for those slow CPU emulators though.
>>
> Be careful before calling at least some of them slow.
Yeah, they're slow compared to native
2015 Feb 22
2
[PATCH] Basic GM206 bringup (as copy of GM100)
---
src/nv_driver.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/nv_driver.c b/src/nv_driver.c
index e726292..4c40763 100644
--- a/src/nv_driver.c
+++ b/src/nv_driver.c
@@ -377,6 +377,7 @@ NVHasKMS(struct pci_device *pci_dev, struct xf86_platform_device *platform_dev)
case 0xf0:
case 0x100:
case 0x110:
+ case 0x120:
break;
default:
xf86DrvMsg(-1, X_ERROR, "Unknown
2008 Apr 06
1
[Bug 15374] New: Selecting team in pinch-hitter became much harder
http://bugs.freedesktop.org/show_bug.cgi?id=15374
Summary: Selecting team in pinch-hitter became much harder
Product: swfdec
Version: git
Platform: x86-64 (AMD64)
URL: http://www.break.com/games/pinch-hitter.html
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2010 Jan 06
3
Removal of Non-KMS support
I did a very quick pass at removing all the non-KMS support from the
DDX. It's tested on G80 but nowhere else currently, I thought some
discussion would be a good idea rather than just ripping it out :)
The non-KMS paths are messy, and lets face it, rotting badly. IMO the
KMS code is stable enough now that we can continue without the UMS
crutch, and indeed, the KMS code supports a lot more
2008 Apr 30
1
Pinch Hitter 1 is playable now, AOL Video progress
Hello!
With today's swfdec, Pinch Hitter 1 can actually be played:
http://www.addictinggames.com/pinchhitter.html
Pinch Hitter 2 still cannot get beyond the "namecheck":
http://www.addictinggames.com/pinchhitter2.html
Pinch Hitter 1 used to consume all memory in the system. AOL Video used
to do the same, but now it doesn't do anything bad (although it still
doesn't play
2006 Aug 24
9
[slightly offtopic] A small, fast Apache2.2 (if there is such a thing)
Hi.
I''m using Apache2.2 built from source + mod-proxy + ssl + svn.
Everything works fine but I''m sure you I could disable a ton of
modules during the build process and in httpd.conf to speed things up
and run a tighter memory footprint.
Has anyone bothered building Apache2.2 from source disabling all the
unneeded modules.
I am planning on going through the Apache docs but I
2015 Jul 07
3
RFC: drop glamor from nouveau ddx
Ben,
Looks like the reality is that glamor is just not hooked up properly
in the nouveau DDX. Mainly it's missing DRI2, which in turn means no
core GL contexts, and probably lots of other issues. While this could
probably be fixed somehow, I doubt there's any advantage to using the
nouveau DDX over something like modesetting nowadays.
How would you feel about dropping glamor support from
2015 Jul 07
2
RFC: drop glamor from nouveau ddx
On Tue, Jul 7, 2015 at 5:05 PM, Ben Skeggs <skeggsb at gmail.com> wrote:
> On 8 July 2015 at 06:06, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
>> Ben,
>>
>> Looks like the reality is that glamor is just not hooked up properly
>> in the nouveau DDX. Mainly it's missing DRI2, which in turn means no
>> core GL contexts, and probably lots of other
2009 Dec 11
4
low memory
On Fri, Dec 11, 2009 at 1:30 PM, Ben Skeggs <skeggsb at gmail.com> wrote:
> On Fri, 2009-12-11 at 13:23 +0100, Anders Eriksson wrote:
>> skeggsb at gmail.com said:
>> > It'd be useful to know of any cases out there where UMS is being used because
>> > KMS is failing, there's a couple of cases on RH bugzilla, but I don't recall
>> > the details
2007 Jan 24
3
System hangs at "Rebooting System" on VIA KM400 chipsets
Hello,
We have a number of systems running KM400 chipsets from VIA (Socket
A/462). Two different models have produced the same results -- DFI
KM400-MLV and MSI KM4M-V. When a /sbin/reboot or /sbin/shutdown -r now
is issued, the system does everything you would expect from a reboot,
but when it gets to Rebooting System, it hangs and requires a power cycle.
The logs do not indicate anything
2009 May 23
3
pre-nv50 KMS
Hi, all
I'm trying to implement kms for pre-nv50 in last cuples of days. My
current work[1] is based on the code of nv50 kms & ddx. Basicly, I
just blindly port the code to kernel land :). I think I'm getting very
close to working state, but it still doesn't work.
Current state:
1) vbios parser is synced with ddx
2) i2c works
3) Something shows on internel LVDS panel and