Bug#836251: linux: [armhf] Please enable support for veyron-speedy
On 2016-08-31, Vagrant Cascadian wrote: > Please enable support for veyron-speedy (a.k.a. ASUS Chromebook C201) > to linux 4.8.x. ... > Haven't had success getting output form the speakers or headphone > jack, though the OS seems to detect at least one device. headphone jack works, too! live well, vagrant > diff --git a/debian/config/armhf/config b/debian/config/armhf/config > index 0a9be6f..4fc638c 100644 > --- a/debian/config/armhf/config > +++ b/debian/config/armhf/config > @@ -1262,3 +1263,28 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m > CONFIG_SND_SOC_TEGRA_MAX98090=m > CONFIG_SND_SOC_TEGRA_RT5677=m > > +CONFIG_BATTERY_SBS=m > +CONFIG_DRM_PANEL=y > +CONFIG_DRM_PANEL_SIMPLE=m > +CONFIG_BACKLIGHT_PWM=m > +CONFIG_CHARGER_GPIO=m > +CONFIG_MFD_CROS_EC=m > +CONFIG_I2C_CROS_EC_TUNNEL=m > +CONFIG_MOUSE_ELAN_I2C=m > +CONFIG_KEYBOARD_CROS_EC=m > +CONFIG_KEYBOARD_GPIO=m > +CONFIG_POWER_RESET_GPIO=y > +CONFIG_POWER_RESET_GPIO_RESTART=y > +CONFIG_MFD_RK808=y > +CONFIG_COMMON_CLK_RK808=m > +CONFIG_REGULATOR_RK808=m > +CONFIG_RTC_DRV_RK808=y > +CONFIG_PHY_ROCKCHIP_DP=m > +CONFIG_MFD_CROS_EC_SPI=m > +CONFIG_ROCKCHIP_DW_MIPI_DSI=m > +CONFIG_DRM_ANALOGIX_DP=m > +CONFIG_ROCKCHIP_ANALOGIX_DP=m > +CONFIG_PHY_ROCKCHIP_EMMC=m > +CONFIG_ROCKCHIP_IODOMAIN=m > +CONFIG_POWER_AVS=y > +CONFIG_ROCKCHIP_PM_DOMAINS=y signature.asc Description: PGP signature
Bug#837627: [armhf] linux-image-4.7.0-1-armmp: Enable options for Novena
Package: linux Version: 4.7.2-1 Severity: wishlist Tags: patch Please enable the following options to add support for hardware present on Novena systems. Thanks! live well, vagrant diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 0a9be6f..d17e003 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -1262,3 +1262,10 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m CONFIG_SND_SOC_TEGRA_MAX98090=m CONFIG_SND_SOC_TEGRA_RT5677=m +CONFIG_BACKLIGHT_PWM=m +CONFIG_DRM_PANEL_SIMPLE=m +CONFIG_MFD_STMPE=y +CONFIG_TOUCHSCREEN_STMPE=m +CONFIG_SND_SOC_IMX_ES8328=m +CONFIG_BATTERY_SBS=m +CONFIG_MMA8452=m signature.asc Description: PGP signature
Processed: Re: Bug#836741: linux: FTBFS on powerpcspe due to the use of unsupported instructions
Processing control commands: > tag -1 upstream patch Bug #836741 [src:linux] linux: FTBFS on powerpcspe due to the use of unsupported instructions Ignoring request to alter tags of bug #836741 to the same tags previously set -- 836741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836741: linux: FTBFS on powerpcspe due to the use of unsupported instructions
Control: tag -1 upstream patch On Sat, 2016-09-10 at 11:01 +0200, John Paul Adrian Glaubitz wrote: > Control: forwarded -1 > https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-September/148424.html > Control: tags -1 +pending > > There is now a suggested patch on the linuxppc-dev mailing list which fixes > this issue [1]. Should be part of the next stable kernel update, will > therefore > tag this bug report as pending. It won't, it's not even in linux-next yet. Please don't add the pending tag just because a patch has been accepted upstream. Anyway, I have applied this to the sid branch so it really is pending now. Ben. -- Ben Hutchings Klipstein's 4th Law of Prototyping and Production: A fail-safe circuit will destroy others. signature.asc Description: This is a digitally signed message part
Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Control: tag -1 pending On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote: [...] > So, can you please deactivate CONFIG_FTRACE completely for 32- and 64bit hppa > configs? > Is it sufficient to add "CONFIG_FTRACE=n" to debian/config/hppa/config ? Done. Ben. -- Ben Hutchings Klipstein's 4th Law of Prototyping and Production: A fail-safe circuit will destroy others. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Processing control commands: > tag -1 pending Bug #837588 [linux] hppa: Please disable CONFIG_FTRACE for hppa architecture Added tag(s) pending. -- 837588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Package: linux Version: 4.7.2-1 Severity: important We sadly will need to disable CONFIG_FTRACE for hppa architecture completely for now. The problem is, that gcc creates lots of overhead when adding the code for the mcount call (minimum 16 bytes per function, plus two relocation symbol entries) which leads that the 64bit vmlinux kernel file for 4.7 becomes around 99MB, while vmlinux for kernel 4.6 was just around 17MB. This size wouldn't be a real problem itself, but sadly the default /boot partition is currently maximum 128 MB in size which is not able to keep the vmlinux file plus the size for the initrd image (which is a lot bigger than 100MB then). That leads to the fact, that people who have a default hppa installation will not be able to install the new kernel (and don't have space in /boot to keep other older images either). So, can you please deactivate CONFIG_FTRACE completely for 32- and 64bit hppa configs? Is it sufficient to add "CONFIG_FTRACE=n" to debian/config/hppa/config ? Thanks! Helge PS: I'm still working on upstream ftrace support for hppa. It's not complete yet, so we don't loose to much when we disable ftrace again now. Further more I will adjust the debian installer to create bigger /boot partitions so that we can enable it later again.
