From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] libmemdraw bug?
Date: Fri, 18 Jan 2019 18:50:58 +0100 [thread overview]
Message-ID: <BC8FA9C8F90ACD92A741C21F84CD8B15@felloff.net> (raw)
In-Reply-To: 29BD3DBBC18C327BB8A22649EADF6E77@wopr.sciops.net
that is documented behaviour. memimages have the scanlines (32bit) word padded.
that means, a scanline will start on a word aligned address... and the end of
a scanline is padded up to full word in memimage memory. while loadimage()'s data
argument is byte aligned... see allocimage(2).
--
cinap
next reply other threads:[~2019-01-18 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 17:50 cinap_lenrek [this message]
2019-01-18 18:23 qwx
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=BC8FA9C8F90ACD92A741C21F84CD8B15@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).