From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) by mx.groups.io with SMTP id smtpd.web09.8368.1618316893162767684 for ; Tue, 13 Apr 2021 05:28:13 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@nuviainc-com.20150623.gappssmtp.com header.s=20150623 header.b=exHIIVgX; spf=pass (domain: nuviainc.com, ip: 209.85.219.169, mailfrom: leif@nuviainc.com) Received: by mail-yb1-f169.google.com with SMTP id g38so17899690ybi.12 for ; Tue, 13 Apr 2021 05:28:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuviainc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JhEOIb/gmGEy9x6ROImX6nbs/gCf33zgUlbNTVXNUn0=; b=exHIIVgXk+5PU/WWMhjrUSNd21sw/M+V3f1QxJ7E19Rjgj7pcs3Y38HYU3EWkUgq+B a5d46SK9llzxWAPcJj5CMGf4h2tp3RU16/7eSzEvGsosxWX+iw/ToQXtbtvNr3hd1WOG q1S92TKoLgXXKR3qpQFarIgbH99kyEZf7w1Kqic9F/5ywjXkN3Eg6mQX0jydqOfEC8v6 NtSzhiQdiyYncZs8TKghAA4vdyBqkzBtS1ryTuwy1AQBEh73/vgy8xvV/cKEIQsm/y2a goWfQVsd2azQTG+tvMUyhcwWZZtlBZp6m6czp5/LQi88DVP5Gbm+z4wj2V08uXEfT/Sp dS/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JhEOIb/gmGEy9x6ROImX6nbs/gCf33zgUlbNTVXNUn0=; b=OI1h/Wqopt16bHrEKlPJmOCYK26PGUGLj/y/zfW42QjSp47U+LXa9jhmgzIJRZ16Dr eQherVyBMbkcHv+2DAp8oDvRq+TP1y3NvXHVR6dulQNURT5WWwG6UUG5sDTP2mWsAy+Q 6yY0G6t+4NrYkXpFekWrZpo5mThvwmxZ47QuFqvy0FOO1W235W4uN609rQ1ybIqP5l+l no8HUzpiB6JMDdR28GjaNp8norXDO+TW5oAjH9mDCyTC+WFyStN39oLo7vEuTq3ZYB65 mXZ7EgmaLVQwiTDkzOb5JHH7PMcvgAff6bNU4Y3q1sXk1jZ8aXCPOrT85Gg4Rl68BtUJ GICA== X-Gm-Message-State: AOAM530fTyoPDEWQ6zr+ks3N2yINMFwdR9PRwempzzY9Du9HAom1zpm8 MQCYWV+2ZKhkA9Fau0ySPHWMAd2nozlZHRDYtYvQJemlq6ImJw== X-Google-Smtp-Source: ABdhPJw2X5AB/j4EPXsdS1RggI6eP0e9UyARYvEk4z1MlYh+U5fLWddtaUhRu6VOsZATgiYRUWyEHJyg4phpSmS/xog= X-Received: by 2002:a25:2b01:: with SMTP id r1mr46568109ybr.91.1618316892137; Tue, 13 Apr 2021 05:28:12 -0700 (PDT) MIME-Version: 1.0 References: <16713E6D64EE917D.25648@groups.io> <2379DE31-D6E1-491E-AE22-416085D73765@intel.com> <66e073bb-366b-0559-4a78-fc5e8215aca1@redhat.com> In-Reply-To: From: "Leif Lindholm" Date: Tue, 13 Apr 2021 13:28:01 +0100 Message-ID: Subject: Re: [edk2-devel] VirtIO Sound Driver (GSoC 2021) To: edk2-devel-groups-io , harlydavidsen@gmail.com Cc: Laszlo Ersek , "Desimone, Nathaniel L" , "afish@apple.com" , Rafael Rodrigues Machado , Gerd Hoffmann Content-Type: multipart/alternative; boundary="0000000000007d904405bfd9c3ba" --0000000000007d904405bfd9c3ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, especially Ethin. Apologies for radio silence - last week I was off on holiday, and before that ... let's just say corporate acquisitions generate some distractions. Anyway, I'm back, and since I'm down as the mentor for this task, feel fre= e to spam me with any remaining/new questions. / Leif On Tue, Apr 6, 2021 at 4:17 PM Ethin Probst wrot= e: > I'll attach the bug for the build tools to the BZ shortly. > Laszlo, thanks for that. I don't know their email addresses though. > And yes, I was going to make it device independent, as the majority > (if not all) of UEFI protocols are. > > On 4/6/21, Laszlo Ersek wrote: > > On 03/31/21 08:41, Nate DeSimone wrote: > >> Another option is to put the protocol definition in MdeModulePkg and > >> mark it with the EDKII_ prefix. For my last =E2=80=9Ccode first=E2=80= = =9D UEFI spec > >> contribution I did this with the PPI that added up getting added. > > > > The new audio protocol should be generic, only its implementation in > > question should be virtio specific. > > > > Please include Gerd Hoffmann (CC'd) in the protocol design, as well as > > the developers of the virtio-sound device model in QEMU. > > > > Thanks > > Laszlo > > > > > >> > >> > >> > >> Thanks, > >> > >> Nate > >> > >> > >> > >> *From: * on behalf of "Andrew Fish via groups.i= o" > >> > >> *Reply-To: *"devel@edk2.groups.io" , > >> "afish@apple.com" > >> *Date: *Tuesday, March 30, 2021 at 10:54 PM > >> *To: *edk2-devel-groups-io , > >> "harlydavidsen@gmail.com" > >> *Cc: *Rafael Rodrigues Machado > >> *Subject: *Re: [edk2-devel] VirtIO Sound Driver (GSoC 2021) > >> > >> > >> > >> > >> > >> On Mar 30, 2021, at 5:01 PM, Ethin Probst >> > wrote: > >> > >> > >> > >> I'm wondering where exactly I should add the VirtIO sound protoco= l. > I > >> just familiarized myself with the build system and am about to te= st > >> 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=E2=80=99d 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 l= ike > >> 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=E2=80=99t want to do that before = it is > >> standardized as that causes compatibility issues. So this is a =E2=80= = =9Ccode > >> first project=E2=80=9D (code prototype and then contribute to the UEF= I Forum for > >> inclusion in the specification) so we need to follow some code first > >> rules that I don=E2=80=99t 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 > >> =3D UEFI_APPLICATION > >> > >> > >> > >> Thanks, > >> > >> > >> > >> Andrew Fish > >> > >> > >> > >> > >> > >> > >> On 3/30/21, Ethin Probst via 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 OS= es > >> is > >> fun, I have to say that learning from the firmware code like > from > >> SeaBIOS has been some of the most enlightening and interestin= g > >> 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 supp= ort > >> second and HDA third. We'll see, but VirtIO definitely is com= ing > >> first. > >> > >> As I said before, I look forward to working with all of you > >> wonderful > >> people! > >> > >> On 3/30/21, Rafael Rodrigues Machado > >> >> > > >> wrote: > >> > >> This would be amazing so people can continue my work rela= ted > >> to > >> accessibility at BIOS. Something desired by the blind peo= ple > >> 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 > >> > >> 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 don= e > >> 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 a= ny > >> future projects! > >> :-) > >> > >> -- > >> Signed, > >> Ethin D. Probst > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> -- > >> Signed, > >> Ethin D. Probst > >> > >> > >> > >> > >> > >> > >> > >> -- > >> Signed, > >> Ethin D. Probst > >> > >> > >> > >> > >> > >> > > > > > > > -- > Signed, > Ethin D. Probst > > >=20 > > > --0000000000007d904405bfd9c3ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all, especially Ethin.

Ap= ologies for radio silence - last week I was off on holiday, and before that= ... let's just say corporate acquisitions generate some distractions.<= /div>
Anyway, I'm back, and since I'm down as the mentor for th= is task, feel free to spam me with any remaining/new questions.
<= br>
/
=C2=A0=C2=A0=C2=A0 Leif

On Tue, Apr 6, 2= 021 at 4:17 PM Ethin Probst <= harlydavidsen@gmail.com> wrote:
I'll attach the bug for the build tools to the B= Z shortly.
Laszlo, thanks for that. I don't know their email addresses though. And yes, I was going to make it device independent, as the majority
(if not all) of UEFI protocols are.

On 4/6/21, Laszlo Ersek <lersek@redhat.com> wrote:
> On 03/31/21 08:41, Nate DeSimone wrote:
>> Another option is to put the protocol definition in MdeModulePkg = and
>> mark it with the EDKII_ prefix. For my last =E2=80=9Ccode first= =E2=80=9D UEFI spec
>> contribution I did this with the PPI that added up getting added.=
>
> The new audio protocol should be generic, only its implementation in<= br> > question should be virtio specific.
>
> Please include Gerd Hoffmann (CC'd) in the protocol design, as we= ll as
> the developers of the virtio-sound device model in QEMU.
>
> Thanks
> Laszlo
>
>
>>
>>
>>
>> Thanks,
>>
>> Nate
>>
>>
>>
>> *From: *<devel@edk2.groups.io> on behalf of "Andrew Fish via groups.io&q= uot;
>> <afish=3Dapple.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<= /a>>
>> *Subject: *Re: [edk2-devel] VirtIO Sound Driver (GSoC 2021)
>>
>>
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0On Mar 30, 2021, at 5:01 PM, Ethin Probst <= harlydavidsen@= gmail.com
>>=C2=A0 =C2=A0 =C2=A0<mailto:harlydavidsen@gmail.com>> wrote:
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0I'm wondering where exactly I should add t= he VirtIO sound protocol. I
>>=C2=A0 =C2=A0 =C2=A0just familiarized myself with the build system= and am about to test
>> it
>>=C2=A0 =C2=A0 =C2=A0by building OVMF if possible, but I'm wond= ering where I should
>>=C2=A0 =C2=A0 =C2=A0actually put the protocol and all that stuff. = Maybe there's
>>=C2=A0 =C2=A0 =C2=A0documentation I've missed as well.
>>
>>
>>
>> Ethin,
>>
>>
>>
>> For the driver I=E2=80=99d 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 wou= ld like
>> to publish the protocol in the UEFI Spec (I can help with that pa= rt) and
>> that would mean we put the Protocol definition in
>> MdePkg/Include/Protocol, but we don=E2=80=99t want to do that bef= ore it is
>> standardized as that causes compatibility issues. So this is a = =E2=80=9Ccode
>> first project=E2=80=9D (code prototype and then contribute to the= UEFI Forum for
>> inclusion in the specification) so we need to follow some code fi= rst
>> rules that I don=E2=80=99t remember of the top of my head? So why= not start out
>> the protocol definition OvmfPkg/Include/Protocol. You can also ad= d 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 place= s to
>> put stuff, and it should be easy enough to move stuff around if >> everything else is working.
>>
>>
>>
>> [1]=C2=A0find OvmfPkg=C2=A0 -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]=C2=A0/Volumes/Case/edk2-github/OvmfPkg>git grep APPLICATIO= N -- *.inf |
>> grep MODULE_TYPE
>>
>> EnrollDefaultKeys/EnrollDefaultKeys.inf:13:=C2=A0 MODULE_TYPE
>> =C2=A0 =C2=A0 =3D UEFI_APPLICATION
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Andrew Fish
>>
>>
>>
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0On 3/30/21, Ethin Probst via=C2=A0groups.io <http://grou= ps.io/>
>>=C2=A0 =C2=A0 =C2=A0<harlydavidsen=3Dgmail.com@groups.io
>>=C2=A0 =C2=A0 =C2=A0<mailto:harlydavidsen=3Dgmail.com@groups.io>> wrote:
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I agree. Plus, it gives me a cha= nce to finally learn the EDK2
>> build
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0system and how it works! I'v= e been working on a hobby OS as a
>> side
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0project and, though learning fro= m other code examples from OSes
>> is
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fun, I have to say that learning= from the firmware code like from
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0SeaBIOS has been some of the mos= t enlightening and interesting
>> times
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0thus far.
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Thanks for the link to your code= , Rafael; once I get virtIO
>> support
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0in, I can work on HDA support, t= hough I might tackle USB support
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0second and HDA third. We'll = see, but VirtIO definitely is coming
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0first.
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0As I said before, I look forward= to working with all of you
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0wonderful
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0people!
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On 3/30/21, Rafael Rodrigues Mac= hado
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<rafaelrodrigues.machado@gmail.co= m
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailto:rafaelrodrigues.machado@g= mail.com>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0wrote:
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This would be amaz= ing so people can continue my work related
>> to
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0accessibility at B= IOS. Something desired by the blind people
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0since the
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A090's
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Just for reference= , this is what I have done:
>>
>>
>> https://github.com/Rafael= RMachado/Msc_UefiHda_PreOs_Accessibility
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Thanks
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Rafael
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Em seg, 29 de mar = de 2021 20:24, Ethin Probst
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<harlydavidsen@gmail.com&= gt;
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0escreveu:
>>
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hell= o everyone,
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This= is the first time I've ever contributed to EDK2. As
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0part= of GSoC
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02021= , I have submitted a proposal to implement a UEFI
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0audi= o output
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0prot= ocol that will utilize the VirtIO sound driver. I've
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alre= ady
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0subm= itted a draft proposal, and apologize if I've done
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0thin= gs out of
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0orde= r. This is my first time doing GSoC 2021, and
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cont= ributing to EDK2
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0felt= like a really fun thing to do!
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I lo= ok forward to working with you guys on this and any
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0futu= re projects!
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:-)<= br> >>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-- >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sign= ed,
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethi= n D. Probst
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Signed,
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethin D. Probst
>>
>>
>>
>>
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0--
>>=C2=A0 =C2=A0 =C2=A0Signed,
>>=C2=A0 =C2=A0 =C2=A0Ethin D. Probst
>>
>>
>>
>>
>>
>>
>
>


--
Signed,
Ethin D. Probst





--0000000000007d904405bfd9c3ba--