public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jesse Taube <mr.bossman075@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>,
	Samuel Holland <samuel@sholland.org>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	George Hilliard <thirtythreeforty@gmail.com>,
	Chris Morgan <macroalpha82@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	linux-sunxi <linux-sunxi@lists.linux.dev>
Subject: Re: Please test U-Boot Allwinner F1C100s support
Date: Sun, 30 Jan 2022 21:12:31 -0500	[thread overview]
Message-ID: <2ba1e2bb-e65d-8b79-dad9-1698b2dc6d12@gmail.com> (raw)
In-Reply-To: <20220131020427.2e57f75d@slackpad.fritz.box>



On 1/30/22 21:04, Andre Przywara wrote:
> Hi,
> 
> thanks to the tireless work of Jesse, I think the basic Allwinner
> F1C100s support for mainline U-Boot is now ready to be merged. Since I
> don't have the hardware, can any of you who have boards please give it a
> try on their hardware? I would really love to see some confirmations
> before I merge it.

I really have to thank you for reviewing!

> I put a branch here:
> https://source.denx.de/u-boot/custodians/u-boot-sunxi/-/tree/f1c100s
> 
> This should probably work on any F1C100s board, using the LicheePi Nano
> defconfig. Also curious about the F1C200s (looking at you, George ;-)

I have tested on both. Giulio has them aswell now.

> 
> This is very basic support at this point, there is no USB or SPI
> support, and even the SD card is not usable from U-Boot proper.

Sd card will work if we add it to the dts.

> I am hopeful we can add MMC and SPI support still in this cycle, but I don't
> want to hold back this series any longer, and it should be relatively
> simple support patches.

I have patches for both spi-boot and U-Boot proper spi suport.
I did manage to get it to find the boot device with:
`u32 brom_call = *(u32*)(fel_stash.sp-4);` in mach-sunxi/board.c with 
the suggestion that Stephen said. Should I submit after it gets into 
master or is tomorrow fine.

Many thanks,
	Jesse Taube
> 
> What should work though is booting via FEL and from SD card (the SPL
> MMC code is in place, if I am not mistaken). Just booting it to a U-Boot
> prompt via both methods would be a great test already. Maybe you can
> even upload a kernel and initrd via FEL and boot it from there, using
> $fdtcontroladdr for the DT address, for instance.
> 
> Any replies would be highly appreciated!
> 
> Many thanks,
> Andre

  reply	other threads:[~2022-01-31  2:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  2:04 Please test U-Boot Allwinner F1C100s support Andre Przywara
2022-01-31  2:12 ` Jesse Taube [this message]
2022-01-31 10:47   ` Giulio Benetti
2022-01-31 12:17     ` Giulio Benetti
2022-01-31 12:57       ` Andre Przywara
2022-01-31 13:07         ` Giulio Benetti
2022-01-31 13:57           ` Andre Przywara
2022-01-31 14:12             ` Giulio Benetti
2022-01-31 14:25               ` Andre Przywara
2022-01-31 18:13           ` Jesse Taube
2022-01-31 20:44             ` Giulio Benetti

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=2ba1e2bb-e65d-8b79-dad9-1698b2dc6d12@gmail.com \
    --to=mr.bossman075@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=macroalpha82@gmail.com \
    --cc=samuel@sholland.org \
    --cc=thirtythreeforty@gmail.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