> Harold Hallikainen wrote:
>> I agree, but since different devices require different SPI settings,
>> the SPI port needs to be initialized before each transaction. The
>> Microchip TCP/IP code does not appear to do this.
>
> That makes sense, as initializing the SPI before each use would be a waste
> in most cases.
>
> The fix sounds pretty easy though.  Use a flag to indicate the SPI is set
> up
> as expected by the ethernet routines.  The low level routine that
> transfers
> a byte checks the flag and initializes the SPI if needed, then proceeds
> normally.
>

That's one approach. Since my other SPI traffic is pretty infrequent, I'm
just going to do a save and restore around my SPI routines.

Thanks!

Harold


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist