From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Playing with the idea of pulling kernel code into i-g-t
Date: Wed, 5 Jun 2013 23:18:55 +0300 [thread overview]
Message-ID: <20130605201854.GL5004@intel.com> (raw)
In-Reply-To: <1370429978-4288-1-git-send-email-damien.lespiau@intel.com>
On Wed, Jun 05, 2013 at 11:59:37AM +0100, Damien Lespiau wrote:
>
> I played a bit with this as that's something thas has been floating around for
> a bit and could be used for:
> - unit testing kernel functions (eg. PLL computations)
> - reuse off some code (intel_reg.h, sideband, device_info struct, ...)
> - Ville wanted to fuzzy test the EDID code (and has a branch somewhere IIRC)
So far I always forgot to push it anywhere. Now it's here:
git://gitorious.org/vsyrjala/drm_edid_test.git
It's just a copy drm_edid.c and some other files, a bunch of stubs make
it compile, and a small program that reads in an edid and prints a bunch
of stuff drm_edid.c managed to parse from it.
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2013-06-05 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 10:59 Playing with the idea of pulling kernel code into i-g-t Damien Lespiau
2013-06-05 10:59 ` [RFC] lib: Import intel_sideband.c from the kernel Damien Lespiau
2013-06-05 20:18 ` Ville Syrjälä [this message]
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=20130605201854.GL5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox