Re: [Intel-gfx] (no subject)

2023-06-20 Thread philly j
Listen, here’s the problem I’m having guys and I need someone to reply back to me. Because I wrote to FSF and they wrote me right back and I join their and I have no problem with free software and complain but I don’t exactly know what you want me to do and I don’t have “git” on my

Re: [Intel-gfx] (no subject)

2022-05-19 Thread Matthew Auld
On Thu, 19 May 2022 at 10:55, Christian König wrote: > > Just sending that out once more to intel-gfx to let the CI systems take > a look. If all went well it should normally appear at [1][2], if CI was able to pick up the series. Since it's not currently there, I assume it's temporarily stuck i

Re: [Intel-gfx] (no subject)

2020-02-26 Thread Ville Syrjälä
On Wed, Feb 26, 2020 at 03:56:36PM +0100, Linus Walleij wrote: > On Wed, Feb 26, 2020 at 3:34 PM Ville Syrjälä > wrote: > > On Wed, Feb 26, 2020 at 01:08:06PM +0100, Linus Walleij wrote: > > > On Wed, Feb 26, 2020 at 12:57 PM Ville Syrjälä > > > wrote: > > > > On Tue, Feb 25, 2020 at 10:52:25PM +

Re: [Intel-gfx] (no subject)

2020-02-26 Thread Linus Walleij
On Wed, Feb 26, 2020 at 3:34 PM Ville Syrjälä wrote: > On Wed, Feb 26, 2020 at 01:08:06PM +0100, Linus Walleij wrote: > > On Wed, Feb 26, 2020 at 12:57 PM Ville Syrjälä > > wrote: > > > On Tue, Feb 25, 2020 at 10:52:25PM +0100, Linus Walleij wrote: > > > > > > I have long suspected that a whole b

Re: [Intel-gfx] (no subject)

2020-02-26 Thread Ville Syrjälä
On Wed, Feb 26, 2020 at 01:08:06PM +0100, Linus Walleij wrote: > On Wed, Feb 26, 2020 at 12:57 PM Ville Syrjälä > wrote: > > On Tue, Feb 25, 2020 at 10:52:25PM +0100, Linus Walleij wrote: > > > > I have long suspected that a whole bunch of the "simple" displays > > > are not simple but contains a

Re: [Intel-gfx] (no subject)

2020-02-26 Thread Linus Walleij
On Wed, Feb 26, 2020 at 12:57 PM Ville Syrjälä wrote: > On Tue, Feb 25, 2020 at 10:52:25PM +0100, Linus Walleij wrote: > > I have long suspected that a whole bunch of the "simple" displays > > are not simple but contains a display controller and memory. > > That means that the speed over the link

Re: [Intel-gfx] (no subject)

2015-06-18 Thread Dave Gordon
On 17/06/15 12:04, Daniel Vetter wrote: > On Fri, Jun 12, 2015 at 09:25:36PM +0100, Dave Gordon wrote: >> Updated version split into two. The first tidies up the _ring_prepare() >> functions and removes the corner case where we might have had to wait >> twice; the second is a temporary workaround t

Re: [Intel-gfx] (no subject)

2015-06-17 Thread Jani Nikula
On Wed, 17 Jun 2015, Daniel Vetter wrote: > On Fri, Jun 12, 2015 at 09:25:36PM +0100, Dave Gordon wrote: >> Updated version split into two. The first tidies up the _ring_prepare() >> functions and removes the corner case where we might have had to wait >> twice; the second is a temporary workaroun

Re: [Intel-gfx] (no subject)

2015-06-17 Thread Daniel Vetter
On Fri, Jun 12, 2015 at 09:25:36PM +0100, Dave Gordon wrote: > Updated version split into two. The first tidies up the _ring_prepare() > functions and removes the corner case where we might have had to wait > twice; the second is a temporary workaround to solve a kernel OOPS that > can occur if log

Re: [Intel-gfx] (no subject)

2014-01-06 Thread Daniel Vetter
On Mon, Dec 30, 2013 at 07:59:49AM +0530, Oravil Nair wrote: > Hi, > > i915_gem_object_pin(), during i915 driver create, seems to write to the > memory written by BIOS. Where can the start address be specified to > allocate memory so that the memory written by BIOS is not overwritten at > initiali

Re: [Intel-gfx] (no subject)

2013-04-03 Thread Daniel Vetter
Hi all, Two things: - Please _always_ include a public mailing list when reporting bugs, your dear maintainer sometimes slacks off. - We need to see the error_state before we can assess what kind of hang you have (it's like gettting a SIGSEGV for a normal program, no two gpu hangs are the same ...