Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!hplabs!hpda!hp-sde!hpfcdc!hpldola!paul
From: paul@hpldola.HP.COM (Paul Bame)
Newsgroups: comp.graphics
Subject: Re: HP 9000 Screen Dump to HP Laser printer
Message-ID: <11390011@hpldola.HP.COM>
Date: 31 May 88 18:40:51 GMT
Article-I.D.: hpldola.11390011
References: <286@gt-eedsp.UUCP>
Organization: HP Elec. Design Div. -ColoSpgs
Lines: 13

>>graphics(7) in the HP-UX manuals details how to talk directly to the
>>frame buffer - it's just a big array - and it's easy to do:
>>
>>	fd = open(/dev/crt)
>>	ioctl(fd, GCMAP?, &ptr)
>>
>Well, when I was using an HP Series 9000 Model 320 with HP-UX (awhile ago),
>I recall finding a system call which maps the frame buffer directly into
>the process's address space, so that normal memory references can be made
>to the locations representing the pixels.  

Yep, the open/ioctl maps the frame buffer into user space just like you
mention.