Войти в систему

Home
    - Создать дневник
    - Написать в дневник
       - Подробный режим

LJ.Rossia.org
    - Новости сайта
    - Общие настройки
    - Sitemap
    - Оплата
    - ljr-fif

Редактировать...
    - Настройки
    - Список друзей
    - Дневник
    - Картинки
    - Пароль
    - Вид дневника

Сообщества

Настроить S2

Помощь
    - Забыли пароль?
    - FAQ
    - Тех. поддержка



Пишет LWN.net ([info]syn_lwnheadline)
@ 2018-11-14 18:56:00


Previous Entry  Add to memories!  Tell a Friend!  Next Entry
[$] Device-tree schemas
Device trees have become ubiquitous in recent years as a way of
describing the hardware layout of non-discoverable systems, such as many
ARM-based devices. The device-tree bindings define how a particular
piece of hardware is described in a device tree. Drivers then implement
those bindings. The device-tree documentation shows how to use the
bindings to describe systems: which properties are available and which values
they may have. In theory, the bindings, drivers and documentation should be
consistent with each other. In practice, they are often not consistent and,
even when they are, using those bindings correctly in actual device trees
is not a trivial task. As a result, developers have
been considering formal validation for device-tree files for years.
Recently, Rob Herring proposed
a move to a more structured documentation format for device-tree bindings
using JSON Schema to allow automated
validation.


(Читать комментарии) (Добавить комментарий)