* Re: [9front] libmemdraw bug?
@ 2019-01-18 18:23 qwx
0 siblings, 0 replies; 2+ messages in thread
From: qwx @ 2019-01-18 18:23 UTC (permalink / raw)
To: 9front
That explains it, thanks!
qwx
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9front] libmemdraw bug?
@ 2019-01-18 17:50 cinap_lenrek
0 siblings, 0 replies; 2+ messages in thread
From: cinap_lenrek @ 2019-01-18 17:50 UTC (permalink / raw)
To: 9front
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-01-18 18:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-18 18:23 [9front] libmemdraw bug? qwx
-- strict thread matches above, loose matches on Subject: below --
2019-01-18 17:50 cinap_lenrek
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).