Skip to contentSkip to conversation

tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

PATCH In review Andre McCurdy 4 participants 6 messages May 31, 2018 – Jun 1, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU

The Quark machine was EOL'ed at the end of 2017 and all support for it has now been removed from meta-intel. Drop the associated tuning file from oe-core.

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c

---
 meta/conf/machine/include/tune-i586-nlp.inc | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
meta/conf/machine/include/tune-i586-nlp.inc deleted +0 -19
deleted file mode 100644
index 88e5903..0000000
@@ -1,19 +0,0 @@
-# Settings for the GCC(1) cpu-type "quark":
-#
-#
-#
-DEFAULTTUNE ?= "i586-nlp-32"
-
-# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
-require conf/machine/include/x86/arch-x86.inc
-
-# x86 with no lock prefix
-TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
-
-# Quark tune feature
-AVAILTUNES = "i586-nlp-32"
-TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
-BASE_LIB_tune-i586-nlp-32 = "lib"
-TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
-PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
Signature · 1 line
1.9.1
#1 lore raw

Someone (maybe me??) needs to create a meta-intel-community in which to capture these sorts of things. Just because Intel, officially, doesn't support it, doesn't mean all the existing Galileos (and I think there's another devboard that uses the Quark?) out there should lose support.

Quoted 49 lines · Andre McCurdy

The Quark machine was EOL'ed at the end of 2017 and all support for it has now been removed from meta-intel. Drop the associated tuning file from oe-core.

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=
5dbc69e339588834317b632119717996584b0d6c

---
 meta/conf/machine/include/tune-i586-nlp.inc | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
meta/conf/machine/include/tune-i586-nlp.inc deleted +0 -21
deleted file mode 100644
index 88e5903..0000000
@@ -1,19 +0,0 @@
-# Settings for the GCC(1) cpu-type "quark":
-#
-#
-#
-DEFAULTTUNE ?= "i586-nlp-32"
-
-# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
-require conf/machine/include/x86/arch-x86.inc
-
-# x86 with no lock prefix
-TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', '
-march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
-
-# Quark tune feature
-AVAILTUNES = "i586-nlp-32"
-TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
-BASE_LIB_tune-i586-nlp-32 = "lib"
-TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
-PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
--

1.9.1

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#2 lore raw
In reply to Andre McCurdy
Quoted 3 lines · Andre McCurdy

The Quark machine was EOL'ed at the end of 2017 and all support for it has now been removed from meta-intel. Drop the associated tuning file from oe-core.

I would rather this remain. There are still a lot of people using the quark based boards as hobbyists... there is little effort to maintain it for now.

(we still have support for ARMv4 for instance, which hasn't really been used in new designs in a while..)

--Mark

Quoted 34 lines

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c

---
 meta/conf/machine/include/tune-i586-nlp.inc | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
meta/conf/machine/include/tune-i586-nlp.inc deleted +0 -19
deleted file mode 100644
index 88e5903..0000000
@@ -1,19 +0,0 @@
-# Settings for the GCC(1) cpu-type "quark":
-#
-#
-#
-DEFAULTTUNE ?= "i586-nlp-32"
-
-# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
-require conf/machine/include/x86/arch-x86.inc
-
-# x86 with no lock prefix
-TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
-
-# Quark tune feature
-AVAILTUNES = "i586-nlp-32"
-TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
-BASE_LIB_tune-i586-nlp-32 = "lib"
-TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
-PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
#3 lore raw
Quoted 10 lines · Mark Hatle
Quoted 3 lines · Andre McCurdy

The Quark machine was EOL'ed at the end of 2017 and all support for it has now been removed from meta-intel. Drop the associated tuning file from oe-core.

I would rather this remain. There are still a lot of people using the quark based boards as hobbyists... there is little effort to maintain it for now.

(we still have support for ARMv4 for instance, which hasn't really been used in new designs in a while..)

Is there ever a case when we would drop old tuning files? Or should they live on forever?

We dropped GPLv2 recipes from oe-core on the grounds that they are old, unmaintained and untested. ARMv4 CPU tuning files meet those criteria too.

Quoted 35 lines
Quoted 34 lines

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c

---
 meta/conf/machine/include/tune-i586-nlp.inc | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
meta/conf/machine/include/tune-i586-nlp.inc deleted +0 -19
deleted file mode 100644
index 88e5903..0000000
@@ -1,19 +0,0 @@
-# Settings for the GCC(1) cpu-type "quark":
-#
-#
-#
-DEFAULTTUNE ?= "i586-nlp-32"
-
-# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
-require conf/machine/include/x86/arch-x86.inc
-
-# x86 with no lock prefix
-TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
-
-# Quark tune feature
-AVAILTUNES = "i586-nlp-32"
-TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
-BASE_LIB_tune-i586-nlp-32 = "lib"
-TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
-PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
#4 lore raw
Quoted 6 lines · Andre McCurdy
Quoted 5 lines · Mark Hatle
Quoted 3 lines · Andre McCurdy

The Quark machine was EOL'ed at the end of 2017 and all support for it has now been removed from meta-intel. Drop the associated tuning file from oe-core.

Quoted 8 lines
Quoted 5 lines

I would rather this remain. There are still a lot of people using the quark based boards as hobbyists... there is little effort to maintain it for now.

(we still have support for ARMv4 for instance, which hasn't really been used in new designs in a while..)

Is there ever a case when we would drop old tuning files? Or should they live on forever?

If we actively know they do not work any longer, (which is probably when GCC support is declared to be obsolete.)

Quoted 3 lines

We dropped GPLv2 recipes from oe-core on the grounds that they are old, unmaintained and untested. ARMv4 CPU tuning files meet those criteria too.

I'm not sure they are unmaintained, but certainly untested. We've had and continue to get contributions to tuning files that are clearly never tested.

(Besides, a lot of us don't use meta-intel, we use our own BSP layers..)

--Mark

Quoted 35 lines
Quoted 35 lines
Quoted 34 lines

http://git.yoctoproject.org/cgit.cgi/meta-intel/commit/?id=5dbc69e339588834317b632119717996584b0d6c

---
 meta/conf/machine/include/tune-i586-nlp.inc | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
meta/conf/machine/include/tune-i586-nlp.inc deleted +0 -19
deleted file mode 100644
index 88e5903..0000000
@@ -1,19 +0,0 @@
-# Settings for the GCC(1) cpu-type "quark":
-#
-#
-#
-DEFAULTTUNE ?= "i586-nlp-32"
-
-# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
-require conf/machine/include/x86/arch-x86.inc
-
-# x86 with no lock prefix
-TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'i586-nlp', ' -march=i586 -Wa,-momit-lock-prefix=yes', '', d)}"
-
-# Quark tune feature
-AVAILTUNES = "i586-nlp-32"
-TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
-BASE_LIB_tune-i586-nlp-32 = "lib"
-TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
-PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
#5 lore raw
In reply to Andre McCurdy
Quoted 18 lines · Andre McCurdy
Quoted 8 lines · Mark Hatle
Quoted 6 lines · Andre McCurdy

The Quark machine was EOL'ed at the end of 2017 and all support for
it has now been removed from meta-intel. Drop the associated tuning
file from oe-core.

Quoted 8 lines

I would rather this remain.  There are still a lot of people using the quark
based boards as hobbyists... there is little effort to maintain it for now.

(we still have support for ARMv4 for instance, which hasn't really been used in
new designs in a while..)

Quoted 6 lines

Is there ever a case when we would drop old tuning files? Or should they live on forever?

We dropped GPLv2 recipes from oe-core on the grounds that they are old, unmaintained and untested. ARMv4 CPU tuning files meet those criteria too.

We removed the GPLv2 recipes as they created a false sense of security for people and a message needed to be sent out about them. They were a maintenance problem.

These tune files aren't really causing a problem right now, from a maintenance or security perspective.

Yes, we should remove things which are stale/obsolete and not useful but I think people are using this file and its not causing a problem.

Cheers,

Richard