mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Giorgio Dal Molin <iw3gtf@arcor.de>
To: Oleksij Rempel <linux@rempel-privat.de>, barebox@lists.infradead.org
Subject: Re: barebox on an intel efi system
Date: Wed, 27 Sep 2017 10:28:45 +0200 (CEST)	[thread overview]
Message-ID: <2068226802.92408.1506500925602@mail.vodafone.de> (raw)
In-Reply-To: <40bfec7f-1874-a29e-74c0-44d35e95ca06@rempel-privat.de>

Hi Oleksij,

this was the solution to my problems,

thank you very much.

giorgio

> Oleksij Rempel hat am 27. September 2017 um 09:11 geschrieben:
> 
> Hi,
> 
> you probably need this fix:
> https://git.pengutronix.de/cgit/barebox/commit/?h=next&id=fc7c42ff3c889ccc993061ee183b0cf1621e3f1c
> 
> It is in barebox/next.
> 
> Am 27.09.2017 um 08:51 schrieb Giorgio Dal Molin:
> > Hi,
> > 
> > I'm currently working with an embedded system based on a "normal"
> > intel (atom) PC with an AMI Bios on it supporting EFI.
> > 
> > I've built a barebox for it based on the 'arch/x86/configs/efi_defconfig'
> > and it basically runs on the target: I get a prompt on the screen, the
> > keyboard works and I can issue commands and boot a kernel.
> > 
> > My problem is now that the '/boot' and '/efi' dirs do not automatically
> > appear as described in http://www.barebox.org/doc/latest/boards/efi.html
> > 
> > After a bit of grepping and browsing in the barebox sources I've found
> > the file:
> > 
> >  fs/efi.c
> > 
> > At the end of it there is the 'efi_fs_driver' and its probe function;
> > I think the driver is registered with the core but the probe function
> > is never called on my system.
> > 
> > Could this be OK on an EFI system or is it an indication that something
> > is not properly configured ?
> > 
> > giorgio
> > 
> > _______________________________________________
> > barebox mailing list
> > barebox@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/barebox
> 
> -- 
> Regards,
> Oleksij
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-09-27  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27  6:51 Giorgio Dal Molin
2017-09-27  7:11 ` Oleksij Rempel
2017-09-27  8:28   ` Giorgio Dal Molin [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=2068226802.92408.1506500925602@mail.vodafone.de \
    --to=iw3gtf@arcor.de \
    --cc=barebox@lists.infradead.org \
    --cc=linux@rempel-privat.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