Is the ARM Zync BSP using the new i2c API? I was looking through the BSP and did not see how it is initialized.
Also, the current libi2c supports SPI. Does anyone see a problem with using libi2c for SPI and the new i2c API for i2c? Finally, will new i2c drivers go in libchip, or in cpukit/dev ? Thanks, Alan On Wed, Dec 10, 2014 at 7:41 PM, Andre Marques < andre.lousa.marq...@gmail.com> wrote: > > On 12/10/14 22:36, Chris Johns wrote: > >> On 11/12/2014 5:27 am, Alan Cudmore wrote: >> >>> Andre, >>> Thanks for submitting this. I think we need one minor change: >>> Could you remove the include and the call to init the mcp23008 driver? >>> >>> After your code is in the tree, I will propose a patch to allow >>> execution of application specific driver init functions that can be >>> called from the BSP i2c and SPI driver init functions. >>> >> >> Is the I2C code for the new I2C API or the old one ? >> >> Chris >> > > It still uses the old API (libi2c) for both i2c and spi. > > --André Marques >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
