On Fri, 2009-02-06 at 14:42 +0100, maximilian attems wrote: [...] > * FIRMWARE_IN_KERNEL > default enabled > we probably don't ship right yet relevant firmware separetly? FIRMWARE_IN_KERNEL enables inclusion of firmware along with drivers in the main kernel image, and has no effect on driver modules. Driver modules that use request_firmware() will always need separate firmware. [...] > * USB_SERIAL_KEYSPAN_MPR > USB_SERIAL_KEYSPAN_USA28 > USB_SERIAL_KEYSPAN_USA28X > USB_SERIAL_KEYSPAN_USA28XA > USB_SERIAL_KEYSPAN_USA28XB > USB_SERIAL_KEYSPAN_USA19 > USB_SERIAL_KEYSPAN_USA18X > USB_SERIAL_KEYSPAN_USA19W > USB_SERIAL_KEYSPAN_USA19QW > USB_SERIAL_KEYSPAN_USA19QI > USB_SERIAL_KEYSPAN_USA49W > USB_SERIAL_KEYSPAN_USA49WLC > bunch of new firmware for some option style serial dev > not looked at their licences yet nor request_firmware() usage This driver uses request_firmware(). > * STAGING > pile of crap drivers > disabled in fedora, users might request it, but currently seems > not really supportable. so i'd be for unsetting, but want opinons? We already distribute some of these, e.g. rt2860. I would favour enabling at least the ones that we currently distribute separately. [...] > * STRICT_DEVMEM > is userspace ready for that!? > probably should da a testboot and see if lenny xorg comes up with it > enabled. This has no effect on the X server, or at least that's the theory. > * X86_VERBOSE_BOOTUP > default yes and guess debian users like it!? [...] This can easily be overridden with "quiet", in any case. Ben.
Attachment:
signature.asc
Description: This is a digitally signed message part