From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 13 Mar 2007 23:02:39 +0300 From: Sergey Vlasov To: devel@lists.altlinux.org Message-ID: <20070313200239.GC4715@procyon.home> Mail-Followup-To: devel@lists.altlinux.org References: <20070313013817.GA20934@nomad.office.altlinux.org> <45F645FB.4090306@altlinux.com> <20070313170756.GC7418@basalt.office.altlinux.org> <20070313192523.GA4715@procyon.home> <20070313193600.GB10451@lks.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yVhtmJPUSI46BTXb" Content-Disposition: inline In-Reply-To: <20070313193600.GB10451@lks.home> Subject: Re: [devel] Q: looking for unneeded kernel modules in installer stage 2 X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.9rc1 Precedence: list Reply-To: ALT Devel discussion list List-Id: ALT Devel discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 20:03:53 -0000 Archived-At: List-Archive: List-Post: --yVhtmJPUSI46BTXb Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 13, 2007 at 10:36:00PM +0300, Konstantin A. Lepikhov wrote: > Hi Sergey! >=20 > Tuesday 13, at 10:25:24 PM you wrote: >=20 > > spi, =D3=CB=CF=D2=C5=C5 =D7=D3=C5=C7=CF, =CD=CF=D6=CE=CF =D5=C2=C9=D2= =C1=D4=D8 - =D7=D2=D1=C4 =CC=C9 =DC=D4=CF =CB=CF=CD=D5-=D4=CF =CE=D5=D6=CE= =CF. > =C4=CC=D1 vmware =CF=CE, =CE=C1=D0=D2=C9=CD=C5=D2, =CE=D5=D6=C5=CE =C9 = =C4=CC=D1 LSI53C1035-based =C4=D5=CD=C1=C0 =D4=CF=D6=C5 > =D0=CF=CE=C1=C2=C9=D4=D3=D1. =FC=D4=CF =CE=C5 =D3 scsi_transport_spi =D0=C5=D2=C5=D0=D5=D4=C1=CE=CF? =F7=CF=CF=C2=DD=C5-=D4=CF =D7 drivers/spi/ =CC=C5=D6=C9=D4 =D7=CF=D4 =DE=D4= =CF: config SPI bool "SPI support" help The "Serial Peripheral Interface" is a low level synchronous protocol. Chips that support SPI can have data transfer rates up to several tens of Mbit/sec. Chips are addressed with a controller and a chipselect. Most SPI slaves don't support dynamic device discovery; some are even write-only or read-only. =20 SPI is widely used by microcontollers to talk with sensors, eeprom and flash memory, codecs and various other controller chips, analog to digital (and d-to-a) converters, and more. MMC and SD cards can be accessed using SPI protocol; and for DataFlash cards used in MMC sockets, SPI must always be used. =20 SPI is one of a family of similar protocols using a four wire interface (select, clock, data in, data out) including Microwire (half duplex), SSP, SSI, and PSP. This driver framework should work with most such devices and controllers. config SPI_BITBANG tristate "Bitbanging SPI master" depends on SPI_MASTER && EXPERIMENTAL help With a few GPIO pins, your system can bitbang the SPI protocol. Select this to get SPI support through I/O pins (GPIO, parallel port, etc). Or, some systems' SPI master controller drivers use this code to manage the per-word or per-transfer accesses to the hardware shift registers. =20 This is library code, and is automatically selected by drivers th= at need it. You only need to select this explicitly to support driv= er modules that aren't part of this kernel tree. =20 config SPI_BUTTERFLY tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" depends on SPI_MASTER && PARPORT && EXPERIMENTAL select SPI_BITBANG help This uses a custom parallel port cable to connect to an AVR Butterfly , an inexpensive battery powered microcontroller evaluation board. This same cable can be used to flash new firmware. --yVhtmJPUSI46BTXb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9wNfW82GfkQfsqIRAk2+AJ9LcPoAo8j9BL5stVlhRRcFN602vwCgirah 5HvPxOsrlTaQmhCEk4s/25w= =oAp+ -----END PGP SIGNATURE----- --yVhtmJPUSI46BTXb--