New loongson processors do not need fix-loongson2f-nop workaround 发自手机邮件客户端 On 2017-01-03 09:22 , Mart Raudsepp Wrote: Ühel kenal päeval, L, 31.12.2016 kell 22:53, kirjutas Javier Vasquez: > > > > On Sat, Dec 31, 2016 at 9:43 PM, Mart Raudsepp <l...@gentoo.org> > > wrote: > > I'm sorry, but what are LSF/CLSF? > > Ups, I wrote them backwards, :-( > > LFS = Linux From Scratch (http://www.linuxfromscratch.org) > CLFS = Cross LFS (http://trac.clfs.org) > > I'm sorry, I thought those were well known terms... LFS, I guess is more known, yeah :) I consider it to be sort of like Gentoo as an end result, but just with unnecessary self-inflicted huge pain to choose over Gentoo which leads to 20x more time needed to get anywhere. > > > > Sure, use Gentoo? :D > > Sure Gentoo is an alternative, though I'd rather go with LFS/CLFS if > possible... BTW, though a big deal, but on Gentoo one needs to start > with -n32 abi. And that's the most sensible thing to use on a loongson2f. n64 would only be for academic use or something imho. But at that point researching NUBI or something might be more interesting, if that's even a thing anymore. n32 IS 64bit, just with 32bit pointers, which on e.g a yeeloong is all you need as you can address 4GB of virtual memory, and that's more than you have there, pretty much. Also the limitation of 4GB would be for one process, you can still have loads of memory, and you can still use it all, just not map more than 4GB in a given single process. If you have limited memory, it is better to have 32bit pointers because it saves process memory and leads to less memory usage. n32 is like x32 when compared to the PC world, not x86, except unlike x32, it's actually rather well supported. o32 is what is 32bit and a waste for a 64bit mips, but n32 still gives you hardware "long long" type, etc. That's why I have not personally looked at n64 Gentoo on my yeeloong. It would simply be worse in every aspect I care, given the RAM it has. For yeeloong, there's a project https://wiki.gentoo.org/wiki/Project:Lemote_Yeeloong_Gentoo_Desktop that provides a loongson2f starting image, albeit currently at a 2014 June state, but it can be upgraded from there, which is definitely faster than doing some LFS. That said, you can certainly have n64 too, might just need a bit more work for an initial setup. There are old n64 stage3's available to start from, hopefully the CPU bugs for which workarounds are necessary on loongson2f aren't hit in the base system too hard to cause issues, but I suspect they might, so might need some messing around, but I doubt anything as extreme as LFS. But I strongly advise n32 unless you need a process to use more than 4GB alone (not total, just one specific process), if you even have 4GB (and don't consider huge swap a solution there). I have 1GB RAM in my yeeloong, I certainly don't want to have larger memory pointers taking memory by using n64 instead of n32. > Just wondering if the same flags, patches and so on, that apply for > loongson 2F would also apply to 3A. That was all... > I'd really hope the newer families don't need the CPU bug workaround flags anymore... -Wa,-mfix-loongson2f-nop etc -- Regards, Mart Raudsepp Gentoo Linux - GNOME, GStreamer, X11, MIPS projects -- You received this message because you are subscribed to the Google Groups "loongson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to loongson-dev+unsubscr...@googlegroups.com. To post to this group, send email to loongson-dev@googlegroups.com. Visit this group at https://groups.google.com/group/loongson-dev. For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "loongson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to loongson-dev+unsubscr...@googlegroups.com. To post to this group, send email to loongson-dev@googlegroups.com. Visit this group at https://groups.google.com/group/loongson-dev. For more options, visit https://groups.google.com/d/optout.
