Difference between Maskable and NonMaskable Interrupts

-
Maskable Interrupt: An Interrupt that can be disabled or ignored by the instructions of CPU are called as Maskable Interrupt.
Eg: RST6.5,RST7.5,RST5.5 OF 8085 are maskable Interrupts.


Non-Maskable Interrupt: An interrupt that cannot be disabled or ignored by the instructions of CPU are called as Non-Maskable Interrupt.
Eg:Trap of 8085

Comments

  1. Unknown20 December 2016 at 08:34

    Good difference

    ReplyDelete
  2. Unknown12 June 2017 at 12:43

    Thank you mr Guru!!!you have made things clear and easy to understand

    ReplyDelete
  3. Unknown8 August 2017 at 23:40

    Thenku sir. Me rely enjoying this blog. U explain it very easy.

    ReplyDelete
  4. Navdeep Sharma8 April 2018 at 07:12

    Sir please fully interpret to this topic. This is not enough.

    ReplyDelete
  5. Unknown11 May 2018 at 21:55

    This comment has been removed by the author.

    ReplyDelete
  6. Unknown26 December 2018 at 10:39

    Wah aur chota kr dete
    1 marks ka question h na ye jaise!!

    ReplyDelete
  7. brajesh singh5 January 2019 at 10:51

    thnks sir ji

    ReplyDelete
  8. Unknown21 January 2019 at 13:26

    Thank you very much!! keep up

    ReplyDelete
  9. Unknown2 February 2019 at 07:55

    I want difference between software and non maskable interrupt

    ReplyDelete
  10. Unknown20 May 2019 at 06:34

    Want more information about this !

    ReplyDelete
  11. Sujash0517 December 2019 at 06:50

    This comment has been removed by the author.

    ReplyDelete
  12. Sujash0517 December 2019 at 06:51

    Want more information about this !

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more