From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: Phillip Tennen <phillip@axleos.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 1/1] OvmfPkg: OVMF supports USB mouses
Date: Tue, 9 Apr 2024 16:51:20 +0100 [thread overview]
Message-ID: <CAKbZUD3WNTNpjAn+T7UkTK0Vyj6gmxEmfk0OWXgHJvnJ_WMX-g@mail.gmail.com> (raw)
In-Reply-To: <6do7bvuicrgx5w3tti6gaoevmswvndr6u27rihmu2c2fwtx7kj@osdsv4vkb2no>
On Tue, Apr 9, 2024 at 12:56 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> On Mon, Apr 08, 2024 at 08:53:10AM +0100, Phillip Tennen wrote:
> > Hi, thank you for taking a look at the patch!
> >
> > This patch can be verified to be working with this app (which was the
> > motivation for submitting this):
> > https://github.com/codyd51/uefirc/releases/tag/1.0.1.
>
> Quoting https://github.com/codyd51/uefirc:
>
> Q: Should I use this?
> A: This should not exist.
>
> Well. This certainly one of the more interesting ways to have some fun
> and improve your rust coding skills. But a justification to include a
> mouse driver by default which is not used by anything else? IMHO it
> isn't.
Maybe some better reasons:
1) It has been conspicuously missing from OVMF. I've heard N questions
over the years (on the #osdev IRC, etc) regarding their mouse code not
working on OVMF, whereas you'd see that protocol in other normal
platforms
2) UsbMouseDxe is part of upstream MdeModulePkg and has no testable
upstream consumers. One needs to patch their OVMF to test this easily
(or flash it onto some other hardware, which is hard to get for most
people, except for maybe the rpi platforms).
3) I don't believe (or would hope) OVMF maintainers will have
maintenance overhead from the inclusion. One would hope UsbMouseDxe
as-is is correct, and that the QEMU USB mouse is correct (or you'd see
the problem from the guest OS's side as well).
4) Mouse support is part of the spec (if you want to argue it
shouldn't be in the spec in the first place, I'd agree)
For sure, UsbMouseDxe isn't #1 on my most desired EFI modules list
(e.g I'd love to eventually be able to consume Ext4Dxe from OVMF,
where it'd actually be useful, if I can ever ditch edk2-platforms),
but I don't really see the harm in doing it.
There's an argument in giving people a full-fledged UEFI
implementation of most protocols. OVMF is *the* platform in mainline
edk2 after all :)
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117549): https://edk2.groups.io/g/devel/message/117549
Mute This Topic: https://groups.io/mt/105365480/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-09 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 12:41 [edk2-devel] [PATCH v2 1/1] OvmfPkg: OVMF supports USB mouses Heinrich Schuchardt
2024-04-08 7:35 ` Gerd Hoffmann
2024-04-08 7:53 ` Phillip Tennen
2024-04-09 11:55 ` Gerd Hoffmann
2024-04-09 12:50 ` Ard Biesheuvel
2024-04-09 15:51 ` Pedro Falcato [this message]
2024-04-10 8:54 ` 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=CAKbZUD3WNTNpjAn+T7UkTK0Vyj6gmxEmfk0OWXgHJvnJ_WMX-g@mail.gmail.com \
--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