From owner-freebsd-hackers Thu Jan 25 11:32:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA11092 for hackers-outgoing; Thu, 25 Jan 1996 11:32:50 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA11083 for ; Thu, 25 Jan 1996 11:32:48 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA03031; Thu, 25 Jan 1996 12:27:04 -0700 From: Terry Lambert Message-Id: <199601251927.MAA03031@phaeton.artisoft.com> Subject: Re: Amancio's tv program with capture! To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 25 Jan 1996 12:27:04 -0700 (MST) Cc: terry@lambert.org, luigi@labinfo.iet.unipi.it, james@miller.cs.uwm.edu, dufault@hda.com, hackers@FreeBSD.org, hasty@rah.star-gate.com, multimedia@rah.star-gate.com In-Reply-To: <19923.822538050@time.cdrom.com> from "Jordan K. Hubbard" at Jan 24, 96 06:47:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > > You might be able to map the region and treat it as a pixmap, if it > > were a linear frame buffer. You would have to mangle a pixmap header > > onto the front of it. > > Terry, with all due respect, I think you *still* don't understand the > problem. The shared memory segment is NOT created by the server, not > is any special formattting of the area reauired. There are extension > calls for using the shared memory segment in a way that is understood > by both server and client. > > I think you really should take a look at the code at this point since > every message I've seen from you on this topic only indicates that > you're getting further from understanding, not closer. I think you are missing the boat, too. 8-). You can map the physical device memory into the user address space, and if you cheat on mapping, get an object that is directly manipulable. But that object can't be exported as a shared memory region of a type the server can understand, since the layout won't match that of the Xshm protocol. So you can save the copy on the way in, but not the copy to the display memory, and if the formats are different, not the copy to the Xshm region (assuming you use that interface to the server). > Greetings from USENIX, BTW. I've talked to a number of your cronies > from Novell. Quite amusing - they all have such interesting stories to > tell! :-) Oh, that's hard to believe. 8-). Tell them "hi" for me! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.