-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/26/2012 04:02 PM, Cristian Rodríguez wrote:

El 26/04/12 14:25, Jeff Mahoney escribió:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi all -

Just a quick heads up that I've disabled a bunch of options on the HEAD kernel.

Funny, I was about to write an email to this list asking why there were so many drivers in the -desktop kernel with no apparent use...

I assume these changes are only applicable to x86(_64?)-{default,desktop,xen} right ?

I've applied the changes to all arches except for armv7l. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPma99AAoJEB57S2MheeWyfK4P/20A2h7KGxtvge83GDKH8+4v 9zeSqneMOqiI4crZG0OvDbJErvpMfcIYNvuOZylowaZnUabH5j5JKvMLDzF0hkYd CDObAhlOtNZIJ9iEGVfZwBxl25xDmFjQUP5oNyEaZPondAEWu8PMzYae3VkA088N Dl0XctBNAJNj8pcqXFthO0gcDfa1nRwiJQ3oCEgGr2zOy64tRad5J47XLFFBY+uE JKHjYN1isFisgK3THqIqbr6caB/aLwc62cRd5Htm85lN/5o2st2IsskxqGcgOGj9 9Ps/J7KD/jj/Wbt4ugAUh5eYZOmO365O2E59SZFp8k3iiGTomAN9wU3dY9HORJxf mBiGCGzEgsHAG2JtfwAGiGsX1vFW02N4KMKQPtRj1kUx7d9NAccTUO6iWp27MloT c2RniEkeSaiHkwuJw4EvA2KS2Z44lQgrIbLYrOs4yx2sb80cRJp15kfzLQ9MgxiN acUrDI5bFUBaeDjmL0NkSlkx3WkqF0Kw7jVyXGINKlCpcsny9/a8RzXgxa4UDJ5f PIiVXIOqpYLDdbUOB6hRvFnE9DgVLTPi7aW87vazHMml4HoEsZHypy03ovWJG2cP EwyUbDlpF4uhAuCqi2mN5kQhu4x8psH5rQh/9gOqmjxbnHKvQCTOjyGSDMFsMjel a36eezs3l/bjDDISho79 =nCmy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/27/2012 09:14 AM, Jean Delvare wrote:

Hi Jeff,

On Thursday 26 April 2012 07:25:15 pm Jeff Mahoney wrote:

...

I've disabled many drivers that can only be used on embedded hardware. While I don't doubt that there are users out there playing with Linux on embedded hardware - I do doubt that they're using an openSUSE-built kernel RPM. The disabled modules include voltage regulators, multifunction devices that are typically found on SoCs, IIO sensor drivers, SPI drivers, and drivers only used on Intel Medfield or Moorestown.

I2C_INTEL_MID would be a candidate too then?

Yes indeed. After a bit more digging I found some others as well. Also disabled: CONFIG_SFI MTD_NAND_DENALI SERIAL_MRST_MAX3110 DRM_GMA600 SPI_DW_MID_DMA APDS9802ALS CONFIG_IWM could probably be disabled as well, but the description just says "typically found on Moorestown". Does anyone happen to know if these devices exist as standalone SD cards that can be used elsewhere? Is SPI also limited to embedded devices? It seems like that's the case. That results in the following options turning off: CONFIG_AD525X_DPOT_SPI CONFIG_CAN_MCP251X CONFIG_EEPROM_93XX46 CONFIG_EEPROM_AT25 CONFIG_ENC28J60 CONFIG_EZX_PCAP CONFIG_GPIO_74X164 CONFIG_GPIO_MAX7301 CONFIG_GPIO_MC33880 CONFIG_INPUT_AD714X_SPI CONFIG_INPUT_ADXL34X_SPI CONFIG_INPUT_PCAP CONFIG_KS8851 CONFIG_LCD_AMS369FG06 CONFIG_LCD_ILI9320 CONFIG_LCD_L4F00242T03 CONFIG_LCD_LD9040 CONFIG_LCD_LMS283GF05 CONFIG_LCD_LTV350QV CONFIG_LCD_S6E63M0 CONFIG_LCD_TDO24M CONFIG_LCD_VGG2432A4 CONFIG_LEDS_DAC124S085 CONFIG_LIBERTAS_SPI CONFIG_M25PXX_USE_FAST_READ CONFIG_MICREL_KS8995MA CONFIG_MMC_SPI CONFIG_MTD_DATAFLASH CONFIG_MTD_DATAFLASH_OTP CONFIG_MTD_DATAFLASH_WRITE_VERIFY CONFIG_MTD_M25P80 CONFIG_MTD_SST25L CONFIG_NET_VENDOR_MICROCHIP CONFIG_OF_SPI CONFIG_P54_SPI CONFIG_RTC_DRV_DS1305 CONFIG_RTC_DRV_DS1390 CONFIG_RTC_DRV_DS3234 CONFIG_RTC_DRV_M41T93 CONFIG_RTC_DRV_M41T94 CONFIG_RTC_DRV_MAX6902 CONFIG_RTC_DRV_PCAP CONFIG_RTC_DRV_PCF2123 CONFIG_RTC_DRV_R9701 CONFIG_RTC_DRV_RS5C348 CONFIG_SENSORS_AD7314 CONFIG_SENSORS_ADCXX CONFIG_SENSORS_ADS7871 CONFIG_SENSORS_LIS3_SPI CONFIG_SENSORS_LM70 CONFIG_SENSORS_MAX1111 CONFIG_SERIAL_IFX6X60 CONFIG_SERIAL_MAX3107 CONFIG_SND_SPI CONFIG_SPI CONFIG_SPI_ALTERA CONFIG_SPI_BITBANG CONFIG_SPI_BUTTERFLY CONFIG_SPI_DEBUG CONFIG_SPI_DESIGNWARE CONFIG_SPI_DW_MMIO CONFIG_SPI_DW_PCI CONFIG_SPI_GPIO CONFIG_SPI_LM70_LLP CONFIG_SPI_MASTER CONFIG_SPI_MPC52xx CONFIG_SPI_OC_TINY CONFIG_SPI_PXA2XX CONFIG_SPI_PXA2XX_PCI CONFIG_SPI_SPIDEV CONFIG_SPI_TLE62X0 CONFIG_SPI_TOPCLIFF_PCH CONFIG_SPI_XILINX CONFIG_TI_DAC7512 CONFIG_TOUCHSCREEN_AD7877 CONFIG_TOUCHSCREEN_AD7879_SPI CONFIG_TOUCHSCREEN_ADS7846 CONFIG_TOUCHSCREEN_CYTTSP_SPI CONFIG_TOUCHSCREEN_PCAP CONFIG_TOUCHSCREEN_TSC2005 CONFIG_WL1251_SPI CONFIG_WL12XX_SPI - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmqfvAAoJEB57S2MheeWyaAcP/RqZsG7UiJD6Sc8r+ZHmtyI/ GSrLkEhwJazR7dxIGoMTmlSDQcFDiHmwwAKz4NrXeMyIuzhXs7LTdSccd8xvfZDj RJEHM303cO3xVXx52ud87WEY5pYmw3jibCYYYSTiKN2OTmKjfsjnkEsnB3nabxth mcfb3wnpkJ7I7Ackavlxzq8Qax98aDNBjL3haOcIlsbwjacuj99weqQFd84BNcOD UF5c6rv0XmvrXoYHwo0jEg+NUH02W89u/wEMXjv+UyppelpNGiVGAY5LQMwNga4u 1Gan+8M6KO2Mvx5B9fiCWbSNXTKG9163Bw7Z8wRSERA0N6U10IPVsGUDhJs9IRlm SnesC4UTSnZ5XNDVq74Rz3WOXQbKhpcO74peKqEAK7VhR7QsnbfmP5qVG/N6njI9 NbES1Udil+5ld1IadtAgiI3G2kSqDXRFCYPvPp9UzmhFeMKAhSiMzbNuJOKLAbKd aUKcj8LXa0tvpUQVUyzZfQC2PqMPREaUtXBh+I4I+7/nBq36Y/fcIaiflZAAspKx nUBbGRTOlJMEjRN9t9BHJKXcNV8bh373upn+U1eNm59mlN3N47RSKna1BVzq4mru 4ZH0YyJdYiYxpgLSUvCTbrwWyNwUTRBs83pJPE0xF254cN/KCP9HPrc431PaAUQP pPmcq292D5Nj+DVqtC39 =20s1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/27/2012 10:33 AM, Guillaume Gardet wrote:

Le 27/04/2012 16:06, Jeff Mahoney a écrit : On 04/27/2012 09:14 AM, Jean Delvare wrote:

...

...

...

Hi Jeff,

On Thursday 26 April 2012 07:25:15 pm Jeff Mahoney wrote:

...

I've disabled many drivers that can only be used on embedded hardware. While I don't doubt that there are users out there playing with Linux on embedded hardware - I do doubt that they're using an openSUSE-built kernel RPM. The disabled modules include voltage regulators, multifunction devices that are typically found on SoCs, IIO sensor drivers, SPI drivers, and drivers only used on Intel Medfield or Moorestown. I2C_INTEL_MID would be a candidate too then? Yes indeed. After a bit more digging I found some others as well.

Also disabled: CONFIG_SFI MTD_NAND_DENALI SERIAL_MRST_MAX3110 DRM_GMA600 SPI_DW_MID_DMA APDS9802ALS

CONFIG_IWM could probably be disabled as well, but the description just says "typically found on Moorestown". Does anyone happen to know if these devices exist as standalone SD cards that can be used elsewhere?

Is SPI also limited to embedded devices? It seems like that's the case. That results in the following options turning off:

...

I think SD/MMC can operate in SPI mode.

Do you have examples of non-embedded hardware that does this? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmq/PAAoJEB57S2MheeWyo2UP/1dipQG/bzyyyOG0Bli/guQo joRnixrrxLlW09q61UvUmdg3kl8a7lPt0WSsjN67z1J2ujlnuZT/otsMqMc60PGf Jfiu8+oP3GhWKKVDsgBeesMJsDPmeqTi9N/oXj5vKe9XQYyDLaCG+Vkg8e1e8ley pwavlZZe1+rpjGgYYeyxDtBrkPwQLrUp2Ym/dMunXckHK8OalbbmDuApFzxWqFLs eV/hFdkGKabClxUvTh44T1fhD8asqN8ycs81kFb8H9c1k6PZ0HG7Zb1KKy+L9E8W ZnyM9jkkG4+NITLXofVGx9Wa9ROX3Ob965Nwh/lHNeW0GIQnO3mAFAQwkVG3eh/x qDC6eTTZ6APwPuw7QB9SAsRTeaX1VehU/1Rty0wpU7fdim+5tg9laYWQGwqHSJg2 zzeloEoZjeABFYxuTvTkXEBeS+lY5PFyhybgpypcXu9pWch0fukQUZ6F9+wXebFK aQxsljfZ7vnZM/0v+b89/LZGmXY231eZvnTQAbZOD+hk+9G7eaKe55wJIj6lIp67 9OvCm1GePJkBa6/yPyxXCZS3ioV1gI5UEbAZ5A+dWdsdQpv0Jno8jMAP89bUPOpx DIXzZAuOkaQMsJYe+2lRRpl02xnF09B91Z8G5WcKVvWbmdymrtGIUEIocbVrbuMU BpyXPy1OB6bC0BZ4C9uV =LtL9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

El 06/05/12 00:42, Cristian Rodríguez escribió:

El 06/05/12 00:14, Cristian Rodríguez escribió:

...

El 26/04/12 14:25, Jeff Mahoney escribió:

You can add to your list

CONFIG_CRYPTO_TEST=NO if !kernel-debug CONFIG_DMATEST=NO if !kernel-debug CONFIG_RTC_DRV_TEST=NO if !kernel-debug

Also ALL of:

CONFIG_FB_GEODE=y CONFIG_FB_GEODE_LX=m CONFIG_FB_GEODE_GX=m CONFIG_FB_GEODE_GX1=m CONFIG_MTD_AMD76XROM=m

enabled only if X86_32

Same case for CONFIG_HW_RANDOM_INTEL depends on X86_32 && !SMP -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

El 07/05/12 03:48, Jan Beulich escribió:

...

Same case for CONFIG_HW_RANDOM_INTEL depends on X86_32&& !SMP

Since when and why?

There are no x86_64 motherboards with that chipset.. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

El 08/05/12 02:44, Jan Beulich escribió:

...

...

...

On 07.05.12 at 18:53, Cristian Rodríguez wrote: El 07/05/12 03:48, Jan Beulich escribió:

...

...

Same case for CONFIG_HW_RANDOM_INTEL depends on X86_32&& !SMP

Since when and why?

There are no x86_64 motherboards with that chipset..

What is "that chipset" in this context? There's quite a list of different ones comprising the driver's pci_tbl[]. And I personally have a Dell system that's 64-bit capable and covered by the table.

Jan

The "Intel i810 Random Number Generator" is not present on any x86_64 machine, only in old single processor, 32 bit systems (Pentium 2, 3..) (not to be confused with newer RDRAND thing) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/06/2012 12:42 AM, Cristian Rodríguez wrote:

El 06/05/12 00:14, Cristian Rodríguez escribió:

...

El 26/04/12 14:25, Jeff Mahoney escribió:

You can add to your list

CONFIG_CRYPTO_TEST=NO if !kernel-debug CONFIG_DMATEST=NO if !kernel-debug CONFIG_RTC_DRV_TEST=NO if !kernel-debug

Also ALL of:

CONFIG_FB_GEODE=y CONFIG_FB_GEODE_LX=m CONFIG_FB_GEODE_GX=m CONFIG_FB_GEODE_GX1=m CONFIG_MTD_AMD76XROM=m

enabled only if X86_32

This one should probably be changed in the source so that the option depends on X86_32 instead of X86. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPqn2mAAoJEB57S2MheeWy3DMP/i4O2y7d18rchV8fzgYDvDkX 67hbnpMQY96H1tPiLDzzlaEOIF8It+4zZ5hYfkhoj+VCBzktjvx9Qo97/OMyj0ck 8Uq4nq3mxSzpsjxTLZRUqIt9bndPPB5QMorOD8a5TyrnWN75DOsWd0rbGDMhVrXK PVGGDIXdafUuKoTYylx0fl3h3SeGecI3TuVNHnQpck5elzwwOLUIbrz9lUS54Gdv xHBLvPydXu9yQB67wAiQ11LbK0IHcyXM5/zNpu1Fh4hjUDNd63QB45VKak1P5jMO +JoKqe+4/Fwail5paajpg0HRN4jCbb2K3LM0XdpnEMAZ+Zh2IMgQvBxlFUGqdnfN dv+W9pYQx2XmFRPsRfdwctTZDsFS9mwBXS3PyvnxjGiwnLuQnzaygqAlNU6+kZbg 2j4XNUNUxtW8fzn2oAPzQzVlb1uG+RAy2lUxFD1qbzWgfiRGhCKMtUuZNDqZrrlR tL0BVVYgL/d7iWi87cfxb9K9Gv3NmdTpyILMRX76oRdVkXsre1KJsqMLYixfmc9Y L/Ma+sbX5bDjjKdhg4bCCZdSptSylaedL7C+Zf/f27oldzjZOOr5IW6Gm8HRMxp5 IHagw/RXyslrMTJwhJCBR9DBAzEMNU1IbfRML7q0xlgzPoOuzR764FOPSuosBNXY Qc7jKkBMuOl4yQ9ZnDa3 =KSBr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

On 10/05/12 00:07, Cristian Rodríguez wrote:

On 26/04/12 14:25, Jeff Mahoney wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi all -

Just a quick heads up that I've disabled a bunch of options on the HEAD kernel.

others for consideration:

CONFIG_TEST_POWER CONFIG_VIDEO_MEM2MEM_TESTDEV

in the !kernel-debug case.

Also, at least CONFIG_USB_STORAGE_KARMA=y should be "m" (was bool, tristate since 2.6.30) unless of course, someone wants to boot from a music player =) Also there a several other usb-storage drivers builtin into the kernel CONFIG_USB_STORAGE_DATAFAB=y CONFIG_USB_STORAGE_FREECOM=y CONFIG_USB_STORAGE_ISD200=y CONFIG_USB_STORAGE_USBAT=y CONFIG_USB_STORAGE_SDDR09=y CONFIG_USB_STORAGE_SDDR55=y CONFIG_USB_STORAGE_JUMPSHOT=y CONFIG_USB_STORAGE_ALAUDA=y CONFIG_USB_STORAGE_ONETOUCH=y CONFIG_USB_STORAGE_CYPRESS_ATACB=y many of them nowdays are "tristate" but previously were only "bool", is this an oversight or this drivers cannot be automagically added into initrd when needed ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org