* [2.4 patch] Configure.help updates from -ac
@ 2003-07-14 1:41 Adrian Bunk
0 siblings, 0 replies; 5+ messages in thread
From: Adrian Bunk @ 2003-07-14 1:41 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: Alan Cox, linux-kernel
Hi Marcelo,
the patch below adds some Configure.help entries that are in pre3-ac1
but are missing in -pre5.
Please apply
Adrian
--- linux.22-pre3/Documentation/Configure.help 2003-07-06 13:35:00.000000000 +0100
+++ linux.22-pre3-ac1/Documentation/Configure.help 2003-07-07 16:19:40.000000000 +0100
@@ -3611,6 +3654,14 @@
Say Y here to support the Serverworks AGP card. See
<http://www.serverworks.com/> for product descriptions and images.
+NVIDIA chipset support
+CONFIG_AGP_NVIDIA
+ This option gives you AGP support for the GLX component of the
+ XFree86 4.x on NVIDIA nForce/nForce2 chipsets.
+
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
+
ALI chipset support
CONFIG_AGP_ALI
This option gives you AGP support for the GLX component of the
@@ -4797,27 +4845,46 @@
packed pixel and 32 bpp packed pixel. You can also use font widths
different from 8.
-Matrox G100/G200/G400/G450/G550 support
-CONFIG_FB_MATROX_G100
- Say Y here if you have a Matrox G100, G200, G400, G450, or G550
- based video card. If you select "Advanced lowlevel driver options",
- you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
- packed pixel and 32 bpp packed pixel. You can also use font widths
+CONFIG_FB_MATROX_G450
+ Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
+ video card. If you select "Advanced lowlevel driver options", you
+ should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+ pixel and 32 bpp packed pixel. You can also use font widths
different from 8.
If you need support for G400 secondary head, you must first say Y to
"I2C support" and "I2C bit-banging support" in the character devices
section, and then to "Matrox I2C support" and "G400 second head
- support" here in the framebuffer section.
+ support" here in the framebuffer section. G450/G550 secondary head
+ and digital output are supported without additional modules.
- If you have G550, you must also compile support for G450/G550 secondary
- head into kernel, otherwise picture will be shown only on the output you
- are probably not using...
+ The driver starts in monitor mode. You must use the matroxset tool
+ (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
+ swap primary and secondary head outputs, or to change output mode.
+ Secondary head driver always start in 640x480 resolution and you
+ must use fbset to change it.
- If you need support for G450 or G550 secondary head, say Y to
- "Matrox G450/G550 second head support" below.
+ Do not forget that second head supports only 16 and 32 bpp
+ packed pixels, so it is a good idea to compile them into the kernel
+ too. You can use only some font widths, as the driver uses generic
+ painting procedures (the secondary head does not use acceleration
+ engine).
+
+ G450/G550 hardware can display TV picture only from secondary CRTC,
+ and it performs no scaling, so picture must have 525 or 625 lines.
+
+CONFIG_FB_MATROX_G100A
+ Say Y here if you have a Matrox G100, G200 or G400 based
+ video card. If you select "Advanced lowlevel driver options", you
+ should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+ pixel and 32 bpp packed pixel. You can also use font widths
+ different from 8.
+
+ If you need support for G400 secondary head, you must first say Y to
+ "I2C support" and "I2C bit-banging support" in the character devices
+ section, and then to "Matrox I2C support" and "G400 second head
+ support" here in the framebuffer section.
-Matrox I2C support
CONFIG_FB_MATROX_I2C
This drivers creates I2C buses which are needed for accessing the
DDC (I2C) bus present on all Matroxes, an I2C bus which
@@ -4860,32 +4926,14 @@
painting procedures (the secondary head does not use acceleration
engine).
-Matrox G450 second head support
-CONFIG_FB_MATROX_G450
- Say Y or M here if you want to use a secondary head (meaning two
- monitors in parallel) on G450, or if you are using analog output
- of G550.
-
- If you compile it as module, two modules are created,
- matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you
- want two independent display devices.
-
- The driver starts in monitor mode and currently does not support
- output in TV modes. You must use the matroxset tool (available
- at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to swap
- primary and secondary head outputs. Secondary head driver always
- start in 640x480 resolution and you must use fbset to change it.
-
- Note on most G550 cards the analog output is the secondary head,
- so you will need to say Y here to use it.
-
- Also do not forget that second head supports only 16 and 32 bpp
- packed pixels, so it is a good idea to compile them into the kernel
- too. You can use only some font widths, as the driver uses generic
- painting procedures (the secondary head does not use acceleration
- engine).
-
-Matrox unified driver multihead support
+CONFIG_FB_MATROX_PROC
+ Say Y or M here if you want to access some informations about driver
+ state through /proc interface.
+
+ You should download matrox_pins tool (available at
+ <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to get human
+ readable output.
+
CONFIG_FB_MATROX_MULTIHEAD
Say Y here if you have more than one (supported) Matrox device in
your computer and you want to use all of them for different monitors
@@ -18759,6 +19122,14 @@
of verbosity. Saying Y enables these statements. This will increase
your kernel size by around 50K.
+ACPI Relaxed AML Checking
+CONFIG_ACPI_RELAXED_AML
+ If you say `Y' here, the ACPI interpreter will relax its checking
+ for valid AML and will ignore some AML mistakes, such as off-by-one
+ errors in region sizes. Some laptops may require this option. In
+ particular, many Toshiba laptops require this for correct operation
+ of the AC module.
+
ACPI Bus Manager
CONFIG_ACPI_BUSMGR
The ACPI Bus Manager enumerates devices in the ACPI namespace, and
@@ -26828,8 +27169,142 @@
If compiled as a module, it will be called scx200_docflash.o.
+BIOS flash chip on AMD76x southbridge
+CONFIG_MTD_AMD76XROM
+ Support for treating the BIOS flash chip on AMD76x motherboards
+ as an MTD device - with this you can reprogram your BIOS.
+
+ BE VERY CAREFUL.
+
+ If compiled as a module, it will be called amd76xrom.o.
+
+BIOS flash chip on Intel Hub Controller 2
+CONFIG_MTD_ICH2ROM
+ Support for treating the BIOS flash chip on ICH2 motherboards
+ as an MTD device - with this you can reprogram your BIOS.
+
+ BE VERY CAREFUL.
+
+ If compiled as a module, it will be called ich2rom.o.
+
+BIOS flash chip on Intel SCB2 boards
+CONFIG_MTD_SCB2_FLASH
+ Support for treating the BIOS flash chip on Intel SCB2 boards
+ as an MTD device - with this you can reprogram your BIOS.
+
+ BE VERY CAREFUL.
+
+ If compiled as a module, it will be called scb2_flash.o.
+
+Flash chips on Tsunami TIG bus
+CONFIG_MTD_TSUNAMI
+ Support for the flash chip on Tsunami TIG bus.
+
+ If compiled as a module, it will be called tsunami_flash.o.
+
+Flash chips on LASAT board
+CONFIG_MTD_LASAT
+ Support for the flash chips on the Lasat 100 and 200 boards.
+
+ If compiled as a module, it will be called lasat.o.
+
+CFI flash device on SnapGear/SecureEdge
+CONFIG_MTD_NETtel
+ Support for flash chips on NETtel/SecureEdge/SnapGear boards.
+
+ If compiled as a module, it will be called nettel.o.
+
+CFI Flash device mapped on DIL/Net PC
+CONFIG_MTD_DILNETPC
+ MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
+ For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
+ and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
+
+ If compiled as a module, it will be called dilnetpc.o.
+
+Size of DIL/Net PC flash boot partition
+CONFIG_MTD_DILNETPC_BOOTSIZE
+ The amount of space taken up by the kernel or Etherboot
+ on the DIL/Net PC flash chips.
+
+CFI Flash device mapped on Epxa10db
+CONFIG_MTD_EPXA10DB
+ This enables support for the flash devices on the Altera
+ Excalibur XA10 Development Board. If you are building a kernel
+ for on of these boards then you should say 'Y' otherwise say 'N'.
+
+ If compiled as a module, it will be called epxa10db-flash.o.
+
+CFI Flash device mapped on the FortuNet board
+CONFIG_MTD_FORTUNET
+ This enables access to the Flash on the FortuNet board. If you
+ have such a board, say 'Y'.
+
+ If compiled as a module, it will be called fortunet.o.
+
+NV-RAM mapping AUTCPU12 board
+CONFIG_MTD_AUTCPU12
+ This enables access to the NV-RAM on autronix autcpu12 board.
+ If you have such a board, say 'Y'.
+
+ If compiled as a module, it will be called autcpu12-nvram.o.
+
+CFI Flash device mapped on EDB7312
+CONFIG_MTD_EDB7312
+ This enables access to the CFI Flash on the Cogent EDB7312 board.
+ If you have such a board, say 'Y' here.
+
+ If compiled as a module, it will be called edb7312.o.
+
+JEDEC Flash device mapped on impA7
+CONFIG_MTD_IMPA7
+ This enables access to the NOR Flash on the impA7 board of
+ implementa GmbH. If you have such a board, say 'Y' here.
+
+ If compiled as a module, it will be called impa7.o.
+
+JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame
+CONFIG_MTD_CEIVA
+ This enables access to the flash chips on the Ceiva/Polaroid
+ PhotoMax Digital Picture Frame.
+ If you have such a device, say 'Y'.
+
+ If compiled as a module, it will be called ceiva.o.
+
+System flash on MBX860 board
+CONFIG_MTD_MBX860
+ This enables access routines for the flash chips on the Motorola
+ MBX860 board. If you have one of these boards and would like
+ to use the flash chips on it, say 'Y'.
+
+ If compiled as a module, it will be called mbx860.o.
+
+PCI MTD driver
+CONFIG_MTD_PCI
+ Mapping for accessing flash devices on add-in cards like the Intel XScale
+ IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
+ (please see the manual for the link settings).
+
+ If compiled as a module, it will be called pci.o.
+
+ If you are not sure, say N.
+
+PCMCIA MTD driver
+CONFIG_MTD_PCMCIA
+ Map driver for accessing PCMCIA linear flash memory cards. These
+ cards are usually around 4-16MiB in size. This does not include
+ Compact Flash cards which are treated as IDE devices.
+
+ If compiled as a module, it will be called pcmciamtd.o.
+
+Generic uClinux RAM/ROM filesystem support
+CONFIG_MTD_UCLINUX
+ Map driver to support image based filesystems for uClinux.
+
+ If compiled as a module, it will be called uclinux.o.
+
NatSemi SCx200 I2C using GPIO pins
CONFIG_SCx200_GPIO
Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
If you don't know what to do here, say N.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [2.4 patch] Configure.help updates from -ac
@ 2003-07-14 13:04 Marc-Christian Petersen
2003-07-14 16:29 ` Adrian Bunk
0 siblings, 1 reply; 5+ messages in thread
From: Marc-Christian Petersen @ 2003-07-14 13:04 UTC (permalink / raw)
To: Adrian Bunk, Marcelo Tosatti; +Cc: lkml
Hi Adrian,
> the patch below adds some Configure.help entries that are in pre3-ac1
> but are missing in -pre5.
why do you remove such things like (only text):
-Matrox G100/G200/G400/G450/G550 support
-Matrox I2C support
-Matrox G450 second head support
-Matrox unified driver multihead support
?
ciao, Marc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [2.4 patch] Configure.help updates from -ac
2003-07-14 13:04 Marc-Christian Petersen
@ 2003-07-14 16:29 ` Adrian Bunk
2003-07-14 16:47 ` Marc-Christian Petersen
0 siblings, 1 reply; 5+ messages in thread
From: Adrian Bunk @ 2003-07-14 16:29 UTC (permalink / raw)
To: Marc-Christian Petersen; +Cc: Marcelo Tosatti, lkml
On Mon, Jul 14, 2003 at 03:04:48PM +0200, Marc-Christian Petersen wrote:
> Hi Adrian,
>
> > the patch below adds some Configure.help entries that are in pre3-ac1
> > but are missing in -pre5.
> why do you remove such things like (only text):
>
> -Matrox G100/G200/G400/G450/G550 support
> -Matrox I2C support
> -Matrox G450 second head support
> -Matrox unified driver multihead support
>
> ?
It's not me, this was directly taken from -ac.
Please correct me if I'm wrong, but AFAIK these lines are used nowhere,
they are just copies of the one-line descriptions in the Config.in
files.
> ciao, Marc
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [2.4 patch] Configure.help updates from -ac
2003-07-14 16:29 ` Adrian Bunk
@ 2003-07-14 16:47 ` Marc-Christian Petersen
0 siblings, 0 replies; 5+ messages in thread
From: Marc-Christian Petersen @ 2003-07-14 16:47 UTC (permalink / raw)
To: Adrian Bunk; +Cc: Marcelo Tosatti, lkml
On Monday 14 July 2003 18:29, Adrian Bunk wrote:
Hi Adrian,
> It's not me, this was directly taken from -ac.
yeah, ok.
> Please correct me if I'm wrong, but AFAIK these lines are used nowhere,
> they are just copies of the one-line descriptions in the Config.in
> files.
nope, you are right. But I think we should either leave all one-line
descriptions from Config.in in or rip all out.
ciao, Marc
^ permalink raw reply [flat|nested] 5+ messages in thread
* [2.4 patch] Configure.help updates from -ac
@ 2003-05-10 12:18 Adrian Bunk
0 siblings, 0 replies; 5+ messages in thread
From: Adrian Bunk @ 2003-05-10 12:18 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: linux-kernel, trivial
Hi Marcelo,
the patch below includes some Configure.help entries for new options in
2.4.21 that aren't in 2.4.21-rc2 from -ac.
It applies (with a few lines offset) against 2.4.21-rc2.
Please apply
Adrian
--- linux.21rc1/Documentation/Configure.help 2003-04-22 16:39:32.000000000 +0100
+++ linux.21rc1-ac4/Documentation/Configure.help 2003-05-03 19:08:44.000000000 +0100
@@ -23168,6 +23545,23 @@
say M here and read <file:Documentation/modules.txt>. The module
will be called radio-sf16fmi.o.
+SF16FMR2 Radio
+CONFIG_RADIO_SF16FMR2
+ Choose Y here if you have one of these FM radio cards. If you
+ compile the driver into the kernel and your card is not PnP one, you
+ have to add "sf16fmr2=<io>" to the kernel command line (I/O address is
+ 0x284 or 0x384, default 0x384).
+
+ In order to control your radio card, you will need to use programs
+ that are compatible with the Video For Linux API. Information on
+ this API and pointers to "v4l" programs may be found on the WWW at
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-sf16fmr2.o.
+
Typhoon Radio (a.k.a. EcoRadio)
CONFIG_RADIO_TYPHOON
Choose Y here if you have one of these FM radio cards, and then fill
@@ -26523,6 +27038,90 @@
If unsure, say N.
+NatSemi SCx200 support
+CONFIG_SCx200
+ This provides basic support for the National Semiconductor SCx200
+ processor. Right now this is just a driver for the GPIO pins.
+
+ If you don't know what to do here, say N.
+
+ This support is also available as a module. If compiled as a
+ module, it will be called scx200.o.
+
+NatSemi SCx200 Watchdog
+CONFIG_SCx200_WDT
+ Enable the built-in watchdog timer support on the National
+ Semiconductor SCx200 processors.
+
+ If compiled as a module, it will be called scx200_watchdog.o.
+
+Flash device mapped with DOCCS on NatSemi SCx200
+CONFIG_MTD_SCx200_DOCFLASH
+ Enable support for a flash chip mapped using the DOCCS signal on a
+ National Semiconductor SCx200 processor.
+
+ If you don't know what to do here, say N.
+
+ If compiled as a module, it will be called scx200_docflash.o.
+
+NatSemi SCx200 I2C using GPIO pins
+CONFIG_SCx200_GPIO
+ Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
+
+ If you don't know what to do here, say N.
+
+ If compiled as a module, it will be called scx200_i2c.o.
+
+GPIO pin used for SCL
+CONFIG_SCx200_I2C_SCL
+ Enter the GPIO pin number used for the SCL signal. This value can
+ also be specified with a module parameter.
+
+GPIO pin used for SDA
+CONFIG_SCx200_I2C_SDA
+ Enter the GPIO pin number used for the SSA signal. This value can
+ also be specified with a module parameter.
+
+NatSemi SCx200 ACCESS.bus
+CONFIG_SCx200_ACB
+ Enable the use of the ACCESS.bus controllers of a SCx200 processor.
+
+ If you don't know what to do here, say N.
+
+ If compiled as a module, it will be called scx200_acb.o.
+
+IPMI top-level message handler
+CONFIG_IPMI_HANDLER
+ This enables the central IPMI message handler, required for IPMI
+ to work. Note that you must have this enabled to do any other IPMI
+ things.
+
+ IPMI is a standard for managing sensors (temperature,
+ voltage, etc.) in a system.
+
+ See Documentation/IPMI.txt for more details on the driver.
+
+ If unsure, say N.
+
+Generate a panic event to all BMCs on a panic
+CONFIG_IPMI_PANIC_EVENT
+ When a panic occurs, this will cause the IPMI message handler to
+ generate an IPMI event describing the panic to each interface
+ registered with the message handler.
+
+Device interface for IPMI
+CONFIG_IPMI_DEVICE_INTERFACE
+ This provides an IOCTL interface to the IPMI message handler so
+ userland processes may use IPMI. It supports poll() and select().
+
+IPMI KCS handler
+CONFIG_IPMI_KCS
+ Provides a driver for a KCS-style interface to a BMC.
+
+IPMI Watchdog Timer
+CONFIG_IPMI_WATCHDOG
+ This enables the IPMI watchdog timer.
+
#
# A couple of things I keep forgetting:
# capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-07-14 16:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-14 1:41 [2.4 patch] Configure.help updates from -ac Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 13:04 Marc-Christian Petersen
2003-07-14 16:29 ` Adrian Bunk
2003-07-14 16:47 ` Marc-Christian Petersen
2003-05-10 12:18 Adrian Bunk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).