home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.development      Operating system development chatter      4,255 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,483 of 4,255   
   mutazilah@gmail.com to Joe Monk   
   Re: drivers   
   10 Jul 21 04:44:09   
   
   From: muta...@gmail.com   
      
   On Saturday, July 10, 2021 at 9:08:47 PM UTC+10, Joe Monk wrote:   
      
   > > I don't know if plugging in a USB device causes an interrupt,   
   > > but if it does, the BIOS/UEFI gets control and does its stuff,   
   > > and then informs the OS via an agreed interrupt that the OS   
   > > hooked in to that there is a new device available?   
      
   > The OS comes first in the interrupt chain, not the hardware.   
   > The OS will trap the interrupt, especially in PM.   
      
   That is a choice of the OS. It's also a choice to directly   
   manipulate I/O ports.   
      
   I'm asking why there can't be some default computer-provided   
   device handler, just like there already is for serial ports. Yes,   
   the OS can bypass INT 14H. But if it doesn't, the computer   
   should be able to handle that particular device, and the OS   
   can choose to make use of it. Why not all devices? Especially   
   Bluetooth when it isn't even plugged in to a USB port.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca