OpenCores

The openrisc bugtracker has been moved to: bugzilla.opencores.org. This page is read-only

Or1ksim does not use consistent config parameter names

Back to bugtracker overview.

Information:
Type :: BUG
Status :: CLOSED
Assigned to :: Jeremy, Bennett

Description:
Or1ksim does not use consistent names for config parameters. This makes errors by the user more likely.

Main culprit is parameters, which are filenames. This is variously called:
- vapi_fn (section vapi)
- filename (sections vga, fb)
- file/rxfile/txfile (sections ethernet, kbd)

I suggest the parameter should be "file" where this is no direction implied and "rxfile" or "txfile" where a direction is implied.

In section gpio, the parameter is called "base_vapi_id", where all other sections refer to this as "vapi_id". Although GPIO is unusual in actually using more than one VAPI ID, all sections may use more than one. For consistency, I suggest that the keyword "vapi_id" is used throughout.

In all cases, the legacy name should be permitted for backwards compatibility.

Comments:

Bennett, Jeremy Oct 12, 2008
These suggestions have been adopted for OpenRISC 0.3.0rc1.

Post a comment:
Login to post comments!

Back to bugtracker overview.

© copyright 1999-2012 OpenCores.org, equivalent to ORSoC AB, all rights reserved. OpenCores®, registered trademark.