Bug 4827 - runqemu shouldn't hard-code machine knowledge
Summary: runqemu shouldn't hard-code machine knowledge
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium enhancement
Target Milestone: 2.2 M3
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
: 9411 (view as bug list)
Depends on:
Blocks: 1018 1683 3990 7459 7887
  Show dependency tree
 
Reported: 2013-07-08 15:40 UTC by Ross Burton
Modified: 2016-09-15 04:15 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2013-07-08 15:40:40 UTC 
There should be some way of putting all of the machine-specific details into configuration files so that runqemu doesn't actually have any machine-specific knowledge.  This way the qemu-zynq and qemu-microblaze details can be in the layer that defines those machines.

(proposing as a 1.6 feature)
Comment 1 Saul Wold 2013-12-02 18:05:20 UTC 
Another option from RP: 
(09:55:48 AM) RP: sgw: I'm not sure it has to be a massive rewrite, just adding the ability to search through something like BBPATH for scripts of a given name, source them then have a common function set
Comment 2 Cristian Iorga 2015-07-28 16:27:45 UTC 
Investigation started.
Comment 3 Saul Wold 2016-02-10 17:15:31 UTC 
Pushing to next release due to change of resources
Comment 4 Ross Burton 2016-04-07 15:39:50 UTC 
*** Bug 9411 has been marked as a duplicate of this bug. ***