From: Steven Cole <elenstev@mesatop.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.7-dj1 add 6 help texts to arch/cris/drivers/Config.help
Date: 25 Mar 2002 18:40:53 -0700 [thread overview]
Message-ID: <1017106854.2679.2.camel@localhost.localdomain> (raw)
This patch adds 6 help texts to arch/cris/drivers/Config.help.
The texts were obtained from ESR's v2.97 Configure.help.
Steven
--- linux-2.5.7-dj1/arch/cris/drivers/Config.help.orig Mon Mar 25 13:52:21 2002
+++ linux-2.5.7-dj1/arch/cris/drivers/Config.help Mon Mar 25 13:52:59 2002
@@ -572,3 +572,39 @@
CONFIG_ETRAX_PARALLEL_PORT1
Say Y here to enable parallel port 1.
+CONFIG_ETRAX_ETHERNET_LPSLAVE
+ This option enables a slave ETRAX 100 or ETRAX 100LX, connected to a
+ master ETRAX 100 or ETRAX 100LX through par0 and par1, to act as an
+ Ethernet controller.
+
+CONFIG_ETRAX_ETHERNET_LPSLAVE_HAS_LEDS
+ Enable if the slave has it's own LEDs.
+
+CONFIG_ETRAX_IDE
+ Enable this to get support for ATA/IDE. You can't use parallel
+ ports or SCSI ports at the same time.
+
+CONFIG_ETRAX_NETWORK_LED_ON_WHEN_ACTIVITY
+ Selecting LED_on_when_link will light the LED when there is a
+ connection and will flash off when there is activity.
+
+ Selecting LED_on_when_activity will light the LED only when
+ there is activity.
+
+ This setting will also affect the behaviour of other activity LEDs
+ e.g. Bluetooth.
+
+CONFIG_ETRAX_NETWORK_LED_ON_WHEN_LINK
+ Selecting LED_on_when_link will light the LED when there is a
+ connection and will flash off when there is activity.
+
+ Selecting LED_on_when_activity will light the LED only when
+ there is activity.
+
+ This setting will also affect the behaviour of other activity LEDs
+ e.g. Bluetooth.
+
+CONFIG_ETRAX_SERIAL_PORT0
+ Enables the ETRAX 100 serial driver for ser0 (ttyS0)
+ Normally you want this on, unless you use external DMA 1 that uses
+ the same DMA channels.
reply other threads:[~2002-03-26 1:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1017106854.2679.2.camel@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox