android9.0 MTK平台添加分区表

最新推荐文章于 2024-08-05 09:42:39 发布
最新推荐文章于 2024-08-05 09:42:39 发布
阅读量3.6k 收藏 22
点赞数 2
分类专栏： MTK 系统开发
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jinron10/article/details/109239465
版权

8257添加分区，主要修改以下文件：

Changes to be committed:
        modified:   build/make/core/Makefile
        modified:   build/make/core/config.mk
        modified:   build/make/core/envsetup.mk
        modified:   build/make/core/main.mk
        modified:   build/make/tools/allmake.sh
        modified:   build/make/tools/releasetools/build_image.py
        modified:   device/autochips/ac8257/init.ac8257.rc
        modified:   device/autochips/ac8257_demo/BoardConfig.mk
        modified:   device/autochips/build/build/tools/ptgen/AC8257/partition_table_AC8257_emmc.csv
        modified:   device/autochips/sepolicy/bsp/non_plat/device.te
        modified:   device/autochips/sepolicy/bsp/non_plat/file.te
        modified:   device/autochips/sepolicy/bsp/non_plat/file_contexts
        modified:   device/autochips/sepolicy/bsp/non_plat/fsck.te
        modified:   device/autochips/sepolicy/bsp/non_plat/init.te
        modified:   device/autochips/sepolicy/bsp/non_plat/system_app.te
        modified:   system/core/rootdir/Android.mk
        modified:   vendor/mediatek/proprietary/hardware/fstab/ac8257/fstab.in.ac8257

以下是修改文件的主要过程，如下：
1、分区表中添加分区(这里添加三个分区)：
device/autochips/build/build/tools/ptgen/AC8257/partition_table_AC8257_emmc.csv
在这里插入图片描述
2、添加flashtool下载时需要的cpuinfo.img、resources.img和ivres.img三个文件的生成，主要修改以下文件
build/make/core/Makefile
build/make/core/config.mk
build/make/core/envsetup.mk
build/make/core/main.mk
build/make/tools/allmake.sh
build/make/tools/releasetools/build_image.py
system/core/rootdir/Android.mk
device/autochips/ac8257_demo/BoardConfig.mk
2.1）在build/make/core/Makefile 文件中添加如下：

$(if $(BOARD_AVMIMAGE_PARTITION_SIZE),$(hide) echo "avm_size=$(BOARD_AVMIMAGE_PARTITION_SIZE)" >> $(1))
+$(if $(BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE),$(hide) echo "resources_fs_type=$(BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE)" >> $(1))
+$(if $(BOARD_RESOURCESIMAGE_PARTITION_SIZE),$(hide) echo "resources_size=$(BOARD_RESOURCESIMAGE_PARTITION_SIZE)" >> $(1))
+$(if $(BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE),$(hide) echo "ivres_fs_type=$(BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE)" >> $(1))
+$(if $(BOARD_IVRESIMAGE_PARTITION_SIZE),$(hide) echo "ivres_size=$(BOARD_IVRESIMAGE_PARTITION_SIZE)" >> $(1))
+$(if $(BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE),$(hide) echo "cpuinfo_fs_type=$(BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE)" >> $(1))
+$(if $(BOARD_CPUINFOIMAGE_PARTITION_SIZE),$(hide) echo "cpuinfo_size=$(BOARD_CPUINFOIMAGE_PARTITION_SIZE)" >> $(1))
$(if $(BOARD_VENDORIMAGE_FILE_SYSTEM_TYPE),$(hide) echo "vendor_fs_type=$(BOARD_VENDORIMAGE_FILE_SYSTEM_TYPE)" >> $(1))

lse # BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE
# we need to ignore the broken cache link when doing the rsync
IGNORE_CACHE_LINK := --exclude=cache
endif # BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE

+#-----add by zhaojr
+# -----------------------------------------------------------------
+# cpuinfo partition image
+ifdef BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE
+INTERNAL_CPUINFOIMAGE_FILES := \
+    $(filter $(TARGET_OUT_CPUINFO)/%,$(ALL_DEFAULT_INSTALLED_MODULES))
+
+cpuinfoimage_intermediates := \
+    $(call intermediates-dir-for,PACKAGING,cpuinfo)
+BUILT_CPUINFOIMAGE_TARGET := $(PRODUCT_OUT)/cpuinfo.img

+define build-cpuinfoimage-target
+  $(call pretty,"Target cpuinfo fs image: $(INSTALLED_CPUINFOIMAGE_TARGET)")
+  @mkdir -p $(TARGET_OUT_CPUINFO)
+  @mkdir -p $(cpuinfoimage_intermediates) && rm -rf +$(cpuinfoimage_intermediates)/cpuinfo_image_info.txt
+  $(call generate-userimage-prop-dictionary, +$(cpuinfoimage_intermediates)/cpuinfo_image_info.txt, skip_fsck=true)
+  $(hide) PATH=$(foreach p,$(INTERNAL_USERIMAGES_BINARY_PATHS),$(p):)$$PATH \
+      build/make/tools/releasetools/build_image.py \
+      $(TARGET_OUT_CPUINFO) $(cpuinfoimage_intermediates)/cpuinfo_image_info.txt +$(INSTALLED_CPUINFOIMAGE_TARGET) $(TARGET_OUT)
+  $(hide) $(call assert-max-image-+size,$(INSTALLED_CPUINFOIMAGE_TARGET),$(BOARD_CPUINFOIMAGE_PARTITION_SIZE))
+endef

+# We just build this directly to the install location.
+INSTALLED_CPUINFOIMAGE_TARGET := $(BUILT_CPUINFOIMAGE_TARGET)
+$(INSTALLED_CPUINFOIMAGE_TARGET): $(INTERNAL_USERIMAGES_DEPS) +$(INTERNAL_CPUINFOIMAGE_FILES) $(BUILD_IMAGE_SRCS)
+	$(build-cpuinfoimage-target)

+.PHONY: cpuinfoimage-nodeps
+cpuinfoimage-nodeps: | $(INTERNAL_USERIMAGES_DEPS)
+	$(build-cpuinfoimage-target)

+else # BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE
+# we need to ignore the broken cpuinfo link when doing the rsync
+IGNORE_CPUINFO_LINK := --exclude=cpuinfo
+endif # BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE
+
+# resources partition image
+ifdef BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE
+INTERNAL_RESOURCESIMAGE_FILES := \
+    $(filter $(TARGET_OUT_RESOURCES)/%,$(ALL_DEFAULT_INSTALLED_MODULES))
+
+resourcesimage_intermediates := \
+    $(call intermediates-dir-for,PACKAGING,resources)
+BUILT_RESOURCESIMAGE_TARGET := $(PRODUCT_OUT)/resources.img
+
+define build-resourcesimage-target
+  $(call pretty,"Target resources fs image: $(INSTALLED_RESOURCESIMAGE_TARGET)")
+  @mkdir -p $(TARGET_OUT_RESOURCES)
+  @mkdir -p $(resourcesimage_intermediates) && rm -rf $(resourcesimage_intermediates)/resources_image_info.txt
+  $(call generate-userimage-prop-dictionary, $(resourcesimage_intermediates)/resources_image_info.txt, skip_fsck=true)
+  $(hide) PATH=$(foreach p,$(INTERNAL_USERIMAGES_BINARY_PATHS),$(p):)$$PATH \
+      build/make/tools/releasetools/build_image.py \
+      $(TARGET_OUT_RESOURCES) $(resourcesimage_intermediates)/resources_image_info.txt $(INSTALLED_RESOURCESIMAGE_TARGET) $(TARGET_OUT)
+  $(hide) $(call assert-max-image-size,$(INSTALLED_RESOURCESIMAGE_TARGET),$(BOARD_RESOURCESIMAGE_PARTITION_SIZE))
+endef
+
+# We just build this directly to the install location.
+INSTALLED_RESOURCESIMAGE_TARGET := $(BUILT_RESOURCESIMAGE_TARGET)
+$(INSTALLED_RESOURCESIMAGE_TARGET): $(INTERNAL_USERIMAGES_DEPS) $(INTERNAL_RESOURCESIMAGE_FILES) $(BUILD_IMAGE_SRCS)
+	$(build-resourcesimage-target)
+
+.PHONY: resourcesimage-nodeps
+resourcesimage-nodeps: | $(INTERNAL_USERIMAGES_DEPS)
+	$(build-resourcesimage-target)
+
+else # BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE
+# we need to ignore the broken cache link when doing the rsync
+IGNORE_RESOURCES_LINK := --exclude=resources
+endif # BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE
+
+# ivres partition image
+ifdef BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE
+INTERNAL_IVRESIMAGE_FILES := \
+    $(filter $(TARGET_OUT_IVRES)/%,$(ALL_DEFAULT_INSTALLED_MODULES))
+
+ivresimage_intermediates := \
+    $(call intermediates-dir-for,PACKAGING,ivres)
+BUILT_IVRESIMAGE_TARGET := $(PRODUCT_OUT)/ivres.img
+
+define build-ivresimage-target
+  $(call pretty,"Target ivres fs image: $(INSTALLED_IVRESIMAGE_TARGET)")
+  @mkdir -p $(TARGET_OUT_IVRES)
+  @mkdir -p $(ivresimage_intermediates) && rm -rf $(ivresimage_intermediates)/ivres_image_info.txt
+  $(call generate-userimage-prop-dictionary, $(ivresimage_intermediates)/ivres_image_info.txt, skip_fsck=true)
+  $(hide) PATH=$(foreach p,$(INTERNAL_USERIMAGES_BINARY_PATHS),$(p):)$$PATH \
+      build/make/tools/releasetools/build_image.py \
+      $(TARGET_OUT_IVRES) $(ivresimage_intermediates)/ivres_image_info.txt $(INSTALLED_IVRESIMAGE_TARGET) $(TARGET_OUT)
+  $(hide) $(call assert-max-image-size,$(INSTALLED_IVRESIMAGE_TARGET),$(BOARD_IVRESIMAGE_PARTITION_SIZE))
+endef
+
+# We just build this directly to the install location.
+INSTALLED_IVRESIMAGE_TARGET := $(BUILT_IVRESIMAGE_TARGET)
+$(INSTALLED_IVRESIMAGE_TARGET): $(INTERNAL_USERIMAGES_DEPS) $(INTERNAL_IVRESIMAGE_FILES) $(BUILD_IMAGE_SRCS)
+	$(build-ivresimage-target)
+
+.PHONY: ivresimage-nodeps
+ivresimage-nodeps: | $(INTERNAL_USERIMAGES_DEPS)
+	$(build-ivresimage-target)
+
+else # BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE
+# we need to ignore the broken ivres link when doing the rsync
+IGNORE_IVRES_LINK := --exclude=ivres
+endif # BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE
+#-----end add by zhaojr
+
# -----------------------------------------------------------------
# system_other partition image
ifeq ($(BOARD_USES_SYSTEM_OTHER_ODEX),true)
BOARD_USES_SYSTEM_OTHER := true

$(BUILT_TARGET_FILES_PACKAGE): \
		$(INSTALLED_BOOTIMAGE_TARGET) \
		$(MTK_BOOTIMAGE_TARGET) \
		$(INSTALLED_RADIOIMAGE_TARGET) \
		$(INSTALLED_RECOVERYIMAGE_TARGET) \
		$(FULL_SYSTEMIMAGE_DEPS) \
		$(INSTALLED_USERDATAIMAGE_TARGET) \
		$(INSTALLED_CACHEIMAGE_TARGET) \
+		$(INSTALLED_CPUINFOIMAGE_TARGET) \
+		$(INSTALLED_RESOURCESIMAGE_TARGET) \
+		$(INSTALLED_IVRESIMAGE_TARGET) \
		$(INSTALLED_INTSDIMAGE_TARGET) \

2.2) build/make/core/config.mk文件修改

dont_bother_goals := out \
    snod systemimage-nodeps \
    stnod systemtarball-nodeps \
    userdataimage-nodeps userdatatarball-nodeps \
    cacheimage-nodeps \
+    resourcesimage-nodeps \
+    ivresimage-nodeps \
+    cpuinfoimage-nodeps \
    bptimage-nodeps \

2.3）build/make/core/envsetup.mk文件的修改

$(TARGET_2ND_ARCH_VAR_PREFIX)TARGET_OUT_VENDOR_NATIVE_TESTS := $(TARGET_OUT_DATA)/nativetest$(TARGET_VENDOR_TEST_SUFFIX)
$(TARGET_2ND_ARCH_VAR_PREFIX)TARGET_OUT_VENDOR_METRIC_TESTS := $(TARGET_OUT_DATA)/benchmarktest$(TARGET_VENDOR_TEST_SUFFIX)
endif

TARGET_OUT_INTSD := $(PRODUCT_OUT)/intsd
TARGET_OUT_AVM := $(PRODUCT_OUT)/avm
TARGET_OUT_CACHE := $(PRODUCT_OUT)/cache
+TARGET_OUT_RESOURCES := $(PRODUCT_OUT)/resources
+TARGET_OUT_IVRES := $(PRODUCT_OUT)/ivres
+TARGET_OUT_CPUINFO := $(PRODUCT_OUT)/cpuinfo

TARGET_OUT_VENDOR := $(PRODUCT_OUT)/$(TARGET_COPY_OUT_VENDOR)
ifneq ($(filter address,$(SANITIZE_TARGET)),)

2.4）build/make/core/main.mk文件的修改

.PHONY: cacheimage
cacheimage: $(INSTALLED_CACHEIMAGE_TARGET)

+.PHONY: resourcesimage
+resourcesimage: $(INSTALLED_RESOURCESIMAGE_TARGET)

+.PHONY: ivres
+ivresimage: $(INSTALLED_IVRESIMAGE_TARGET)

+.PHONY: cpuinfoimage
+cpuinfoimage: $(INSTALLED_CPUINFOIMAGE_TARGET)

.PHONY: intsdimage
intsdimage: $(INSTALLED_INTSDIMAGE_TARGET)

.PHONY: avmimage
avmimage: $(INSTALLED_AVMIMAGE_TARGET)

# Build files and then package it into the rom formats
.PHONY: droidcore
droidcore: files \
	systemimage \
	$(INSTALLED_BOOTIMAGE_TARGET) \
	$(MTK_BOOTIMAGE_TARGET) \
	$(INSTALLED_RECOVERYIMAGE_TARGET) \
	$(INSTALLED_INTSDIMAGE_TARGET) \
	$(INSTALLED_AVMIMAGE_TARGET) \
	$(INSTALLED_VBMETAIMAGE_TARGET) \
	$(INSTALLED_USERDATAIMAGE_TARGET) \
	$(INSTALLED_CACHEIMAGE_TARGET) \
+	$(INSTALLED_RESOURCESIMAGE_TARGET) \
+	$(INSTALLED_IVRESIMAGE_TARGET) \
+	$(INSTALLED_CPUINFOIMAGE_TARGET) \
	$(INSTALLED_BPTIMAGE_TARGET) \

2.5）build/make/tools/allmake.sh文件的修改
IMAGES="*_Android_scatter.txt resources.img ivres.img cpuinfo.img arm2.img
添加resources.img ivres.img cpuinfo.img文件拷贝
2.6）build/make/tools/releasetools/build_image.py 文件的修改

 elif mount_point == "cache":
    copy_prop("cache_fs_type", "fs_type")
    copy_prop("cache_size", "partition_size")
+  elif mount_point == "cpuinfo":
+    copy_prop("cpuinfo_fs_type", "fs_type")
+    copy_prop("cpuinfo_size", "partition_size")
+  elif mount_point == "resources":
+    copy_prop("resources_fs_type", "fs_type")
+    copy_prop("resources_size", "partition_size")
+  elif mount_point == "ivres":
+    copy_prop("ivres_fs_type", "fs_type")
+    copy_prop("ivres_size", "partition_size")
  elif mount_point == "intsd":
    copy_prop("intsd_fs_type", "fs_type")
    copy_prop("intsd_size", "partition_size")
  elif mount_point == "avm":
    copy_prop("avm_fs_type", "fs_type")
    copy_prop("avm_size", "partition_size")

   elif image_filename == "cache.img":
      mount_point = "cache"
 +   elif image_filename == "cpuinfo.img":
 +     mount_point = "cpuinfo"
 +   elif image_filename == "resources.img":
 +     mount_point = "resources"
 +   elif image_filename == "ivres.img":
 +     mount_point = "ivres"
    elif image_filename == "intsd.img":
      mount_point = "intsd"
    elif image_filename == "avm.img":
      mount_point = "avm"

2.7 system/core/rootdir/Android.mk 文件的修改

ifdef BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE
  LOCAL_POST_INSTALL_CMD += ; mkdir -p $(TARGET_ROOT_OUT)/cache
else
  LOCAL_POST_INSTALL_CMD += ; ln -sf /data/cache $(TARGET_ROOT_OUT)/cache
endif

+###add by zhaojr#####
+ifdef BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE
+  LOCAL_POST_INSTALL_CMD += ; mkdir -p $(TARGET_ROOT_OUT)/cpuinfo
+endif
+ifdef BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE
+  LOCAL_POST_INSTALL_CMD += ; mkdir -p $(TARGET_ROOT_OUT)/resources
+endif
+ifdef BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE
+  LOCAL_POST_INSTALL_CMD += ; mkdir -p $(TARGET_ROOT_OUT)/ivres
+endif
+####end add by zhaojr####

ifdef BOARD_ROOT_EXTRA_SYMLINKS

2.8 device/autochips/ac8257_demo/BoardConfig.mk 文件的修改

# Create avm partition
#ifeq ($(strip $(ATC_AVM_SUPPORT)),yes)
BOARD_AVMIMAGE_FILE_SYSTEM_TYPE := ext4
#endif
+#add by zhaojr resources ivres cpuinfo
+BOARD_CPUINFOIMAGE_FILE_SYSTEM_TYPE := ext4
+BOARD_RESOURCESIMAGE_FILE_SYSTEM_TYPE := ext4
+BOARD_IVRESIMAGE_FILE_SYSTEM_TYPE := ext4
+#end by zhaojr

3、修改fstab文件添加分区的挂载和系统启动时挂载权限
修改：vendor/mediatek/proprietary/hardware/fstab/ac8257/fstab.in.ac8257

DEVPATH(protect1)   /mnt/vendor/protect_f   ext4   FS_FLAG_COMMIT   FSMGR_FLAG_FMT
DEVPATH(protect2)   /mnt/vendor/protect_s   ext4   FS_FLAG_COMMIT   FSMGR_FLAG_FMT
DEVPATH(nvdata)     /mnt/vendor/nvdata      ext4   FS_FLAG_DISCARD  FSMGR_FLAG_FMT
DEVPATH(nvcfg)      /mnt/vendor/nvcfg       ext4   FS_FLAG_COMMIT   FSMGR_FLAG_FMT
+DEVPATH(cpuinfo)      /cpuinfo     ext4   FS_FLAG_COMMIT FSMGR_FLAG_FMT
+DEVPATH(resources)  /resources  ext4   FS_FLAG_COMMIT FSMGR_FLAG_FMT
+DEVPATH(ivres)      /ivres      ext4   FS_FLAG_COMMIT FSMGR_FLAG_FMT

修改：device/autochips/ac8257/init.ac8257.rc

on post-fs-data
  ........................
  ................................
      #Create flash folder
    mkdir /data/vendor/flash
    chown root system /data/vendor/flash
    chmod 0771 /data/vendor/flash

    #add by zhaojr
+    # We chown/chmod /cpuinfo again so because mount is run as root + defaults
+    chown system system /cpuinfo
+    chmod 0771 /cpuinfo

+    # We chown/chmod /resources again so because mount is run as root + defaults
+    chown system system /resources
+    chmod 0771 /resources

+    # We chown/chmod /ivres again so because mount is run as root + defaults
+    chown system system /ivres
+    chmod 0771 /ivres
+    #end add by zhaojr
    
    #Create NDD mount point
    mkdir /data/vendor/camera_dump
    chown root system /data/vendor/camera_dump
    chmod 0771 /data/vendor/camera_dump

4、添加挂载分区的selinux权限，否则系统启动无法挂载
device/autochips/sepolicy/bsp/non_plat/device.te
device/autochips/sepolicy/bsp/non_plat/file.te
device/autochips/sepolicy/bsp/non_plat/file_contexts
device/autochips/sepolicy/bsp/non_plat/fsck.te
device/autochips/sepolicy/bsp/non_plat/init.te
device/autochips/sepolicy/bsp/non_plat/system_app.te
4.1 定义设备块文件
device/autochips/sepolicy/bsp/non_plat/device.te

# add by zhaojr
# Purpose: Add cpuinfo partition sepolicy
type cpuinfo_device, dev_type;
type cpuinfo_block_device, dev_type;
# Purpose: Add resources partition sepolicy
type resources_device, dev_type;
type resources_block_device, dev_type;
# Purpose: Add ivres partition sepolicy
type ivres_device, dev_type;
type ivres_block_device, dev_type;
# end add by zhaojr

4.2 定义文件类型
device/autochips/sepolicy/bsp/non_plat/file.te

# add by zhaojr
# Date : 2019/05/27
# Operation : Migration
# Purpose: Add cpuinfo partition sepolicy
type cpuinfo_file, file_type, data_file_type;

# Date : 2019/05/27
# Operation : Migration
# Purpose: Add resources partition sepolicy
type resources_file, file_type, data_file_type;

# Date : 2019/05/27
# Operation : Migration
# Purpose: Add ivres partition sepolicy
type ivres_file, file_type, data_file_type;
#end add by zhaojr

4.3 添加分区生成和挂载目录的访问权限
device/autochips/sepolicy/bsp/non_plat/file_contexts

# add for avm partition
/dev/block/platform/bootdevice/by-name/avm u:object_r:avm_block_device:s0
/avm(/.*)? u:object_r:avm_file:s0

# add by zhaojr
# add for cpuinfo partition
/dev/block/platform/bootdevice/by-name/cpuinfo u:object_r:cpuinfo_block_device:s0
/cpuinfo(/.*)? u:object_r:cpuinfo_file:s0

# add for resources partition
/dev/block/platform/bootdevice/by-name/resources u:object_r:resources_block_device:s0
/resources(/.*)? u:object_r:resources_file:s0

# add for ivres partition
/dev/block/platform/bootdevice/by-name/ivres u:object_r:ivres_block_device:s0
/ivres(/.*)? u:object_r:ivres_file:s0
# end add by zhaojr

# add for backcar partition
/data/vendor/backcar(/.*)? u:object_r:backcar_file:s0

4.4 添加fsck访问分区的权限
device/autochips/sepolicy/bsp/non_plat/fsck.te

#============= fsck ==============
allow fsck sysfs_fs_ext4_features:dir search;
allow fsck avm_block_device:blk_file rw_file_perms;
#add by zhaojr
allow fsck cpuinfo_block_device:blk_file rw_file_perms;
allow fsck resources_block_device:blk_file rw_file_perms;
allow fsck ivres_block_device:blk_file rw_file_perms;
#end add by zhaojr

4.5 添加init和system进程访问的权限
device/autochips/sepolicy/bsp/non_plat/init.te

# for avm partition
allow init avm_block_device:blk_file relabelto;
allow init avm_file:dir mounton;

#add by zhaojr
# for cpuinfo partition
allow init cpuinfo_block_device:blk_file relabelto;
allow init cpuinfo_file:dir mounton;
# for resources partition
allow init resources_block_device:blk_file relabelto;
allow init resources_file:dir mounton;
# for ivres partition
allow init ivres_block_device:blk_file relabelto;
allow init ivres_file:dir mounton;
#end add by zhaojr

# for backcar partition
allow init backcar_file:dir mounton;

device/autochips/sepolicy/bsp/non_plat/system_app.te

# for avm partition access
allow system_app avm_file:file { getattr unlink open read write create };
allow system_app avm_file:dir rw_dir_perms;
allow system_app atc_cem_prop:file { getattr open };
allow system_app atccam_prop:file { getattr open };
allow system_app hal_fastavm_daemon:fd use;
#add by zhaojr for partition system access
# for cpuinfo partition access
allow system_app cpuinfo_file:file { getattr unlink open read write create };
allow system_app cpuinfo_file:dir rw_dir_perms;
# for resources partition access
allow system_app resources_file:file { getattr unlink open read write create };
allow system_app resources_file:dir rw_dir_perms;
# for ivres partition access
allow system_app ivres_file:file { getattr unlink open read write create };
allow system_app ivres_file:dir rw_dir_perms;
#end add by zhaojr for partition system access

# Date: 2019/05/27
# Purpose: Allow app to get atc_backcar_prop
# Package: app
get_prop(system_app, atc_backcar_prop);

全部修改完成后，全编译系统，然后烧录即可。

jinron10
关注
专栏目录
MTK分区之（七）MTK分区修改规则总结
qq_39695119的博客
07-16 1926
1、对于客户，闻泰新加的分区 （1）要放在分区表靠后的位置 （2）如果分区大小以后需要扩大，或者很有可能，最好放在动态分区里 （3）和提需求的owner或客户确认添加的分区在升级的时候需不需要不丢失数据 如果需要不丢失数据，分区表Operation_Type列要设为PROTECTED 2、对于persist、sec1、seccfg、md1img、vendor、system、super、userdata、ints...
28.mtk分区表
老道
12-26 1973
[DESCRIPTION]//Project mk中的宏优先级比较高 默认的分区表文件partition_table_${PLATFORM}.xls是放在alps/mediatek/build/tools/ptgen/{PLATFORM}/目录(JB/KK)或alps/device/mediatek/build/build/tools/ptgen/{PLATFORM}/ 目录(L)下...
android10.0(Q) MTK 6765 user版本打开root权限
最新发布
u010345983的博客
08-05 4425
相比较 Android8.1、9.0 而言，Android10.0 版本 的 root变得相当麻烦，10.0 中引入了动态分区机制，同样的要想完全 adb root，需要 fastboot 解锁，然后关闭 verity 才能 adb remount 成功。我尝试和之前一样修改 fstab.in.mt6765 中的 ro 和 rw 初始值，容易导致无法正常开机，在这耗费了很长时间，就暂时先跳过吧，apk root 是 ok的。
mtk6516分区表
weixin_34252686的博客
09-06 182
[ 1.379981] Creating 13 MTD partitions on "MT6516-Nand": [ 1.380708] 0x000000000000-0x000000020000 : "preloader" [ 1.383166] 0x000000020000-0x000000320000 : "nvram" [ 1.3852...
MTK Android10添加分区
xuyewen288的博客
10-16 656
MTK Android10添加分区
AndroidQ(10.0) MTK平台添加新分区
cczhengv
05-14 3872
65 平台增加一个新分区，用于保存特殊数据，修改文件列表如下 modified: build/make/core/Makefile modified: build/make/core/config.mk modified: build/make/core/envsetup.mk modified: build/make/core/main.mk modified: build/make/tools/releasetools/build_image.py modified:
Android11.0(R) MTK平台添加新分区
cczhengv
09-15 7128
mtk 平台增加一个新分区test，修改文件列表如下 modified: device/mediatek/mt6765/init.mt6765.rc modified: device/mediatek/mt6765/sepolicy/basic/device.te modified: device/mediatek/mt6765/sepolicy/basic/file_contexts modified: device/mediatek/mt6765/ueventd.mt6765.e
Android 9.0 10.0 framework添加KeyEvent按键事件流程.rar
09-14
本资料主要探讨在Android 9.0 (Pie) 和 Android 10.0 (Q) 操作系统版本中，在framework层添加KeyEvent事件的详细流程。了解这一流程对于系统开发者或定制ROM的工程师至关重要，因为这涉及到对硬件按键行为的自定义和...
Android9.0 MTK7668U.rar
06-04
《Android 9.0平台MTK7668U模块：蓝牙+wifi驱动源码解析》 在Android系统中，硬件驱动是连接操作系统与硬件设备的关键桥梁，它使得上层应用能够有效地控制和利用硬件资源。本文将深入探讨基于Android 9.0平台的MTK...
MTK9.0添加开机铃声补丁.zip
02-05
标题“MTK9.0添加开机铃声补丁.zip”暗示了这是一个针对MediaTek（MTK）芯片组的Android系统更新补丁，主要用于在启动过程中添加或修改开机铃声。MediaTek是一家知名的手机和平板电脑处理器制造商，其硬件平台广泛...
Android9.0 MTK8666平台摄像头数据分析
zjy764219923的专栏
08-08 2838
MTK8666从VideoTexProducer和StreamHandler打开摄像头开始分析到Hal层
添加新分区FDRAM并挂载到根目录.zip
07-22
MTK平台Android9.0后，以前添加新分区和挂载的方法已经不适用，附件为最新的修改方法，以分区FDRAM为例，在MT6761平台上添加新分区FDRAM并挂载到根目录上，且具备读写权限。
android 平板固定横屏,Android9.0 MTK 平板横屏方案修改
weixin_35337252的博客
05-25 1559
拆解步骤1、app强制横屏显现，无视android:screenOrientation=”portrait”属性2、屏幕接触坐标修正为横屏3、开机动画横屏4、开机logo、关机充电动画横屏5、RecoveryUI横屏上代码1、app强制横屏显现修正rotationForOrientationLw(),默许回来270frameworks\base\services\core\java\com\and...
MTK分区之（一）MTK分区布局及分区基础
qq_39695119的博客
07-16 2765
一、MTK分区布局及分区基础 上图就是MTK分区布局图 首先为了让大家能看懂这张图，先介绍一下这种图上看上去比较陌生的词 （这些陌生的概念我们必须了解一下，因为后面我讲MTK分区工具ptgen的时候也要用到这些知识） （一）MBR、GPT介绍 看上面的MTK分区布局图，首先从左往右看， 左边是MBR分区方案、右边是GPT分区方案。 下面介绍一下这两种分区方案 1、MBR 上图就是MBR分区方案示意图 从左往右看，MBR分区方案使用第一个物理扇区作为分区表的空间保存..
MTK 平台增加分区流程 及 注意事项
jimbo的专栏
06-06 1426
MTK 平台增加新的分区流程及注意事项
Android13 MTK平台新增分区
weixin_51115260的博客
07-26 1327
基于MTK平台，split build1.5方式的mt6789平台上进行调试。驱动和系统层代码分别在S/T版本下。新增分区zlintek。
Android 新增一个分区
求变，从思想开始
04-14 4705
在最新的Android 版本上如何新增一个分区呢？总的来说，细节是比较复杂的，由于新的版本上 增加Image签名，Verify，动态分区等功能概念，所以还是有很多细节需要处理。大的原则上是： 1、增加分区表，不同平台方法不一样；高通通过修改xml，MTK通过修改Excel文件 2、是否是纯数据分区，是否需要Signed。这个比较关键，因为脚本build_image.py...
mtk平台dump系统分区
一路到黑
09-25 4880
声明 为什么要dump Android分区 mtk平台如何将Android分区dump出来 旧事重提声明郑重声明：博文为原创内容，可以转载或引用，但须在明显位置标明原文作者和出处，未经同意不得擅自修改本文内容！博客地址：http://blog.csdn.net/luzhenrong451. 为什么要dump Android分区？一般来讲，Android设备可以正常开机情况下，我们可以通过各种方式和手
MT8127_Android_scatter.txt 文件添加backup分区
lb5761311的专栏
12-08 9644
最近在做mtk盒子时候。发现用flash_tool烧写rom的时不能正常识别backup 分区（上图）。需要手动添加backup.img。特别麻烦。通过代码查看发现MT8127_Android_scatter.txt 文件主要由mediatek/build/tools/ptgen/MT8127/ptgen.pl 生成。 open (SCAT_NAME, ">$SCAT_NAME") or
评论 8
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值