Peter Stuge wrote:
Dongdong Deng wrote:
Removing the following harmless build warning to let compiler happy.
@@ -1170,7 +1170,8 @@ static void intel_sdvo_mode_set(struct drm_encoder
*encoder,
switch (sdvo_pixel_multiply) {
case 1: rate = SDVO_CLOCK_RATE_MULT_1X; break;
On Sun, 2010-10-31 at 15:32 +0100, Sedat Dilek wrote:
> On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> > On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> >> I made a 2nd wayland build:
> >>
> >
> > In my case, it was because mesa was compiled without --disable-gallium
> >
> > That
On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> I made a 2nd wayland build:
>
> OK, there is definitely a problem with $DISPLAY,
> if I use a different one (for example DISPLAY=:1.0), I get "failed to
> create compositor".
> If I want to use DISPLAY=:0.0, the error-message is "failed to
>
https://bugs.freedesktop.org/show_bug.cgi?id=30761
Jeff Cook changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=30761
Jeff Cook changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Sun, Oct 31, 2010 at 6:33 PM, Joe Perches wrote:
> Signed-off-by: Joe Perches
> ---
> ?drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c ? ? | ? ?2 +-
> ?drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | ? ?2 +-
> ?2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
On Sun, Oct 31, 2010 at 6:33 PM, Joe Perches wrote:
> Signed-off-by: Joe Perches
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 2 +-
> drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
Hi Dave,
This hasn't shown up in one of your branches, yet. Do you want me to
change something or was this patch simply lost somewhere?
Thanks, Daniel
On Wed, Oct 06, 2010 at 06:39:07PM +0200, Daniel Vetter wrote:
> From: Benjamin Herrenschmidt
>
> Without this, we attempt the handover too lat
reedesktop.org/archives/dri-devel/attachments/20101031/550339a3/attachment-0001.png>
-- next part --
$ mising_debian_pkgs="libffi-dev libxcb-dri2-0-dev libxcb-xfixes0-dev
libpoppler-glib-dev libx11-xcb-dev"
$ echo $mising_debian_pkgs
libffi-dev libxcb-dri2-0-de
Signed-off-by: Joe Perches
---
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
index a01c47d..29113c9 100
Joe Perches (4):
drivers/gpu/drm/vmwgfx: Fix k.alloc switched arguments
drivers/scsi/pmcraid.c: Fix k.alloc switched arguments
drivers/staging/udlfb/udlfb.c: Fix k.alloc switched arguments
scripts/checkpatch.pl: Add check for k.alloc GFP as first argument
drivers/gpu/drm/vmwgfx/vmwgfx_ldu
Signed-off-by: Joe Perches
---
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
index a01c47d..29113c9 100
Joe Perches (4):
drivers/gpu/drm/vmwgfx: Fix k.alloc switched arguments
drivers/scsi/pmcraid.c: Fix k.alloc switched arguments
drivers/staging/udlfb/udlfb.c: Fix k.alloc switched arguments
scripts/checkpatch.pl: Add check for k.alloc GFP as first argument
drivers/gpu/drm/vmwgfx/vmwgfx_ldu
On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
>> I made a 2nd wayland build:
>>
>> OK, there is definitely a problem with $DISPLAY,
>> if I use a different one (for example DISPLAY=:1.0), I get "failed to
>> create compositor".
>> If
On Sun, 2010-10-31 at 15:32 +0100, Sedat Dilek wrote:
> On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> > On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> >> I made a 2nd wayland build:
> >>
> >
> > In my case, it was because mesa was compiled without --disable-gallium
> >
> > That
On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
> I made a 2nd wayland build:
>
> OK, there is definitely a problem with $DISPLAY,
> if I use a different one (for example DISPLAY=:1.0), I get "failed to
> create compositor".
> If I want to use DISPLAY=:0.0, the error-message is "failed to
>
https://bugs.freedesktop.org/show_bug.cgi?id=31265
Summary: r600g: Adobe Flash Plugin crashes (Regression)
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=31265
Summary: r600g: Adobe Flash Plugin crashes (Regression)
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Before I forget, I switched als Window-Manager from KDE4 to Fluxbox to
see if the WM has influence on Wayland.
Here is what I see in VT-1 from where I started X via startx command
(I always bootup into runlevel-3):
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting defa
I made a 2nd wayland build:
OK, there is definitely a problem with $DISPLAY,
if I use a different one (for example DISPLAY=:1.0), I get "failed to
create compositor".
If I want to use DISPLAY=:0.0, the error-message is "failed to
initialize display" ending with a Segmentation fault.
Having a look
Hi Dave,
This hasn't shown up in one of your branches, yet. Do you want me to
change something or was this patch simply lost somewhere?
Thanks, Daniel
On Wed, Oct 06, 2010 at 06:39:07PM +0200, Daniel Vetter wrote:
> From: Benjamin Herrenschmidt
>
> Without this, we attempt the handover too lat
On Sun, Oct 31, 2010 at 3:21 PM, Peter Clifton wrote:
> On Sun, 2010-10-31 at 10:36 +0100, Sedat Dilek wrote:
>> I made a 2nd wayland build:
>>
>> OK, there is definitely a problem with $DISPLAY,
>> if I use a different one (for example DISPLAY=:1.0), I get "failed to
>> create compositor".
>> If
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #10 from pejakm 2010-10-31 07:26:04 PDT ---
Created an attachment (id=39924)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39924)
Zuma backtrace
I'm sorry, this is everything I could get. I know it's not the thing you need.
Bu
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #10 from pejakm 2010-10-31 07:26:04 PDT ---
Created an attachment (id=39924)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39924)
Zuma backtrace
I'm sorry, this is everything I could get. I know it's not the thing you need.
Bu
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #9 from Marek Olšák 2010-10-31 06:47:51 PDT ---
The logs are not backtraces. A backtrace is actually a call stack.
r300_get_swizzle_combined+0x21 is the first line of it.
Could you possibly use this HOWTO to get the whole backtrace?
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #9 from Marek Ol??k 2010-10-31 06:47:51 PDT
---
The logs are not backtraces. A backtrace is actually a call stack.
r300_get_swizzle_combined+0x21 is the first line of it.
Could you possibly use this HOWTO to get the whole backtrace?
https://bugs.freedesktop.org/show_bug.cgi?id=30693
darkbasic changed:
What|Removed |Added
Summary|[R600c KWin 4.5.2] Blur |[R600c KWin 4.5.2] Blur
|d
https://bugs.freedesktop.org/show_bug.cgi?id=30693
darkbasic changed:
What|Removed |Added
Summary|[R600c KWin 4.5.2] Blur |[R600c KWin 4.5.2] Blur
|d
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #8 from pejakm 2010-10-31 05:23:17 PDT ---
These are the compilation flags:
./autogen.sh --prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers=swrast,radeon,r200,r300,r600 \
--with-state-t
https://bugs.freedesktop.org/show_bug.cgi?id=31232
--- Comment #8 from pejakm 2010-10-31 05:23:17 PDT ---
These are the compilation flags:
./autogen.sh --prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers=swrast,radeon,r200,r300,r600 \
--with-state-t
WARN uses sometimes use KERN_ but mostly don't
have any prefix.
Change the WARN macros and the warn_slowpath function to preface
KERN_WARNING and remove all the KERN_ uses from WARN sites.
Neatening clean up of include/asm-generic/bug.h
Update WARN macros
Add KERN_WARNING to WARN output
Remove a
This reverts commit 6ec3d0c0e9c0c605696e91048eebaca7b0c36695.
When DDC documentation refers to "address 0xA0", it means what the Linux
I2C subsystem calls address 0x50. Both refer to the address used for
reading EDID over DDC.
I2C documentation often suffers from confusion over whether the addre
Before I forget, I switched als Window-Manager from KDE4 to Fluxbox to
see if the WM has influence on Wayland.
Here is what I see in VT-1 from where I started X via startx command
(I always bootup into runlevel-3):
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting defa
I made a 2nd wayland build:
OK, there is definitely a problem with $DISPLAY,
if I use a different one (for example DISPLAY=:1.0), I get "failed to
create compositor".
If I want to use DISPLAY=:0.0, the error-message is "failed to
initialize display" ending with a Segmentation fault.
Having a look
https://bugs.freedesktop.org/show_bug.cgi?id=31250
--- Comment #1 from Pavel Ondračka 2010-10-31 01:45:59 PDT
---
Created an attachment (id=39919)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39919)
menu with RADEON_NO_TCL=1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.
https://bugs.freedesktop.org/show_bug.cgi?id=31250
--- Comment #1 from Pavel Ondra?ka 2010-10-31 01:45:59
PDT ---
Created an attachment (id=39919)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39919)
menu with RADEON_NO_TCL=1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.
https://bugs.freedesktop.org/show_bug.cgi?id=31250
Summary: Unigine Sanctuary v2.2: menus are broken
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: med
https://bugs.freedesktop.org/show_bug.cgi?id=31250
Summary: Unigine Sanctuary v2.2: menus are broken
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: med
38 matches
Mail list logo
