Hi Alan,
We had a report [1] of a machine with a Cedarview chip in it not being
able to have the backlight level adjusted with the hardware function
keys in F17. Matthew suggested that gma500 needs to work with opregion
and the reporter (CC'd) tried a rawhide kernel based on
v3.5-rc6-186-gac7d181
FB console is OK, when switching to VT7, there is no KDM prompt.
Instead looping messages appear:
Failed to idle channel 1
0x2634 != chid: 0x0011
PFIFO: unknown status 0x0100
PFIFO - playlist update failed
Failed to idle channel 2
...
Hi Inki,
how urgent is this? Linus isn't really up for something this large
post -rc7, major regressions or oops fixes only at this point.
If its not urgent can we just stick it in -next and if needs be you
can get stable on required patches.
Dave.
> Please pull from
> git://git.infrade
Hi Dave,
> -Original Message-
> From: Dave Airlie [mailto:airl...@gmail.com]
> Sent: Wednesday, July 18, 2012 5:14 PM
> To: Inki Dae
> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
> kyungmin.p...@samsung.com; sw0312@samsung.com
> Subject: Re: [GIT PULL] updated exynos-drm-fix
Hi Dave,
as promised here is the second pull request for -next:
git://people.freedesktop.org/~deathsimple/linux next
It contains the following changes:
Alex Deucher (16):
drm/radeon: update ib_execute for SI (v2)
drm/radeon: remove radeon_ring_index()
drm/radeon: update rp
On Tue, Jul 17, 2012 at 11:56 AM, Laurent Pinchart
wrote:
> The passed mode must not be modified by the operation, make it const.
>
> Signed-off-by: Laurent Pinchart
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/ast/ast_mode.c |6 +++---
> drivers/gpu/drm/cirrus/cirr
On 06/27/2012 03:30 PM, Sascha Hauer wrote:
> Many embedded drm devices do not have a IOMMU and no dedicated
> memory for graphics. These devices use CMA (Contiguous Memory
> Allocator) backed graphics memory. This patch provides helper
> functions to be able to share the code. The code technically
Hi Dave,
Can you please pick this one up for -next? There are a few other issues
where the fb helper is a bit too intimate with the crtc helper (i.e. it
depends upon callbacks and behaviour only provided when using the crtc
helpers). But this one here is the only one I can't work around in i915.ko
Actually including Dave on the recipient list might work bettter ;-)
On Wed, Jul 18, 2012 at 05:49:22PM +0200, Daniel Vetter wrote:
> Hi Dave,
>
> Can you please pick this one up for -next? There are a few other issues
> where the fb helper is a bit too intimate with the crtc helper (i.e. it
> de
On Sun, Jun 24, 2012 at 07:57:24PM +0200, Daniel Vetter wrote:
> Userspace uses long in quite a few places more than the kernel. Which
> gives me neat proof that I'm the only guy on this side of the galaxy
> who ever tried to run glxgears on a 64bit machine with sis graphics on
> linux.
>
> Note t
On Fri, Jun 15, 2012 at 10:32:20AM +0100, Chris Wilson wrote:
> On Fri, 15 Jun 2012 11:01:22 +0200, Daniel Vetter
> wrote:
> > Ok, this requires quite a dance to actually hit:
> > 1) We plug in a 2nd screen, enable it in both X and (by vt-switching)
> > in the fbcon.
> > 2) We disable that screen
On Thu, Jun 14, 2012 at 12:24:55PM +0200, Daniel Vetter wrote:
> Hi all,
>
> Blind me has finally found the bug that killed via - dropping locks again in
> the
> early exit path is highly advised ;-)
>
> The big part of this series is cleaning up buffer handling in the
> teardown/lastclose path:
Hi Dave,
This one plus the pci_disable_device and related error path cleanups are
part of the series to move the agp setup into drivers.
I've implemented your suggestion to work around the midlayer, so drm/i915
doesn't block for this at all. But I still think this is the right way to
solve this.
If a connector has had its state forced by the user, there's no point
polling for changes; the force state overrides the detected state.
Simply skip the connector if it's been forced, and don't bother setting up
the periodic poll if the only connectors that need it are forced.
Signed-off-by: Simo
This adds interfaces for the X driver to use to create a
prime handle from a buffer, and create a bo from a handle.
v2: use Chris's suggested naming (well from at least for consistency)
v3: git commit --amend fail
v4: fix as per Chris's suggestions, group assignments, add get tiling
Signed-off-by
https://bugs.freedesktop.org/show_bug.cgi?id=49030
Alexandre Demers changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Wed, Jul 18, 2012 at 1:01 AM, Laurent Pinchart
wrote:
> On Wednesday 30 May 2012 19:12:11 Laurent Pinchart wrote:
>> On Wednesday 30 May 2012 13:29:06 Michel D?nzer wrote:
>> > On Mit, 2012-05-30 at 00:58 +0200, Laurent Pinchart wrote:
>> > > DRM_IOCTL_MODESET_CTL must only be used for UMS driv
Hi David,
On Tuesday 17 July 2012 14:23:18 David Herrmann wrote:
> On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox wrote:
> >> The main issue is that fbdev has been designed with the implicit
> >> assumption that an fbdev driver will always own the graphics memory it
> >> uses. All components in the st
Hello Dave,
Please pull from
git://git.infradead.org/users/kmpark/linux-samsung exynos-drm-fixes
these patch sets are based on git repository below:
git://people.freedesktop.org/~airlied/linux.git drm-fixes
commit-id: a3928c6b5f43bcd561802b52049b6024b8da675f
this pull req
FB console is OK, when switching to VT7, there is no KDM prompt.
Instead looping messages appear:
Failed to idle channel 1
0x2634 != chid: 0x0011
PFIFO: unknown status 0x0100
PFIFO - playlist update failed
Failed to idle channel 2
...
Hi Inki,
how urgent is this? Linus isn't really up for something this large
post -rc7, major regressions or oops fixes only at this point.
If its not urgent can we just stick it in -next and if needs be you
can get stable on required patches.
Dave.
> Please pull from
> git://git.infrade
Hi Dave,
> -Original Message-
> From: Dave Airlie [mailto:airlied at gmail.com]
> Sent: Wednesday, July 18, 2012 5:14 PM
> To: Inki Dae
> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
> kyungmin.park at samsung.com; sw0312.kim at samsung.com
> Subject: Re: [GIT PULL] updated
Hi Dave,
as promised here is the second pull request for -next:
git://people.freedesktop.org/~deathsimple/linux next
It contains the following changes:
Alex Deucher (16):
drm/radeon: update ib_execute for SI (v2)
drm/radeon: remove radeon_ring_index()
drm/radeon: update
On Tue, Jul 17, 2012 at 11:56 AM, Laurent Pinchart
wrote:
> The passed mode must not be modified by the operation, make it const.
>
> Signed-off-by: Laurent Pinchart
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/ast/ast_mode.c |6 +++---
> drivers/gpu/drm/cirrus/cirr
On 06/27/2012 03:30 PM, Sascha Hauer wrote:
> Many embedded drm devices do not have a IOMMU and no dedicated
> memory for graphics. These devices use CMA (Contiguous Memory
> Allocator) backed graphics memory. This patch provides helper
> functions to be able to share the code. The code technically
Hi Dave,
Can you please pick this one up for -next? There are a few other issues
where the fb helper is a bit too intimate with the crtc helper (i.e. it
depends upon callbacks and behaviour only provided when using the crtc
helpers). But this one here is the only one I can't work around in i915.ko
Actually including Dave on the recipient list might work bettter ;-)
On Wed, Jul 18, 2012 at 05:49:22PM +0200, Daniel Vetter wrote:
> Hi Dave,
>
> Can you please pick this one up for -next? There are a few other issues
> where the fb helper is a bit too intimate with the crtc helper (i.e. it
> de
On Sun, Jun 24, 2012 at 07:57:24PM +0200, Daniel Vetter wrote:
> Userspace uses long in quite a few places more than the kernel. Which
> gives me neat proof that I'm the only guy on this side of the galaxy
> who ever tried to run glxgears on a 64bit machine with sis graphics on
> linux.
>
> Note t
On Fri, Jun 15, 2012 at 10:32:20AM +0100, Chris Wilson wrote:
> On Fri, 15 Jun 2012 11:01:22 +0200, Daniel Vetter
> wrote:
> > Ok, this requires quite a dance to actually hit:
> > 1) We plug in a 2nd screen, enable it in both X and (by vt-switching)
> > in the fbcon.
> > 2) We disable that screen
On Thu, Jun 14, 2012 at 12:24:55PM +0200, Daniel Vetter wrote:
> Hi all,
>
> Blind me has finally found the bug that killed via - dropping locks again in
> the
> early exit path is highly advised ;-)
>
> The big part of this series is cleaning up buffer handling in the
> teardown/lastclose path:
Hi Dave,
This one plus the pci_disable_device and related error path cleanups are
part of the series to move the agp setup into drivers.
I've implemented your suggestion to work around the midlayer, so drm/i915
doesn't block for this at all. But I still think this is the right way to
solve this.
If a connector has had its state forced by the user, there's no point
polling for changes; the force state overrides the detected state.
Simply skip the connector if it's been forced, and don't bother setting up
the periodic poll if the only connectors that need it are forced.
Signed-off-by: Simo
32 matches
Mail list logo
