public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Christian Melki <christian.melki@t2data.com>
Cc: u-boot@lists.denx.de
Subject: Re: Hints on how to use efi_driver/efi_block_device.c
Date: Fri, 13 Aug 2021 10:21:02 +0900	[thread overview]
Message-ID: <20210813012102.GA67965@laputa> (raw)
In-Reply-To: <63da56b7-85d2-c39e-2112-9d1296d87aad@t2data.com>

On Thu, Aug 12, 2021 at 04:34:01PM +0200, Christian Melki wrote:
> I was hoping that U-boot would detect BLOCK_IO devices provided by UEFI
> automatically. But I can't see anything attached under lsblk or find some
> other information about this.

I'm not sure what you intend to do here, but please try
the commands, "efidebug devices" and/or "efidebug dh"
to find out what you're looking for.

Please note that you have to enumerate (block) devices
in advance with, say, "mmc rescan", "scsi scan" (and
probably "virtio scan" as well).

-Takahiro Akashi

> For example, Barebox works just fine on both Virtualbox and real hardware in
> this regard.
> 
> Barebox does not have an emmc driver for the real hardware but piggybacks
> off the UEFI protocol for this.
> 
> I'm sure that the idea with this U-boot driver is something like that, but
> would appreciate some hints on how to use it.
> 
> Ie, standard usage. UEFI boots of a drive, posts some handles(?) to a block
> device and U-boot picks it up, not knowing more about the abstracted
> hardware.
> 
> Best regards,
> Christian

      parent reply	other threads:[~2021-08-13  1:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 14:34 Hints on how to use efi_driver/efi_block_device.c Christian Melki
2021-08-12 21:49 ` Simon Glass
2021-08-13  0:36   ` Heinrich Schuchardt
2021-08-13  7:56     ` Christian Melki
2021-08-13 10:02       ` Heinrich Schuchardt
2021-09-08 13:30         ` Simon Glass
2021-08-13  1:21 ` AKASHI Takahiro [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210813012102.GA67965@laputa \
    --to=takahiro.akashi@linaro.org \
    --cc=christian.melki@t2data.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox