<p></p>
<blockquote>
<p>this results in both configs being part of the CI compilation tests.</p>
</blockquote>
<p>It is already the case if both (conflicting) configurations are kept: when testing <code>periph_spi</code>, <code>stm32-eth</code> related configuration is not built/used and vice-versa.</p>
<blockquote>
<p>We could just disable stm32_eth there and add nucleo-f767zi-eth which uses alternative pins for SPI.</p>
</blockquote>
<p>I don't think it's worth having a new board because of this. It's a matter of configuration and the work in progress related to Kconfig/device-tree should help a lot here.</p>
<blockquote>
<p>I wonder why ST does not create a new revision in which they map the pins in a way to avoid this conflict. It is a pity that we have to choose in the first place.</p>
</blockquote>
<p>I agree.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/13861#issuecomment-624066121">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYH6FAYUND5ZR5NB5ZLRQAKKPANCNFSM4MHFJZKA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABE7WYA6C3T3VLLVWQGQAKLRQAKKPA5CNFSM4MHFJZKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUZH4SI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/pull/13861#issuecomment-624066121",
"url": "https://github.com/RIOT-OS/RIOT/pull/13861#issuecomment-624066121",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>