Date: Fri, 14 Jul 2006 15:53:55 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: scottl@samsco.org Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/arm/at91 at91_spi.c at91_spiio.h at91_spireg.h Message-ID: <20060714.155355.255408591.imp@bsdimp.com> In-Reply-To: <44B81042.2090009@samsco.org> References: <200607142135.k6ELZxol050056@repoman.freebsd.org> <44B81042.2090009@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <44B81042.2090009@samsco.org>
Scott Long <scottl@samsco.org> writes:
: Warner Losh wrote:
: > imp 2006-07-14 21:35:59 UTC
: >
: > FreeBSD src repository
: >
: > Modified files:
: > sys/arm/at91 at91_spi.c at91_spireg.h
: > Removed files:
: > sys/arm/at91 at91_spiio.h
: > Log:
: > MF p4:
: >
: > Adapt to forthcoming spi framework. The ioctls for SPI commands and such
: > belong in the higher level driver.
: >
:
: SCSI Parallel Interface?
SPI == Serial Peripheral Interface. It is common in the embedded
world. The 'bus' is nothing more than 4 signals: chip select, clock,
MOSI (master out, slave in) and MISO (master in, slave out). Lots of
cool things live on the spi bus, but I'll just be committing support
for AT45 DataFlash parts. The framework is general enough to support
other things. In one of the hardware hacking lists I'm on, people
were talking about writing a driver for a SPI Ethernet whatsit, but
I'm unsure how that works, since there's no interrupt signal on this
bus...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060714.155355.255408591.imp>