diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/zero-shot/108/other/764252 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | qemu-analysis-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz qemu-analysis-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/zero-shot/108/other/764252')
| -rw-r--r-- | results/classifier/zero-shot/108/other/764252 | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/764252 b/results/classifier/zero-shot/108/other/764252 new file mode 100644 index 000000000..1150b2645 --- /dev/null +++ b/results/classifier/zero-shot/108/other/764252 @@ -0,0 +1,33 @@ +device: 0.853 +graphic: 0.747 +semantic: 0.707 +network: 0.678 +other: 0.655 +permissions: 0.594 +vnc: 0.581 +files: 0.572 +socket: 0.571 +PID: 0.541 +performance: 0.496 +boot: 0.464 +KVM: 0.445 +debug: 0.365 + +wishlist: kirkwood support + +This is a feature request for qemu to emulate the Marvell Kirkwood chipset. It is used by Sheevaplug, Guruplug, and many NAS devices. + +This was added in 2011, is there a plan to integrate support for kirkwood? + +With "this" I mean the bugreport, not the feature requested. + +If somebody wants to write and submit code I will review it. I am not aware of anybody who is working on kirkwood emulation support or with plans to do so. + + +Apparently nobody submitted code for this, and I assume nobody is interested in this kirkwood platform nowadays any more, so I'm closing this ticket now. + +For the record, I still regularly use a Kirkwood device (a QNAP NAS). Being able to compile software for it in qemu would be handy once in a while, though it's not a high priority for me. + +My offer from comment #3 to review code if anybody wants to submit it still stands, but given the amount of work required to implement a model of a new SoC in QEMU I'm not surprised nobody's ever taken me up on it. + + |