Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black
On Fri, May 09, 2014 at 03:17:28AM +0100, Ben Hutchings wrote: On Wed, 2014-05-07 at 18:10 -0700, Vagrant Cascadian wrote: On Wed, May 07, 2014 at 01:46:53PM -0700, Vagrant Cascadian wrote: USB support seems flaky, at best... not sure if there are other options that could improve that. I think that's because the MUSB driver can only be built with support for one type of DMA controller, and so doesn't support DMA at all in multiplatform kernels. hrm. That doesn't sound promising... CONFIG_DMA_OMAP=y +CONFIG_TI_CPPI41=y Why not =m? Updated to use =m. +CONFIG_I2C_CHARDEV=y This symbol seems to be enabled in most configurations that have I2C, but often as a module. Updated to use =m. +CONFIG_SERIAL_OF_PLATFORM=y Removed. Also removed the various DEVFREQ entries; there were no enabled drivers, just governors... diff --git a/config/armhf/config.armmp b/config/armhf/config.armmp index c43f74e..d9b2308 100644 --- a/config/armhf/config.armmp +++ b/config/armhf/config.armmp @@ -136,6 +136,12 @@ CONFIG_OMAP_OCP2SCP=m CONFIG_OMAP_INTERCONNECT=m ## +## file: drivers/char/hw_random/Kconfig +## +CONFIG_HW_RANDOM=m +CONFIG_HW_RANDOM_OMAP=m + +## ## file: drivers/clk/Kconfig ## CONFIG_CLK_TWL6040=m @@ -170,6 +176,8 @@ CONFIG_IMX_SDMA=y CONFIG_IMX_DMA=y CONFIG_MXS_DMA=y CONFIG_DMA_OMAP=y +CONFIG_TI_CPPI41=m +CONFIG_TI_EDMA=y ## ## file: drivers/gpio/Kconfig @@ -178,6 +186,22 @@ CONFIG_GPIO_SYSFS=y CONFIG_GPIO_DA9052=m CONFIG_GPIO_TWL4030=y CONFIG_GPIO_TWL6040=y +CONFIG_GPIO_GENERIC_PLATFORM=m + +## +## file: drivers/gpu/drm/Kconfig +## +CONFIG_DRM=m + +## +## file: drivers/gpu/drm/i2c/Kconfig +## +CONFIG_DRM_I2C_NXP_TDA998X=m + +## +## file: drivers/gpu/drm/tilcdc/Kconfig +## +CONFIG_DRM_TILCDC=m ## ## file: drivers/hwspinlock/Kconfig @@ -185,6 +209,11 @@ CONFIG_GPIO_TWL6040=y CONFIG_HWSPINLOCK_OMAP=m ## +## file: drivers/i2c/Kconfig +## +CONFIG_I2C_CHARDEV=m + +## ## file: drivers/i2c/busses/Kconfig ## CONFIG_I2C_GPIO=y @@ -199,6 +228,11 @@ CONFIG_I2C_VERSATILE=m CONFIG_IIO=m ## +## file: drivers/iio/adc/Kconfig +## +CONFIG_TI_AM335X_ADC=m + +## ## file: drivers/iio/light/Kconfig ## CONFIG_SENSORS_TSL2563=m @@ -229,6 +263,7 @@ CONFIG_SERIO_AMBAKMI=m ## CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_TSC2005=m +CONFIG_TOUCHSCREEN_TI_AM335X_TSC=m ## ## file: drivers/iommu/Kconfig @@ -491,6 +526,11 @@ CONFIG_WLCORE_SDIO=m CONFIG_PHY_SUN4I_USB=m ## +## file: drivers/pinctrl/Kconfig +## +CONFIG_PINCTRL_SINGLE=y + +## ## file: drivers/pinctrl/vt8500/Kconfig ## CONFIG_PINCTRL_WM8850=y @@ -592,6 +632,8 @@ CONFIG_SERIAL_VT8500_CONSOLE=y CONFIG_SERIAL_ARC=y CONFIG_SERIAL_ARC_CONSOLE=y CONFIG_SERIAL_ARC_NR_PORTS=1 +CONFIG_SERIAL_OMAP=y +CONFIG_SERIAL_OMAP_CONSOLE=y ## ## file: drivers/tty/serial/8250/Kconfig @@ -663,6 +705,8 @@ CONFIG_OMAP_USB3=m CONFIG_TWL4030_USB=m CONFIG_TWL6030_USB=m CONFIG_USB_MXS_PHY=m +CONFIG_AM335X_CONTROL_USB=m +CONFIG_AM335X_PHY_USB=m ## ## file: drivers/video/Kconfig live well, vagrant signature.asc Description: Digital signature
Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black
On Fri, 2014-05-09 at 03:17 +0100, Ben Hutchings wrote: [...] +CONFIG_SERIAL_OF_PLATFORM=y [...] This seems to select some glue code for 8250-like serial ports, and the following symbols don't depend on it. Ignoring the beaglebone aspect for the moment -- might support for 8250-like serial ports via OF be a good thing for the armmp kernel to have anyway? On first glance the platforms using those compatibility strings which I recognise look mainly to be armel, but I've not dug into the ones I don't recognise yet. The only one I know I have seen with an 8250 in it is 64-bit ARM which isn't relevant in this config. Ian. $ grep compatible drivers/tty/serial/of_serial.c | cut -f2 -d\ | sort -u | while read i ; do grep -Rl $i arch/arm/boot/dts; done arch/arm/boot/dts/da850.dtsi arch/arm/boot/dts/dove.dtsi arch/arm/boot/dts/kirkwood.dtsi arch/arm/boot/dts/bcm5301x.dtsi arch/arm/boot/dts/orion5x.dtsi arch/arm/boot/dts/nspire-classic.dtsi arch/arm/boot/dts/lpc32xx.dtsi arch/arm/boot/dts/k2l.dtsi arch/arm/boot/dts/moxart.dtsi arch/arm/boot/dts/keystone.dtsi arch/arm/boot/dts/omap-zoom-common.dtsi arch/arm/boot/dts/da850.dtsi arch/arm/boot/dts/dove.dtsi arch/arm/boot/dts/kirkwood.dtsi arch/arm/boot/dts/orion5x.dtsi arch/arm/boot/dts/lpc32xx.dtsi arch/arm/boot/dts/k2l.dtsi arch/arm/boot/dts/moxart.dtsi arch/arm/boot/dts/keystone.dtsi arch/arm/boot/dts/omap-zoom-common.dtsi arch/arm/boot/dts/tegra124.dtsi arch/arm/boot/dts/tegra114.dtsi arch/arm/boot/dts/tegra30.dtsi arch/arm/boot/dts/tegra20.dtsi arch/arm/boot/dts/lpc32xx.dtsi $ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399620651.27638.7.ca...@dagon.hellion.org.uk
Bug#747482: Add IPMI drivers to 64bit parisc kernel
Package: linux Version: 3.14 Severity: bug Tags: patch 64bit (but not 32bit) parisc machines (like the C8000) do provide a BMC with IPMI support. This patchs adds IPMI support to the 64bit debian kernel. Please apply to the next kernel. Thanks, Helge diff -up ./debian/config/hppa/config.parisc64-smp.org ./debian/config/hppa/config.parisc64-smp --- ./debian/config/hppa/config.parisc64-smp.org 2014-05-09 10:59:19.997166749 +0200 +++ ./debian/config/hppa/config.parisc64-smp 2014-05-09 11:00:49.493146882 +0200 @@ -31,6 +31,15 @@ CONFIG_DRM_TTM=m CONFIG_DRM_RADEON=m ## +## file: drivers/char/ipmi/Kconfig +## +CONFIG_IPMI_HANDLER=m +CONFIG_IPMI_DEVICE_INTERFACE=m +CONFIG_IPMI_SI=m +CONFIG_IPMI_WATCHDOG=m +CONFIG_IPMI_POWEROFF=m + +## ## file: mm/Kconfig ## ## choice: Memory model
Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black
On Fri, May 09, 2014 at 08:30:51AM +0100, Ian Campbell wrote: On Fri, 2014-05-09 at 03:17 +0100, Ben Hutchings wrote: [...] +CONFIG_SERIAL_OF_PLATFORM=y [...] This seems to select some glue code for 8250-like serial ports, and the following symbols don't depend on it. Ignoring the beaglebone aspect for the moment -- might support for 8250-like serial ports via OF be a good thing for the armmp kernel to have anyway? On first glance the platforms using those compatibility strings which I recognise look mainly to be armel, but I've not dug into the ones I don't recognise yet. The only one I know I have seen with an 8250 in it is 64-bit ARM which isn't relevant in this config. OMAP plans to reuse 8250 code, but it doesn't seem to be ready for 3.16 (so not relevant for jessie): http://article.gmane.org/gmane.linux.drivers.devicetree/70986/match=serial+8250+add+omap+glue -- Sebastian signature.asc Description: Digital signature
Bug#746232: linux-image-3.2.0-4-rt-686-pae: rcu_preempt detected stalls at boot
On Mon, 2014-04-28 at 14:20 +0400, Alexandra N. Kossovsky wrote: Package: src:linux Version: 3.2.57-3 Severity: important Kernel 3.2.0-4-rt-686-pae does not boot for me. 3.2.0-4-686-pae (non-rt) works fine. Some other computers boot this kernel just fine. Serial console log with 3.2.0-4-rt-686-pae 3.2.57-3: [...] Is this a regression from version 3.2.54-2? Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Bug#744166: Any thoughts?
This has now happened to me twice in the past week. Once I got booted back to a console; once the screen completely locked up and I couldn't even switch VTs. SSHing in revealed that GDM, X, et all had been killed, but I couldn't seem to do anything to get the screen back without a reboot. If anyone has any suggestions on providing suggestions for how to find more information about this problem, I'm all ears. -- Brian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cac0bmdwcrk2alkaxb3nh26kqkvhjtuegvjpucrtq-ipftzk...@mail.gmail.com
