All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v5, 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot
Date: Tue, 25 Aug 2015 16:44:20 +0200	[thread overview]
Message-ID: <1440513860.9743.23.camel@collins> (raw)
In-Reply-To: <55DC64FD.8010808@schmelzer.or.at>

> > If I got everything right, the bootrom is passing BOOT_DEVICE_UART as
> > boot device, but you haven't selected CONFIG_SPL_YMODEM_SUPPORT. Thus,
> > it falls back to asking omap_sys_boot_device, which is not implemented.
> I don't think, there is everything right. Have a closer look to the #ifdef.
> 
> #if (defined(BOOT_DEVICE_UART) && !defined(CONFIG_SPL_YMODEM_SUPPORT)) || \
>      (defined(BOOT_DEVICE_USB) && !defined(CONFIG_SPL_USB_SUPPORT)) || \
>      (defined(BOOT_DEVICE_USBETH) && !defined(CONFIG_SPL_USBETH_SUPPORT))
> 
> I have enabled CONFIG_SPL_YMODEM_SUPPORT, look at bur_am335x_common.h.
> 
> > The real problem here is that you have not enabled support for loading
> > the main U-Boot binary via UART, with CONFIG_SPL_YMODEM_SUPPORT.
> >
> > UART booting is unrelated to CONFIG_SPL_USBETH_SUPPORT.
> No, due to the fact that defined(BOOT_DEVICE_USBETH) is allways true 
> (spl.h) and i don't have
> CONFIG_SPL_USBETH_SUPPORT enabled, the #ifdef above:
> 
> defined(BOOT_DEVICE_USBETH) && !defined(CONFIG_SPL_USBETH_SUPPORT)
> 
> becomes true and the followed switch/case does the rest.

Oh you're right, I hadn't thought this through.

I'll think about how to solve this in the cleanest way (I wouldn't want
to duplicate the ifdef logic too much). Thanks for bringing this up.

> >> further i think that this construct isn't complete yet, because it
> >> wants to handle all peripheral booting on AM335x or OMAP in general.
> >>
> >> following peripherals are currently handled:
> >>
> >> BOOT_DEVICE_UART
> >> BOOT_DEVICE_USB
> >> BOOT_DEVICE_USBETH
> >>
> >> but there is also
> >> BOOT_DEVICE_CPGMAC
> >>
> >> Summary i think this changeset isn't complete.
> > Can the bootrom indicate that it booted from BOOT_DEVICE_CPGMAC?
> > I haven't seen that and don't really know what it corresponds to. But if
> > you think it is concerned by this fallback mechanism, you could add
> > support for it. I only made this for the omap devices I have (and I
> > don't have any am33xx board) and I didn't want to blindly implement too
> > much for am33xx.
> Yes, thats possible von AM335x.
> I will have a close look if it is necessary to implement here some fallback.
> But probably not, because the most likely case is that "full" U-Boot 
> supports Ethernet and the SPL doesn't and not otherwise :-)

Alright then, that's fine with me. It's okay if the fallback mechanism
doesn't handle all use cases, too.

-- 
Paul Kocialkowski, Replicant developer

Replicant is a fully free Android distribution running on several
devices, a free software mobile operating system putting the emphasis on
freedom and privacy/security.

Website: http://www.replicant.us/
Blog: http://blog.replicant.us/
Wiki/tracker/forums: http://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150825/1c871ac1/attachment.sig>

  reply	other threads:[~2015-08-25 14:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 14:02 [U-Boot] [PATCH v5 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
2015-07-15 14:02 ` [U-Boot] [PATCH v5 1/8] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-07-28 14:58   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 2/8] omap: SPL boot devices cleanup and completion Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 3/8] omap-common: Boot device define instead of hardcoded value Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 4/8] siemens-am33x-common: Hardcoded value instead of non-included define Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-08-25  8:40     ` Schmelzer Hannes
2015-08-25 12:27       ` Paul Kocialkowski
2015-08-25 12:52         ` Hannes Schmelzer
2015-08-25 14:44           ` Paul Kocialkowski [this message]
2015-07-15 14:02 ` [U-Boot] [PATCH v5 6/8] omap3: Definitions for SYS_BOOT-based fallback boot device selection Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 7/8] omap4: " Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 8/8] omap5: " Paul Kocialkowski
2015-07-28 14:59   ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-26 16:29 ` [U-Boot] [PATCH v5 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski

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=1440513860.9743.23.camel@collins \
    --to=contact@paulk.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.