Bug#774896: Exynos4 CONFIG_HZ
With the improvements in upstream support for exynos4 devices I've been looking into adding support odroid devices to Debian's armmp kernel. The kernel config changes needed are quite minimal as can be seen here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774896 Mostly enabling support and various modules. However as Ian Campbell notes, enabling ARCH_EXYNOS4 triggers the following from arch/arm/Kconfig: config HZ_FIXED int default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \ ARCH_S5PV210 || ARCH_EXYNOS4 default AT91_TIMER_HZ if ARCH_AT91 default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE_LEGACY default 0 This forces CONFIG_HZ=200 for the entire armmp kernel, which is undesirable. The reason for this setting isn't very clear to either me or Ian. I personally have verified that HZ=250 (the default for debian armmp kernels) boots fine. Is there a particular reason for this setting? Would a patch removing this requirement for ARCH_EXYNOS4 be accepted? -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774896: Info received (Bug#774896: Acknowledgement (linux: The armmp kernel config doesn't support exynos4 / odroid hardware))
As an additional note, I have performed some tests with CONFIG_REGULATOR_MAX77686=m This works - if the module is included in the initramfs. However initramfs-tools fails to include the max77686 module by default (the dependency between the mtd / mmc modules and max77686 isn't worked out) I could only get this to work when I forced it by adding the module to /etc/initramfs-tools/modules. The end result is a non-booting system with no easy way to fix it. From a user perspective it would certainly be preferrable to set CONFIG_REGULATOR_MAX77686=y because then the default initramfs works and gets you a bootable system. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774896: Acknowledgement (linux: The armmp kernel config doesn't support exynos4 / odroid hardware)
Please note that CONFIG_REGULATOR_MAX77686 needs to be built-in, I tried building it as a module but that caused mmc/sdhci failures ( and no rootfs ). -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774896: linux: The armmp kernel config doesn't support exynos4 / odroid hardware
Package: src:linux Version: 3.18-1~exp1 Severity: important File: linux Tags: newcomer patch Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Currently there is no working debian kernel for exynos4 / odroid platforms. The vendor hands out 3.8 / 3.10 kernels - with custom patches and minimal configs. However device-tree support is available in upstream uboot versions and newer kernels have pretty complete support for the hardware. * What exactly did you do (or not do) that was effective (or ineffective)? I have patched the armmp kernel config with the options needed for odroid / exynos support. NB: I've only verified serial-console boot / networking. * What was the outcome of this action? See dmesg - it works. Please add the following patch to the armmp config: --- config.armmp.orig 2015-01-06 19:27:33.883364445 +0100 +++ config.armmp2015-01-08 08:57:53.031773518 +0100 @@ -12,6 +12,7 @@ CONFIG_SMP_ON_UP=y CONFIG_HIGHMEM=y CONFIG_XEN=y +CONFIG_ARM_AMBA=y CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y ## choice: Kernel command line type @@ -31,7 +32,7 @@ ## CONFIG_ARCH_EXYNOS=y # CONFIG_ARCH_EXYNOS3 is not set -# CONFIG_ARCH_EXYNOS4 is not set +CONFIG_ARCH_EXYNOS4=y CONFIG_ARCH_EXYNOS5=y ## @@ -141,17 +142,19 @@ ## CONFIG_COMMON_CLK_S2MPS11=m CONFIG_CLK_TWL6040=m +CONFIG_COMMON_CLK_MAX77686=m +CONFIG_COMMON_CLK_MAX77802=m ## ## file: drivers/cpufreq/Kconfig ## CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_STAT=m -CONFIG_CPUFREQ_DT=m ## ## file: drivers/cpufreq/Kconfig.arm ## +CONFIG_CPUFREQ_DT=m CONFIG_ARM_IMX6Q_CPUFREQ=m ## @@ -265,6 +268,7 @@ ## ## file: drivers/iio/adc/Kconfig ## +CONFIG_EXYNOS_ADC=m CONFIG_TI_AM335X_ADC=m CONFIG_TWL4030_MADC=m @@ -307,6 +311,7 @@ ## CONFIG_OMAP_IOMMU=y # CONFIG_OMAP_IOMMU_DEBUG is not set +CONFIG_EXYNOS_IOMMU=y ## ## file: drivers/leds/Kconfig @@ -315,6 +320,7 @@ CONFIG_LEDS_GPIO=m CONFIG_LEDS_LP5523=m CONFIG_LEDS_DA9052=m +CONFIG_LEDS_MAX8997=m CONFIG_LEDS_PWM=m ## @@ -364,8 +370,15 @@ ## ## file: drivers/mfd/Kconfig ## +CONFIG_MFD_CROS_EC=y +CONFIG_MFD_CROS_EC_I2C=y +CONFIG_MFD_CROS_EC_SPI=y CONFIG_MFD_DA9052_SPI=y CONFIG_MFD_DA9052_I2C=y +CONFIG_MFD_MAX77686=y +CONFIG_MFD_MAX77693=y +CONFIG_MFD_MAX8997=y +CONFIG_MFD_TPS65090=y CONFIG_MFD_MC13XXX_SPI=m CONFIG_MFD_MC13XXX_I2C=m CONFIG_MFD_SEC_CORE=y @@ -394,11 +407,13 @@ CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_SDHCI_ESDHC_IMX=m +CONFIG_MMC_SDHCI_S3C=m CONFIG_MMC_OMAP=m CONFIG_MMC_OMAP_HS=m CONFIG_MMC_MVSDIO=m CONFIG_MMC_SPI=m CONFIG_MMC_DW=m +CONFIG_MMC_DW_IDMAC=y CONFIG_MMC_DW_EXYNOS=m CONFIG_MMC_WMT=m CONFIG_MMC_SUNXI=m @@ -610,6 +625,8 @@ CONFIG_BATTERY_BQ27x00=m CONFIG_CHARGER_ISP1704=m CONFIG_CHARGER_BQ2415X=m +CONFIG_CHARGER_MAX8997=m +CONFIG_CHARGER_TPS65090=m ## ## file: drivers/power/reset/Kconfig @@ -623,6 +640,7 @@ ## CONFIG_PWM=y CONFIG_PWM_IMX=m +CONFIG_PWM_SAMSUNG=m CONFIG_PWM_TIECAP=m CONFIG_PWM_TIEHRPWM=m CONFIG_PWM_TWL=m @@ -635,11 +653,17 @@ CONFIG_REGULATOR=y CONFIG_REGULATOR_ANATOP=m CONFIG_REGULATOR_DA9052=m +CONFIG_REGULATOR_GPIO=m +CONFIG_REGULATOR_MAX8997=m +CONFIG_REGULATOR_MAX77693=m +CONFIG_REGULATOR_MAX77686=y +CONFIG_REGULATOR_MAX77802=m CONFIG_REGULATOR_MC13783=m CONFIG_REGULATOR_MC13892=m CONFIG_REGULATOR_S2MPA01=m CONFIG_REGULATOR_S2MPS11=m CONFIG_REGULATOR_S5M8767=m +CONFIG_REGULATOR_TPS65090=m CONFIG_REGULATOR_TWL4030=y CONFIG_REGULATOR_VEXPRESS=m @@ -657,9 +681,13 @@ CONFIG_RTC_DRV_VT8500=y CONFIG_RTC_DRV_SUNXI=y CONFIG_RTC_DRV_MV=y +CONFIG_RTC_DRV_MAX77686=y +CONFIG_RTC_DRV_MAX77802=y +CONFIG_RTC_DRV_MAX8997=y CONFIG_RTC_DRV_MC13XXX=y CONFIG_RTC_DRV_MXC=y CONFIG_RTC_DRV_SNVS=y +CONFIG_RTC_DRV_S3C=y ## ## file: drivers/scsi/Kconfig @@ -697,6 +725,8 @@ ## file: drivers/thermal/Kconfig ## CONFIG_ARMADA_THERMAL=y +CONFIG_EXYNOS_THERMAL=y +CONFIG_EXYNOS_THERMAL_CORE=y ## ## file: drivers/tty/serial/Kconfig @@ -849,6 +879,7 @@ CONFIG_ARM_SP805_WATCHDOG=m CONFIG_OMAP_WATCHDOG=m CONFIG_ORION_WATCHDOG=m +CONFIG_S3C2410_WATCHDOG=m CONFIG_SUNXI_WATCHDOG=m CONFIG_TWL4030_WATCHDOG=m CONFIG_IMX2_WDT=m @@ -890,3 +921,17 @@ CONFIG_SND_OMAP_SOC_OMAP_HDMI=m CONFIG_SND_OMAP_SOC_OMAP3_PANDORA=m +## +## file: sound/soc/samsung/Kconfig +## +CONFIG_SND_SOC_SAMSUNG=m +CONFIG_SND_SAMSUNG_PCM=m +CONFIG_SND_SAMSUNG_SPDIF=m +CONFIG_SND_SAMSUNG_I2S=m +CONFIG_SND_SOC_SAMSUNG_SMDK_WM8994=m +CONFIG_SND_SOC_SAMSUNG_SMDK_SPDIF=m +CONFIG_SND_SOC_SMDK_WM8994_PCM=m +CONFIG_SND_SOC_SNOW=m +CONFIG_SND_SOC_ODROIDX2=m +CONFIG_SND_SOC_ARNDALE_RT5631_ALC5631=m +CONFIG_SND_SOC_I2C_AND_SPI=m -- Package-specific info: ** Version: Linux version 3.18.0-trunk-armmp (debian-ker...@lists.debian.org) (gcc version 4.9.1 (Debian 4.9.1-19) ) #1 SMP Debian 3.18-1~exp1 (2014-12-11) ** Command line: console=tty1 console=ttySAC1,115200n8 root=/dev/mmcblk0p2 rootwait ro earlyprintk ** Not tai
Bug#650670: Info received (Bug#650670: ladvd: FTBFS (check_cli failure))
I've submitted ladvd 0.9.2-2 to mentors which fixes these issues. http://mentors.debian.net/debian/pool/main/l/ladvd/ladvd_0.9.2-2.dsc -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#650670: ladvd: FTBFS (check_cli failure)
On Thu, 1 Dec 2011, Julien Cristau wrote: Package: ladvd Version: 0.9.2-1.1 Severity: serious Justification: fails to build from source (but built successfully in the past) See https://buildd.debian.org/status/package.php?p=ladvd Only the tests fail with libevent 2.0, the rest of the code works. There are two ways to solve this, either merge a fix for the tests or just skip the tests when building the package. Not sure which is the preferred solution. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636200: ladvd log spam
I can confirm that this patch fixes the reported issue. The same code has been added to upstream in: https://github.com/reubenhwk/radvd/commit/6e120ac9027a25f719a5a74560c5b162a4a7aa93 https://github.com/reubenhwk/radvd/commit/4218c7ddb7d2a87ebd4559a3df8b88c61ed56ab5#process.c I suggest adding this patch for testing and upgrading to 1.8.3 (which includes this patch) for unstable. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572336: RFP: ladvd -- cdp / lldp sender for unix
Package: wnpp Severity: wishlist * Package name: ladvd Version : 0.8.6 Upstream Author : Sten Spans * URL : http://www.blinkenlights.nl/software/ladvd/ * License : ISC Programming Lang: C Description : cdp / lldp sender for unix ladvd uses cdp / lldp frames to inform switches about connected hosts, which simplifies ethernet switch management. It does this by creating a raw socket at startup, and then switching to a non-privileged user for the remaining runtime. Every 30 seconds it will transmit CDP/LLDP packets reflecting the current system state. Interfaces (bridge, bonding, wireless), capabilities (bridging, forwarding, wireless) and addresses (IPv4, IPv6) are detected dynamically. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
