From: "Andrew Fish" <afish@apple.com>
To: Ethin Probst <harlydavidsen@gmail.com>
Cc: devel@edk2.groups.io, nathaniel.l.desimone@intel.com,
Rafael Rodrigues Machado <rafaelrodrigues.machado@gmail.com>
Subject: Re: [edk2-devel] VirtIO Sound Driver (GSoC 2021)
Date: Sun, 04 Apr 2021 21:42:12 -0700 [thread overview]
Message-ID: <A394C4B5-0F21-4248-AC31-B221E3D26556@apple.com> (raw)
In-Reply-To: <CAJQtwF2dz3j+RCUOi6S60SesRZTQyfFeew7XsAe4h_Jeto0QYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6491 bytes --]
Ethin I’m not sure what issue you are hitting with VFR? When you built the C build tools it should have built the VFR compiler that matches the code?
Did you run edksetup.bat Rebuild?
> On Mar 31, 2021, at 10:05 PM, Ethin Probst <harlydavidsen@gmail.com> wrote:
>
> Hello there,
>
> Some good advice, and thank you! I might add it to the other virtIO*
> drivers if I can figure out a good template for that.
>
> One thing I'm running into right now is that my build setup is
> currently unable to build MdeModulePkg (which is required to build
> OVMF, according to the readme). I've reported it on the bugzilla; its
> issue 3289. This doesn't appear to occur on Linux, however, which is
> odd.
>
> Are there any suggestions that you guys have for improving my
> proposal? I didn't want to write too much or go overboard, like
> explaining how the sound driver would work and such, since I assumed
> -- while writing it -- that anyone who wanted to know those inner
> details would go read the VirtIO specification. But I'd appreciate any
> extra feedback before I submit my final version; I haven't made any
> changes since my initial proposal as of yet.
>
>> On 3/31/21, Nate DeSimone <nathaniel.l.desimone@intel.com> wrote:
>> Another option is to put the protocol definition in MdeModulePkg and mark it
>> with the EDKII_ prefix. For my last “code first” UEFI spec contribution I
>> did this with the PPI that added up getting added.
>>
>> Thanks,
>> Nate
>>
>> From: <devel@edk2.groups.io> on behalf of "Andrew Fish via groups.io"
>> <afish=apple.com@groups.io>
>> Reply-To: "devel@edk2.groups.io" <devel@edk2.groups.io>, "afish@apple.com"
>> <afish@apple.com>
>> Date: Tuesday, March 30, 2021 at 10:54 PM
>> To: edk2-devel-groups-io <devel@edk2.groups.io>, "harlydavidsen@gmail.com"
>> <harlydavidsen@gmail.com>
>> Cc: Rafael Rodrigues Machado <rafaelrodrigues.machado@gmail.com>
>> Subject: Re: [edk2-devel] VirtIO Sound Driver (GSoC 2021)
>>
>>
>>
>> On Mar 30, 2021, at 5:01 PM, Ethin Probst
>> <harlydavidsen@gmail.com<mailto:harlydavidsen@gmail.com>> wrote:
>>
>> I'm wondering where exactly I should add the VirtIO sound protocol. I
>> just familiarized myself with the build system and am about to test it
>> by building OVMF if possible, but I'm wondering where I should
>> actually put the protocol and all that stuff. Maybe there's
>> documentation I've missed as well.
>>
>> Ethin,
>>
>> For the driver I’d match the patter of OVMF [1] and use
>> OvmfPkg/VirtioSoundDxe/. Maybe even use one of the other drivers as a
>> template.
>>
>> The protocol is more of a public thing. I think eventually we would like to
>> publish the protocol in the UEFI Spec (I can help with that part) and that
>> would mean we put the Protocol definition in MdePkg/Include/Protocol, but we
>> don’t want to do that before it is standardized as that causes compatibility
>> issues. So this is a “code first project” (code prototype and then
>> contribute to the UEFI Forum for inclusion in the specification) so we need
>> to follow some code first rules that I don’t remember of the top of my head?
>> So why not start out the protocol definition OvmfPkg/Include/Protocol. You
>> can also add a test application looks like you can just use the root [2] of
>> OVMF for that. That way the project is not blocked.
>>
>> We can have a conversation on the mailing list about better places to put
>> stuff, and it should be easy enough to move stuff around if everything else
>> is working.
>>
>> [1] find OvmfPkg -iname '*Virtio*.inf'
>> OvmfPkg/VirtioPciDeviceDxe/VirtioPciDeviceDxe.inf
>> OvmfPkg/VirtioScsiDxe/VirtioScsi.inf
>> OvmfPkg/Library/VirtioMmioDeviceLib/VirtioMmioDeviceLib.inf
>> OvmfPkg/Library/VirtioLib/VirtioLib.inf
>> OvmfPkg/VirtioGpuDxe/VirtioGpu.inf
>> OvmfPkg/VirtioBlkDxe/VirtioBlk.inf
>> OvmfPkg/Virtio10Dxe/Virtio10.inf
>> OvmfPkg/VirtioNetDxe/VirtioNet.inf
>> OvmfPkg/VirtioRngDxe/VirtioRng.inf
>>
>>
>> [2] /Volumes/Case/edk2-github/OvmfPkg>git grep APPLICATION -- *.inf | grep
>> MODULE_TYPE
>> EnrollDefaultKeys/EnrollDefaultKeys.inf:13: MODULE_TYPE
>> = UEFI_APPLICATION
>>
>> Thanks,
>>
>> Andrew Fish
>>
>>
>>
>>
>> On 3/30/21, Ethin Probst via groups.io<http://groups.io/>
>> <harlydavidsen=gmail.com@groups.io<mailto:harlydavidsen=gmail.com@groups.io>>
>> wrote:
>>
>> I agree. Plus, it gives me a chance to finally learn the EDK2 build
>> system and how it works! I've been working on a hobby OS as a side
>> project and, though learning from other code examples from OSes is
>> fun, I have to say that learning from the firmware code like from
>> SeaBIOS has been some of the most enlightening and interesting times
>> thus far.
>> Thanks for the link to your code, Rafael; once I get virtIO support
>> in, I can work on HDA support, though I might tackle USB support
>> second and HDA third. We'll see, but VirtIO definitely is coming
>> first.
>>
>> As I said before, I look forward to working with all of you wonderful
>> people!
>>
>> On 3/30/21, Rafael Rodrigues Machado
>> <rafaelrodrigues.machado@gmail.com<mailto:rafaelrodrigues.machado@gmail.com>>
>> wrote:
>>
>> This would be amazing so people can continue my work related to
>> accessibility at BIOS. Something desired by the blind people since the
>> 90's
>> Just for reference, this is what I have done:
>>
>> https://github.com/RafaelRMachado/Msc_UefiHda_PreOs_Accessibility
>>
>> Thanks
>> Rafael
>>
>> Em seg, 29 de mar de 2021 20:24, Ethin Probst <harlydavidsen@gmail.com>
>> escreveu:
>>
>>
>> Hello everyone,
>>
>> This is the first time I've ever contributed to EDK2. As part of GSoC
>> 2021, I have submitted a proposal to implement a UEFI audio output
>> protocol that will utilize the VirtIO sound driver. I've already
>> submitted a draft proposal, and apologize if I've done things out of
>> order. This is my first time doing GSoC 2021, and contributing to EDK2
>> felt like a really fun thing to do!
>>
>> I look forward to working with you guys on this and any future projects!
>> :-)
>>
>> --
>> Signed,
>> Ethin D. Probst
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Signed,
>> Ethin D. Probst
>>
>>
>>
>>
>>
>>
>>
>> --
>> Signed,
>> Ethin D. Probst
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Signed,
> Ethin D. Probst
[-- Attachment #2: Type: text/html, Size: 15078 bytes --]
next prev parent reply other threads:[~2021-04-05 4:42 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 20:28 VirtIO Sound Driver (GSoC 2021) Ethin Probst
2021-03-30 3:17 ` [edk2-devel] " Nate DeSimone
2021-03-30 14:41 ` Ethin Probst
2021-03-31 6:34 ` Nate DeSimone
2021-03-30 21:50 ` Rafael Machado
2021-03-30 22:12 ` Ethin Probst
[not found] ` <16713E6D64EE917D.25648@groups.io>
2021-03-31 0:01 ` Ethin Probst
2021-03-31 5:02 ` Andrew Fish
2021-03-31 6:41 ` Nate DeSimone
2021-04-01 5:05 ` Ethin Probst
2021-04-05 4:42 ` Andrew Fish [this message]
2021-04-05 4:43 ` Ethin Probst
2021-04-05 5:10 ` Andrew Fish
2021-04-06 14:16 ` Laszlo Ersek
2021-04-06 15:17 ` Ethin Probst
2021-04-13 12:28 ` Leif Lindholm
2021-04-13 14:16 ` Andrew Fish
2021-04-13 16:53 ` Ethin Probst
2021-04-13 21:38 ` Andrew Fish
2021-04-13 23:47 ` Ethin Probst
[not found] ` <16758FB6436B1195.32393@groups.io>
2021-04-14 1:20 ` Ethin Probst
2021-04-14 3:52 ` Andrew Fish
2021-04-14 20:47 ` Ethin Probst
2021-04-14 22:30 ` Michael D Kinney
2021-04-14 23:54 ` Andrew Fish
2021-04-15 4:01 ` Ethin Probst
2021-04-15 4:58 ` Andrew Fish
2021-04-15 5:28 ` Ethin Probst
2021-04-15 12:07 ` Michael Brown
2021-04-15 16:42 ` Andrew Fish
2021-04-15 20:11 ` Ethin Probst
2021-04-15 22:35 ` Andrew Fish
2021-04-15 23:42 ` Ethin Probst
2021-04-16 0:59 ` Michael Brown
2021-04-16 5:13 ` Andrew Fish
2021-04-16 5:33 ` Ethin Probst
2021-04-16 11:34 ` Leif Lindholm
2021-04-16 17:03 ` Andrew Fish
2021-04-16 17:45 ` Ethin Probst
2021-04-16 17:55 ` Ethin Probst
2021-04-16 18:09 ` Andrew Fish
2021-04-16 23:50 ` Ethin Probst
2021-04-16 18:02 ` Andrew Fish
2021-04-17 16:51 ` Marvin Häuser
2021-04-17 17:31 ` Andrew Fish
2021-04-17 18:04 ` Marvin Häuser
2021-04-18 8:55 ` Ethin Probst
2021-04-18 15:22 ` Andrew Fish
2021-04-18 19:11 ` Marvin Häuser
2021-04-18 19:22 ` Marvin Häuser
2021-04-18 21:00 ` Andrew Fish
2021-04-16 13:22 ` Marvin Häuser
2021-04-16 14:34 ` Andrew Fish
2021-04-16 15:03 ` Marvin Häuser
[not found] ` <16762C957671127A.12361@groups.io>
2021-04-16 0:59 ` Ethin Probst
2021-04-16 1:03 ` Michael Brown
2021-04-16 2:06 ` Ethin Probst
2021-04-16 3:48 ` Andrew Fish
2021-04-16 4:29 ` Ethin Probst
2021-04-15 9:51 ` Laszlo Ersek
2021-04-15 16:01 ` Andrew Fish
2021-04-04 22:05 ` Marvin Häuser
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=A394C4B5-0F21-4248-AC31-B221E3D26556@apple.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