From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id AB98778003C for ; Fri, 20 Oct 2023 08:45:39 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=YDiXRHi6em5/C8D5FzOZGMLCoQ2THqsz1mYgWXlJkDE=; c=relaxed/simple; d=groups.io; h=Subject:To:From:User-Agent:MIME-Version:Date:References:In-Reply-To:Message-ID:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type; s=20140610; t=1697791538; v=1; b=sqfg84+6CIuwZ+Qt7DDa4Xlua489fosJ05kISgE272Bqt8+S5YERLYyM3AczDNs7l4vS41Fn Q/H29/m+22mROqN42QwjsfGwnw8WnCMeOZ0WX63K5qOL8bz1hO0zPee7Wnf0XMEGVaMPYtiAKdm YARVaJ/qypmOvBEdGUhSb30A= X-Received: by 127.0.0.2 with SMTP id WDEXYY7687511x0MOK4xxkkP; Fri, 20 Oct 2023 01:45:38 -0700 Subject: Re: [edk2-devel] [PATCH v1 5/6] StarFive/JH7110Pkg: Implement boot services memory allocation driver To: Sunil V L ,devel@edk2.groups.io From: "John Chew" X-Originating-Location: Banting, Selangor, MY (202.188.176.82) X-Originating-Platform: Windows Chrome 118 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 20 Oct 2023 01:45:37 -0700 References: In-Reply-To: Message-ID: <19195.1697791537333045361@groups.io> Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,yuinyee.chew@starfivetech.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: RUHYCep6sJRA3hqLeLJNZTtex7686176AA= Content-Type: multipart/alternative; boundary="glfHHCMrIQaOygplhP95" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=sqfg84+6; dmarc=none; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io --glfHHCMrIQaOygplhP95 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Sunil, You're right. The MMC DMA destination buffer (64-bit) actually allocated in EDK2 code and= passed into the EDK2-platform MMC driver. Now that you mention it, I think I can allocate another buffer (force to us= e 32-bit) in the MMC driver and use that buffer for tx/rx. Then, copy the content from the buffer (32-bit) to the MMC destination buff= er (64-bit). In this case, there is no need to change any code in EDK2 and this "boot service memory allocation" driver is no longer neede= d. I will remove this driver and add the handling in DwEmmcDxe.c in Patch V2. Thank you!! =3D) -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#109826): https://edk2.groups.io/g/devel/message/109826 Mute This Topic: https://groups.io/mt/102053685/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --glfHHCMrIQaOygplhP95 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi Sunil,

 

You're right.

 

The MMC DMA destination buffer (64-bit) actually allocated in EDK2 code = and passed into the EDK2-platform MMC driver. 

Now that you mention it, I think I can allocate another buffer (force to= use 32-bit) in the MMC driver and use that buffer for tx/rx. 

Then, copy the content from the buffer (32-bit) to the MMC destination b= uffer (64-bit). In this case, there is no need to change any code

in EDK2 and this "boot service memory allocation" driver is no longer ne= eded.

 

I will remove this driver and add the handling in DwEmmcDxe.c in Patch V= 2.

 

Thank you!! =3D)

_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#109826) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
--glfHHCMrIQaOygplhP95--