(ℹ) Join us now at the IRC channel | ䷉ Find the plain text version at this address (HTTP) or in Gemini (how to use Gemini) with a full GemText version.
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 01:35 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 01:45 | |
| schestowitz[TR] | <li> | Apr 10 05:35 |
|---|---|---|
| schestowitz[TR] | <h5><a href="https://drewdevault.com/2023/04/08/2023-04-08-Drivers-and-mercury.html">Writing Helios drivers in the Mercury driver environment</a></h5> | Apr 10 05:35 |
| schestowitz[TR] | <blockquote> | Apr 10 05:35 |
| schestowitz[TR] | <p>As you may remember from my FOSDEM talk, the Ares operating system is built out of several layers which provide progressively higher-level environments for an operating system. At the bottom is the Helios microkernel, and today we’re going to talk about the second layer: the Mercury environment, which is used for writing and running device drivers in userspace. Let’s take a look at a se | Apr 10 05:35 |
| schestowitz[TR] | rial driver written against Mercury and introduce some of the primitives used by driver authors in the Mercury environment.</p> | Apr 10 05:35 |
| schestowitz[TR] | </blockquote> | Apr 10 05:35 |
| schestowitz[TR] | </li> | Apr 10 05:35 |
| schestowitz[TR] | Apr 10 05:35 | |
| -TechBytesBot/#techbytes-drewdevault.com | Writing Helios drivers in the Mercury driver environment | Apr 10 05:35 | |
| *Noisytoot has quit (Ping timeout: 2m30s) | Apr 10 06:25 | |
| *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes | Apr 10 06:26 | |
| *Noisytoot has quit (Ping timeout: 2m30s) | Apr 10 14:58 | |
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 15:04 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 15:05 | |
| *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes | Apr 10 15:09 | |
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 15:13 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 15:13 | |
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 15:14 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 15:15 | |
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 15:30 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 15:30 | |
| *Noisytoot has quit (Ping timeout: 2m30s) | Apr 10 15:42 | |
| *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes | Apr 10 15:45 | |
| *u-amarsh04 has quit (Quit: Konversation terminated!) | Apr 10 16:08 | |
| *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes | Apr 10 16:08 | |
| schestowitz[TR] | This appears to be going way belong simple use of ... ☞ http://ipkitten.blogspot.com/2023/04/construing-claims-to-include-technical.html?showComment=1681130147875#c1355105711940794574 | Apr 10 17:53 |
| schestowitz[TR] | This appears to be going way belong simple use of the descrption to aid claim interpretation and is an attempt to rely on features that should actually be included in the claims. I don't believe it assists aither side in the argument over amendment of the description to be in accordance with the claims. | Apr 10 17:53 |
| -TechBytesBot/#techbytes-ipkitten.blogspot.com | Construing the claims to include technical effects mentioned in the description (T 1924/20) - The IPKat | Apr 10 17:53 | |
| *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes | Apr 10 23:42 | |
| *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes | Apr 10 23:49 | |
| *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes | Apr 10 23:56 | |
Generated by irclog2html.py 2.6 | ䷉ find the plain text version at this address (HTTP) or in Gemini (how to use Gemini) with a full GemText version.