-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| Could be that s3c24xx_spi is acting up. If I don't find what's | happening, then I'll switch to s3c24xx_spi_gpio (which is of | course the driver we most emphatically don't want to use in the | end). In terms of proving viability of s3c2442 SPI, maybe it is more critical to prove s3c24xx_spi can work at all / work with DMA than complete the stack. Because shifting the rest of the big stack over to SPI is going to be a very phyrric victory if it turns out that fast SPI is broken and we can't really use it on 2442 anyway. I recall sitting there with Willie trying to get the motion sensors working with s3c24xx_spi and having to switch to s3c24xx_spi_gpio about 6 months ago. We bitbanged it ourselves in the end but it won't fly for WLAN. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkipuscACgkQOjLpvpq7dMpsKACdGpiKEGpPO/3azuZ5ReedL7OR hYMAn2chNcai3qdRdrf7xzPpdarfht7P =RQab -----END PGP SIGNATURE-----
