Overview :: News :: Architecture :: OpenRISC 1200 :: VMware image :: NEW GNU Toolchain Port :: Architectural Simulator :: U-Boot :: Linux :: uClinux :: RTEMS :: ATS :: ORP :: ORPmon :: ORPsoc :: Survey :: Forum :: Silicon :: Downloads :: Tracker

OpenRISC 1000: Tracker : Or1ksim does not use consistent config parameter names Monitor this item You will be notified via email when status of this item is changed or if somebody adds a comment. Your email   Or1ksim does not use consistent config parameter names Type BUG Status CLOSED 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.   Stats Nobody is monitoring this item Progress   Submited date 28-Sep-2008 Submited by Jeremy Bennett   Assigned date 12-Oct-2008 Assigned to Jeremy Bennett   Closed date 12-Oct-2008 Closed by Jeremy Bennett Comments by Jeremy Bennett on 12-Oct-2008 These suggestions have been adopted for OpenRISC 0.3.0rc1.   Add your comment Your email: Retype key: