The following configuration symbols are missing help entries. If you can
supply a help entry for one or more of these, please send it to me for
incorporation in the master Configure.help file.
Yes, some of these are choice symbols that don't strictly need entries in CML1.
Please send entries in anyway; in CML2, choice symbols will have their own
help entries.
ALPHA_EV67
ARCH_ANAKIN
ARCH_CAMELOT
ARCH_CDB89712
ARCH_CLEP7312
ARCH_CLPS711X
ARCH_CLPS7500
ARCH_CO285
ARCH_EDB7211
ARCH_FOOTBRIDGE
ARCH_INTEGRATOR
ARCH_SA1100
ARCH_SHARK
ARC_CONSOLE
ATM_IDT77252
ATM_IDT77252_RCV_ALL
ATM_LANAI
AU1000_SERIAL_CONSOLE
AU1000_UART
BLK_DEV_IT8172
BLK_DEV_Q40IDE
CF_AREA6
CF_BASE_ADDR
CPU_ARM1020_D_CACHE_ON
CPU_ARM1020_FORCE_WRITE_THROUGH
CPU_ARM1020_I_CACHE_ON
CPU_ARM1020_ROUND_ROBIN
CPU_ARM920_CPU_IDLE
CPU_ARM920_D_CACHE_ON
CPU_ARM920_I_CACHE_ON
CPU_ARM920_WRITETHROUGH
CPU_ARM926T
CPU_ARM926_CPU_IDLE
CPU_ARM926_D_CACHE_ON
CPU_ARM926_I_CACHE_ON
CPU_ARM926_ROUND_ROBIN
CPU_ARM926_WRITETHROUGH
CPU_FREQ
DASD_AUTO_DIAG
DASD_AUTO_ECKD
DASD_AUTO_FBA
EFI_VARS
EP7211_IR
EP72XX_ROM_BOOT
ETRAX_ETHERNET_LPSLAVE
ETRAX_ETHERNET_LPSLAVE_HAS_LEDS
ETRAX_NETWORK_LED_ON_WHEN_ACTIVITY
ETRAX_NETWORK_LED_ON_WHEN_LINK
ETRAX_POWERBUTTON_BIT
ETRAX_ROOT_DEVICE
ETRAX_SERIAL_PORT0
ETRAX_SHUTDOWN_BIT
ETRAX_SOFT_SHUTDOWN
EUROTECH_WDT
EVB_PCI1
FB_TX3912
FORWARD_KEYBOARD
GEN_RTC
GSC_DINO
HWC_CPI
I2C_ALGO8XX
I2C_PPC405_ADAP
I2C_PPC405_ALGO
I2C_RPXLITE
I82092
IA64_GRANULE_16MB
IA64_GRANULE_64MB
IA64_SGI_SN_DEBUG
IA64_SGI_SN_SIM
IP6_NF_MATCH_MULTIPORT
IP6_NF_MATCH_OWNER
IP6_NF_TARGET_LOG
IT8172_REVC
IT8172_SCR0
IT8172_SCR1
IT8172_TUNING
ITE_I2C_ADAP
ITE_I2C_ALGO
JFFS_PROC_FS
LASI_82596
LP486E
MAPLE_KEYBOARD
MAPLE_MOUSE
MEMORY_SET
MEMORY_SIZE
MIPS_AU1000_ENET
MTD_ABSENT
MTD_ARM_INTEGRATOR
MTD_BLKMTD
MTD_CDB89712
MTD_JEDECPROBE
MTD_L440GX
MTD_LART
MTD_OBSOLETE_CHIPS
MTD_SOLUTIONENGINE
MTD_TQM8XXL
PCIBA
PCI_PERMEDIA
PCMCIA_AXNET
PCMCIA_XIRCOM
PFAULT
PHONE_IXJ_PCMCIA
PPPOATM
PROFILE
PROFILE_SHIFT
SA1100_ADSBITSY
SA1100_CERF_16MB
SA1100_CERF_32MB
SA1100_CERF_64MB
SA1100_CERF_8MB
SA1100_CERF_CPLD
SA1100_CERF_FLASH_16MB
SA1100_CERF_FLASH_32MB
SA1100_CERF_FLASH_8MB
SA1100_EXTENEX1
SA1100_EXTENEX1_16MB
SA1100_FIR
SA1100_FLEXANET
SA1100_FREEBIRD
SA1100_GRAPHICSMASTER
SA1100_HUW_WEBPANEL
SA1100_ITSY
SA1100_JORNADA720
SA1100_OMNIMETER
SA1100_PFS168
SA1100_PLEB
SA1100_SHERMAN
SA1100_SIMPAD
SA1100_YOPY
SCSI_DECSII
SCSI_LASI
SCSI_QLOGIC_FC_FIRMWARE
SCSI_SIM
SERIAL_21285_OLD
SERIAL_SGI_L1_PROTOCOL
SERIAL_TX3912
SERIAL_TX3912_CONSOLE
SGIWD93_SCSI
SHARED_KERNEL
SH_ADX
SH_PCIDMA_NONCOHERENT
SIMETH
SIM_SERIAL
SOUND_CMPCI_FM
SOUND_CMPCI_FMIO
SOUND_CMPCI_LINE_BASS
SOUND_CMPCI_LINE_REAR
SOUND_CMPCI_MIDI
SOUND_CMPCI_MPUIO
SOUND_CMPCI_SPDIFINVERSE
SOUND_VRC5477
ST40_LMI_MEMORY
SYSCLK_100
SYSCLK_75
SYSCLK_83
TN3215
TN3215_CONSOLE
TN3270
TN3270_CONSOLE
TULIP_MMIO
UCODE_PATCH
USB_SERIAL_IR
USB_STORAGE_DATAFAB
USB_STORAGE_HP8200e
USB_STORAGE_JUMPSHOT
USERIAL
VETH
VIDEO_ZORAN_BUZ
VIDEO_ZORAN_DC10
VIDEO_ZORAN_LML33
VLAN_8021Q
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Question with boldness even the existence of a God; because, if there
be one, he must more approve the homage of reason, than that of
blindfolded fear.... Do not be frightened from this inquiry from any
fear of its consequences. If it ends in the belief that there is no
God, you will find incitements to virtue in the comfort and
pleasantness you feel in its exercise...
-- Thomas Jefferson, in a 1787 letter to his nephew
On Thu, 15 Nov 2001 02:33:37 -0500,
"Eric S. Raymond" <[email protected]> wrote:
>The following configuration symbols are missing help entries. If you can
>supply a help entry for one or more of these, please send it to me for
>incorporation in the master Configure.help file.
These are a mixture of IA64, SGI and SGI/IA64 configs. I will do them
tomorrow.
>EFI_VARS
>IA64_GRANULE_16MB
>IA64_GRANULE_64MB
>IA64_SGI_SN_DEBUG
>IA64_SGI_SN_SIM
>PCIBA
>SCSI_SIM
>SERIAL_SGI_L1_PROTOCOL
>SIMETH
>SIM_SERIAL
On Thu, Nov 15, 2001 at 02:33:37AM -0500, Eric S. Raymond wrote:
> USB_SERIAL_IR
Here's the patch against 2.4.15-pre4 for this symbol.
thanks,
greg k-h
diff --minimal -Nru a/Documentation/Configure.help b/Documentation/Configure.help
--- a/Documentation/Configure.help Thu Nov 15 10:46:22 2001
+++ b/Documentation/Configure.help Thu Nov 15 10:46:22 2001
@@ -12717,6 +12717,17 @@
The module will be called visor.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
+USB IR Dongle Serial Driver
+CONFIG_USB_SERIAL_IR
+ Say Y here if you want to enable simple serial support for USB IrDA
+ devices. This is useful if you do not want to use the full IrDA
+ stack.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called ir-usb.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
USB Belkin and Paracom Single Port Serial Driver
CONFIG_USB_SERIAL_BELKIN
Say Y here if you want to use a Belkin USB Serial single port
[email protected] said:
> The following configuration symbols are missing help entries. If you
> can supply a help entry for one or more of these, please send it to me
> for incorporation in the master Configure.help file.
CONFIG_MTD_ARM_INTEGRATOR left for rmk.
i82092 compatible bridge support
CONFIG_I82092
This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
found in some older laptops and more commonly in evaluation boards for the
chip.
CONFIG_JFFS_PROC_FS
Enabling this option will cause statistics from mounted JFFS file systems
to be made available to the user in the /proc/fs/jffs/ directory.
Support for absent chips in bus mapping
CONFIG_MTD_ABSENT
This option enables support for a dummy probing driver used to
allocated placeholder MTD devices on systems that have socketed
or removable media. Use of this driver as a fallback chip probe
preserves the expected registration order of MTD device nodes on
the system regardless of media presence. Device nodes created
with this driver will return -ENODEV upon access.
MTD Emulation using block device
CONFIG_MTD_BLKMTD
This driver allows a block device to appear as an MTD. It would
generally be used in the following cases:
Using Compact Flash as an MTD, these usually present themselves to
the system as an ATA drive.
Testing MTD users (eg JFFS2) on large media and media that might
be removed during a write (using the floppy drive).
Cirrus CDB89712 evaluation board mappings
CONFIG_MTD_CDB89712
This enables access to the flash or ROM chips on the CDB89712 board.
If you have such a board, say 'Y'.
Detect non-CFI AMD/JEDEC-compatible flash chips
CONFIG_MTD_JEDECPROBE
This option enables JEDEC-style probing of flash chips which are not
compatible with the Common Flash Interface, but will use the common
CFI-targetted flash drivers for any chips which are identified which
are in fact compatible in all but the probe method. This actually
covers most AMD/Fujitsu-compatible chips, and will shortly cover also
non-CFI Intel chips (that code is in MTD CVS and should shortly be sent
for inclusion in Linus' tree)
BIOS flash chip on Intel L440GX boards
CONFIG_MTD_L440GX
Support for treating the BIOS flash chip on Intel L440GX motherboards
as an MTD device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
28F160xx flash driver for LART
CONFIG_MTD_LART
This enables the flash driver for LART. Please note that you do
not need any mapping/chip driver for LART. This one does it all
for you, so go disable all of those if you enabled some of them (:
Older (theoretically obsoleted now) drivers for non-CFI chips
CONFIG_MTD_OBSOLETE_CHIPS
This option does not enable any code directly, but will allow you to
select some other chip drivers which are now considered obsolete,
because the generic CONFIG_JEDEC_PROBE code above should now detect
the chips which are supported by these drivers, and allow the generic
CFI-compatible drivers to drive the chips. Say 'N' here unless you have
already tried the CONFIG_JEDEC_PROBE method and reported its failure
to the MTD mailing list at <[email protected]>
CFI Flash device mapped on Hitachi SolutionEngine
CONFIG_MTD_SOLUTIONENGINE
This enables access to the flash chips on the Hitachi SolutionEngine and
similar boards. Say 'Y' if you are building a kernel for such a board.
Flash chip mapping on TQM8xxL PPC board
CONFIG_MTD_TQM8XXL
The TQM8xxL PowerPC board has up to two banks of CFI-compliant
chips, currently uses AMD one. This 'mapping' driver supports
that arrangement, allowing the CFI probe and command set driver
code to communicate with the chips on the TQM8xxL board. More at
(http://www.denx.de/embedded-ppc-en.html).
Darkness
CONFIG_MEMORY_SET
This is an option about which you will never be asked a question.
Therefore, I conclude that you do not exist - go away.
Are you still here? Piss off, I tell you.
There is a grue here.
Physical memory size
CONFIG_MEMORY_SIZE
This sets the default memory size assumed by your SH kernel. It can
be overridden as normal by the 'mem=' argument on the kernel command
line. If unsure, consult your board specifications or just leave it
as 0x00400000 which was the default value before this became
configurable.
CONFIG_SH_PCIDMA_NONCOHERENT
Enable this option if your platform does not have a CPU cache which
remains coherent with PCI DMA. It is safest to say 'Y', although you
will see better performance if you can say 'N', because the PCI DMA
code will not have to flush the CPU's caches. If you have a PCI host
bridge integrated with your SH CPU, refer carefully to the chip specs
to see if you can say 'N' here. Otherwise, leave it as 'Y'.
--
dwmw2
> Darkness
> CONFIG_MEMORY_SET
> This is an option about which you will never be asked a question.
> Therefore, I conclude that you do not exist - go away.
>
> Are you still here? Piss off, I tell you.
>
Umm.. the policy has been rude words in source code = ok, rude word in
errors that might one day appear to a user = not ok
[email protected] said:
> Umm.. the policy has been rude words in source code = ok, rude word
> in errors that might one day appear to a user = not ok
That message should _never_ appear to a user. Anyone who wants to
gratuitously change that can write a suitable help text.
Actually I'm hoping that CML2, if adopted, will allow us to get rid of the
CONFIG_MEMORY_SET cruft in arch/sh/config.in altogether.
But not, of course, until after the initial adoption of the CML2 codebase -
actual changes to the behaviour of the config options _must_ be done
separately to the change in mechanism.
--
dwmw2