DOCSLIB.ORG

VISUALIZATION of GRAPHIC INFORMATION in the GENERAL-PURPOSE OPERATING SYSTEMS Konstantin V

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VISUALIZATION of GRAPHIC INFORMATION in the GENERAL-PURPOSE OPERATING SYSTEMS Konstantin V INFORMATION TECHNOLOGIES 217 VISUALIZATION OF GRAPHIC INFORMATION IN THE GENERAL-PURPOSE OPERATING SYSTEMS Konstantin V. Pugin, Kirill A. Mamrosenko, Alexander M. Giatsintov Scientific Research Institute of System Analysis of the RAS, Center of Visualization and Satellite Information Technologies, https://niisi.ru Moscow 117218, Russian Federation [email protected], [email protected], [email protected] Abstract. Article describes solutions for developing programs for interaction between Linux operating system and display controller. Operating system architecture encourages creating a driver — component, which task is to perform interaction of hardware controller and OS kernel with the use of many protocols. The development of drivers for the open source OS is difficult due to continuous changes in the structure of the kernel, which breaks backward compatibility frequently. Several approaches to display controller driver development are provided in the article. Basic concepts of these drivers include Kernel Mode Setting (or KMS), meant to provide driver in the kernel and User Mode Setting, meant to provide driver in graphical server. Specific way is used for develop Linux kernel drivers - it is half-procedural, and half-object oriented. Sometimes it is called as “OOP in C”, because it is based on GNU C Language extensions usage to simulate object-oriented techniques. GNU C usage almost prevents using non-GNU compilers to build a driver. Newest concept of writing display controller driver for Linux kernel is based upon atomic mode setting concept, in modern Linux it is achieved via state concept - intermediate states of an object are stored and modified without side effects to other objects. In order to make this concept work, driver should conform to the principle “disable function undoes all effects of enable and nothing more”. Several approaches for display driver development are provided in this article, and most modern method – atomic KMS mode setting, - is described in detail. Keywords: drivers, embedded, KMS, kernel module, development UDC 004.454 Bibliography - 11 references Received 23.01.2019, accepted 05.02.2019 RENSIT, 2019, 11(2):217-224 DOI: 10.17725/rensit.2019.11.217 CONTENTS 1. INTRODUCTION 1. INTRODUCTION (217) Currently, due to the increase in the share 2. COMPONENTS OF THE GRAPHIC SYSTEM of various wearable and embedded systems, (218) it is a relevant objective to develop drivers 3. LINUX GRAPHIC SYSTEMS AND DRIVERS for them. Many embedded systems use the (2182) Linux OS, which has the support of a large 4. KERNEL MODE SETTING AND USER MODE number of processor architectures, as well SETTING. HISTORicAL BAckgROUND (219) as the support of loadable modules, which 5. OBJECT MODEL OF THE LINUX KERNEL allows the process of adding a driver to be (220) greatly simplified. 6. KMS ATOMIC DROVERS. BASIC ENTITIES On many Linux-based embedded systems, AND INTERFACES NECESSARY FOR displaying information has its own specifics. IMPLEMENTATION (221) Often, a certain embedded system requires 7. DEBUGGING DRIVER (222) the development of specialized drivers for 8. CONCLUSION (223) the applicable display controller. REFERENCES (223) RENSIT | 2019 | Vol. 11 | No.2 218 KONSTANTIN V. PUGIN, KIRILL A.MAMROSENKO, ALEXANDER M. GIATSINTOV INFORMATION TECHNOLOGIES When developing a display controller interacting with video capture devices, driver based on the Linux operating system, and specialized random access memory it is necessary to take into account a number (Graphics Double Data Rate, GDDR) of aspects related to the kernel development for use by the graphic accelerator. style, development patterns, and rapid This list of components is not mandatory, changes in the kernel interaction interface since there are graphic subsystems in which (API). There are also few documents on one or more components are missing or not the development of open-source display involved. For example, in some NVIDIA controller drivers, and are mainly limited to Optimus solutions installed in laptops, the extracts from comments in the source code on-screen display controller is not involved, files of the Linux kernel, or schemes based the entire configuration of monitor modes on them. This article will look at a modern occurs through the controller of another approach to writing a display controller driver graphics card - Intel. Only a graphics for the Linux OS. accelerator is used from NVIDIA. You can also find systems with a different combination 2. COMPONENTS OF THE of selected components of the graphics GRAPHIC SYSTEM system. Due to the need for 3D rendering, high- intensity calculation of shaders, high- 3. LINUX GRAPHIC SYSTEMS AND resolution video processing and other DRIVERS requirements of a modern user of computer The graphic system in Linux is represented systems, the PC graphic subsystem has by a graphic stack and various libraries used become significantly more complicated in in it (Fig. 1) [2]. comparison with it in the early years, and If we consider the components of the most often a modern graphic system includes Linux graphical stack from top to bottom, [1]: we can say that the vast majority of them 1. A Graphic accelerator (Graphics are designed to interact with the GPU, in Processing Unit, GPU). It is its particular: most of the Wayland and libdrm, performance that is mainly measured by fully EGL and almost completely X. Only tests and various prototype software (for a small part of DDX. (Device Dependent example, by startup of 3D applications X) (Fig. 1.) and Wayland, as well as libgbm at maximum settings or specially created interacts with the on-screen display controller. scenes), it runs the shaders using a specialized multi-threaded architecture. 2. The display controller. This part of the graphics subsystem is used to determine the modes of graphics displaying, as well as to interact with monitors (obtaining available monitor resolutions, sending a finished frame, etc.). 3. You can also find specialized chips in the graphic system for video output, for Fig. 1. Graphic stack Linux. No. 2 | Vol. 11 | 2019 | RENSIT VISUALIZATION OF GRAPHIC INFORMATION IN 219 INFORMATION TECHNOLOGIES GENERAL-PURPOSE OPERATING SYSTEMS 4.KERNEL MODE SETTING power management, and deleting the old AND USER MODE SETTING. code of the frame buffer drivers (in the era HISTORICAL BACKGROUND of tables and VBE (and for some drivers Initially, there was only user mode setting, even now), the kernel also contained a which was produced in the DDX drivers frame buffer management subsystem, which and enabled to set the mode for displaying allowed graphic output to be used without graphical information. [3] The detemination loading the graphic server for displaying was often executed through mode tables, console messages, or for drawing console and was not extensible, or it was done using programs). algorithms within a code that were unique to The first version of the KMS protocol [5] each chip. There was also a solution such as was built on the XRandR 1.2 model, which VBE (Vesa BIOS Extensions), an extension was good enough at that time to install modes for IBM PC BIOS, which allowed for some on ordinary workstations. But with the advent limited operations of installing modes with of mobile devices, the capabilities of the first its use (without writing a direct algorithm KMS specification began to be insufficient - for interacting with the graphics subsystem). in order to reduce energy consumption, the Gradually, most drivers for IBM PCs concept of unified planes was developed, switched to VBE. But VBE had some serious which was used to display video on a certain downsides: screen, to activate the hardware cursor (in the • Lack of support for multiple CRT first versions of KMS, the hardware cursor controllers (in most cases it is necessary interacted with the screen mode controller to support output from multiple graphic according to a separate protocol), and for accelerators to several displays or output other such cases. to TV). Then support for other KMS objects • Problems if there were several different was added, which allowed the gamma of the outputs (and they could be different on displayed output to be changed, the displayed the same chip series). image to be rotated directly in the driver, and • Problems of use of several different so on [6]. timers. There is one problem with all of this - for To solve these problems in 2008, an the interaction of these subsystems with the extension was accepted to the kernel [4], kernel, a large number of ioctl was required. which provided support for setting modes And when trying to interact, each device inside the kernel (kernel mode setting, or had to check every ioctl, which was very KMS). Along with the problems that this inconvenient. extension brought (such as some decrease in Due to these KMS problems on mobile the stability of the kernel due to the fact that devices, Google has developed its own the drivers are written not very properly, as interface to set modes, the Android Atomic well as the expansion of the kernel because Display Framework (ADF), for the Linux it includes many graphic drivers), there were kernel as part of the Android OS [7]. also some advantages, such as simplified Despite many advantages (atomic update debugging (because there is the entire mode of layers, ease of new drivers’ development), tuning code inside the kernel), simplified ADF had the following disadvantages: RENSIT | 2019 | Vol. 11 | No.2 220 KONSTANTIN V. PUGIN, KIRILL A.MAMROSENKO, ALEXANDER M. GIATSINTOV INFORMATION TECHNOLOGIES • There is only one update queue, and, This is how KMS introduced the concept therefore, the support of multi-screen of atomic updates. The modern driver of modes is very poor. If there were 2 the display controller must be written in the displays with different update rates, the kernel space using this concept. update rate was led to the same (most 5. OBJECT MODEL OF THE LINUX often less) one, which resulted in either KERNEL jerking at a faster display or slowing down To write a driver in kernel space, it is necessary at a slower one.
Load more

Recommended publications
  • Ati Driver Freebsd
    Ati driver freebsd Hey, I`m new to teh the bsd *BSD world and just installed Freebsd FreeBSD. Only thing missing is my video driver. ATI Radeon X How to Solved - Switch between ATI and VESA drivers? If you want to automatically load a video driver at boot time, we recommend to do it from /etc/:Radeon​: ​ It allows the use of newer xfvideo-ati drivers and AMD GPUs. This project started in January Initial radeon code comes from Linux. EndSection DESCRIPTION radeon is an Xorg driver for ATI/AMD RADEON-based video cards with the following features: o Full support for 8-, , and. This package contains the xfvideo-ati driver. xdrivers/drm-kmod: Port for the DRM kernel drivers for FreeBSD This port. If I boot X11 with no or with ati driver, the system stops responding, although cursor continues to follow mouse movements. (I suppose. To all those concerned, I have read that FreeBSD would be supported by the latest graphic card drivers, which was also confirmed by. I bought an expensive ATI card when they announced they'll go Note that AMD doesn't provide a driver for FreeBSD, so you'll be using the. We now know for sure that FreeBSD will ship with a kernel mode-setting driver for supporting open-source AMD Radeon graphics with its. AMD tech support has allegedly confirmed that Catalyst is being ported to FreeBSD. A Phoronix reader pointed out this thread. I am not sure that FreeBSD will fully support this card. The Xorg version for FreeBSD is and the ATI driver used is version The reason is, AMD/ATI doesn't support FreeBSD, and you have to resort to the sucky open source drivers.
    [Show full text]
  • A Simplified Graphics System Based on Direct Rendering Manager System
    J. lnf. Commun. Converg. Eng. 16(2): 125-129, Jun. 2018 Regular paper A Simplified Graphics System Based on Direct Rendering Manager System Nakhoon Baek* , Member, KIICE School of Computer Science and Engineering, Kyungpook National University, Daegu 41566, Korea Abstract In the field of computer graphics, rendering speed is one of the most important factors. Contemporary rendering is performed using 3D graphics systems with windowing system support. Since typical graphics systems, including OpenGL and the DirectX library, focus on the variety of graphics rendering features, the rendering process itself consists of many complicated operations. In contrast, early computer systems used direct manipulation of computer graphics hardware, and achieved simple and efficient graphics handling operations. We suggest an alternative method of accelerated 2D and 3D graphics output, based on directly accessing modern GPU hardware using the direct rendering manager (DRM) system. On the basis of this DRM support, we exchange the graphics instructions and graphics data directly, and achieve better performance than full 3D graphics systems. We present a prototype system for providing a set of simple 2D and 3D graphics primitives. Experimental results and their screen shots are included. Index Terms: Direct rendering manager, Efficient handling, Graphics acceleration, Light-weight implementation, Prototype system I. INTRODUCTION Rendering speed is one of the most important factors for 3D graphics application programs. Typical present-day graph- After graphics output devices became publicly available, a ics programs need to be able to handle very large quantities large number of graphics applications were developed for a of graphics data. The larger the data size, and the more sen- broad spectrum of uses including computer animations, com- sitive to the rendering speed, the better the speed-up that can puter games, user experiences, and human-computer inter- be achieved, even for minor aspects of the graphics pipeline.
    [Show full text]
  • Porting X Windows System to Operating System Compliant with Portable Operating System Interface
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 11, No. 7, 2020 Porting X Windows System to Operating System Compliant with Portable Operating System Interface Andrey V. Zhadchenko1, Kirill A. Mamrosenko2, Alexander M. Giatsintov3 Center of Visualization and Satellite Information Technologies Scientific Research Institute of System Analysis Moscow, Russia Abstract—Now-a-days graphical interface is very important separated process contexts [4]. Current graphical subsystem for any operating system, even the embedded ones. Adopting is server-client X windows system implementation named existing solutions will be much easier than developing your XFree86 with version 4.8.0. Although XFree86 [5] supports up own. Moreover, a lot of software may be reused in this case. to the X11R6.6 protocol version, which is barely enough to run This article is devoted to X Window System adaptation for modern applications, absence of many important extensions, Portable Operating System Interface (POSIX) compliant real- for example, Xrender [6], implies heavy limits upon software. time operating system Baget. Many encountered problems come from the tight connection between X and Linux, therefore it is expected to encounter these issues during usage of X on non- Nowadays existing free software solutions in display Linux systems. Discussed problems include, but not limited to servers for operating systems are limited to two options: X the absence of dlopen, irregular file paths, specific device drivers. Windows System and Wayland [7]. However, there is a big Instructions and recommendations to solve these issues are given. ideological difference between them. X started it’s history a A comparison between XFree86 and Xorg implementations of X long time ago in the ’80s and was developed as an all-around is discussed.
    [Show full text]
  • ECS2100 Series CLI Reference Guide
    ECS2100-10T/PE/P ECS2100-28T/P/PP 10/28-Port Web-smart Pro Gigabit Ethernet Switch CLI Reference Guide Software Release v1.2.2.15 www.edge-core.com CLI Reference Guide ECS2100-10T Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 8 10/100/1000BASE-T (RJ-45) Ports and 2 Gigabit SFP Ports ECS2100-10PE Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 8 10/100/1000BASE-T (RJ-45) 802.3 af/at PoE Ports with 2 Gigabit SFP Ports (PoE Power Budget: 65W) ECS2100-10P Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 8 10/100/1000BASE-T (RJ-45) 802.3 af/at PoE Ports and 2 Gigabit SFP Ports (PoE Power Budget: 125 W) ECS2100-28T Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 24 10/100/1000BASE-T (RJ-45) Ports and 4 Gigabit SFP Ports ECS2100-28P Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 24 10/100/1000BASE-T (RJ-45) 802.3 af/at PoE Ports and 4 Gigabit SFP Ports (PoE Power Budget: 200 W) ECS2100-28PP Gigabit Ethernet Switch Web-smart Pro Gigabit Ethernet Switch with 24 10/100/1000BASE-T (RJ-45) 802.3 af/at PoE Ports and 4 Gigabit SFP Ports (PoE Power Budget: 370 W, can extend to 740 W) E012019-CS-R05 How to Use This Guide This guide includes detailed information on the switch software, including how to operate and use the management functions of the switch. To deploy this switch effectively and ensure trouble-free operation, you should first read the relevant sections in this guide so that you are familiar with all of its software features.
    [Show full text]
  • Zynq Ultrascale+ Mpsoc TRD User Guide (UG1221)
    Zynq UltraScale+ MPSoC Base Targeted Reference Design User Guide UG1221 (v2016.4) March 22, 2017 Revision History The following table shows the revision history for this document. Date Version Revision 03/22/2017 2016.4 Released with Vivado Design Suite 2016.4 with no changes from previous version. 12/15/2016 2016.3 Updated for Vivado Design Suite 2016.3: Updated Reference Design Overview. Replaced Chapter 2, Reference Design. Updated Figure 3-1 and the following paragraph. Updated Figure 4-1 and perfapm library descriptions in Chapter 4, RPU-1 Software Stack (Bare-metal). Updated Figure 6-1, Figure 6-2, and DDR region descriptions under Memories in Chapter 6. Updated Figure 7-1, Figure 7-4, and Figure 7-5. Added X11 section, deleted first paragraph under EGLFS QPA, and modified “Evdev” section to “Libinput” in Chapter 7, APU Software Platform. Updated Table 8-2 and clock descriptions under Clocks, Resets and Interrupts in Chapter 8. 07/22/2016 2016.2 Updated for Vivado Design Suite 2016.2: Added “GPU” to hardware interfaces and IP under Key Features. Changed link under Design Modules from the wiki site to the HeadStart Lounge and updated link under Tutorials to the Base TRD wiki site. Deleted steps 2 and 4 under Tutorials and added reference tutorial (last bullet). Added second to last sentence to second paragraph under Boot Process. Added “Load PMU FW” component to Figure 6-1. Clarified Message Passing section (text only). Changed “PCA9546” to PCA9548” in Figure 8-7. 06/29/2016 2016.1 Initial Xilinx release. Zynq UltraScale+ MPSoC Base TRD www.xilinx.com Send Feedback 2 UG1221 (v2016.4) March 22, 2017 Table of Contents Revision History .
    [Show full text]
  • GPU Scheduling for Real-Time Multi-Tasking Environments
    TimeGraph: GPU Scheduling for Real-Time Multi-Tasking Environments Shinpei Kato† ‡, Karthik Lakshmanan†, and Ragunathan (Raj) Rajkumar†, Yutaka Ishikawa‡ † Department of Electrical and Computer Engineering, Carnegie Mellon University ‡ Department of Computer Science, The University of Tokyo Abstract transition. Especially recent trends on 3-D browser and desktop applications, such as SpaceTime, Web3D, 3D- The Graphics Processing Unit (GPU) is now commonly Desktop, Compiz Fusion, BumpTop, Cooliris, and Win- used for graphics and data-parallel computing. As more dows Aero, are all intriguing possibilities for future user and more applications tend to accelerate on the GPU in interfaces. GPUs are also leveraged in various domains multi-tasking environments where multiple tasks access of general-purpose GPU (GPGPU) processing to facili- the GPU concurrently, operating systems must provide tate data-parallel compute-intensive applications. prioritization and isolation capabilities in GPU resource Real-time multi-tasking support is a key requirement management, particularly in real-time setups. for such emerging GPU applications. For example, users We present TimeGraph, a real-time GPU scheduler could launch multiple GPU applications concurrently in at the device-driver level for protecting important GPU their desktop computers, including games, video play- workloads from performance interference. TimeGraph ers, web browsers, and live messengers, sharing the same adopts a new event-driven model that synchronizes the GPU. In such a case, quality-aware soft real-time ap- GPU with the CPU to monitor GPU commands issued plications like games and video players should be pri- from the user space and control GPU resource usage in oritized over live messengers and any other applications a responsive manner.
    [Show full text]
  • Integrating Virtual DRM Between VISION SDK and PSDK on Jacinto6 SOC
    www.ti.com Table of Contents Application Report Integrating Virtual DRM Between VISION SDK and PSDK on Jacinto6 SOC Fredy Zhang, Joe Shen, and Peter Li ABSTRACT The Direct Rendering Manager (DRM) is widely used by user-space graphic stacks. In a setup where A15 is not allowed to access DSS, a working omapdrm driver is not available to display content. Virtual DRM is a driver framework to expose DRM devices to Linux® userspace in such a setup, therefore, enabling Linux DRM applications to continue functioning. Project collateral and source code discussed in this document can be downloaded from the following URL: https://www.ti.com/lit/zip/spracx5. Table of Contents 1 Introduction.............................................................................................................................................................................2 1.1 Standard DRM Framework................................................................................................................................................ 3 1.2 vDRM-Based Framework...................................................................................................................................................3 2 Display Content Based vDRM on Linux................................................................................................................................4 3 Multimedia Support Based vDRM on Linux......................................................................................................................... 4 3.1 Gstreamer.........................................................................................................................................................................
    [Show full text]
  • Freebsd 10 - Powerful Virtualization Solutions Freebsd 10 - ARM-Ready Freebsd 10 - Modern Hardware Support
    FreeBSD 10 - Powerful Virtualization Solutions FreeBSD 10 - ARM-Ready FreeBSD 10 - Modern Hardware Support FreeBSD pioneered operating system-level virtualization FreeBSD continues to improve its support for the ARM New console driver, vt(4), provides multiple virtual terminals with the Jail facility in 2000. This early innovation in family of processors, including support for ARMv6 and with an extensive feature set. It includes support for UTF-8, virtualization forged a path for similar technologies such ARMv7, SMP, and thread-local storage (TLS). double-wide characters, Asian character sets, graphics-mode as Solaris Zones (2005) and Linux Containers/Docker Supported processors include: consoles, and integration with Kernel Mode Setting (KMS) video (2014). drivers for switching between the X Window System and virtual • CHROMEBOOK (Samsung Exynos 5250) FreeBSD 10 includes several virtualization technologies, terminals.* providing users with greater flexibility for provisioning a • COLIBRI (Freescale Vybrid) virtualized solution that matches their workflow. These FreeBSD 10 adds Unified Extensible Firmware Interface (UEFI) solutions include: • COSMIC (Freescale Vybrid) boot loader support. The root file system may be UFS or ZFS, and the loader supports multiple ZFS boot environments * • The BSD Hypervisor, bhyve(8). This Type-2 hypervisor supports • Genesi Efika MX SmartBook and SmartTop (Freescale a number of guests, including FreeBSD, OpenBSD, NetBSD and i.MX515)* The Open Fabrics Enterprise Distribution (OFED) and OFED Infiniband core version provides parity with Linux, including many Linux® distributions. Combining bhyve and ZFS volumes • IMX53-QSB (Freescale i.MX53) enables powerful capabilities in provisioning, snapshotting and Mellanox drivers for 56Gb Infiniband. rolling back virtual machines. • QUARTZ (Freescale Vybrid) The nvme(4) driver provides NVM Express support.
    [Show full text]
  • Release Notes for X11R7.6 the X.Org Foundation [ November 2010
    Release Notes for X11R7.6 The X.Org Foundation [http://www.x.org/wiki/XorgFoundation] November 2010 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R7.6 release. Table of Contents Introduction to the X11R7.6 Release ...................................................................................... 1 Summary of new features in X11R7.6 .................................................................................... 2 Overview of X11R7.6 ......................................................................................................... 3 Details of X11R7.6 components ............................................................................................ 3 Video Drivers ............................................................................................................ 3 Input Drivers ............................................................................................................. 5 Xorg server ............................................................................................................... 5 Font support .............................................................................................................. 8 Build changes and issues ..................................................................................................... 8 Silent build rules ........................................................................................................ 8 New configure options for font modules ........................................................................
    [Show full text]
  • A Brief Overview of DRM/KMS and Its Status in Netbsd
    A brief overview of DRM/KMS and its status in NetBSD Taylor `Riastradh' Campbell [email protected] [email protected] AsiaBSDcon 2015 Tokyo, Japan March 13, 2015 No, not that DRM! I DRM: Direct rendering manager: Linux kernel interface for commanding GPU to render directly into framebuffer for display. I Originally, DRM was only a kernel interface for mapping graphics card MMIO registers and waiting for vertical blank interrupts. I Actual driver for display lived in userland: used DRM to disable kernel's idea of VGA console and grant exclusive access to display registers to X server, peeked and poked them in userland to detect and configure displays. I Userland used legacy /dev/agp device to allocate physical memory for graphics and program it into the GPU's page tables. DRM/KMS: DRM with a real kernel display driver I Maybe userland shouldn't be mapping the device's MMIO registers, handling mode-setting, etc.: `user mode-setting', or UMS. I Would be nice if kernel could suspend/resume display without X's help. I DRM/KMS: DRM with kernel mode-setting. GEM and TTM: Graphics buffer management I GEM: Graphics Extent Manager I TTM: Texture and Tiling Manager I Fancy names for two different sets of ioctls to manage swappable buffers shared by CPU and GPU. DRM portability I DRM implementation maintained in Linux. I Used to be a coordinated porting effort to BSDs. I Lost coordination in switch from UMS to KMS. I New ports to *BSD all different now! I NetBSD: shims to make most Linux code run unmodified and updates less painful.
    [Show full text]
  • Development Tools on Freebsd
    FOR NOVICE AND ADVANCED USERS Development tools on FreeBSD Experimenting with XEN Model View Whatever Introduction to origins NetBSD 10 Things Your CIO Should Know About TrueNAS Vol. 09 No. 11 ISSUE 75 1898-9144 1 2 EDITORS’ WORD Dear Readers, I know that many of you don’t celebrate Christmas, so I will not wish you Merry Christmas. But I hope that for all of you, December and the end of the year will be a wonderful time, no matter where you come from, which language you speak or what your beliefs are. I also know that you have been waiting for more FreeBSD re- Editor in Chief: lated articles. So, here they are. Marta Ziemianowicz Great, as always, David Carlier will introduce you to Develop- ment Tools on FreeBSD. If you would like to switch from Linux [email protected] to FreeBSD, this article is definitely for you. Contributing: The next article is an introduction to NetBSD. Siju Oommen David Carlier, Siju Oommen, Damian Czernous, Michael Boelem, Valerie George wrote a guide for you that is another must read for all Heatley, Mark VonFange, Roger Pau Monne and Rob Somerville. beginners, but I hope that professionals and old timers will like it as well. Top Betatesters & Proofreaders: After BSD, it is time for something new. Say “Hi” to Damian Annie Zhang, Denise Ebery, Eric Geissinger, Luca Ferrari, Imad Soltani, Czernous and the origins of Model View Whatever. Not really Olaoluwa Omokanwaye, Radjis Mahangoe, Mani Kanth, Ben Milman, Mark VonFange and David Carlier related to Open Source? Maybe it will be useful for some of you anyway and will broaden your horizons.
    [Show full text]
  • Release Notes for X11R7.6 the X.Org Foundation [ December 2010
    Release Notes for X11R7.6 The X.Org Foundation [http://www.x.org/wiki/XorgFoundation] December 2010 Abstract These release notes contain information about features and their status in the X.Org Foun- dation X11R7.6 release. Table of Contents Dedication .............................................................................................................. 1 Introduction to the X11R7.6 Release .................................................................... 1 Summary of new features in X11R7.6 .................................................................. 2 Overview of X11R7.6 ............................................................................................. 3 Details of X11R7.6 components ............................................................................ 4 Video Drivers ................................................................................................. 4 Input Drivers .................................................................................................. 6 Xorg server .................................................................................................... 6 Font support ................................................................................................... 9 Build changes and issues .................................................................................... 10 Silent build rules ......................................................................................... 10 New configure options for font modules ....................................................
    [Show full text]