**** BEGIN LOGGING AT Fri May 07 02:59:57 2021
May 07 11:32:27 <YadnikBendale[m]> jduchniewicz: I was facing a few minor issues but resolved them.
May 07 11:33:34 <YadnikBendale[m]> I was able to build the micropython port for QEMU.
May 07 11:33:53 * YadnikBendale[m] uploaded an image: (154KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KtrQBJxNzADQmWiVKExgUgny/Screenshot%20from%202021-05-07%2015-57-16.png >
May 07 11:33:59 * YadnikBendale[m] uploaded an image: (128KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/CNptjZpxwSWMwmzLChLBdnKe/Screenshot%20from%202021-05-07%2015-58-08.png >
May 07 11:34:03 * YadnikBendale[m] uploaded an image: (117KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/gpgxmiiJixbTnGIUUCysbNxa/Screenshot%20from%202021-05-07%2015-58-15.png >
May 07 11:35:25 <YadnikBendale[m]> jduchniewicz and  jkridner can you'll please have a look.
May 07 11:36:41 <YadnikBendale[m]> I followed this https://github.com/micropython/micropython/blob/master/ports/zephyr/README.md.
May 07 19:32:03 <DhruvaG2000[m]> I had a basic question... How exactly does software know which BealgeBoard it is running on? Like how and where is this model name retrieved from? (I am guessing EEPROM? )
May 07 19:32:03 <DhruvaG2000[m]> Also, what is the naming convention? Like for BBB part number was BB-BONE-MRF24J40 I guess?
May 07 19:50:30 <satacker[m]> The device tree binary is passed by uboot arguments
May 07 19:50:30 <satacker[m]> And if the concern here is the kernel then I guess it's built with appropriate configuration
May 07 19:51:36 <satacker[m]> https://elinux.org/Building_BBB_Kernel
May 07 19:54:11 <satacker[m]> https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967#BeagleBoneBlack-Bootloader:U-Boot
May 07 20:00:24 <DhruvaG2000[m]> Okay thanks satacker will go through
May 07 22:10:48 <vedant16[m]> you can find it in proc/device-tree/model
**** ENDING LOGGING AT Sat May 08 02:59:57 2021