From: Andrew Victor <andrew-eS41wJS13H5l57MIdRCFDg@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
LTI-mKfYHFOTJHu+onKQ3Rj6Dg@public.gmane.org
Subject: Re: Revisiting "problem with converting from at91_spi to atmel_spi (AT91RM9200)"
Date: 03 Oct 2007 19:00:03 +0200 [thread overview]
Message-ID: <1191430802.13741.219.camel@fuzzie.sanpeople.com> (raw)
In-Reply-To: <20071003163358.6C79A235028-ZcXrCSuhvln6VZ3dlLfH/g4gEjPzgfUyLrfjE7I9kuVHxeISYlDBzl6hYfS7NtTn@public.gmane.org>
hi David,
> Andrew Victor had partial success after updating the platform setup
> code appropriately. I don't know what the status of that patch is.
I never seemed to get it working consistently with DataFlash.
Changing dataflash_status() to only perform a single transfer made CS0
work. But no luck with the DataFlash card on CS3 (tried both GPIO and
Periphereral mode).
No problems using the old at91_spi and at91_dataflash though.
Regards,
Andrew Victor
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-03 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 17:01 Revisiting "problem with converting from at91_spi to atmel_spi (AT91RM9200)" LTI. - Ticmanis, Linards
[not found] ` <37ED64EE21A398409D609EAF7B0525A02164EB-4fFKm6SzF271qYPpFx2fzhn/E98GtLqgrE5yTffgRl4@public.gmane.org>
2007-10-03 16:33 ` David Brownell
[not found] ` <20071003163358.6C79A235028-ZcXrCSuhvln6VZ3dlLfH/g4gEjPzgfUyLrfjE7I9kuVHxeISYlDBzl6hYfS7NtTn@public.gmane.org>
2007-10-03 17:00 ` Andrew Victor [this message]
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=1191430802.13741.219.camel@fuzzie.sanpeople.com \
--to=andrew-es41wjs13h5l57midrcfdg@public.gmane.org \
--cc=LTI-mKfYHFOTJHu+onKQ3Rj6Dg@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).