| Age | Commit message (Collapse) | Author |
|---|
|
Consider this 5+ year old commit
commit bcbc7bbc4fb967d8d4ae6333f71b73491a80b94e
Author: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Date: Thu Mar 1 16:00:41 2018 +0200
latencytop: remove recipe
Last commit and release were in 2009; website is down; it's a dead project.
(From OE-Core rev: 36aae56e7f86a4d5ce93e4528e7dcc42f60c705e)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Given that, it seems sensible to drop it from default inclusion across
the BSPs. I've left the feature itself, so anyone who still cares can
easily manually add it still.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
These commits were unlinked by commenting them out back in 2015:
commit d341564a1ff749f87cfc9b2819b2759903c1efba
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Thu Jul 16 15:08:13 2015 -0400
qemuppc: remove old PREP platform patches
We've been using the MAC99 platform for some time now, there's no need
to carry the old PReP platform patches.
We can safely push them off a cliff now, some 9-ish years later.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Upstream is dropping support for is not set, so we adjust our
configs accordingly.
Commit:
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=for-next&id=55de8686df7ed2b5237867b130e30c728bbd9db4
kconfig: change .config format to use =n instead of "is not set"
The .config file uses "# CONFIG_FOO is not set" form to represent
disabled options. In the old days, it was useful because the .config
was directly included from Makefiles. For example, you can use
"ifdef CONFIG_FOO" in Makefiles to check if the option is enabled.
Commit c955ccafc38e ("kconfig: fix .config dependencies") introduced
include/config/auto.conf, which mirrors the .config, but trims down
all disabled options.
Since then, include/config/auto.conf defines CONFIG options during the
build. The .config is used just for storing the user's configuration.
I do not see a strong reason to use a particular pattern of comment
for disabled options.
With this commit, Kconfig will output disable options in a more natural
form, "CONFIG_FOO=n".
Kconfig accepts both "# CONFIG_FOO is not set" and "CONFIG_FOO=n" as a
valid input. You do not need to update arch/*/configs/*_defconfig files
for now. "git bisect" should be able to cross the commit in both ways
without any issue.
A problem may occur if you parse the .config for the "# ... is not set"
patterns.
I adjusted streamline_config.pl, merge_config.sh,
scripts/kconfig/tests/.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Boris Kolpackov <boris@codesynthesis.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Drop references to config_ide, since the driver has been removed
from the 5.14 kernel:
commit b7fb14d3ac63117e0e8beabe75f4ea52051fbe3a
Author: Christoph Hellwig <hch@lst.de>
Date: Wed Jun 16 15:46:58 2021 +0200
ide: remove the legacy ide driver
The legay ide driver has been replace with libata starting in 2003 and has
been scheduled for removal for a while. Finally kill it off so that we
can start cleaning up various bits of cruft it forced on the block layer.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Now that we are explicitly disabling CONFIG_SERIAL_PMACZILOG, we
don't need the associated enable options. Particulary since they
trigger a warning about duplicate optinos in the same fragment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Richard reported:
We've been seeing a lot of the qemuppc shutdown issue and I decided to
look into it. The really worrying thing looking at the logs locally is the
serial ports are showing irq issues and becoming disabled as nobody would
handle them.
Errors like:
[ 9.194886] irq 36: nobody cared (try booting with the "irqpoll" option)
[ 9.198712] CPU: 0 PID: 127 Comm: bootlogd Not tainted 5.10.30-yocto-standard #1
[ 9.202283] Call Trace:
[ 9.205611] [d1005f00] [c00a0da8] __report_bad_irq+0x50/0x138 (unreliable)
[ 9.209347] [d1005f30] [c00a0cc0] note_interrupt+0x324/0x378
[ 9.212855] [d1005f70] [c009d138] handle_irq_event+0xe8/0x104
[ 9.216353] [d1005fa0] [c00a1d9c] handle_fasteoi_irq+0xc0/0x29c
[ 9.219960] [d1005fc0] [c009b798] generic_handle_irq+0x40/0x5c
[ 9.223496] [d1005fd0] [c00075d0] __do_irq+0x58/0x188
[ 9.226948] [d1005ff0] [c0010040] call_do_irq+0x20/0x38
[ 9.230391] [d29eda60] [c0007788] do_IRQ+0x88/0xfc
[ 9.233860] [d29eda90] [c0016454] ret_from_except+0x0/0x14
[ 9.237288] --- interrupt: 501 at __setup_irq+0x3c4/0x838
[ 9.237288] LR = __setup_irq+0x790/0x838
[ 9.244155] [d29edb88] [c009f0a4] request_threaded_irq+0x114/0x1c8
[ 9.247672] [d29edbb8] [c07a5a18] pmz_startup+0x17c/0x32c
[ 9.251203] [d29edbd8] [c07a1140] uart_port_startup+0x184/0x2f8
[ 9.254651] [d29edc08] [c07a1974] uart_port_activate+0x78/0xf4
[ 9.258141] [d29edc28] [c07839f8] tty_port_open+0xd4/0x170
[ 9.261579] [d29edc58] [c079db74] uart_open+0x2c/0x48
[ 9.265116] [d29edc68] [c077a288] tty_open+0x168/0x640
[ 9.268574] [d29edcd8] [c0280be8] chrdev_open+0x138/0x2a4
[ 9.272123] [d29edd18] [c027421c] do_dentry_open+0x228/0x410
[ 9.275643] [d29edd48] [c028e9f4] path_openat+0xb04/0xf28
[ 9.279184] [d29eddd8] [c02917e4] do_filp_open+0x120/0x164
[ 9.282535] [d29ede98] [c0276238] do_sys_openat2+0xd8/0x19c
[ 9.285790] [d29edee8] [c0276574] sys_openat+0x88/0xdc
[ 9.289096] [d29edf38] [c00160d8] ret_from_syscall+0x0/0x34
[ 9.292620] --- interrupt: c01 at 0xfec3738
[ 9.292620] LR = 0xfec36e0
[ 9.299035] handlers:
[ 9.302312] [<7f7f7da8>] pmz_interrupt
[ 9.305541] Disabling IRQ #36
(and the irqpoll option does not help)
This is problematic as the shutdown test uses the serial interface to
shut down the system. If the serial interface fails to login or run the command,
game over for the test.
CONFIG_SERIAL_PMACZILOG complicates that handling, but doesn't provide
any output or capabilities that we need. So we disable it here, and
reduce the chances of issues during shutdown.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
oprofile is being removed from the kernel, since the oprofile userspace
tools use the perf syscalls (and have for quite a while).
So we drop our remaining configs to avoid obselete config warnings
reference:
https://lore.kernel.org/lkml/CAHk-=whw9t3ZtV8iA2SJWYQS1VOJuS14P_qhj3v5-9PCBmGQww@mail.gmail.com/
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Changing CONFIG_SCSI from '=m' to '=y' to be consistent with its
direct dependency, which is 'CONFIG_SCSI_VIRTIO=y' in virtio.cfg.
Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yann CARDAILLAC <ycnakajsph@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
CONFIG_PNP will be excluded from the final .config via our
lack of ISA support. We don't need this feature (since it
is disabled), and due to the way Kconfig processes options
CONFIG_PNP is not it the final .config at all.
This lack of "is not set" triggers a warning. To avoid the
warning, we drop the option.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
CONFIG_MII is a tristate with no user prompt, as such, it is
only selected by other kernel configs. If we have it in our fragments
we'll be warned when it isn't in the final .config.
The warning isn't useful, since if this is needed another option will
select it.
To avoid the warning, we just drop CONFIG_MII from our fragments
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
These platforms do not have the required AGP and DRM support to use
the cirrus module, so we remove it from their configuration.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To allow platforms to take advantage of better graphics support, we
enable the following options as module:
config DRM_CIRRUS_QEMU
tristate "Cirrus driver for QEMU emulated device"
depends on DRM && PCI
select FB_SYS_FILLRECT
select FB_SYS_COPYAREA
select FB_SYS_IMAGEBLIT
select DRM_KMS_HELPER
select DRM_KMS_FB_HELPER
select DRM_TTM
help
This is a KMS driver for emulated cirrus device in qemu.
It is *NOT* intended for real cirrus devices. This requires
the modesetting userspace X.org driver.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We've been using the MAC99 platform for some time now, there's no need
to carry the old PReP platform patches.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Further consolidation of the WACOM driver has unified BT and USB support
into the generically named HID_WACOM driver. So we rename our fragments
to match.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
USB configurations were implicitly being enabled via the WACOM
USB tablet Kconfig. To align the arm, ppc and mips qemu machine with
the other BSPs, we should explicitly include the USB options, rather
than relying on the implicit mechanism.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
commit 471d17148c8b [Input: wacom - move the USB (now hid) Wacom driver in drivers/hid]
changes the config value for USB wacom support. So we adjust our fragments accordingly.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
commit fb28d58b72aa9215b26f1d5478462af394a4d253
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Wed Apr 25 17:15:29 2012 -0700
USB: remove CONFIG_USB_DEVICEFS
This option has been deprecated for many years now, and no userspace
tools use it anymore, so it should be safe to finally remove it.
Reported-by: Kay Sievers <kay@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
qemuppc had some old profiling options in its BSP configuration
fragments. These are better pulled from the profiling feature.
This also removes a warning when options like CONFIG_FRAME_POINTER
are dropped from the final .config (since they are not available
on the arch).
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Clean up some QEMU and non-x86 BSPs kernel config, including
qemuarm
qemuppc
qemux86
beagleboard
mpc8315e_rdb
Only obsolete/invalid kernel configs are removed.
Signed-off-by: Yang Shi <yang.shi@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Repalce emulation of qemuppc from prep to mac99. Also add
qemu-ppc32-gfx.cfg file to support framebuffer and touchscreen.
Signed-off-by: Liming Wang <liming.wang@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Cleaning the configuration of the qemu base board descriptions to remove
obselete options, re-use common config features and declare options as
being valid for the BSPs to define.
With this change the kernel configuration audit is clean for all the
qemu machines.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The qemuppc rt board description did not match the recent change to
a board specific branch on the end of the preempt-rt kernel type. This
resulted in kernel configuration validation errors since the board
description didn't match the tree and was discarded. This updates the
.scc file to have a proper branch and series description.
The .cfg file is also update to remove obselete config values and provide
a clean configuration audit.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Create the preempt-rt definition for qemuppc support. This
configuration re-uses existing branches since no board specific
changes are currently required. If board specific fixes are
required, this definition will be updated.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@windriver.com
Subject: qemuppc: irq disable fixups
Date: Wed, 15 Jun 2011 16:12:17 -0400
Mapping the qemuppc interupt handling to the new interrupt
routines means that we call irq_state_clr_disabled
to enable irqs, not disable them. So we should modify function
"irq_state_set_disabled" with our custom qemppc mods.
Signed-off-by: Liming Wang <liming.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Have common-pc-64 use the hpet feature, and remove the corresponding
options in common-pc64.cfg. Also remove the hpet options from arm and
ppc machines where they're noops.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Roughly corresponds to:
commit db575247e16e50ce5160e18907e253c6a43b6feb
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Mon Apr 4 00:27:55 2011 -0400
yocto: 2.6.39 baseline
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
...in the full history repo, but with some extraneous files that were
deleted post db575247 deleted right here and now at the baseline
instead.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
Paul Gortmaker
Bruce Ashfield
Yanfei Xu
Yann CARDAILLAC
Bruce Ashfield
Yang Shi
Liming Wang
Darren Hart
Tom Zanussi