1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
ppc: 0.748
device: 0.729
semantic: 0.705
mistranslation: 0.688
files: 0.670
graphic: 0.652
architecture: 0.616
vnc: 0.607
performance: 0.604
socket: 0.601
register: 0.594
kernel: 0.583
user-level: 0.573
PID: 0.561
permissions: 0.550
network: 0.548
risc-v: 0.516
arm: 0.511
debug: 0.503
peripherals: 0.496
boot: 0.478
hypervisor: 0.462
assembly: 0.452
VMM: 0.449
TCG: 0.409
i386: 0.402
x86: 0.392
virtual: 0.368
KVM: 0.330
cmd_mode_sense always reports 0x70, no CDROM present
cmd_mode_sense
https://git.qemu.org/?p=qemu.git;a=blob;f=hw/ide/atapi.c;hb=refs/heads/master#l852
always reports 0x70 in byte 2 returned, indicating no CD-ROM present.
If CD-ROM is present, should report 0x01 (or 0x11).
If CD-ROM absent, should report 0x70.
Hi, if you can quote the relevant spec, would you like to include that in a commit message and send a patch?
Also, does this result in a bug anywhere visible that we can test against?
Since I posted this bug report, I have done a little more research and this specific part of this command is actually quite obsolete. It use to be documented (MMC v1.2 Draft), but later versions have actually removed this part of the command, even stating "obsolete" in some of the documentation.
If you want to still allow it, it actually does state 0x70 is an empty drive. However, being it is so obsolete, you may wish to change this status to closed.
Thanks for asking. I don't mind if you close this bug report.
Ben
Roger that, thanks!
I don't think we're very careful about which version we try to emulate. In practice it's "Whatever seems to work across the largest swatch of guest operating systems simultaneously".
If this comes up again, feel free to file against a specific guest OS that appears to be non-functioning.
Thanks!
--js
|