<div dir="ltr">Yea, RDC3308. I have several hundred out there working. I'm working on a new development environment to take me to kernel 3.X </div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 21, 2016 at 7:35 PM, Craig Garner <span dir="ltr"><<a href="mailto:craigcgarner@gmail.com" target="_blank">craigcgarner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>i586, why? Yes using some of the really cheap chip on a whatever...<br><br></div>Anything that you could make at this point having any value is i686 and x86_64.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 21, 2016 at 6:57 PM, Chris Fowler <span dir="ltr"><<a href="mailto:linxdev@gmail.com" target="_blank">linxdev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This is where I'm confused. I guess I was expecting was that all packages created in chapter 5 to be truly targeted to i586. Of course I'm still compiling in 6. Add in that I'm doing this on x86_64 and targeting i586 the host and target are too similar to get a good lesson in cross-compiling a system. It may be helpful if I was to use a host of arm-cross-linux-gnueabihf to target i586. Probably be a two day compile. :)<div><br></div><div>Currently I'm at 10.11 and have chroot'ed into CLFS via the i586 machine by mounting it NFS, setting virtuals, and doing the chroot. I'm going to finish up the chapter there. </div><div><br></div><div>If your curious this is the target:</div><div><br></div><div><div>root:~/ch10# cat /proc/cpuinfo </div><div>processor<span style="white-space:pre-wrap"> </span>: 0</div><div>vendor_id<span style="white-space:pre-wrap"> </span>: Genuine RDC</div><div>cpu family<span style="white-space:pre-wrap"> </span>: 5</div><div>model<span style="white-space:pre-wrap"> </span>: 8</div><div>model name<span style="white-space:pre-wrap"> </span>: 05/08</div><div>stepping<span style="white-space:pre-wrap"> </span>: 6</div><div>cpu MHz<span style="white-space:pre-wrap"> </span>: 999.991</div><div>fdiv_bug<span style="white-space:pre-wrap"> </span>: no</div><div>hlt_bug<span style="white-space:pre-wrap"> </span>: no</div><div>f00f_bug<span style="white-space:pre-wrap"> </span>: no</div><div>coma_bug<span style="white-space:pre-wrap"> </span>: no</div><div>fpu<span style="white-space:pre-wrap"> </span>: yes</div><div>fpu_exception<span style="white-space:pre-wrap"> </span>: yes</div><div>cpuid level<span style="white-space:pre-wrap"> </span>: 1</div><div>wp<span style="white-space:pre-wrap"> </span>: yes</div><div>flags<span style="white-space:pre-wrap"> </span>: fpu tsc cx8 mmx up</div><div>bogomips<span style="white-space:pre-wrap"> </span>: 1999.98</div><div>clflush size<span style="white-space:pre-wrap"> </span>: 32</div><div>cache_alignment<span style="white-space:pre-wrap"> </span>: 32</div><div>address sizes<span style="white-space:pre-wrap"> </span>: 32 bits physical, 32 bits virtual</div><div>power management:</div><div><br></div></div><div><br></div><div>Linux <a href="http://cs-buford.k4fh.com" target="_blank">cs-buford.k4fh.com</a> 2.6.38 #135 SMP Fri May 13 19:16:23 UTC 2016 i586 GNU/Linux</div><div><br></div><div>Eventually I'd like to do the multi, but for all packages. The same root would target the RDC (i586) and a J1900 BayTrail (i686 32). My kernels will be same version, but different processor config. I could use initrd to then create all proper symlinks in root before executing pivot_root. These systems are small and the root it actually loaded off flash into a ramdisk. The RDC sis discontinued, but I still need to support it.<span><font color="#888888"><br><div><br></div><div>Chris</div></font></span></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 4:35 PM, William Harrington <span dir="ltr"><<a href="mailto:kb0iic@berzerkula.org" target="_blank">kb0iic@berzerkula.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tue, May 17, 2016 19:06, Chris Fowler wrote:<br>
> Yea, I've compiled Linus' code and ran on the RDC3308 itself. I've not<br>
> compiled the code in this environment. I'm not sure if I should see cmov<br>
> instructions in the binary or not. I am using uname hack. If I rebuilt<br>
> gmp and coreutils would cmov be included?<br>
><br>
</span>Hello Chris,<br>
<br>
In gmp configure git master:<br>
<br>
i586 | pentium)<br>
gcc_cflags_cpu="-mtune=pentium -mcpu=pentium -m486"<br>
gcc_cflags_arch="-march=pentium"<br>
path="x86/pentium x86"<br>
<br>
You can do what is done in ch10 during ch6 GMP build:<br>
<br>
mv -v config{fsf,}.guess<br>
mv -v config{fsf,}.sub<br>
<br>
Then it'll use generic targets not optimized with the host CPU.<br>
<br>
I don't know if cmov will be removed. GMP checks the assembler to see if<br>
supports cmov, and is supposed to be enabled in gmp when i686/pentium pro<br>
or newer is in the target triplet. It isn't supposed to be included with<br>
i586/pentium or older.<br>
<div><div><br>
Sincerely,<br>
<br>
William Harrington<br>
_______________________________________________<br>
Clfs-support mailing list<br>
<a href="mailto:Clfs-support@lists.clfs.org" target="_blank">Clfs-support@lists.clfs.org</a><br>
<a href="http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org" rel="noreferrer" target="_blank">http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Clfs-support mailing list<br>
<a href="mailto:Clfs-support@lists.clfs.org" target="_blank">Clfs-support@lists.clfs.org</a><br>
<a href="http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org" rel="noreferrer" target="_blank">http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Clfs-support mailing list<br>
<a href="mailto:Clfs-support@lists.clfs.org">Clfs-support@lists.clfs.org</a><br>
<a href="http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org" rel="noreferrer" target="_blank">http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org</a><br>
<br></blockquote></div><br></div>