<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shoud we use nrfx driver, or nrf legacy driver?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55484/shoud-we-use-nrfx-driver-or-nrf-legacy-driver</link><description>In the SDK it suggests we use those new nrfx drivers, and says the legacy will no longer supported in the future. However, in the examples of the SDK, it uses the legacy driver. I didn&amp;#39;t see any examples using new nrfx drivers. 
 Should I follow examples</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 08 Feb 2020 02:56:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55484/shoud-we-use-nrfx-driver-or-nrf-legacy-driver" /><item><title>RE: Shoud we use nrfx driver, or nrf legacy driver?</title><link>https://devzone.nordicsemi.com/thread/233388?ContentTypeID=1</link><pubDate>Sat, 08 Feb 2020 02:56:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71cb1723-4024-4ae8-9b46-c3085cd1b242</guid><dc:creator>Keith Wakeham</dc:creator><description>&lt;p&gt;This is an inconsistency in answer. This answer indicates nrfx is a replacement while simonr in the other post indicates that legacy layer is the recommended layer as NRFX is just a &amp;quot;universal&amp;quot; but that is feature incomplete.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Shoud we use nrfx driver, or nrf legacy driver?</title><link>https://devzone.nordicsemi.com/thread/224861?ContentTypeID=1</link><pubDate>Wed, 11 Dec 2019 09:03:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba210ffe-34d6-4ba3-babd-677787f4e508</guid><dc:creator>kfcube</dc:creator><description>&lt;p&gt;Got it, thanks a lot&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Shoud we use nrfx driver, or nrf legacy driver?</title><link>https://devzone.nordicsemi.com/thread/224860?ContentTypeID=1</link><pubDate>Wed, 11 Dec 2019 09:02:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c040393-33bf-4d62-9a18-8daf84796f70</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The SDK uses a legacy-layer that translates from the old API (nrf_drv) to the new API (nrfx). This is useful for backwards compatibility. But it&amp;#39;s the new nrfx drivers that are actually being used by the SDK. See also &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/55174/why-are-legacy-files-driving-sdk-16-examples/223624#223624"&gt;this answer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>