# Fabric node in device tree added by meta-xilinx-pynq

**URL:** <https://discuss.pynq.io/t/fabric-node-in-device-tree-added-by-meta-xilinx-pynq/2505>\
**Category:** Support\
**Created:** [April 6, 2021, 1:06pm UTC](https://discuss.pynq.io/t/fabric-node-in-device-tree-added-by-meta-xilinx-pynq/2505 "2021-04-06T13:06:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@Abhishek](https://discuss.pynq.io/u/Abhishek)\
**Post date:** [April 6, 2021, 1:06pm UTC](https://discuss.pynq.io/t/fabric-node-in-device-tree-added-by-meta-xilinx-pynq/2505/1 "2021-04-06T13:06:26Z")

</div>

Hi,

The following node is added in device tree by pynq-overlay recipe in meta-xilinx-pynq:-

fabric@A0000000 {  
compatible = “generic-uio”;  
reg = \<0x0 0xA0001000 0x0 0x1000\>;  
status = “okay”;  
interrupt-parent = \<&gic\>;  
interrupts = \<0 89 4\>;  
};

Since I’m trying to add pynq package in a custom zynqmp SOM. I’d like to know what the address “0xA0001000” and interrupt “0 89 4” is referring to ?

So that I may remove or change this to appropriate values.

---

<div class="post-metadata">

**Author:** ![PeterOgden](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/peterogden/32/55_2.png) [@PeterOgden](https://discuss.pynq.io/u/PeterOgden)\
**Post date:** [April 6, 2021, 3:04pm UTC](https://discuss.pynq.io/t/fabric-node-in-device-tree-added-by-meta-xilinx-pynq/2505/2 "2021-04-06T15:04:16Z")

</div>

This device is solely used for interrupt support. The address doesn’t matter as long as it doesn’t conflict with another device in the device-tree. The interrupt line is making a level-triggered interrupt on the first PL to PS interrupt line in accordance with the expectations for the [pynq interrupt framework](https://pynq.readthedocs.io/en/v2.6.1/overlay_design_methodology/pspl_interface.html#interrupt).

Depending on what you’re planning on doing with your SOM you can either remove it if you don’t need PYNQ interrupt support, move it to a different interrupt/address if it conflicts with something in your default PL design or leave it as is.

Peter