search for: thunderx

Displaying 15 results from an estimated 15 matches for "thunderx".

Did you mean: thunder
2016 Aug 08
4
Syslinux Aarch64 porting
Hi, Is there any information available on porting Syslinux to 64bit ARM? Specifically, I have a Cavium ThunderX board (Gigabyte R120-T30) which boots using UEFI - b2b.gigabyte.com/products/product-page.aspx?pid=5864#ov I'd be very interested in getting this to work, as currently the only option for booting on this platform is Grub 2 or EFI Stub. If anyone can point me in the right direction it would...
2016 Aug 08
0
Syslinux Aarch64 porting
...ux] Syslinux Aarch64 porting > Message-ID: <05476825-bf5e-9898-4aaa-3eaa927bbd0c at nrv-linux.io> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > Is there any information available on porting Syslinux to 64bit ARM? > > Specifically, I have a Cavium ThunderX board (Gigabyte R120-T30) which > boots using UEFI - b2b.gigabyte.com/products/product-page.aspx?pid=5864#ov > Penguin Computing is also working with Gigabyte and Cavium to deliver their Cavium ThunderX boards in our products (under the name "Valkre" product line) and would also li...
2017 Jul 25
2
ARM support from CentOS
Hello, I would like to know which ARM processors does CentOS support? Does it support Freescale/NXP? Thanks and regards Jay
2016 Aug 10
0
Syslinux Aarch64 porting
Michael Davies wrote: >Is there any information available on porting Syslinux to 64bit ARM? > >Specifically, I have a Cavium ThunderX board (Gigabyte R120-T30) which >boots using UEFI - b2b.gigabyte.com/products/product-page.aspx?pid=5864#ov > >I'd be very interested in getting this to work, as currently the only >option for booting on this platform is Grub 2 or EFI Stub. If anyone can >point me in the right...
2017 Jul 25
0
ARM support from CentOS
To give you a proper answer, I'd need to know if you're looking for 64bit arm (aarch64/arm64) support or 32bit armhfp support. Assuming 64bit, we support Applied Micro's X-Gene family of processors, Cavium's ThunderX, as well as Qualcomm's QDF 24xx line. We maintain support for the AMD Seattle SoC as well, but that doesn't appear to be getting updates that I know of. We do not currently support the NXP/Freescale line, but if someone wants to supply patches I'm happy to add them in. On 07/25/2017 0...
2017 Jan 04
0
Release for CentOS 7.3.1611 on ARM64/AArch64
...may lose connectivity when using 4.5.0-19+ based kernels. Please ensure your hardware is running the most recent firmware available to avoid network issues. 2. Merlin based boards should be on the most recent firmware version, in order to take full advantage of recent kernel improvements. 3. Some ThunderX based boards have been reported to have MAC address inconsistency when using older firmware versions. Please make sure you have the most recent firmware applied to your hardware to avoid network issues. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA...
2016 Aug 10
1
Syslinux Aarch64 porting
...e would *not* want syslinux to be portable? It's nice to have options. Regards, Michael On 10/08/2016 10:49 PM, Steve McIntyre wrote: > Michael Davies wrote: > >> Is there any information available on porting Syslinux to 64bit ARM? >> >> Specifically, I have a Cavium ThunderX board (Gigabyte R120-T30) which >> boots using UEFI - b2b.gigabyte.com/products/product-page.aspx?pid=5864#ov >> >> I'd be very interested in getting this to work, as currently the only >> option for booting on this platform is Grub 2 or EFI Stub. If anyone can >>...
2017 Jan 05
0
CentOS-announce Digest, Vol 143, Issue 3
...may lose connectivity when using 4.5.0-19+ based kernels. Please ensure your hardware is running the most recent firmware available to avoid network issues. 2. Merlin based boards should be on the most recent firmware version, in order to take full advantage of recent kernel improvements. 3. Some ThunderX based boards have been reported to have MAC address inconsistency when using older firmware versions. Please make sure you have the most recent firmware applied to your hardware to avoid network issues. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA...
2020 Jan 23
3
How to find out the default CPU / Features String for a given triple?
...rve-x26,-reserve-x27,-reserve-x28,-reserve-x3,-reserve-x4,-reserve-x5,-reserve-x6,-reserve-x7,-reserve-x9,-saphira,+sb,+sel2,-sha2,-sha3,-slow-misaligned-128store,-slow-paired-128,-slow-strqro-store,-sm4,-spe,+specrestrict,+ssbs,-strict-align,-sve,-sve2,-sve2-aes,-sve2-bitperm,-sve2-sha3,-sve2-sm4,-thunderx,-thunderx2t99,-thunderxt81,-thunderxt83,-thunderxt88,+tlb-rmi,-tpidr-el1,-tpidr-el2,-tpidr-el3,+tracev8.4,-tsv110,+uaops,-use-aa,+use-postra-scheduler,-use-reciprocal-square-root,+v8.1a,+v8.2a,+v8.3a,+v8.4a,+v8.5a,+vh,-zcm,-zcz,-zcz-fp,-zcz-fp-workaround,-zcz-gp Now, I understand that qemu crashin...
2016 Nov 14
0
FreeBSD Quarterly Status Report - Third Quarter 2016
...hanges * Made many stability fixes, the most important of which were UFS issues and an i386 bug * Improved the process management and ptrace code Ed Maste, our Project Development Director, accomplished this work last quarter: * Worked on FreeBSD/arm64 issues and Cavium ThunderX deployment (including RMAs) * Worked with upstream developers to test works in progress and prepare LLD as the replacement linker in the FreeBSD base system * Switched to using LLVM's libunwind in the base system * Improved the reproducibility of builds in the FreeB...
2016 Nov 14
0
FreeBSD Quarterly Status Report - Third Quarter 2016
...hanges * Made many stability fixes, the most important of which were UFS issues and an i386 bug * Improved the process management and ptrace code Ed Maste, our Project Development Director, accomplished this work last quarter: * Worked on FreeBSD/arm64 issues and Cavium ThunderX deployment (including RMAs) * Worked with upstream developers to test works in progress and prepare LLD as the replacement linker in the FreeBSD base system * Switched to using LLVM's libunwind in the base system * Improved the reproducibility of builds in the FreeB...
2018 Feb 07
2
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
...ore information WARNING: modpost: missing MODULE_LICENSE() in drivers/power/reset/zx-reboot.o see include/linux/module.h for more information >> ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined! ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined! ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined! --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation -------------- next part -------------- A...
2018 Feb 07
2
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
...ore information WARNING: modpost: missing MODULE_LICENSE() in drivers/power/reset/zx-reboot.o see include/linux/module.h for more information >> ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined! ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined! ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined! --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation -------------- next part -------------- A...
2015 Jun 17
3
[LLVMdev] Build times on ARM
I recently got a tegra TK1 and was curious how fast it was compared to my previous arm "build machine": the original arm Samsung chromebook. I timed running ninja to build just llvm in Release+Asserts using clang as the host compiler. chromebook: real 84m30.939s user 163m50.145s sys 4m0.100s TK1: real 34m7.376s user 132m44.417s sys 3m3.543s A really nice
2017 Mar 11
3
Is there a way to know the target's L1 data cache line size?
I guess that in this case, what I would like to know is a reasonable upper bound of the cache line size on the target architecture. Something that I can align my data structures on at compile time so as to minimize the odds of false sharing. Think std::hardware_destructive_interference_size in C++17. Le 11/03/2017 à 13:16, Bruce Hoult a écrit : > There's no way to know, until you run