From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to read/write pixels from Memimage
Date: Sat, 26 Jan 2008 09:05:53 -0500 [thread overview]
Message-ID: <20080126140548.766191E8C1C@holo.morphisms.net> (raw)
In-Reply-To: <7BDD11E8-7753-4E44-9BD2-2FA5944D43E8@mac.com>
> Hello. I'm porting Bell Labs' Pico image language over to Plan 9 to
> use the Plan 9 native image format (image(6)), and I chose to use
> Memimage. I'd like to know how to get the 32-bit RGB pixel
> information out of a Memimage and into a properly allocated array of
> u32ints, and to do the reverse. Is that possible? Thanks.
A good way to answer questions like these is to
cd /sys/src/cmd
grep -n Memimage *.c */*.c */*/*.c
Looking through the output, all of these:
/sys/src/cmd/crop.c
/sys/src/cmd/resample.c
/sys/src/cmd/jpg/writepng.c
are examples of programs that use memimages
in a byte-at-a-time fashion.
Russ
next prev parent reply other threads:[~2008-01-26 14:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:05 Pietro Gagliardi
2008-01-26 14:05 ` Russ Cox [this message]
2008-01-26 14:09 ` Pietro Gagliardi
2008-01-26 14:55 ` Russ Cox
2008-01-26 23:22 ` Pietro Gagliardi
2008-01-27 18:05 ` Skip Tavakkolian
2008-01-27 18:55 ` Pietro Gagliardi
2008-01-27 19:29 ` [9fans] pico Steve Simon
2008-01-28 23:36 ` Russ Cox
2008-01-29 0:30 ` Pietro Gagliardi
2008-01-29 5:30 ` Bruce Ellis
2008-01-29 20:33 ` Pietro Gagliardi
2008-01-29 20:35 ` Pietro Gagliardi
2008-01-29 22:46 ` Russ Cox
2008-01-30 1:13 ` Pietro Gagliardi
2008-01-30 6:53 ` Bruce Ellis
2008-01-30 23:42 ` Pietro Gagliardi
2008-01-30 23:55 ` Pietro Gagliardi
2008-01-31 7:41 ` Bruce Ellis
2008-02-05 3:01 ` Pietro Gagliardi
2008-01-27 19:14 ` [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-27 23:44 ` Pietro Gagliardi
2008-01-28 0:18 ` Pietro Gagliardi
2008-01-28 1:08 ` Pietro Gagliardi
2008-01-28 1:22 ` erik quanstrom
2008-01-28 3:23 ` Pietro Gagliardi
2008-01-28 9:24 ` mattmobile
2008-01-28 16:20 ` ron minnich
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=20080126140548.766191E8C1C@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).