Hi Thomas,
Thomas Chou wrote:
With nios2-generic approach, the fpga parameter header file can be generated from hardware designs using tools. Porting u-boot for
What tools are you referring to?
- sopc-create-config-files
The script is available at
http://sopc.et.ntust.edu.tw/?p=toolchain-build.git; a=blob_plain;f=tools/sopc-create-config-files;hb=HEAD
Ok ... GPL ... very nice! This addresses several of my big concerns.
We cannot add every board, and a generic approach should be taken as Michal suggested. We, (you, I , the community and Altera), should work together to offer a better solution.
Agreed. And please realize that I think the "generic approach" is a great way to proceed. I listed my concerns in an earlier response to Dalon. The availability of your GPL-ed script addresses most of them.
The binary generated with the nios2-generic target should work on these three boards. I tested on EP1C20 and I believe it will work on the other two. These boards are still supported, just under a different name.
I tested on the 1c20 this evening as well ... works fine. I will test on the 2c35 board tomorrow. I'd like to get a positive confirmation WRT the 1S10 and 1S40 before applying this patch.
no need to include other boards support for nios2 in the u-boot mainline.
I'm not convinced that this is true.
Michal's work on microblaze-generic already proved this.
Michal proved the concept ... and the microblaze implementation (many thanks for your contributions Michal). I'd like to _know_ that nothing is broken before we remove existing code -- I don't want to leave anyone high and dry. I've been in such situations ... it's no fun.
I'll apply the generic board patch to the nios 'next' branch, but I'd like to hold off on blowing away those other board trees until we get a chance to test the generic board on the actual targets. Fair enough?
Thanks for your efforts.
Regards, --Scott