From: Mike Frysinger Date: Thu, 22 Oct 2009 04:02:22 -0400 Subject: [U-Boot] My SPI driver not working in u-boot. In-Reply-To: <532dd5840910220027g6112deaap6810241e432e270@mail.gmail.com> References: <25998508.post@talk.nabble.com> <59b21cf20910212333h52f0a5acn3188fcf2cda776d9@mail.gmail.com> <532dd5840910220027g6112deaap6810241e432e270@mail.gmail.com> Message-ID: <200910220402.24143.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thursday 22 October 2009 03:27:34 Ravi Kumar Kulkarni wrote: > On Thu, Oct 22, 2009 at 12:03 PM, Magnus Lilja wrote: > > >> >>except that there's now a common SPI framework for you to use > > >> > > >> (drivers/spi/) > > >> > > >> >>as well as an already existing atmel_spi.c driver > > > > > > Yeah exactly . Its also there in u-boot-1.3.4. anyways im using the > > > same driver atmel_spi.c in /drivers/spi/ . > > > atleast can u tell me how to printf to print on ttyS0 in my code so tat > > > > i > > > > > see my flow is workin correct. thanks. > > > > > >>printf("%s:%d\n", __FILE__, __LINE__);? Given that printf and the UART > > >> > > >>works on your board that is. > > I tried with this > printf("%s:%d\n", /drivers/spi/spi-new.c, 72); > 72 is the my line number but im gettin error . so what exactly should i > specify in __FILE_ and __LINE__ places . this makes me wonder if you actually know how to write C code and you should instead be contracting your work to someone who knows what's going on -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20091022/305f4ce6/attachment.pgp