mail archive opensuse-kernel.opensuse.org
(List home) (Recent threads) (97 other OpenSUSE lists)
Subscription Options
- RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
- Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
- Low traffic list: less than 3 messages per day
- This list contains about 4,657 messages, beginning Aug 2007
- 0 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no
[CONFIG] Disabled options
Ad
Hi all -
Just a quick heads up that I've disabled a bunch of options on the
HEAD kernel.
I've disabled DECNet and ARCnet. I've disabled LocalTalk drivers on
i386-default.
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.
I'd like to try to clear out as many of the drivers we're building
that are
inappropriate for desktop, server, or notebook systems. That includes
drivers that
are only used for embedded devices and hardware that is so ancient
that nobody is
likely to be using it anymore. The former is pretty easy but the
latter gets tricky.
The goal is to save on users' disk space, download bandwidth, and
build resources.
DECNet and ARCnet were rare already in my former life as a sysadmin.
That was over 10
years ago.
Here's the full list of disabled options:
CONFIG_ARCNET
CONFIG_ARCNET_1051
CONFIG_ARCNET_1201
CONFIG_ARCNET_CAP
CONFIG_ARCNET_COM20020_CS
CONFIG_ARCNET_COM20020
CONFIG_ARCNET_COM20020_PCI
CONFIG_ARCNET_COM90xxIO
CONFIG_ARCNET_COM90xx
CONFIG_ARCNET_RAW
CONFIG_ARCNET_RIM_I
CONFIG_DECNET
CONFIG_DECNET_NF_GRABULATOR
CONFIG_COPS
CONFIG_LTPC
CONFIG_AD2S1200, CONFIG_AD2S1210, CONFIG_AD2S90, CONFIG_AD5064,
CONFIG_AD5360, CONFIG_AD5380, CONFIG_AD5421, CONFIG_AD5446,
CONFIG_AD5504,
CONFIG_AD5624R_SPI, CONFIG_AD5686, CONFIG_AD5764, CONFIG_AD5791,
CONFIG_AD5930, CONFIG_AD5933, CONFIG_AD7150, CONFIG_AD7152,
CONFIG_AD7192,
CONFIG_AD7280, CONFIG_AD7291, CONFIG_AD7298, CONFIG_AD7476,
CONFIG_AD7606_IFACE_PARALLEL, CONFIG_AD7606_IFACE_SPI, CONFIG_AD7606,
CONFIG_AD7746, CONFIG_AD7780, CONFIG_AD7793, CONFIG_AD7816,
CONFIG_AD7887,
CONFIG_AD799X, CONFIG_AD799X_RING_BUFFER, CONFIG_AD9832,
CONFIG_AD9834,
CONFIG_AD9850, CONFIG_AD9852, CONFIG_AD9910, CONFIG_AD9951,
CONFIG_ADE7753, CONFIG_ADE7754, CONFIG_ADE7758, CONFIG_ADE7759,
CONFIG_ADE7854_I2C, CONFIG_ADE7854, CONFIG_ADE7854_SPI,
CONFIG_ADIS16060,
CONFIG_ADIS16080, CONFIG_ADIS16130, CONFIG_ADIS16201,
CONFIG_ADIS16203,
CONFIG_ADIS16204, CONFIG_ADIS16209, CONFIG_ADIS16220,
CONFIG_ADIS16240,
CONFIG_ADIS16260, CONFIG_ADIS16400, CONFIG_ADT7310,
CONFIG_ADT7316_I2C,
CONFIG_ADT7316, CONFIG_ADT7316_SPI, CONFIG_ADT7410, CONFIG_ADXRS450,
CONFIG_BACKLIGHT_WM831X, CONFIG_CAN_JANZ_ICAN3, CONFIG_FB_SM501,
CONFIG_GPIO_JANZ_TTL, CONFIG_GPIO_RDC321X, CONFIG_GPIO_STMPE,
CONFIG_GPIO_TIMBERDALE, CONFIG_GPIO_WM831X, CONFIG_IIO_BUFFER,
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2, CONFIG_IIO_GPIO_TRIGGER,
CONFIG_IIO_KFIFO_BUF, CONFIG_IIO, CONFIG_IIO_PERIODIC_RTC_TRIGGER,
CONFIG_IIO_SIMPLE_DUMMY, CONFIG_IIO_ST_HWMON, CONFIG_IIO_SW_RING,
CONFIG_IIO_SYSFS_TRIGGER, CONFIG_IIO_TRIGGER,
CONFIG_INPUT_MC13783_PWRBUTTON, CONFIG_INPUT_WM831X_ON,
CONFIG_KEYBOARD_STMPE, CONFIG_KXSD9, CONFIG_LEDS_MC13783,
CONFIG_LEDS_REGULATOR, CONFIG_LEDS_WM831X_STATUS,
CONFIG_LIS3L02DQ_BUF_KFIFO, CONFIG_LIS3L02DQ, CONFIG_MAX1363,
CONFIG_MAX1363_RING_BUFFER, CONFIG_MAX517, CONFIG_MFD_CORE,
CONFIG_MFD_JANZ_CMODIO, CONFIG_MFD_MC13783, CONFIG_MFD_MC13XXX,
CONFIG_MFD_RDC321X, CONFIG_MFD_SM501_GPIO, CONFIG_MFD_SM501,
CONFIG_MFD_STMPE, CONFIG_MFD_TIMBERDALE, CONFIG_MFD_TPS65217,
CONFIG_MFD_WM831X_SPI, CONFIG_MFD_WM831X, CONFIG_MFD_WM8400,
CONFIG_RADIO_TIMBERDALE, CONFIG_REGMAP_I2C, CONFIG_REGMAP_SPI,
CONFIG_REGMAP, CONFIG_REGULATOR_AD5398, CONFIG_REGULATOR_DA903X,
CONFIG_REGULATOR_DEBUG, CONFIG_REGULATOR_DUMMY,
CONFIG_REGULATOR_FIXED_VOLTAGE, CONFIG_REGULATOR_GPIO,
CONFIG_REGULATOR_ISL6271A, CONFIG_REGULATOR_LP3971,
CONFIG_REGULATOR_LP3972, CONFIG_REGULATOR_MAX1586,
CONFIG_REGULATOR_MAX8649, CONFIG_REGULATOR_MAX8660,
CONFIG_REGULATOR_MAX8952, CONFIG_REGULATOR_MC13783,
CONFIG_REGULATOR_MC13892, CONFIG_REGULATOR_MC13XXX_CORE,
CONFIG_REGULATOR_PCAP, CONFIG_REGULATOR_TPS6105X,
CONFIG_REGULATOR_TPS62360, CONFIG_REGULATOR_TPS65023,
CONFIG_REGULATOR_TPS6507X, CONFIG_REGULATOR_TPS65217,
CONFIG_REGULATOR_TPS6524X, CONFIG_REGULATOR_USERSPACE_CONSUMER,
CONFIG_REGULATOR_VIRTUAL_CONSUMER, CONFIG_REGULATOR_WM831X,
CONFIG_REGULATOR_WM8400, CONFIG_REGULATOR, CONFIG_RFKILL_REGULATOR,
CONFIG_RTC_DRV_MC13XXX, CONFIG_RTC_DRV_WM831X, CONFIG_SCA3000,
CONFIG_SENSORS_AK8975, CONFIG_SENSORS_HMC5843,
CONFIG_SENSORS_ISL29018,
CONFIG_SENSORS_MC13783_ADC, CONFIG_SENSORS_TSL2563,
CONFIG_SENSORS_WM831X,
CONFIG_SERIAL_MFD_HSU, CONFIG_SERIAL_UARTLITE, CONFIG_STMPE_I2C,
CONFIG_STMPE_SPI, CONFIG_TOUCHSCREEN_MC13783,
CONFIG_TOUCHSCREEN_STMPE,
CONFIG_TOUCHSCREEN_WM831X, CONFIG_TPS6105X, CONFIG_TSL2583,
CONFIG_WM831X_BACKUP, CONFIG_WM831X_POWER, CONFIG_WM831X_WATCHDOG
- -Jeff
El 26/04/12 14:25, Jeff Mahoney escribió:>
> 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 ?
On 04/26/2012 04:02 PM, Cristian Rodríguez wrote: > El 26/04/12 14:25, Jeff Mahoney escribió:>> >> 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
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?
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
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.> 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
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
Le 27/04/2012 16:40, Jeff Mahoney a écrit :>
> 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?No. Maybe some special SD cards (wifi SD cards or things like that)?
I know there are also some sensors (e.g. temperature) on motherboards or graphics cards which use i2c or spi interfaces but I do not know if something special must be enabled in the kernel.
It should be safe to disable SPI related things in non-ARM kernels.
Guillaume
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
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
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
>>> On 06.05.12 at 07:12, Cristian Rodríguez< wrote:
> 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 && !SMPSince when and why?
Jan
>>> 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
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.
>
> JanThe "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)
>>> On 08.05.12 at 18:57, Cristian Rodríguez< wrote:
> 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.
>
> The "Intel i810 Random Number Generator" is not present on any x86_64
> machine,Which is documented where?
> only in old single processor, 32 bit systems (Pentium 2, 3..)
Definitely not for the "single processor part" - I've got a PIII
dual-socket Dell system that has one (which I had actually used
to put together improvements to the driver a couple of years
ago).
> (not to be confused with newer RDRAND thing)
Of course.
Jan
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_32This one should probably be changed in the source so that the option depends on X86_32 instead of X86. - -Jeff
On 10/05/12 00:07, Cristian Rodríguez wrote:
> On 26/04/12 14:25, Jeff Mahoney wrote:>>
>> 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 ?
On 05/10/2012 12:47 AM, Cristian Rodríguez wrote: > On 10/05/12 00:07, Cristian Rodríguez wrote: >> On 26/04/12 14:25, Jeff Mahoney wrote:>>> >>> 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 ? >Yeah it was an oversight. USB_STORAGE was static. Only -desktop is affected. Fixed now. -Jeff
Ad