218c4e68c1
Rather than using linuxapp and bsdapp everywhere, we can change things to use the, more readable, terms "linux" and "freebsd" in our build configs. Rather than renaming the configs we can just duplicate the existing ones with the new names using symlinks, and use the new names exclusively internally. ["make showconfigs" also only shows the new names to keep the list short] The result is that backward compatibility is kept fully but any new builds or development can be done using the newer names, i.e. both "make config T=x86_64-native-linuxapp-gcc" and "T=x86_64-native-linux-gcc" work. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
57 lines
969 B
Plaintext
57 lines
969 B
Plaintext
# SPDX-License-Identifier: BSD-3-Clause
|
|
# Copyright(c) 2010-2014 Intel Corporation
|
|
|
|
#include "common_linux"
|
|
|
|
CONFIG_RTE_MACHINE="native"
|
|
|
|
CONFIG_RTE_ARCH="i686"
|
|
CONFIG_RTE_ARCH_I686=y
|
|
CONFIG_RTE_ARCH_X86=y
|
|
|
|
CONFIG_RTE_TOOLCHAIN="gcc"
|
|
CONFIG_RTE_TOOLCHAIN_GCC=y
|
|
|
|
#
|
|
# KNI is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_KNI=n
|
|
|
|
#
|
|
# Solarflare PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n
|
|
|
|
#
|
|
# AES-NI multi-buffer PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n
|
|
|
|
#
|
|
# AES-NI GCM PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=n
|
|
|
|
#
|
|
# KASUMI PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_PMD_KASUMI=n
|
|
|
|
#
|
|
# ZUC PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_PMD_ZUC=n
|
|
|
|
#
|
|
# AVP PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_AVP_PMD=n
|
|
|
|
#
|
|
# NFP PMD is not supported on 32-bit
|
|
#
|
|
CONFIG_RTE_LIBRTE_NFP_PMD=n
|
|
|
|
# 32-bit doesn't break up memory in lists, but does have VA allocation limit
|
|
CONFIG_RTE_MAX_MEM_MB=2048
|