From: Tomek Domek <tomekdomek8585@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Missing FDT description in DTB
Date: Fri, 6 Dec 2019 13:37:48 +0100 [thread overview]
Message-ID: <CAHB2bXAp8VZ-+zmL2yoAF5sZorDsfSmF20payfqW_LGk=pW4vw@mail.gmail.com> (raw)
In-Reply-To: <85045.1575631571@turing-police>
[-- Attachment #1.1: Type: text/plain, Size: 1069 bytes --]
Yes, it is for bringup purpose. We have working uboot software and we split
the code in order to have FSBL and SSBL and I had such problem but it was a
matter of deleting "-f auto" and -E option from mkimage for building
u-boot.img. Now FSBL, SSBL and kernel starts successfully.
pt., 6 gru 2019 o 12:26 Valdis Klētnieks <valdis.kletnieks@vt.edu>
napisał(a):
> On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said:
>
> > And this uboot and spl is somekind of experimental software which is in
> > the middle of creation. Could anyone try to guide what might be possible
> > the reason of the issue as I am a bit new in u-boot development?
>
> Is there a reason why you're using an experimental uboot/spl rather than
> a known-stable working version for whatever hardware this is?
>
> (Of course, if this is bring-up of a new architecture that has never been
> supported by uboot, so there's never been a working uboot for the device,
> it's
> time to quote the movie Animal House: "My advice to you is to start
> drinking
> heavily")
>
>
[-- Attachment #1.2: Type: text/html, Size: 1411 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-12-06 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 9:03 Missing FDT description in DTB Tomek Domek
2019-12-06 11:16 ` Tomek Domek
2019-12-06 11:26 ` Valdis Klētnieks
2019-12-06 12:37 ` Tomek Domek [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='CAHB2bXAp8VZ-+zmL2yoAF5sZorDsfSmF20payfqW_LGk=pW4vw@mail.gmail.com' \
--to=tomekdomek8585@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).