| Slackware - ARM This forum is for the discussion of Slackware ARM. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
12-04-2018, 10:25 PM
|
#1
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Rep: 
|
Orange Pi Plus 2E H3 (unofficial)
Last edited by sndwvs; 12-04-2018 at 10:36 PM.
|
|
|
|
|
12-05-2018, 03:47 AM
|
#2
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
Quote:
Originally Posted by sndwvs
|
Thanks for this. Since 4.19 is an LTS, let's get some of this back up stream in to Slackware ARM.
Can you tell me which patches specifically are required to enable HDMI for the H3? I think a newer U-boot is required as well, but that ought to be (I hope) a simple upgrade. |
|
|
1 members found this post helpful.
|
|
12-05-2018, 09:53 AM
|
#3
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
Quote:
Originally Posted by drmozes
Thanks for this. Since 4.19 is an LTS, let's get some of this back up stream in to Slackware ARM.
Can you tell me which patches specifically are required to enable HDMI for the H3? I think a newer U-boot is required as well, but that ought to be (I hope) a simple upgrade.
|
1. u-boot was taken the last cut with git
2. the linux source was taken from here branch orange-pi-4.19
3. I only used these patches and it works (patches are also applied to mainline)
Code:
0099-dt-bindings-sun4i-drm-add-HDMI-VCC-supply-property-f.patch
0100-drm-sun4i-Add-support-for-HDMI-voltage-regulator.patch
0126-drm-bridge-move-ANA78xx-driver-to-analogix-subdirect.patch
0127-drm-bridge-split-some-definitions-of-ANX78xx-to-dedi.patch
0128-drm-bridge-extract-some-Analogix-I2C-DP-common-code.patch
0130-drm-bridge-Add-Analogix-anx6345-support.patch
4. configure kernel
Code:
CONFIG_DRM_SUN4I_HDMI=y
CONFIG_DRM_SUN4I_HDMI_CEC=y
CONFIG_DRM_SUN8I_DW_HDMI=y
CONFIG_DRM_DW_HDMI=y
CONFIG_HDMI=y
|
|
|
1 members found this post helpful.
|
|
12-05-2018, 12:22 PM
|
#4
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
I upgraded to
Code:
U-Boot 2019.01-rc1 (Dec 05 2018 - 17:34:37 +0000) Allwinner Technology
=> saveenv
Saving Environment to FAT... Unable to use mmc 1:0... Failed (1)
Where are you storing the environment? I haven't looked yet but may be I just need to edit the defaults in the source and rebuild. |
|
|
1 members found this post helpful.
|
|
12-05-2018, 12:28 PM
|
#5
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
I use /boot/ boot.cmd /boot/boot.scr |
|
|
1 members found this post helpful.
|
|
12-06-2018, 01:57 AM
|
#6
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
Quote:
Originally Posted by sndwvs
|
Where are you writing u-boot to? the eMMC?
It isn't as straight forward as I had hoped and it's not obvious what they changed, so I might ask on the u-boot mailing list. |
|
|
|
|
12-06-2018, 02:32 AM
|
#7
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
Quote:
Originally Posted by drmozes
Where are you writing u-boot to? the eMMC?
It isn't as straight forward as I had hoped and it's not obvious what they changed, so I might ask on the u-boot mailing list.
|
to boot from eMMC, you need to write u-boot:
# clear u-boot
Code:
dd if=/dev/zero of=/dev/mmcblk1 bs=1k count=1023 seek=1 status=noxfer
dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 status=noxfer
after that add root to boot in /boot/uEnv.txt:
Code:
verbosity=8
console=both
rootdev=/dev/mmcblk1p1
transfer boot.cmd boot.scr to eMMC in /boot
and change fstab on eMMC to mind:
Code:
/dev/mmcblk1p1 / ext4 noatime,nodiratime,derrors=remount-ro 0 1
Last edited by sndwvs; 12-06-2018 at 02:34 AM.
|
|
|
|
|
12-06-2018, 07:10 AM
|
#8
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
Quote:
Originally Posted by sndwvs
to boot from eMMC, you need to write u-boot:
# clear u-boot
Code:
dd if=/dev/zero of=/dev/mmcblk1 bs=1k count=1023 seek=1 status=noxfer
dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 status=noxfer
after that add root to boot in /boot/uEnv.txt:
Code:
verbosity=8
console=both
rootdev=/dev/mmcblk1p1
transfer boot.cmd boot.scr to eMMC in /boot
and change fstab on eMMC to mind:
Code:
/dev/mmcblk1p1 / ext4 noatime,nodiratime,derrors=remount-ro 0 1
|
How does u-boot know where to find /boot ? are you using the default environment present within the u-boot binary that scans available media?
One of the precepts I work to is that people installing Slackware ARM should be safe, if they follow the instructions.
If I suggest overwriting u-boot on the eMMC, and it doesn't work out, you've got a bricked device - which is usually hard to fix.
That's why I go with the SD card approach: at least this is a safe approach.
I'm not sure that I can do that with this method, unless I'm missing something?
Last edited by drmozes; 12-06-2018 at 07:12 AM.
|
|
|
|
|
12-06-2018, 07:49 AM
|
#9
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
Quote:
Originally Posted by drmozes
How does u-boot know where to find /boot ? are you using the default environment present within the u-boot binary that scans available media?
|
yes, the default u-boot is used.
Quote:
Originally Posted by drmozes
One of the precepts I work to is that people installing Slackware ARM should be safe, if they follow the instructions.
If I suggest overwriting u-boot on the eMMC, and it doesn't work out, you've got a bricked device - which is usually hard to fix.
That's why I go with the SD card approach: at least this is a safe approach.
I'm not sure that I can do that with this method, unless I'm missing something?
|
i also want the images for SDcard, the transfer from SDcard to eMMC is described above.
for orange pi with non-working u-boot in eMMC, it will boot from SDcard. |
|
|
|
|
12-06-2018, 08:30 AM
|
#10
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
Quote:
Originally Posted by sndwvs
for orange pi with non-working u-boot in eMMC, it will boot from SDcard.
|
Aha! I didn't know that.
Thanks. This might simplify things then. |
|
|
|
|
12-06-2018, 08:57 AM
|
#11
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
for information Boot Process |
|
|
|
|
12-07-2018, 04:33 AM
|
#12
|
|
LQ Newbie
Registered: May 2018
Posts: 3
Rep:
|
I don't see this config option mentioned in this thread:
CONFIG_SUN8I_DE2_CCU=y
I believe I had to add this one, back when I did an experimental DE2/HDMI backport to the 4.16 kernel for my little H3 device.
|
|
|
|
|
12-07-2018, 06:31 AM
|
#13
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
Quote:
Originally Posted by Broder Tuck
I don't see this config option mentioned in this thread:
CONFIG_SUN8I_DE2_CCU=y
I believe I had to add this one, back when I did an experimental DE2/HDMI backport to the 4.16 kernel for my little H3 device.
|
this parameter is included in this build. |
|
|
|
|
12-08-2018, 04:11 AM
|
#14
|
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,593
|
Quote:
Originally Posted by sndwvs
|
Having thought it through, this is helpful for someone who wants to use the SD card slot for something else, but not for a new user.
We still need a way to place the newer u-boot on to the eMMC - which would mean they need to boot a Linux OS (which may not work properly with the factory version of u-boot, or may have different options - e.g. "save" used to save the environment, and now it is an unknown operation: I need to be able to document from a known state), or do it from u-boot directly (either way requires more documentation). With the SD card route they can do this on an x86.
I'll have to find out why the newer version no longer can save its environment.
Last edited by drmozes; 12-08-2018 at 05:10 AM.
|
|
|
|
|
11-29-2019, 01:32 PM
|
#15
|
|
Senior Member
Registered: Aug 2014
Posts: 2,009
Original Poster
Rep:
|
Last edited by sndwvs; 11-29-2019 at 02:27 PM.
|
|
|
|
All times are GMT -5. The time now is 08:56 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
