These features enable DEBUG_KERNEL, which is no longer standard.
They are still available in the -developer BSPs.
Signed-off-by: California Sullivan
---
bsp/common-pc-64/common-pc-64-standard.scc | 2 --
bsp/common-pc/common-pc-standard.scc | 2 --
2 files changed, 4 deletions(-)
diff --g
The developer ktype now has the functionality of the previous standard
ktype. To keep preempt-rt's functionality consistent we must include
developer.
Signed-off-by: California Sullivan
---
ktypes/preempt-rt/preempt-rt.scc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ktype
These -developer BSPs use the developer ktype, giving the same
functionality of the old -standard BSPs. With the changes to the
standard and base ktypes, the -standard BSPs no longer have EMBEDDED,
EXPERT, or DEBUG_KERNEL, creating a more production-ready default.
Signed-off-by: California Sulliva
Since we include the developer ktype we should include developer drivers.
Signed-off-by: California Sullivan
---
bsp/intel-common/intel-core2-32-preempt-rt.scc | 1 +
bsp/intel-common/intel-corei7-64-preempt-rt.scc | 1 +
2 files changed, 2 insertions(+)
diff --git a/bsp/intel-common/intel-cor
Targetted for yocto-4.4 and master
Changes since last revision:
*Removed branch command from developer ktype*
Including standard does this already.
*Removed "default policy" comment from -developer common-pc BSPs*
This was copied from the -standard BSPs and is no longer accurate.
I could have ch
Without EXPERT, we hit a select on I2C_I801, forcing it to yes and
causing a warning. Set I2C_I801 to yes, and if a BSP wants to build it
as a module, it can be done through a developer ktype BSP.
Signed-off-by: California Sullivan
---
bsp/haswell-wc/haswell-wc.cfg | 2 +-
bsp/mohonpeak/moh
DEBUG_KERNEL should not be in the base ktype, as a production kernel
may not necessarily want any debug turned on. EMBEDDED is also removed,
as EMBEDDED selects EXPERT which selects DEBUG_KERNEL.
Signed-off-by: California Sullivan
---
ktypes/base/base.cfg | 6 +++---
1 file changed, 3 insertions
The base ktype no longer enables EXPERT, so PROCESSOR_SELECT cannot be
enabled by default. Nothing relying on PROCESSOR_SELECT is changed from
default, and PROCESSOR_SELECT itself only enables a printk, so this will
have no functional change on BSPs using these fragments.
Signed-off-by: California
These BSPs use the developer ktype and add the intel-developer-drivers.scc
file. They should have the same functionality as the -standard BSPs had
previously.
Signed-off-by: California Sullivan
---
bsp/intel-common/intel-core2-32-developer.scc | 14 ++
bsp/intel-common/intel-corei7-
Profiling and latencytop enable DEBUG_KERNEL, which is no longer a
standard config option. Move these features to a new file called
intel-developer-drivers.scc, which is to be included in intel developer
BSPs.
Signed-off-by: California Sullivan
---
bsp/intel-common/intel-common-drivers.scc|
The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL,
opening up more kernel options and setting some defaults.
Signed-off-by: California Sullivan
---
ktypes/developer/developer.cfg | 19 +++
ktypes/developer/developer.scc | 9 +
2 files changed, 28 insertions(
Romley is supported by the intel-core* BSP which already include
profiling and latencytop where appropriate.
Signed-off-by: California Sullivan
---
bsp/romley/romley.scc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/bsp/romley/romley.scc b/bsp/romley/romley.scc
index 9967407..20ffb88 100
Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base
ktype, we can no longer assume DEBUG_KERNEL is enabled.
Also add this fragment to features that require DEBUG_KERNEL.
Signed-off-by: California Sullivan
---
features/debug/debug-kernel.cfg| 3 +++
features/debug/debug-
On Wed, 2016-02-17 at 11:25 -0500, Bruce Ashfield wrote:
> On 16-02-16 05:01 PM, Saul Wold wrote:
> > Bruce,
> >
> > This is this is a set of patches for 4.1, there is another similar
> > that I will be sending shortly for 4.4. The only difference between
> > the 4.1 and 4.4 patch set is 07/07 gp
On 16-02-12 08:42 PM, California Sullivan wrote:
Targetted for yocto-4.4 and master.
Changes since last revision:
*Renamed extended to developer*
More descriptive name than extended.
*Add DEBUG_PREEMPT to debug-kernel feature*
This is an important debug feature that we should explicitly enable
On 16-02-12 08:42 PM, California Sullivan wrote:
By using the developer ktype instead of standard, these BSPs have the
same functionality of the old -standard BSPs.
And we are keeping the -standard variants to have a more production
default build, correct ?
Bruce
Signed-off-by: California S
On 16-02-12 08:42 PM, California Sullivan wrote:
The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL,
opening up more kernel options and setting some defaults.
Signed-off-by: California Sullivan
---
ktypes/developer/developer.cfg | 19 +++
ktypes/developer/develope
On 16-02-12 08:42 PM, California Sullivan wrote:
Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base
ktype, we can no longer assume DEBUG_KERNEL is enabled.
Also add this fragment to features that require DEBUG_KERNEL.
Signed-off-by: California Sullivan
---
features/debu
On 16-02-16 05:01 PM, Saul Wold wrote:
Bruce,
This is this is a set of patches for 4.1, there is another similar
that I will be sending shortly for 4.4. The only difference between
the 4.1 and 4.4 patch set is 07/07 gpio-pca953x does not apply to 4.4,
the other 6 do
These patches are mostly ta
On 16-02-16 05:01 PM, Saul Wold wrote:
From: Ismo Puustinen
Galileo gen 2 has support for setting GPIO modes. Expose these
properties through the GPIO sysfs interface. This approach is bit hacky,
since it changes the interface semantics.
The original patch was by Josef Ahmad and
made on top o
On 16-02-16 05:01 PM, Saul Wold wrote:
From: Todor Minchev
Original author is Bogdan Pricop .
Upstream-status: Forward-ported from Intel IOT Develper Kit Quark BSP
Same comment about the upstream status here. The source is good, but
so is the destination.
Also, in a case like this, I'd just
On 16-02-16 05:01 PM, Saul Wold wrote:
From: Ismo Puustinen
Slave devices were not enumerated by ACPI data because the ACPI handle
for the spi-pxa2xx controller was NULL if it was itself enumerated by
PCI.
Upstream-status: Inappropriate, real fix forthcoming
This of course leaves us wonderin
On 16-02-16 05:01 PM, Saul Wold wrote:
From: Josef Ahmad
There is also a driver for the same chip in drivers/pwm. This version
has support for setting the output in GPIO mode in addition to the PWM
mode.
Upstream-status: Forward-ported from Intel IOT Develper Kit Quark BSP
This doesn't reall
You'll have a better chance of a response if you email the oe-core
mailing list (openembedded-c...@lists.openembedded.org).
linux-yocto is primarily where kernel build/issues/patches are
discussed.
Bruce
On 16-02-17 04:26 AM, winis...@futuraautomation.com wrote:
Dear,
I tried to build core-ima
Dear,
I tried to build core-image-sato. It spits out the following error.
winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-sato
Parsing recipes: 100% |###| ETA: 00:00:00
Parsing of 1060 .bb files complete (0 cached, 1060 parsed). 1496 targets, 138
skipped
25 matches
Mail list logo
