{"push_id":1270188201,"size":2,"distinct_size":2,"ref":"refs/heads/integrate-osd","head":"cabb80f88c8a3b3866c168b896c9abacf2786787","before":"74dfc657818cca0e65553695fb9604782f43ccaa","commits":[{"sha":"0c24a5c9e3e18a7dfac55f1fd4fccea0b71768e2","author":{"name":"Stefan Wallentowitz","email":"6fe76ede026e27600863a1ff38da4e776dcaecdf@wallentowitz.de"},"message":"New config structure\n\nWe now use a struct as static configuration parameter that contains\nall configuration settings. This eases passing those parameters\nthrough the hierarchy and thereby avoids mistakes and increases\nreadability.\n\nThere are two struct: The base_config_t struct contains all\nconfiguration settings. It is used to setup the system. The config_t\nstruct contains some extra settings, which are derived from the base\nsettings. You can call the function derive_config to convert a\nbase_config_t struct into a config_t.\n\nWhen you add a base variable you need to add it at three positions:\n\n - In base_config_t\n\n - In config_t\n\n - The copy operation in derive_config\n\nIf it is a derived setting, you only need to add it to the latter two.\n\nWhile the use of the struct works pretty well with verilator and\nvivado so far, the lack of support for variable-sized arrays in SV\nneeds us to workaround with \"max size\" arrays for now. Actually,\nclasses as parameters would be great..","distinct":true,"url":"https://api.github.com/repos/optimsoc/sources/commits/0c24a5c9e3e18a7dfac55f1fd4fccea0b71768e2"},{"sha":"cabb80f88c8a3b3866c168b896c9abacf2786787","author":{"name":"Stefan Wallentowitz","email":"6fe76ede026e27600863a1ff38da4e776dcaecdf@wallentowitz.de"},"message":"Switch to the new config structure\n\nReplace the toplevel parameters and clean up. Need to migrate the\nsubmodules next.","distinct":true,"url":"https://api.github.com/repos/optimsoc/sources/commits/cabb80f88c8a3b3866c168b896c9abacf2786787"}]}
{"actor":{"display_login":"wallento"}}