Lines Matching refs:bootdev
13 - bootdev - a device which can hold or access a distro (e.g. MMC, Ethernet)
14 - bootmeth - a method to scan a bootdev to find bootflows (e.g. distro boot)
69 job of bootdev. A bootdev is simply a layer on top of a media device (such as
70 MMC, NVMe). The bootdev accesses the device, including partitions and
73 For example, an MMC bootdev provides access to the individual partitions on the
78 attached via USB. To deal with this, each bootdev has an associated 'hunter'
80 bootdev scans the SCSI bus looking for devices, creating a bootdev for each
99 Note that some bootmeths are 'global', meaning that they select the bootdev
112 while (get next bootdev)
129 above bootdev scanning.
160 bootmeths are tried on each bootdev. If the variable is empty, the default
171 The bootdev uclass provides an simple API call to obtain a bootflows from a
177 This takes a iterator which indicates the bootdev, partition and bootmeth to
178 use. It returns a bootflow. This is the core of the bootdev implementation. The
179 bootdev drivers that implement this differ depending on the media they are
193 A bootdev driver is typically fairly simple. Here is one for mmc::
208 { .compatible = "u-boot,bootdev-mmc" },
222 block device and calls a bootdev helper function to do the rest. The
228 Each bootdev has a priority, which indicates the order in which it is used,
296 A bootdev device is a child of the media device. In this example, you can see
297 that the bootdev is a sibling of the block device and both are children of
302 bootdev 0 [ ] mmc_bootdev | | `-- mmc@7e202000.bootdev
305 bootdev 1 [ ] mmc_bootdev | | `-- sdhci@7e300000.bootdev
307 The bootdev device is typically created automatically in the media uclass'
314 return log_msg_ret("bootdev", ret);
321 return log_msg_ret("bootdev", ret);
324 Here, `eth_bootdev` is the name of the Ethernet bootdev driver and `dev`
359 If a bootdev is complicated or needs configuration information, it can be
361 bootdev which reads a bootflow from SPI flash. The devicetree fragment might
370 bootdev {
371 compatible = "u-boot,sf-bootdev";
378 The `sf-bootdev` driver can implement a way to read from the SPI flash, using
422 `bootdev`
424 getting information about it. See :doc:`../usage/cmd/bootdev`
475 those bootdevs. So, all up, we need a single bootstd device, one or more bootdev
487 in a valid bootflow, whether to iterate through just a single bootdev, etc.
491 - When `dev` is provided, then a single bootdev is scanned. In this case,
495 - Otherwise, when `label` is provided, then a single label or named bootdev is
499 - If `label` indicates a numeric bootdev number (e.g. "2") then
500 `BOOTFLOW_METHF_SINGLE_DEV` is set. In this case, moving to the next bootdev
503 `BOOTFLOWIF_SINGLE_MEDIA` is set. In this case, moving to the next bootdev
511 through `boot_targets` environment variable (or `bootdev-order` device tree
521 bootdev and disturb the original ordering.
541 bootdev.
565 bootdev part method
581 table on that bootdev, `max_part` can be updated during the iteration to a
583 exceeds its maximum, then the next bootdev is used. In this way, iter_incr()
594 bootdev part method notes
612 Note that the value in the `bootdev` column above is not actually stored - it is
614 whether to move to the next bootdev in the uclass, the next child of the media
630 to the next partition, or bootdev, for example. The special values
632 `BF_NO_MORE_PARTS` it knows that it should immediately move to the next bootdev.
643 method `bootdev_get_bootflow()` to ask the bootdev to return a bootflow. It
644 passes the iterator to the bootdev method, so that function knows what we are
646 with just the `method` and `dev` intiialised. But the bootdev may fill in more,
651 Based on what the bootdev or bootmeth responds with, `bootflow_check()` either
658 be generated from a particular iteration, or not, rests with the bootdev (or
661 Going down a level, what does the bootdev do in its `get_bootflow()` method?
662 Let us consider the MMC bootdev. In that case the call to
664 parent device of the bootdev, i.e. the `UCLASS_MMC` device itself, then finds
667 bootdev that is based on a media device.
669 The `bootdev_find_in_blk()` helper is implemented in the bootdev uclass. It
732 currently selected bootdev and bootflow (for use by commands). This is in
735 Each bootdev device has its own `struct bootdev_uc_plat` which holds a
755 - add bootdev drivers for dhcp, sata, scsi, ide, virtio