Dear Holger,
In message 4FFAEE4F.3090600@keymile.com you wrote:
shouldn't be there an exception for strictly board specific peripheral drivers like an custom-made FPGA?
I see two situations:
1) We are talking about code to load a bitstream into the FPGA, i. e. to "program it". Such code should always be generic enough to put it under drivers/fpga/ (if the existing code there does not already cover the task).
2) We are talking about driver code for some preipheral implemented in the FPGA. In many cases we find these peripherals to be pretty generic (say, UARTs, GPIOs, network interfaces, etc.). In such cases there is no doubt that driver code should go to drivers/ . ONly in case you have areally, really special feature implemented that you need supported in U-Boot. OK, then such drivers are probably better kept in your board directory.
Note that there will always be cases where hindsight will show that the initial location was not perfect. That is perfectly normal ;-)
Best regards,
Wolfgang Denk