Changes between Version 2 and Version 3 of FlattenedDeviceTree

Timestamp:

Oct 28, 2009, 11:11:30 AM (16 years ago)

Author:

Nicolas Pouillon

Comment:

--

FlattenedDeviceTree

@@ -20 +20 @@
  * The Linux kernel documentation tree contains [http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Documentation/powerpc/booting-without-of.txt;h=79f533f38c6112d64bed9398c44d31cf3b552f6b;hb=HEAD an useful document] about device trees (`Documentation/powerpc/booting-without-of.txt`)
 
-= Implementation and example =
+= Implementation =
 
 In MutekH, FDT is handled through an hardware enumerator device driver, it behaves like the other enumerators (PCI, ISAPnP).
-
-Drivers may export themselves as FDT-aware, and define which device name string to match. For instance, the following subtree defines a tty device:
-
-{{{
-        tty@0 {
-            device_type = "soclib:tty";
-                tty_count = <1>;
-                reg = <0x90600000 0x10>;
-                icudev = &{/icu@0};
-                irq = <1>;
-        };
-}}}
-
-In turn, the SoCLib tty driver declares itself (in source:trunk/mutekh/drivers/device/char/tty-soclib/tty-soclib.c#L146) as:
-
-{{{
-static const struct devenum_ident_s     tty_soclib_ids[] =
-{
-        DEVENUM_FDTNAME_ENTRY("soclib:tty", 0, 0),
-        { 0 }
-};
-
-const struct driver_s   tty_soclib_drv =
-{
-  .class                = device_class_char,
-  .id_table             = tty_soclib_ids,
-  .f_init               = tty_soclib_init,
-  .f_cleanup            = tty_soclib_cleanup,
-  .f_irq                = tty_soclib_irq,
-  .f.chr = {
-    .f_request          = tty_soclib_request,
-  }
-};
-}}}
-
-This will make the FDT enumerator use the correct driver, matching `"soclib:tty"`
 
 = MutekH-Specific Node syntax quick reference =
@@ -148 +112 @@
  `PARAM_DATATYPE_BOOL`::
    a simple boolean, i.e. a property with no value, if present it is true, if absent it is false (like the `cached` attribute in memory nodes)
+
+= Example =
+
+Drivers may export themselves as FDT-aware, and define which device name string to match. For instance, the following subtree defines a tty device:
+
+{{{
+        tty@0 {
+            device_type = "soclib:tty";
+                tty_count = <1>;
+                reg = <0x90600000 0x10>;
+                icudev = &{/icu@0};
+                irq = <1>;
+        };
+}}}
+
+In turn, the SoCLib tty driver declares itself (in source:trunk/mutekh/drivers/device/char/tty-soclib/tty-soclib.c#L146) as:
+
+{{{
+static const struct devenum_ident_s     tty_soclib_ids[] =
+{
+        DEVENUM_FDTNAME_ENTRY("soclib:tty", 0, 0),
+        { 0 }
+};
+
+const struct driver_s   tty_soclib_drv =
+{
+  .class                = device_class_char,
+  .id_table             = tty_soclib_ids,
+  .f_init               = tty_soclib_init,
+  .f_cleanup            = tty_soclib_cleanup,
+  .f_irq                = tty_soclib_irq,
+  .f.chr = {
+    .f_request          = tty_soclib_request,
+  }
+};
+}}}
+
+This will make the FDT enumerator use the correct driver, matching `"soclib:tty"`