On Wed, Jun 11, 2014 at 11:32:29AM +0200, Daniel Vetter wrote:
> On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
> >
> > On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> > > On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> > > > On Sun, Jun 08,
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
> (resending because Daniel was dropped from the reply list - I don't know
> why)
>
> On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> > On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> > > On Sun,
(resending because Daniel was dropped from the reply list - I don't know
why)
On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> > On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
> > > With a tree
(resending because Daniel was dropped from the reply list - I don't know
why)
On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
With a tree that is
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
(resending because Daniel was dropped from the reply list - I don't know
why)
On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
On Sun, Jun 08,
On Wed, Jun 11, 2014 at 11:32:29AM +0200, Daniel Vetter wrote:
On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
On Sun, Jun 08, 2014 at
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
> > With a tree that is close to 3.15 final I'm regularly seeing the
> > following on my EeePC 900 when starting ioquake3:
> >
> > [drm:intel_pipe_config_compare]
On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
> With a tree that is close to 3.15 final I'm regularly seeing the
> following on my EeePC 900 when starting ioquake3:
>
> [drm:intel_pipe_config_compare] *ERROR* mismatch in
> gmch_pfit.lvds_border_bits (expected 32768, found 0)
On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
With a tree that is close to 3.15 final I'm regularly seeing the
following on my EeePC 900 when starting ioquake3:
[drm:intel_pipe_config_compare] *ERROR* mismatch in
gmch_pfit.lvds_border_bits (expected 32768, found 0)
Hm,
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
With a tree that is close to 3.15 final I'm regularly seeing the
following on my EeePC 900 when starting ioquake3:
[drm:intel_pipe_config_compare] *ERROR*
With a tree that is close to 3.15 final I'm regularly seeing the
following on my EeePC 900 when starting ioquake3:
[drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits
(expected 32768, found 0)
[ cut here ]
WARNING: CPU: 0 PID: 1594 at
With a tree that is close to 3.15 final I'm regularly seeing the
following on my EeePC 900 when starting ioquake3:
[drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits
(expected 32768, found 0)
[ cut here ]
WARNING: CPU: 0 PID: 1594 at
12 matches
Mail list logo