From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Mike Maslenkin <mike.maslenkin@gmail.com>
Cc: devel@edk2.groups.io, dann.frazier@canonical.com,
michael.d.kinney@intel.com,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>, Min Xu <min.m.xu@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
1016359@bugs.debian.org
Subject: Re: [edk2-devel] [Patch 1/2] OvmfPkg: Change default to disable MptScsi and PvScsi
Date: Wed, 7 Dec 2022 08:41:23 +0100 [thread overview]
Message-ID: <20221207074123.ccj63ciwywubqj6k@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAL77WPAQ6rqKinAiDZ-mf7goxeWJx5kXG_OVvuUa3iAcfdcvUA@mail.gmail.com>
Hi,
> A patch mentioned above set MPT_SCSI_ENABLE=FALSE, that removed
> support for LSI 53C1030 and SAS1068.
> These SCSI controllers were emulated by VMware, Parallels and I guess
> VitualBox.
> This is generic setup for VMware VMs, as far as I remember.
> So the booting of such VMs (probably migrated from VMware and others)
> was definitely broken.
Yes. Problem is there is no maintainer for the driver. There used to
be one, but the email address started bouncing. So we updated
Maintainers.txt and flipped the switch to not build the unmaintained
drivers by default.
If debian is fine with shipping unmaintained software to its users you
can flip the config switches of course, at least as long as the drivers
are still in the tree. The drivers are at risk of being removed though
in case we don't find a new maintainer within a year or two.
take care,
Gerd
next prev parent reply other threads:[~2022-12-07 7:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:46 [Patch 0/2] Remove MptScsi and PvScsi reviewers Michael D Kinney
2022-07-26 19:46 ` [Patch 1/2] OvmfPkg: Change default to disable MptScsi and PvScsi Michael D Kinney
2022-12-05 23:36 ` [edk2-devel] " dann frazier
2022-12-06 1:25 ` Michael D Kinney
2022-12-06 2:07 ` dann frazier
2022-12-06 5:56 ` Gerd Hoffmann
2022-12-06 14:37 ` dann frazier
2022-12-06 14:55 ` Mike Maslenkin
2022-12-07 7:41 ` Gerd Hoffmann [this message]
2022-12-07 14:09 ` Ard Biesheuvel
2022-12-07 14:14 ` James Bottomley
2022-12-07 16:01 ` Gerd Hoffmann
2022-12-07 16:04 ` Ard Biesheuvel
2022-12-07 16:22 ` James Bottomley
2022-12-07 21:59 ` dann frazier
2022-07-26 19:46 ` [Patch 2/2] Maintainers.txt: Remove MptScsi and PvScsi reviewers Michael D Kinney
2022-07-26 20:39 ` [Patch 0/2] " Ard Biesheuvel
2022-07-27 0:38 ` Yao, Jiewen
2022-08-15 15:00 ` Gerd Hoffmann
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-list 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=20221207074123.ccj63ciwywubqj6k@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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