The LoongArch architecture is an Instruction Set Architecture (ISA) that has Reduced Instruction Set Computer (RISC) style. The LoongArch Reference Manual is used to explain the LoongArch specification.
LoongArch has the typical characteristics of RISC. LoongArch instructions are of fixed size and have regular instruction formats. Most of the instructions have two source operands and one destination operand. LoongArch is a load-store architecture; this means only the load/store instructions can access memory the operands of the other instructions are within the processor core or the immediate number in the instruction opcode.
LoongArch is divided into two versions, the 32-bit version (LA32) and the 64-bit version (LA64). LA64 applications are “application-level backward binary compatibility” with LA32 applications. That means LA32 applications can run directly on the machine compatible with LA64, but the behavior of system softwares (such as the kernel) on the machine compatible with LA32 is not guaranteed to be the same as on the machine compatible with LA64.
LoongArch is composed of a basic part (Loongson Base) and an expanded part, as shown in the figure. The expansion part includes Loongson Binary Translation (LBT), Loongson VirtualiZation (LVZ), Loongson SIMD EXtension (LSX), and Loongson Advanced SIMD EXtension(LASX).
License: CC BY-NC-ND v4.0 International
HTTP encodings, headers, media types, methods, relations and status codes, all summarized and linking to their specification.
VIM has all features of a modern programmer's editor - macro language, syntax highlighting, customizable user interface, easy integration with various IDEs plus a set of features which makes VIM so attractive to its users: crash recovery, automatic commands, session management. I started this tutorial for one simple reason - I like regular expressions. Nothing compares to the satisfaction from a well-crafted regexp which does exactly what you wanted it to do :-).
Documentation and the Verilog model of the Soviet microprocessor 1801VM1 (also VM2 and VM3).
This site is dedicated to cataloging and sharing information on repairing devices. It's named "Caps" wiki because in older electronics capacitors are one of the more common causes of problems. But any repair information such as ICs, batteries, belts, 3D printer models, or more for devices of any age is welcome here!
This site is designed to provide background info on ChromeOS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your ChromeOS device, you've come to the right place.
It's also the home of the ChromeOS Firmware Utility Script and Kodi E-Z Setup Script, which simplify and automate many of the tasks required to run an alternate OS and/or Kodi Media Center on your Chromebook/Chromebox.
Area 50 is a collection of unusual, difficult, or simply lightly documented projects. Much of the information in Area 50 is intended for experienced hobbyists - not beginners. The information may be incomplete or even incorrect and readers are assumed to have sufficient knowledge of the areas covered to evaluate the suitability and veracity of the information. Many projects will have kernels of information that are useful for other purposes and those will be mentioned at the end of the page.
The Internet Archive Manual Library is a collection of manuals, instructions, walkthroughs and datasheets for a massive spectrum of items. Manuals covering electronic and mechanical products, instructions on mixing or blending items, and instruction sets for software and computer items are all included.
Having the manual for an item can mean the difference between that item being useful (and therefore not immediately junked) and being forgotten, or replaced with similar products. They also give insight into the intentions and goals of the companies making these products, as well as avenues of troubleshooting and repair.
A database of motherboards, BIOS images, chipsets, manufacturers, drivers, software. If you have an ancient PC and you're trying to figure it out, check here first.
This is an in-depth guide to the different elements of the Pebble code language. It is set up to be a reference more than a tutorial, so if you are just starting out, you might want to go through the welcome document first. (This is the first file that loads when you start Pebble.) Or you could try out one of the demo files, by typing demo1, demo2, or demo3 into the File bar and pressing Load. You can also enter help to access this guide in-program, or use ref to get the quick-reference guide. The default soundpack is sounds which you can import (IMP sounds) to access many basic sounds, or you can load it directly to scope out how they are created.
The Pebble code language is modular, which means that all the sounds, instruments, and patterns are created by combining and arranging different modules, each of which typically performs a simple function (like addition, or changing volume).
Official documentation for the Kraken SDR.
Rc is a command interpreter for Plan 9 that provides similar facilities to UNIX’s Bourne shell, with some small additions and less idiosyncratic syntax. This paper uses numerous examples to describe rc’s features, and contrasts rc with the Bourne shell, a model that many readers will be familiar with.
So you have a Four Thieves Abortion Card, what do you do with it?
First off, if you don't need it now, do not break the seal of the mylar bag. The main vulnerability of Misoprostol is humidity. So, keep it sealed, and out of extreme heat or sunlight.
...
Read and save for later, should you need it.
Construction documentation for the Null 2 Linux-powered handheld console.
Somebody put together a very helpful list of all of the PIC microcontrollers out there, their specifics, and most importantly what their configuration bits (fuses) mean and what the constants map to. For example, MCLRE=off is 0xfdf.
Liquid is a template language created by Shopify. It's available as an open source project on GitHub, and is used by many different software projects and companies.
This reference documents the Liquid tags, filters, and objects that you can use to build Shopify Themes.
Of course, this applies to anything else that uses Liquid as its templating language.
Modern XMPP is an independent project launched to improve the quality of user-to-user messaging applications that use XMPP. XMPP is a mature open standard for internet messaging. If you are reading this, you have probably heard of it.
We are developing a handful of simple documents aimed at people who wish to build on top of XMPP. The recommendations are derived from healthy discussions between developers from multiple XMPP projects and other members of the XMPP community.
Our recommendations highlight only the XEPs you need to implement for a modern messaging application, ignoring historical cruft and excessive backwards-compatibility.
We also intend to provide a comprehensive set of guidelines for UI and UX design. Developing a client was never just about the protocol. In fact in most cases the protocol is a secondary concern. Having a concrete set of guidelines will help to provide a more uniform user experience between different applications, ensuring they use the same terminology, and provide interoperable feature sets.
Github repository for the Kraken SDR.
This software is intended to demonstrate the direction of arrival (DoA) estimation capabilities of the KrakenSDR and other RTL-SDR based coherent receiver systems which use the compatible data acquisition system - HeIMDALL DAQ Firmware.
The complete application is broken down into two main modules in terms of implementation, into the DAQ Subsystem and to the DSP Subsystem. These two modules can operate together either remotely through Ethernet connection or locally on the same host using shared-memory.
Running these two subsystems on separate processing units can grant higher throughput and stability, while running on the same processing unit makes the entire system more compact.
There is a beta Raspbian image available for download that includes all of the necessary software.
Designed with the RasPi 4 specifically in mind.
Documentation for the Kraken SDR is in this repo's wiki.
Also, thankfully, has instructions for installing the software yourself so you're not reliant upon their builds.
This site provides summary information about, and access to, the “public inspection file” (or “public file”) for the following types of entities: licensed full-service radio and television broadcast stations, Class A television stations, cable television systems, direct broadcast satellite (“DBS”) providers, and satellite radio (also referred to as “Satellite Digital Audio Radio Services” or “SDARS”) licensees.
The Commission first adopted rules requiring broadcast stations to keep a public file more than 40 years ago and certain political programming files have been public for nearly 75 years. The public file for broadcast stations contains a variety of information about each station’s operations and service to its community of license, including information about political time sold or given away by each station, quarterly lists of the most significant programs each station aired concerning issues of importance to its community, data on ownership of each station and active applications each station has filed with the Commission. The Commission adopted the public inspection file requirement to "make information to which the public already has a right more readily available, so that the public will be encouraged to play a more active part in dialogue with broadcast licensees."
Cable, DBS, and SDARS entities also have public and political file requirements. These entities’ political file requirements are substantially similar to those of television and radio broadcasters. Apart from the political file, however, cable, DBS, and SDARS entities’ other public file requirements differ somewhat from the public file requirements applicable to broadcasters.