From: Anastasios Vacharakis <1856724@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1856724] Re: SB.PCI0.SMB0 device drivers unavailable
Date: Sat, 21 Dec 2019 16:10:20 -0000 [thread overview]
Message-ID: <157694462046.28116.1070785121776220476.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 157659673737.27526.16943710669363851261.malonedeb@chaenomeles.canonical.com
what is this shit?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856724
Title:
SB.PCI0.SMB0 device drivers unavailable
Status in QEMU:
New
Bug description:
QEMU 4.2 introduces new device with this code:
static void build_smb0(Aml *table, I2CBus *smbus, int devnr, int func)
{
Aml *scope = aml_scope("_SB.PCI0");
Aml *dev = aml_device("SMB0");
aml_append(dev, aml_name_decl("_HID", aml_eisaid("APP0005")));
aml_append(dev, aml_name_decl("_ADR", aml_int(devnr << 16 | func)));
build_acpi_ipmi_devices(dev, BUS(smbus), "\\_SB.PCI0.SMB0");
aml_append(scope, dev);
aml_append(table, scope);
}
It is detected by Windows 10 as 'Unknown Device' and there is no driver available.
Please provide a working Windows driver or give ability to disable this device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1856724/+subscriptions
next prev parent reply other threads:[~2019-12-21 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 15:32 [Bug 1856724] [NEW] SB.PCI0.SMB0 device drivers unavailable Rafal Kupiec
2019-12-21 16:10 ` Anastasios Vacharakis [this message]
2019-12-29 11:10 ` [Bug 1856724] " Deorder
2020-01-28 20:57 ` Rafal Kupiec
2020-01-29 21:11 ` Eric Corriveau
2020-01-30 19:16 ` John Snow
2020-04-30 13:40 ` Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=157694462046.28116.1070785121776220476.malone@chaenomeles.canonical.com \
--to=1856724@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).