Date: Sat, 27 Jan 1996 23:10:31 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Terry Lambert <terry@lambert.org> Cc: 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 Subject: Re: Amancio's tv program with capture! Message-ID: <28161.822813031@time.cdrom.com> In-Reply-To: Your message of "Thu, 25 Jan 1996 12:27:04 MST." <199601251927.MAA03031@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Maybe I really am missing the boat, but I'm still having a hard time understanding that if (and forgive me if I resort to pseudo- code - it's been a long week): fbmem = mmap(.. blah ..) shmid = shmget(.. some memory chunk size and allocation info ..) ximage->data = shmat(shmid, 0, 0); bcopy(fbmem, ximage->data, ..size..) Works *just fine*, e.g. the ximage data is happy to point at the memory allocated by shmget and I can bcopy straight into this region from the frame buffer, sans any special offsets or conversion, then how can: fbmem = mmap(.. blah ..) shmid = shmget(.. no memory please, just an entry ..) ximage->data = shmat(shmid, fbmem, 0); work when shmget() doesn't support any such semantics? It seems like that would be the minimum level of hacking required to even give this a ghost's chance of working. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28161.822813031>