From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21619 invoked by alias); 4 Jun 2008 20:23:24 -0000 Received: (qmail 21610 invoked by uid 22791); 4 Jun 2008 20:23:24 -0000 X-Spam-Check-By: sourceware.org Received: from el-out-1112.google.com (HELO el-out-1112.google.com) (209.85.162.177) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 04 Jun 2008 20:22:55 +0000 Received: by el-out-1112.google.com with SMTP id m34so149549ele.12 for ; Wed, 04 Jun 2008 13:22:53 -0700 (PDT) Received: by 10.143.33.19 with SMTP id l19mr148321wfj.112.1212610972862; Wed, 04 Jun 2008 13:22:52 -0700 (PDT) Received: by 10.142.113.7 with HTTP; Wed, 4 Jun 2008 13:22:52 -0700 (PDT) Message-ID: Date: Wed, 04 Jun 2008 20:23:00 -0000 From: "Tom Deconinck" To: "=?ISO-8859-1?Q?Huguenin_Fr=E9d=E9ric?=" , ecos-discuss@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: RE : RE : [ECOS] SPI X-SW-Source: 2008-06/txt/msg00022.txt.bz2 You can just use C-code, but if you are using a target that is already supported there is a big chance there's a cdl package define all devices for that specific hardware target. For my hardware, I usually create such a cdl package. See the the ecoscentric documentation about SPI. I was just referring to the at91sam7sek target as an example on how to add the required SPI cdl packages to your target. On Wed, Jun 4, 2008 at 4:14 PM, Huguenin Fr=E9d=E9ric wrote: > I don't understand : > > --You'll have to define an extra package to export your SPI devices, > --like you do for i2c. > --A good starting point might be the at91sam7sek target. > > Do I have to create an eCos package ? Or it's just > as standard C package in my project. > > > -------- Message d'origine-------- > De: Tom Deconinck [mailto:t.deconinck@gmail.com] > Date: mer. 04/06/2008 15:29 > =C0: Huguenin Fr=E9d=E9ric; ecos-discuss@sourceware.org > Objet : Re: RE : [ECOS] SPI > > eCoscentric has some pretty decent documentation about eCos and SPI: > http://ecoscentric.com/ecospro/doc.cgi/html/ref/spi.html > > To enable the driver you have to add these CDL packages to your platform: > > CYGPKG_IO_SPI : enables the SPI generic interface layer > CYGPKG_DEVS_SPI_ARM_AT91 : enables the at91 SPI bus driver > > You'll have to define an extra package to export your SPI devices, > like you do for i2c. > A good starting point might be the at91sam7sek target. > > On Wed, Jun 4, 2008 at 2:42 PM, Huguenin Fr=E9d=E9ric > wrote: >> Thanks I'm using the atmel. Does this driver have documentation ? >> >> >> -------- Message d'origine-------- >> De: Tom Deconinck [mailto:t.deconinck@gmail.com] >> Date: mer. 04/06/2008 13:01 >> =C0: Huguenin Fr=E9d=E9ric; ecos-discuss@sourceware.org >> Objet : Re: [ECOS] SPI >> >> Which ARM processor are you using? >> >> For the Atmel family, there's an SPI driver available: devs/spi/arm/at91/ >> >> On Wed, Jun 4, 2008 at 12:16 PM, Huguenin Fr=E9d=E9ric >> wrote: >>> Hello, >>> >>> How do you use the SPI bus for ARM with eCos ? >>> >>> -- >>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos >>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss >>> >>> >> >> > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss