Jiri Kosina writes:
> On Mon, 21 Oct 2013, Egbert Eich wrote:
>
> > > On Thu, 3 Oct 2013, Daniel Vetter wrote:
> > >
> > > > Can you please attach full dmesg from boot up to the first WARN with
> > > > drm.debug=0xe? This really shouldn'
Jiri Kosina writes:
On Mon, 21 Oct 2013, Egbert Eich wrote:
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
A bit
Hi Jiri,
Just found your email, it got missed do to a temporary inaccessibility to
my email.
Jiri Kosina writes:
> On Thu, 3 Oct 2013, Daniel Vetter wrote:
>
> > Can you please attach full dmesg from boot up to the first WARN with
> > drm.debug=0xe? This really shouldn't happen and
Hi Jiri,
Just found your email, it got missed do to a temporary inaccessibility to
my email.
Jiri Kosina writes:
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a
Alan Cox writes:
> On Llu, 2005-01-17 at 14:29, Egbert Eich wrote:
> > OK, sounds promising. The changed Xserver pieces are in HEAD of the
> > X.Org tree. I'll see that I make the necessary adjustments to have
> > a soft detection if you can give me a version number of
Alan Cox writes:
On Llu, 2005-01-17 at 14:29, Egbert Eich wrote:
OK, sounds promising. The changed Xserver pieces are in HEAD of the
X.Org tree. I'll see that I make the necessary adjustments to have
a soft detection if you can give me a version number of the kernel
which will have
Alan Cox writes:
> On Llu, 2005-01-17 at 09:07, Egbert Eich wrote:
> > Can you point me to these reports?
> > I tested with a couple chipsets here and didn't find any problems.
>
> I'll take a dig. The ones I've got are for 2.4 so relate to old code.
>
> >
[Please leave me in Cc: as I'm not subscribed to this list]
Alan Cox writes:
> On Maw, 2005-01-11 at 14:28, Egbert Eich wrote:
> > I'm fully aware that in the long run we will need to look into a new
> > driver model for graphics where no two instances fight over who gets
>
[Please leave me in Cc: as I'm not subscribed to this list]
Alan Cox writes:
On Maw, 2005-01-11 at 14:28, Egbert Eich wrote:
I'm fully aware that in the long run we will need to look into a new
driver model for graphics where no two instances fight over who gets
register access
Alan Cox writes:
On Llu, 2005-01-17 at 09:07, Egbert Eich wrote:
Can you point me to these reports?
I tested with a couple chipsets here and didn't find any problems.
I'll take a dig. The ones I've got are for 2.4 so relate to old code.
We could check for the kernel version
10 matches
Mail list logo
