From 34489d5f946f41b587987df83f44cde92706dc31 Mon Sep 17 00:00:00 2001 From: bunnie Date: Tue, 30 Apr 2024 17:08:09 +0800 Subject: [PATCH] raise visibility of internal ifram structures allows for abstraction violations but at this stage of debugging, we'll need it. --- libs/cramium-hal/src/ifram.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libs/cramium-hal/src/ifram.rs b/libs/cramium-hal/src/ifram.rs index 636a8e6f6..a5d79cb61 100644 --- a/libs/cramium-hal/src/ifram.rs +++ b/libs/cramium-hal/src/ifram.rs @@ -9,8 +9,8 @@ pub enum IframBank { /// `IframRange` is a range of memory that is suitable for use as a DMA target. pub struct IframRange { - pub(crate) phys_range: MemoryRange, - pub(crate) virt_range: MemoryRange, + pub phys_range: MemoryRange, + pub virt_range: MemoryRange, /// The connection is optional, because in some special cases the range "outlives" /// the OS (e.g. serial ports handed to us from the loader), and thus also can't /// be "dropped".