From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Sledge <john_sledget@yahoo.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: DRM Inquiry
Date: Fri, 25 May 2018 11:33:36 +0300 [thread overview]
Message-ID: <87k1rs2kyn.fsf@intel.com> (raw)
In-Reply-To: <1337918406.1091217.1527235879310@mail.yahoo.com>
On Fri, 25 May 2018, John Sledge <john_sledget@yahoo.com> wrote:
> Hi Jani,
> I seek 0-800 and here's what I get, all 11 0A in hex. Not sure if this is the brightness value of the display. I also did a test, when I disconnect the DP to the display and execute the dd commands, it would say error reading 'dev/drm_dp_aux1': Connection timed out. So I think my display setup is okay and the 11 0A values are really coming out from the display.
> Output in hex:11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A 11 0A ....
>
> int main(int argc, char **argv)
> { int ret = 0; int offset = 0; char call[100]; for(offset=0;offset<800;offset++) { sprintf(call,"dd if=/dev/drm_dp_aux1 bs=1 count=2 seek=%d >> out.txt",offset); ret = system(call); } return 0;}
Look, in this case dd is for debugging and testing on the command line,
to verify your approach before writing C. For your real thing, use the
open, read, write, lseek system calls. Don't call dd from C.
I've directed you to the right direction, and this is the right place to
ask about drm and kms related stuff. But for the basics, you might be
better off asking at stackoverflow or something.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-25 8:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <471791572.2287221.1526561265798.ref@mail.yahoo.com>
2018-05-17 12:47 ` DRM Inquiry John Sledge
2018-05-18 9:50 ` Jani Nikula
2018-05-24 4:19 ` John Sledge
2018-05-24 10:57 ` John Sledge
2018-05-24 11:23 ` Jani Nikula
2018-05-25 6:36 ` John Sledge
2018-05-25 6:55 ` Jani Nikula
2018-05-25 8:11 ` John Sledge
2018-05-25 8:33 ` Jani Nikula [this message]
2018-05-25 15:56 ` Taylor, Clinton A
2018-05-25 17:14 ` Jani Nikula
2018-06-11 10:16 ` RE: [Intel-gfx] " John Sledge
2018-06-11 11:36 ` Jani Nikula
2018-06-13 2:07 ` John Sledge
2018-06-13 7:07 ` Jani Nikula
2018-06-13 8:21 ` John Sledge
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=87k1rs2kyn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john_sledget@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).