All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/dumb_buffer: Tests for creation
Date: Thu, 28 Nov 2019 17:49:22 +0530	[thread overview]
Message-ID: <20191128121922.GA22156@intel.com> (raw)
In-Reply-To: <157494144413.7216.543982190380419945@skylake-alporthouse-com>

On 2019-11-28 at 11:44:04 +0000, Chris Wilson wrote:
> Quoting Ramalingam C (2019-11-28 11:35:36)
> > On 2019-11-28 at 16:57:33 +0530, Ramalingam C wrote:
> > > Tests are developed for dumb buffer creation.
> > > 
> > > v2:
> > >   Made as a generic test for dumb buffer creation [Chris]
> > Chris,
> > 
> > As you have mentioned I have made this as generic test.
> 
> We have a different idea about generic :)
> 
> gem_write/gem_read are i915 ioctls.
> 
> We want to only use DUMB_CREATE, DUMB_MMAP, DUMB_DESTROY and then it
> will work with DRIVER_ANY.
Except DUMP_MMAP used all other stuff... missed that gem_read is using
DRM_IOCTL_I915_GEM_PREAD. I tried with dumb_mmap + mem_cpy instead of gem_read. But failed there for unknown reasons.

Will fix it and send the acceptable generic form :)

-Ram

> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-11-28 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 11:27 [igt-dev] [PATCH i-g-t v2] tests/dumb_buffer: Tests for creation Ramalingam C
2019-11-28 11:35 ` Ramalingam C
2019-11-28 11:44   ` Chris Wilson
2019-11-28 12:19     ` Ramalingam C [this message]
2019-11-28 12:30       ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191128121922.GA22156@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.