http://bugs.freedesktop.org/show_bug.cgi?id=23379
Maciej Piechotka changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Was it necessary?
ATI and Nvidia both provide a compact archive with a kernel module, xorg
driver, and
OpenGL libraries.
Why couldn't the Intel developers?
I can load the latest Nvidia driver on several old kernel versions and
Xorg versions.
Yet it's a packaged deal with the new Intel offerin
> Was it necessary?
Yes.
>
> Intel needs to hire Alan Cox. At least he had the balls to throw in the
> towel.
they did.
no, thank you.
Dave.
>
> Thanks a lot .
>
>
>
> --
> Let Crystal Reports handle the report
Hello.
I have started to make linux-solo compilable with latest dri interfaces.
Attached is patch.
It compiles (needs a little tricks to get server/intel_dri.c compiled).
But than it gets all linked and installed.
I tried to run it. And here is error.
[miniglx] probed chipset 0x2a02
got MMIOAdd
On Mon, Aug 24, 2009 at 09:22:58PM -0400, squirrl wrote:
> Linus needs to rip out the GEM subsystem. Xorg needs to remove your
> contributions.
>
> Mesa should seriously consider stepping back their code base.
>
> Honestly it'll be 2011 before we got anything usable the way it is now.
>
> Inte
http://bugs.freedesktop.org/show_bug.cgi?id=23504
Summary: KDE's Kubrick has problems with xf86-video-ati driver
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medi
On Tue, 2009-08-25 at 12:12 +0200, Peter Hanzel wrote:
> Hello.
>
> I have started to make linux-solo compilable with latest dri interfaces.
> Attached is patch.
> It compiles (needs a little tricks to get server/intel_dri.c compiled).
> But than it gets all linked and installed.
>
> I tried to r
http://bugs.freedesktop.org/show_bug.cgi?id=23504
--- Comment #1 from Pauli 2009-08-25 08:03:41 PST ---
I can't reproduce this with that latest git driver in DRI2 mode.
Can you give more details how to reproduce this? I see a problem that Kubrick
is somehow very slow to run and takes a lot
http://bugs.freedesktop.org/show_bug.cgi?id=23513
Summary: Radeon APG KMS don't work or is too slow.
Product: DRI
Version: XOrg CVS
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: high
http://bugs.freedesktop.org/show_bug.cgi?id=23240
--- Comment #3 from Nicolai Hähnle 2009-08-25 12:30:26
PST ---
Some additional information might be useful, especially: What hardware are you
using? Consider attaching output of lspci, and your Xorg.0.log.
Also, what about dmesg output *bef
http://bugs.freedesktop.org/show_bug.cgi?id=23393
--- Comment #1 from Nicolai Hähnle 2009-08-25 13:42:40
PST ---
Is your version of Mesa from recent Git master? I remember fixing the exact
same symptom (though it might have been caused by something else) not so long
ago.
--
Configure bug
http://bugs.freedesktop.org/show_bug.cgi?id=23504
--- Comment #2 from Johannes Obermayr 2009-08-25
14:34:45 PST ---
Oh sorry - I forgot... I only try starting Kubrick and then it crashes...
I did a rpmbuild --rebuild for libdrm-2.4.99-9.1.src.rpm and
Mesa-7.5.99-16.1.src.rpm (above source)
http://bugs.freedesktop.org/show_bug.cgi?id=23393
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Tue, 25 Aug 2009, mailing54 wrote:
> Linus Torvalds schrieb:
> > Are you using the same config? It sounds very much like your -rc7 problems
> > are due to the Intel KMS (kernel mode setting) driver, which I know has had
> > problems on at least Mac Mini's. And I wonder if the -rc6 kernel deb
http://bugs.freedesktop.org/show_bug.cgi?id=23240
--- Comment #5 from Stephen E. Baker 2009-08-25 15:21:22
PST ---
Created an attachment (id=28909)
--> (http://bugs.freedesktop.org/attachment.cgi?id=28909)
Current Xorg log
Since filing this bug I've downgraded back to mesa 7.3 and xf86-vi
http://bugzilla.kernel.org/show_bug.cgi?id=14060
Summary: oops: sysfs_remove_link and i915
Product: Drivers
Version: 2.5
Kernel Version: 2.6.31-rc7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
On Tue, 25 Aug 2009 22:23:05 GMT
bugzilla-dae...@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14060
>
>Summary: oops: sysfs_remove_link and i915
>Product: Drivers
>Version: 2.5
> Kernel Version: 2.6.31-rc7
> Platform: Al
http://bugs.freedesktop.org/show_bug.cgi?id=23393
--- Comment #3 from Brian Paul 2009-08-25
15:15:55 PST ---
Should that fix get cherry-picked to the 7.5 branch?
I'm planning on a 7.5.1 release soon...
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You
http://bugs.freedesktop.org/show_bug.cgi?id=23240
--- Comment #4 from Stephen E. Baker 2009-08-25 15:16:39
PST ---
Created an attachment (id=28908)
--> (http://bugs.freedesktop.org/attachment.cgi?id=28908)
lspci output
My computer is a Lenovo ThinkPad T60 with an ATI Radeon X1400
--
Co
This message contains a list of some regressions from 2.6.30, for which there
are no fixes in the mainline I know of. If any of them have been fixed already,
please let me know.
If you know of any other unresolved regressions from 2.6.30, please let me know
either and I'll add them to the list.
On Tue, 2009-08-25 at 15:07 -0700, Linus Torvalds wrote:
>
> On Tue, 25 Aug 2009, mailing54 wrote:
>
> > Linus Torvalds schrieb:
> > > Are you using the same config? It sounds very much like your -rc7 problems
> > > are due to the Intel KMS (kernel mode setting) driver, which I know has
> > > ha
On Mon, 03 Aug 2009 08:30:57 +0200
"David Müller (ELSOFT AG)" wrote:
> Hello
>
> Any news regarding this issue?
I don't see the patch anymore, but if the VBT pin info is correct we
should probably be using it more broadly.
--
Jesse Barnes, Intel Open Source Technology Center
On Mon, 13 Jul 2009 13:24:35 +0200
"David Müller (ELSOFT AG)" wrote:
> Hello
>
> What about a patch like the attached one; would this be acceptable?
Ah here it is; I think Ling is off doing other things...
I think we can probably expand it to include other chipsets. We can
probably assume its
This message contains a list of some regressions introduced between 2.6.29 and
2.6.30, for which there are no fixes in the mainline I know of. If any of them
have been fixed already, please let me know.
If you know of any other unresolved regressions introduced between 2.6.29
and 2.6.30, please l
http://bugs.freedesktop.org/show_bug.cgi?id=23504
--- Comment #3 from Pauli 2009-08-25 17:51:42 PST ---
Can you try latest version from git?
commit ce7ed63f0c2f5cb1c030f73a5d8f6544eaac0f81 did merge fix or that space
check problem. So no surprise that I can't trigger it any more in git vers
http://bugs.freedesktop.org/show_bug.cgi?id=23402
--- Comment #9 from David Ronis 2009-08-25 18:05:27
PST ---
Created an attachment (id=28910)
--> (http://bugs.freedesktop.org/attachment.cgi?id=28910)
Better backtrace
This is a case the SIGSEGV'd. I'd updated/rebuilt drm and mesa as well
On 2009.08.25 15:33:57 -0700, Eric Anholt wrote:
> > However, the problem remains that KMS gets the output wrong, in ways that
> > clearly X does not. Eric - it's clearly not just Mac Mini and my
> > experimental machine that have problems, but also a Macbook 2.1.
> >
> > I wonder why the Intel
http://bugzilla.kernel.org/show_bug.cgi?id=14060
Zhang Rui changed:
What|Removed |Added
Status|NEW |NEEDINFO
Component|Video(DRI)
From: Dave Airlie
This adds code to the drm_mm to talk to debugfs, and adds
support to radeon to add the VRAM and GTT mm lists to debugfs.
I tested with spinlock debugging and it doesn't give out.
changes since v2:
use proper locking.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/drm_mm.c
http://bugs.freedesktop.org/show_bug.cgi?id=23402
--- Comment #10 from David Ronis 2009-08-25 20:31:17
PST ---
Created an attachment (id=28911)
--> (http://bugs.freedesktop.org/attachment.cgi?id=28911)
Better backtrace, different crash
Here's a better backtrace, different from 28910
--
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
>
> > In my experience, the BIOS setup doesn't reflect what outputs should be
> > used at runtime, and certainly not the correct configuration of the
> > enabled outputs. For example, if we went to this, the giant monitor
> > attached to my laptop that I a
On Wed, Aug 26, 2009 at 1:33 PM, Linus
Torvalds wrote:
>
>
> On Wed, 26 Aug 2009, Zhenyu Wang wrote:
>>
>> > In my experience, the BIOS setup doesn't reflect what outputs should be
>> > used at runtime, and certainly not the correct configuration of the
>> > enabled outputs. For example, if we wen
On 2009.08.25 20:33:32 -0700, Linus Torvalds wrote:
> On Wed, 26 Aug 2009, Zhenyu Wang wrote:
> >
> > > In my experience, the BIOS setup doesn't reflect what outputs should be
> > > used at runtime, and certainly not the correct configuration of the
> > > enabled outputs. For example, if we went t
On Wed, 26 Aug 2009, Dave Airlie wrote:
> >
> > If you actually detected things _right_, none of this would be an issue.
> > But you don't. And you seem to have a really hard time even admitting
> > that. You try to re-detect things, and you SCREW UP.
>
> This isn't anything to do with redetecti
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
>
> We can't depend on any BIOS display config as you noted before our driver.
But you do. You depend on the even _less_ reliable existence of a VBT
table.
> And our driver does more flexible config than VBIOS does.
If by "flexible" you mean "doesn't w
On Wed, Aug 26, 2009 at 2:13 PM, Linus
Torvalds wrote:
>
>
> On Wed, 26 Aug 2009, Dave Airlie wrote:
>> >
>> > If you actually detected things _right_, none of this would be an issue.
>> > But you don't. And you seem to have a really hard time even admitting
>> > that. You try to re-detect things,
On Wed, Aug 26, 2009 at 4:26 PM, Eric Anholt wrote:
> On Wed, 2009-08-26 at 13:47 +1000, Dave Airlie wrote:
>> On Wed, Aug 26, 2009 at 1:33 PM, Linus
>> Torvalds wrote:
>> >
>> >
>> > On Wed, 26 Aug 2009, Zhenyu Wang wrote:
>> >>
>> >> > In my experience, the BIOS setup doesn't reflect what outputs
37 matches
Mail list logo
