On Mon, 27 Jan 2014, Daniel Vetter wrote:
> On Mon, Jan 27, 2014 at 11:05:47AM -0500, Alan Stern wrote:
> > On Mon, 27 Jan 2014, Daniel Vetter wrote:
> >
> > > > By the way, I tried getting an up-to-date version of your
> > > > drm-intel-nightly branch, and ended up with the following:
> > > >
On Mon, Jan 27, 2014 at 11:05:47AM -0500, Alan Stern wrote:
> On Mon, 27 Jan 2014, Daniel Vetter wrote:
>
> > > By the way, I tried getting an up-to-date version of your
> > > drm-intel-nightly branch, and ended up with the following:
> > >
> > > $ git clone --depth 1 -b drm-intel-nightly
> > >
On Mon, 27 Jan 2014, Daniel Vetter wrote:
> > By the way, I tried getting an up-to-date version of your
> > drm-intel-nightly branch, and ended up with the following:
> >
> > $ git clone --depth 1 -b drm-intel-nightly
> > http://cgit.freedesktop.org/~danvet/drm-intel/
> > Cloning into 'drm-inte
On Mon, Jan 27, 2014 at 10:30:11AM -0500, Alan Stern wrote:
> On Mon, 27 Jan 2014, Daniel Vetter wrote:
>
> > On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern
> > wrote:
> > > Don't bother. I'll redo it using the drm-intel-nightly branch, but I
> > > won't have time for a few days.
> >
> > My apolo
On Mon, 27 Jan 2014, Daniel Vetter wrote:
> On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern wrote:
> > Don't bother. I'll redo it using the drm-intel-nightly branch, but I
> > won't have time for a few days.
>
> My apologies for the delay in getting around to this. Can you please
> test the patch i
On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern wrote:
> Don't bother. I'll redo it using the drm-intel-nightly branch, but I
> won't have time for a few days.
My apologies for the delay in getting around to this. Can you please
test the patch i've just posted?
http://patchwork.freedesktop.org/patc
On Tue, 14 Jan 2014, Daniel Vetter wrote:
> On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
> > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> >
> > > On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> > > > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> > > >
> > > > > On Wed, Ja
On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
> > On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> > > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> > >
> > > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > > >
On Wed, 8 Jan 2014, Daniel Vetter wrote:
> On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> > On Wed, 8 Jan 2014, Daniel Vetter wrote:
> >
> > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > > > On Tue, 7 Jan 2014, Daniel Vetter wrote:
> > > >
> > > > > I really wa
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
> > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > > On Tue, 7 Jan 2014, Daniel Vetter wrote:
> > >
> > > > I really want users to report these issues, and excessive WARNs see
On Wed, 8 Jan 2014, Daniel Vetter wrote:
> On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > On Tue, 7 Jan 2014, Daniel Vetter wrote:
> >
> > > I really want users to report these issues, and excessive WARNs seems
> > > to be the only way to get those reports. Please boot with
> > >
On Tue, Jan 7, 2014 at 7:50 PM, Alan Stern wrote:
> After all, it's not like there's anything I can do to fix the hardware,
> is there? And it doesn't look like the pipe state mismatch is going to
> go away by itself. Or is this a genuine, fixable, software bug?
These are genuine software bugs
12 matches
Mail list logo
