On 1/30/21 8:31 PM, Lev wrote:
> Hi Jon,
Hi,
[...]
> Thanks, I appreciate it. I have some additional patches. The first is an
> AArch64 fix that resolves ticket 102 according to the reporter. The other two
> are to revamp CDE’s internationalization support.
I've merged these (and fixed the typo). Also added
programs/dtdspmsg/MsgCat.c
programs/dtexec/MsgCat.c
programs/dtsr/MsgCat.c
programs/localized/util/MsgCat.c
to .gitignore as these appear to be generated now.
Tried a test build and all seemed to work and run. Thanks!
[...]
> Just please no more 80+ character single-sentence commit lines :)
> Duly noted. May I have permission to edit the contributing to CDE section to
> add this as a style guideline? Also, if I can get CDE building on the
> historic platforms during my next break, could I please add a link under that
> section?
Absolutely - you will need an SF account though. Then I can add you as
a Member and that will give you access to the wiki.
Just let me know what it is (off-list) and I'll do that.
[...]
> Thanks for the overview, that’s really interesting. The last time I did
> direct work with a graphics card, I was programming CRTC parameters, and
> things were much simpler :) If I understand correctly that Xsvc was designed
> to be an compact, ultra-portable kernel to userspace accelerator adapter, was
> context switching the major drawback? Perhaps once there’s no more commercial
> interest, they’ll open the code. I know the BSD’s have a very hard time
> continually porting Linux’s DRM stack, and I can also see the advantage for
> systems where you don’t have access to the kernel source code.
Yeah, xsvc was meant to just provide an interface to the hardware so
userspace could handle the rest.
[...]
--
Jon Trulson
"Entropy. It isn't what it used to be."
-- Sheldon
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
