Playing with upstream (Exynos4412)

Share here your ideas for new projects

Moderators: odroid, meveric, mdrjr

Re: Playing with upstream (Exynos4412)

Unread postby Tuigje » Wed Sep 30, 2015 3:16 pm

In order to load the latest kernel with devictree on my X2, I updated u-boot to https://github.com/tobiasjakobi/u-boot/tree/stable.
Booting from the SD-card gets stuck, as shown below. The SD-card works fine after restoring the original u-boot with sd_fusing.sh.
Does anyone have any suggestions?

Code: Select all
U-Boot 2015.10-rc3-00305-gb0debbf (Sep 29 2015 - 23:01:17 +0200)

CPU:   Exynos4412 @ 1 GHz
Model: Odroid based on Exynos4412
Board: Odroid based on Exynos4412
Model: x2                       
DRAM:  2 GiB                   
LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling   
LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling   
LDO21@TFLASH_2.8V: set 2800000 uV; enabling       
MMC:   SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
sdhci_transfer_data: Error detected in status(0x208002)!
sdhci_transfer_data: Error detected in status(0x208002)!
sdhci_transfer_data: Error detected in status(0x208000)!
*** Warning - read failed, using default environment

Net:   No ethernet found.
Hit any key to stop autoboot:  0
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...

Tuigje
 
Posts: 60
Joined: Thu Jun 20, 2013 1:00 am
languages_spoken: english dutch german
ODROIDs: Odroid X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Sep 30, 2015 4:08 pm

Doesn't work at the moment. See u-boot ml for the recent discussion on Odroid breakage.

EDIT: If you can, enable debug in the relevant files and provide a more verbose log.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Tuigje » Thu Oct 01, 2015 1:42 am

Ah, I thought the u-boot ml was about another problem, which was fixed by
https://github.com/tobiasjakobi/u-boot/commit/e060bf5165e30a7b32df1714787ea92575349000
from the mail in
http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/235132

I'll see if I can add some usefull debug prints in drivers/mmc/sdhci.c.

Edit: I've added #define CONFIG_MMC_TRACE to the top of drivers/mmc/mmc.c, which gives http://pastebin.com/FSm9yfST.
I'll ponder about this for a while, not sure yet how it helps.
Tuigje
 
Posts: 60
Joined: Thu Jun 20, 2013 1:00 am
languages_spoken: english dutch german
ODROIDs: Odroid X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Thu Oct 01, 2015 5:46 am

If you read the whole thread (which you should _always_ do) you can see that patch 4/4 is incorrect. What's currently in my stable branch is the revised series and what Przemyslaw cooked up. I have yet to test if that works on my hardware.

If Przemyslaw's series doesn't restore operation for you (my v2 series only introduces better error handling now), then you should report this on the u-boot ml.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Thu Oct 01, 2015 8:40 am

This is with my current stable branch:
Code: Select all
U-Boot 2015.10-rc4-00008-g5a03e21 (Oct 01 2015 - 01:32:16 +0200)

CPU:   Exynos4412 @ 1 GHz
Model: Odroid based on Exynos4412
Board: Odroid based on Exynos4412
Model: x2
DRAM:  2 GiB
LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
LDO21@TFLASH_2.8V: set 2800000 uV; enabling
MMC:   SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
Net:   No ethernet found.
Hit any key to stop autoboot:  0
reading boot.scr
1166 bytes read in 211 ms (4.9 KiB/s)
## Executing script at 40408000
reading zImage-4.2-odroid
2396296 bytes read in 1010 ms (2.3 MiB/s)
reading odroid-x2-4.2.dtb
54917 bytes read in 320 ms (167 KiB/s)
Kernel image @ 0x40008000 [ 0x000000 - 0x249088 ]
## Flattened Device Tree blob at 41f00000
   Booting using the fdt blob at 0x41f00000
   reserving fdt memory region: addr=41f00000 size=e000
   Using Device Tree in place at 41f00000, end 41f10fff

Starting kernel ...
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Fri Oct 02, 2015 1:15 am

Panzerknacker wrote:The old U3 (the server from above) never has reboot problems.
The U3+ get's often stuck on reboot.
Both U3s run your odroid-4.3.y headless with minor .config changes, ondemand and boost=0.

I rechecked the reboot issue and it looks like there were still some DTS entries missing. Just pushed some patches which should make it work.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Fri Oct 02, 2015 5:29 pm

Deployed 4.3.0-rc3-debug+ to U3-Server and U3+ yesterday, both with boost=1 and ondemand gov.
Both reboot fine, on U3+ 10 tests.
This is a hint, no proof, see the white swan / black swan problem.

But there is now a new issue:
When I'm logged in via ssh and start mc, mc takes around 150s to come up.
Switching mc on and off with Ctrl-O works fine.
Exit mc and starting it again takes again 150s.
mcedit shows same behaviour, nano runs fine.
Found no useful log entry.
Apache, owncloud,... run fine.
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby Tuigje » Sat Oct 03, 2015 4:24 pm

LiquidAcid wrote:This is with my current stable branch:
Code: Select all
U-Boot 2015.10-rc4-00008-g5a03e21 (Oct 01 2015 - 01:32:16 +0200)
Starting kernel ...


Mmm, that particular version also doesn't work for me, same results as before.
Booting from MMC instead of SD works fine.
Thanks for the feedback. I'll do some further experimenting before I post to the u-boot ml.
Tuigje
 
Posts: 60
Joined: Thu Jun 20, 2013 1:00 am
languages_spoken: english dutch german
ODROIDs: Odroid X2

Re: Playing with upstream (Exynos4412)

Unread postby ozcoder » Wed Oct 14, 2015 9:49 pm

ozcoder
 
Posts: 12
Joined: Mon Nov 04, 2013 9:20 pm
Location: Sydney, Australia
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Oct 14, 2015 11:28 pm


In what way is that useful and for which issue?
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Mon Oct 19, 2015 11:56 pm

Status update (a bit late):
- odroid-4.2.y rebased on stable/linux-4.2.3
- odroid-4.3.y rebased on torvalds's 4.3-rc6
- odroid-4.1.y removed (I'm aware it's LTS)

I'm going to keep odroid-4.0.y around for some more weeks, but eventually it's going to disappear as well.

Corresponding configs can again be found in odroid-env.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Tue Oct 20, 2015 9:45 pm

Updated my U3s to 4.3-rc6 with
vanilla-4.3-debug.conf + hwmon/pwm-fan
Issue with mc (see above) gone.

halt -p works (power 0W)
reboot does not work, stuck at 0.5W, after
systemd-shutdown[1]: rebooting.

Btw. perhaps for U3 pwm fan should be enabled in default config.
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Tue Oct 20, 2015 10:14 pm

Hmm, I can't reproduce this. Actualy I've double-checked that shutdown/reboot still works after applying Alim's series. If it doesn't work for you, make sure to raise this on the ml.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby daviessm » Wed Oct 28, 2015 4:34 am

I have a problem with 4.3.0-rc6+ rebooting on my X2 as well. It gets as far as "reboot: Restarting system" but powers off.

PanzerKnacker, did you figure out anything to do with this?
daviessm
 
Posts: 85
Joined: Thu Jul 25, 2013 2:14 am
Location: Belfast, UK
languages_spoken: English, German
ODROIDs: X2, XU4

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Wed Oct 28, 2015 4:39 am

Yes, apply this patch, if you work on eMMC:
https://patchwork.kernel.org/patch/7457391/
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby daviessm » Wed Oct 28, 2015 4:58 am

I'll give it a go but I use an SD card so it's probably something else for me. I'm using performance governor and boost is not set.

LiquidAcid, is there anything you could recommend changing to narrow this down?
daviessm
 
Posts: 85
Joined: Thu Jul 25, 2013 2:14 am
Location: Belfast, UK
languages_spoken: English, German
ODROIDs: X2, XU4

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Oct 28, 2015 5:07 am

daviessm wrote:I'll give it a go but I use an SD card so it's probably something else for me. I'm using performance governor and boost is not set.

LiquidAcid, is there anything you could recommend changing to narrow this down?

And you're sure that you've enabled the corresponding reset drivers?
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby daviessm » Wed Oct 28, 2015 6:29 am

That was it, I was missing:

Code: Select all
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_SYSCON=y
CONFIG_POWER_RESET_SYSCON_POWEROFF=y

Thanks for the help.
daviessm
 
Posts: 85
Joined: Thu Jul 25, 2013 2:14 am
Location: Belfast, UK
languages_spoken: English, German
ODROIDs: X2, XU4

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Tue Nov 10, 2015 11:19 pm

The usual rebasing and clean-ups:
- odroid-4.2.y rebased on stable/linux-4.2.6
- odroid-4.3.y rebased on stable/linux-4.3
- odroid-4.0.y removed

I'm probably going to wait for at least rc2 before pushing odroid-4.4.y. So far I don't see that many invasive changes, in the sense that it could complicate rebase/cherry-picking operation.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby daviessm » Mon Jan 18, 2016 8:21 pm

Hi LiquidAcid, I noticed your GitHub repository doesn't exist any more. Are you no longer working on this?

No problem, just wondering. :-)
daviessm
 
Posts: 85
Joined: Thu Jul 25, 2013 2:14 am
Location: Belfast, UK
languages_spoken: English, German
ODROIDs: X2, XU4

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Thu Jan 28, 2016 12:27 am

daviessm wrote:Hi LiquidAcid, I noticed your GitHub repository doesn't exist any more. Are you no longer working on this?

I've split private and public development for the kernel. linux-odroid still exists, but isn't visible to regular users. linux-odroid-public is the new repository that you should use.

Currently it only contains a 4.2.y and 4.3.y branch, but probably I'm going to push 4.4.y this weekend. As pointed out in the Mali ioctl thread I found some time to finally do the r5p0 integration.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby rooted » Fri Jan 29, 2016 6:09 pm

LiquidAcid wrote:
daviessm wrote:Hi LiquidAcid, I noticed your GitHub repository doesn't exist any more. Are you no longer working on this?

I've split private and public development for the kernel. linux-odroid still exists, but isn't visible to regular users. linux-odroid-public is the new repository that you should use.

Currently it only contains a 4.2.y and 4.3.y branch, but probably I'm going to push 4.4.y this weekend. As pointed out in the Mali ioctl thread I found some time to finally do the r5p0 integration.


Looking forward to that.
User avatar
rooted
 
Posts: 3572
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1
C1+
C2
XU3 Lite
XU4
VU7+
HiFi Shield 2
Smart Power (original)

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Feb 03, 2016 10:05 pm

Just pushed odroid-4.4.y and made it the default branch on linux-odroid-public.

rooted wrote:Looking forward to that.

Make sure to test the ioctl wrapper with it. A build script can be found here.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Sat Mar 05, 2016 11:51 pm

Rebased on stable/linux-4.4.4 and updated the X2 guide on the Linux-Exynos Wiki.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby memeka » Sun Mar 06, 2016 5:58 am

i see MFC is the only block that needs testing, is there something else that is not working?
btw, there is the EXYNOS x11 ddx that has G2D acceleration, in the tizen sources.
User avatar
memeka
 
Posts: 3439
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: Playing with upstream (Exynos4412)

Unread postby nijhawank » Sun Mar 06, 2016 5:35 pm

does it provide mali 3d acceleration?
nijhawank
 
Posts: 34
Joined: Sat Aug 03, 2013 7:35 am
languages_spoken: english

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Tue Mar 08, 2016 10:51 pm

nijhawank wrote:does it provide mali 3d acceleration?

You should work on your reading skills.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Mon Mar 14, 2016 11:52 pm

Just pushed odroid-4.4.5 to GitHub. Still working on odroid-4.5.y (some RCU locking issues left, and SDHCI voltage selection shows some warnings).
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Tue Mar 15, 2016 12:32 am

LiquidAcid wrote:Just pushed odroid-4.4.5 to GitHub. Still working on odroid-4.5.y (some RCU locking issues left, and SDHCI voltage selection shows some warnings).


This helped to get rid of two of three warnings:
exynos4412-odroid-common.dtsi
ldo21_reg: LDO21 {
regulator-name = "tflash_2.8V";
regulator-min-microvolt = <2800000>;
- regulator-max-microvolt = <2800000>;
+ regulator-max-microvolt = <2900000>;
regulator-boot-on;
LDO21-supply = <&reg_sysvdd>;
};

Trying to set vdd to 0x0 still warns.
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Tue Mar 15, 2016 12:44 am

Panzerknacker wrote:Trying to set vdd to 0x0 still warns.

That's the one I meant (the rest can be removed by patching the SDHCI core). Is this with vanilla? Asking because I was wondering if I should report this upstream.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Tue Mar 15, 2016 12:48 am

LiquidAcid wrote:
Panzerknacker wrote:Trying to set vdd to 0x0 still warns.

That's the one I meant (the rest can be removed by patching the SDHCI core). Is this with vanilla? Asking because I was wondering if I should report this upstream.


No, 4.5 vanilla is fine, introduced into -next about 10 days ago.
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Tue Mar 15, 2016 3:47 am

Hmm, my analysis shows that upstream commit d234d2123fa734c8018f7d01ed5d663cf5e6f665 (mmc: core: Keep host claimed in mmc_rescan() while calling host ops) introduces the issue. And that commit is in 4.5.y. As Ulf even points out in the commit message this now calls pm_runtime_get_sync(), which when propagated through s3c-sdhci triggers sdhci_do_set_ios() before ios->vdd is initialized.
I've traced this further through the calls, and in our case it's always the NOP case, i.e. sdhci_do_set_ios() exits before doing anything.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Panzerknacker » Tue Mar 15, 2016 4:17 am

Sorry for my quickshot, tested vanilla 4.5 today on XU4 only, no SDHCI failures there.
So yes, it is possible that mainstream introduced it in -next two weeks ago.
Thanks for finding out.
User avatar
Panzerknacker
 
Posts: 237
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X, XU, XU3, XU4, W

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Thu Mar 17, 2016 11:57 pm

Another rebase onto stable/linux-4.4.6.

I've fixed all remaining issues with odroid-4.5.y and just need to do some final cherry-picking from odroid-4.4.y.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby gkkpch » Fri Mar 25, 2016 2:54 am

Hi guys,

thanks a lot for keeping the X2 alive with a mainstream kernel.
I will test this as a headless Volumio 2 audio device (which is already available with C1/C2/XU4).
u-boot and kernel have been built successfully. With overlayfs, which is not available in the HK kernel, the "old" X2 should be volumio-ready.
U2/U3 should also work, can't test as I don't own one.
User avatar
gkkpch
 
Posts: 237
Joined: Mon Feb 25, 2013 11:47 pm
Location: Switzerland
languages_spoken: english, dutch, german
ODROIDs: Odroid-C1+, Odroid-C1+ HiFi shield, Odroid-C1, Odroid-X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Sun Mar 27, 2016 1:43 am

@gkkpch: I had a look at that project and it seems to be only a wrapper around MPD, or am I missing something here?
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby gkkpch » Mon Mar 28, 2016 3:20 am

LiquidAcid wrote:@gkkpch: I had a look at that project and it seems to be only a wrapper around MPD, or am I missing something here?


"only" is something you'd better not mention to the devoted developers :o They'l have you keelhauled :mrgreen:
But in a sense yes, albeit a very big wrapper. mpd and spotify are key components, with a lot of extra stuff mpd or spotify don't deliver.
Making it into an audiophile system you can very well use and enjoy without being a linux techie.
User avatar
gkkpch
 
Posts: 237
Joined: Mon Feb 25, 2013 11:47 pm
Location: Switzerland
languages_spoken: english, dutch, german
ODROIDs: Odroid-C1+, Odroid-C1+ HiFi shield, Odroid-C1, Odroid-X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Mon Mar 28, 2016 3:39 am

Well, I tend to ignore stuff that has the "audiophile" label applied, since it's mostly used by people listening on their Apple earbuds to material compressed to a tiny 3dB dynamic range window. :)

My playback chain currently looks like this (on a dedicated headless system):
- PulseAudio (with optional bs2b crossfeed)
- DIY DAC attached via USB
- DIY headphone amp
- AKG k701 / Sennheiser HD650 (depends on what I listen to)

Player software are MPD (local), MPV (local, for CDDA) and CMus (over network). MPD is controlled via GMPC, ncmpcpp, MPDroid and LIRC. MPV via SSH and LIRC.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby gkkpch » Mon Mar 28, 2016 4:14 am

LiquidAcid wrote:Well, I tend to ignore stuff that has the "audiophile" label applied, since it's mostly used by people listening on their Apple earbuds to material compressed to a tiny 3dB dynamic range window. :)


As long as I don't have listen to their crippled music I don't care what they call themselves..
I'm using a HD650 but not an AKG, picked up a Beyerdynamic dt880 as a second.
MPV sounds interesting, need to have a look at that in more detail.
User avatar
gkkpch
 
Posts: 237
Joined: Mon Feb 25, 2013 11:47 pm
Location: Switzerland
languages_spoken: english, dutch, german
ODROIDs: Odroid-C1+, Odroid-C1+ HiFi shield, Odroid-C1, Odroid-X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Mon Mar 28, 2016 4:44 am

gkkpch wrote:I'm using a HD650 but not an AKG, picked up a Beyerdynamic dt880 as a second.

I hear a lot positive about Beyerdynamic, though I'm probably going for a AKG k712 if I decide to replaced by k701 (which is around 8yrs old by now).

gkkpch wrote:MPV sounds interesting, need to have a look at that in more detail.

Back when I assembled the system it was mplayer, since it was the only application at that time that was fully scriptable and could play CDDA by digital extraction. mplayer became mplayer2, which eventually became MPV.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby gkkpch » Wed Mar 30, 2016 1:46 am

anyway, back on-topic. I'm having trouble with uInitrd (works fine with C1/C2/XU4).
The boot process waits for rootfs, so for some reason it will read the uInitrd image but won't start it.
uInitrd is supposed to (amoungst some other things) mount a .sqsh file (the rootfs), overlay with a rw data partition and then perform switch_root.
Did I overlook something?

This is the uart log:
Code: Select all

U-Boot 2016.03-00394-gd085ecd (Mar 24 2016 - 18:05:32 +0100)

CPU:   Exynos4412 @ 1 GHz
Model: Odroid based on Exynos4412
Board: Odroid based on Exynos4412
Type:  x2
DRAM:  2 GiB
LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
LDO21@TFLASH_2.8V: set 2800000 uV; enabling
MMC:   SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

Net:   No ethernet found.
Hit any key to stop autoboot:  0
reading boot.scr
1009 bytes read in 110 ms (8.8 KiB/s)
## Executing script at 42000000
reading zImage
2847160 bytes read in 497 ms (5.5 MiB/s)
reading uInitrd
3754906 bytes read in 556 ms (6.4 MiB/s)
reading exynos4412-odroidx2.dtb
60044 bytes read in 315 ms (185.5 KiB/s)
Kernel image @ 0x40008000 [ 0x000000 - 0x2b71b8 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    3754842 Bytes = 3.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 41f00000
   Booting using the fdt blob at 0x41f00000
   reserving fdt memory region: addr=41f00000 size=f000
   Using Device Tree in place at 41f00000, end 41f11fff

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0xa00
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.6-vanilla (odroidx2@VolumioOS) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 2014.11) ) #1 SMP PREEMPT Mon Mar 28 11:33:03 CEST 2016
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Hardkernel ODROID-X2 board based on Exynos4412
[    0.000000] Reserved memory: created DMA memory pool at 0x43000000, size 8 MiB
[    0.000000] Reserved memory: initialized node region@43000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x51000000, size 8 MiB
[    0.000000] Reserved memory: initialized node region@51000000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 128 MiB at 0xb7c00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe4412220
[    0.000000] Running under secure firmware.
[    0.000000] PERCPU: Embedded 12 pages/cpu @eef8b000 s19136 r8192 d21824 u49152
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 518400
[    0.000000] Kernel command line: video=HDMI-A-1:1280x720M@60 console=tty1 console=ttySAC1,115200n8 rootwait rw imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1919168K/2079744K available (5691K kernel code, 248K rwdata, 1756K rodata, 296K init, 248K bss, 29504K reserved, 131072K cma-reserved, 1178624K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc074dfe4   (7448 kB)
[    0.000000]       .init : 0xc074e000 - 0xc0798000   ( 296 kB)
[    0.000000]       .data : 0xc0798000 - 0xc07d6340   ( 249 kB)
[    0.000000]        .bss : 0xc07d9000 - 0xc0817224   ( 249 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C: platform provided aux values permit register corruption.
[    0.000000] L2C: DT/platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310: enabling full line of zeros but not enabled in Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 8 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310: CACHE_ID 0x4100c4c8, AUX_CTRL 0x7e470001
[    0.000000] Exynos4x12 clocks: sclk_apll = 1000000000, sclk_mpll = 800000000
[    0.000000]  sclk_epll = 96000000, sclk_vpll = 350000000, arm_clk = 1000000000
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000004] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000263] Console: colour dummy device 80x30
[    0.001007] console [tty1] enabled
[    0.001032] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.001067] pid_max: default: 32768 minimum: 301
[    0.001150] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001174] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001618] Initializing cgroup subsys devices
[    0.001653] CPU: Testing write buffer coherency: ok
[    0.001948] CPU0: thread -1, cpu 0, socket 10, mpidr 80000a00
[    0.002330] Setting up static identity map for 0x40008200 - 0x40008258
[    0.040338] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[    0.055318] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[    0.070311] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[    0.070354] Brought up 4 CPUs
[    0.070426] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    0.070445] CPU: All CPU(s) started in SVC mode.
[    0.071050] devtmpfs: initialized
[    0.083594] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.084023] lcd0-power-domain@10023C80 has as child subdomain: tv-power-domain@10023C20.
[    0.084474] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[    0.089076] pinctrl core: initialized pinctrl subsystem
[    0.089763] NET: Registered protocol family 16
[    0.091446] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104993] cpuidle: using governor ladder
[    0.119988] cpuidle: using governor menu
[    0.135115] exynos-audss-clk 3810000.clock-controller: setup completed
[    0.145444] iommu: Adding device 11800000.fimc to group 0
[    0.145796] iommu: Adding device 11810000.fimc to group 1
[    0.146123] iommu: Adding device 11820000.fimc to group 2
[    0.146453] iommu: Adding device 11830000.fimc to group 3
[    0.150437] iommu: Adding device 13400000.codec to group 4
[    0.155634] iommu: Adding device 11c00000.fimd to group 5
[    0.156110] iommu: Adding device 11840000.jpeg-codec to group 6
[    0.156425] iommu: Adding device 12810000.rotator to group 7
[    0.160416] iommu: Adding device 12c10000.mixer to group 8
[    0.167404] iommu: Adding device 10800000.g2d to group 9
[    0.170832] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.170870] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.178596] SCSI subsystem initialized
[    0.178737] usbcore: registered new interface driver usbfs
[    0.178806] usbcore: registered new interface driver hub
[    0.178899] usbcore: registered new device driver usb
[    0.179395] s3c-i2c 13860000.i2c: slave address 0x10
[    0.179424] s3c-i2c 13860000.i2c: bus frequency set to 390 KHz
[    0.204702] s3c-i2c 13860000.i2c: i2c-0: S3C I2C adapter
[    0.204947] s3c-i2c 13870000.i2c: slave address 0x10
[    0.204997] s3c-i2c 13870000.i2c: bus frequency set to 390 KHz
[    0.205300] s3c-i2c 13870000.i2c: i2c-1: S3C I2C adapter
[    0.205461] s3c-i2c 13880000.i2c: slave address 0x00
[    0.205487] s3c-i2c 13880000.i2c: bus frequency set to 97 KHz
[    0.205669] s3c-i2c 13880000.i2c: i2c-2: S3C I2C adapter
[    0.205773] s3c-i2c 138e0000.i2c: slave address 0x00
[    0.205799] s3c-i2c 138e0000.i2c: bus frequency set to 97 KHz
[    0.206041] s3c-i2c 138e0000.i2c: i2c-8: S3C I2C adapter
[    0.206284] Linux video capture interface: v2.00
[    0.206721] Advanced Linux Sound Architecture Driver Initialized.
[    0.207360] clocksource: Switched to clocksource mct-frc
[    0.215526] NET: Registered protocol family 2
[    0.215970] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.216060] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.216170] TCP: Hash tables configured (established 8192 bind 8192)
[    0.216239] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.216283] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.216439] NET: Registered protocol family 1
[    0.216687] RPC: Registered named UNIX socket transport module.
[    0.216711] RPC: Registered udp transport module.
[    0.216729] RPC: Registered tcp transport module.
[    0.216747] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.217142] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.218389] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.218523] audit: initializing netlink subsys (disabled)
[    0.218575] audit: type=2000 audit(0.215:1): initialized
[    0.224850] NFS: Registering the id_resolver key type
[    0.224899] Key type id_resolver registered
[    0.224918] Key type id_legacy registered
[    0.224948] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.225014] ntfs: driver 2.1.32 [Flags: R/W].
[    0.227430] bounce: pool size: 64 pages
[    0.227612] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.227653] io scheduler noop registered
[    0.227675] io scheduler deadline registered
[    0.227718] io scheduler cfq registered (default)
[    0.228173] 125b0000.exynos-usbphy supply vbus not found, using dummy regulator
[    0.231752] dma-pl330 12680000.pdma: Loaded driver for PL330 DMAC-141330
[    0.231787] dma-pl330 12680000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.234284] dma-pl330 12690000.pdma: Loaded driver for PL330 DMAC-141330
[    0.234318] dma-pl330 12690000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.235168] dma-pl330 12850000.mdma: Loaded driver for PL330 DMAC-141330
[    0.235200] dma-pl330 12850000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.236104] 13800000.serial: ttySAC0 at MMIO 0x13800000 (irq = 70, base_baud = 0) is a S3C6400/10
[    0.236459] 13810000.serial: ttySAC1 at MMIO 0x13810000 (irq = 71, base_baud = 0) is a S3C6400/10
[    1.092856] console [ttySAC1] enabled
[    1.096886] 13820000.serial: ttySAC2 at MMIO 0x13820000 (irq = 72, base_baud = 0) is a S3C6400/10
[    1.105676] 13830000.serial: ttySAC3 at MMIO 0x13830000 (irq = 73, base_baud = 0) is a S3C6400/10
[    1.115180] [drm] Initialized drm 1.1.0 20060810
[    1.121139] s5p-g2d 10800000.g2d: The exynos g2d(ver 4.1) successfully probed
[    1.126711] exynos-drm-fimc 11820000.fimc: drm fimc registered successfully.
[    1.133311] exynos-drm-fimc 11830000.fimc: drm fimc registered successfully.
[    1.140378] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully.
[    1.149068] exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops)
[    1.154554] exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops)
[    1.161709] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.168288] [drm] No driver support for vblank timestamp query.
[    1.174600] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    1.182575] loop: module loaded
[    1.183804] usbcore: registered new interface driver smsc95xx
[    1.517405] dwc2 12480000.hsotg: EPs: 16, dedicated fifos, 7808 entries in SPRAM
[    1.519569] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.525702] ehci-exynos: EHCI EXYNOS driver
[    1.530400] exynos-ehci 12580000.ehci: EHCI Host Controller
[    1.535437] exynos-ehci 12580000.ehci: new USB bus registered, assigned bus number 1
[    1.543328] exynos-ehci 12580000.ehci: irq 68, io mem 0x12580000
[    1.557387] exynos-ehci 12580000.ehci: USB 2.0 started, EHCI 1.00
[    1.557968] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.564633] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.571842] usb usb1: Product: EHCI Host Controller
[    1.576692] usb usb1: Manufacturer: Linux 4.4.6-vanilla ehci_hcd
[    1.582682] usb usb1: SerialNumber: 12580000.ehci
[    1.587856] hub 1-0:1.0: USB hub found
[    1.591110] hub 1-0:1.0: 3 ports detected
[    1.595661] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.601271] ohci-exynos: OHCI EXYNOS driver
[    1.822387] usb3503 0-0008: switched to HUB mode
[    1.822463] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.827671] max77686-rtc max77686-rtc: max77686_rtc_probe
[    1.932390] usb 1-2: new high-speed USB device number 2 using exynos-ehci
[    1.963183] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0
[    1.965472] s3c-rtc 10070000.rtc: failed to find rtc source clock
[    1.971283] i2c /dev entries driver
[    1.976953] s3c2410-wdt 10060000.watchdog: watchdog inactive, reset disabled, irq disabled
[    1.983265] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
[    1.993414] sdhci: Secure Digital Host Controller Interface driver
[    1.997314] sdhci: Copyright(c) Pierre Ossman
[    2.001924] s3c-sdhci 12530000.sdhci: clock source 2: mmc_busclk.2 (50000000 Hz)
[    2.009096] s3c-sdhci 12530000.sdhci: Got CD GPIO
[    2.042462] mmc0: SDHCI controller on samsung-hsmmc [12530000.sdhci] using ADMA
[    2.044266] Synopsys Designware Multimedia Card Interface Driver
[    2.050677] dwmmc_exynos 12550000.mmc: IDMAC supports 32-bit address mode.
[    2.057037] dwmmc_exynos 12550000.mmc: Using internal DMA controller.
[    2.062703] usb 1-2: New USB device found, idVendor=0424, idProduct=3503
[    2.062707] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.063031] hub 1-2:1.0: USB hub found
[    2.063198] hub 1-2:1.0: 3 ports detected
[    2.075933] mmc0: new high speed SDHC card at address 0001
[    2.076182] mmcblk0: mmc0:0001 00000 29.3 GiB
[    2.077065]  mmcblk0: p1 p2 p3
[    2.097884] dwmmc_exynos 12550000.mmc: Version ID is 240a
[    2.103277] dwmmc_exynos 12550000.mmc: DW MMC controller at irq 120,32 bit host data width,128 deep fifo
[    2.112911] dwmmc_exynos 12550000.mmc: allocated mmc-pwrseq
[    2.147381] dwmmc_exynos 12550000.mmc: 1 slots initialized
[    2.148182] alg: skcipher: encryption failed on test 1 for ecb-aes-s5p: ret=22
[    2.154524] s5p-sss driver registered
[    2.158295] usbcore: registered new interface driver usbhid
[    2.163645] usbhid: USB HID core driver
[    2.168060] exynos-bus bus_dmc: unable to get devfreq-event device : ppmu-event3-dmc0
[    2.175635] exynos-bus bus_leftbus: unable to get devfreq-event device : ppmu-event3-leftbus
[    2.184771] usbcore: registered new interface driver snd-usb-audio
[    2.191851] NET: Registered protocol family 10
[    2.194683] sit: IPv6 over IPv4 tunneling driver
[    2.199232] NET: Registered protocol family 17
[    2.203458] ThumbEE CPU extension supported.
[    2.207572] Registering SWP/SWPB emulation handler
[    2.213112] s3c-rtc 10070000.rtc: rtc disabled, re-enabling
[    2.218057] s3c-rtc 10070000.rtc: rtc core: registered s3c as rtc1
[    2.247523] max98090 1-0010: MAX98090 REVID=0x43
[    2.248167] max98090 1-0010: use default 2.8v micbias
[    2.255399] asoc-simple-card sound: HiFi <-> 3830000.i2s mapping ok
[    2.259321] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    2.265026] vdd_hdmi_1.0V: disabling
[    2.268850] unused_2.8V: disabling
[    2.272225] vdd_g3d: disabling
[    2.275891] ALSA device list:
[    2.277425]   #0: Odroid-X2
[    2.280828] Waiting for root device ...
[    2.347402] usb 1-2.1: new high-speed USB device number 3 using exynos-ehci
[    2.452732] usb 1-2.1: New USB device found, idVendor=0424, idProduct=9514
[    2.453968] usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.462126] hub 1-2.1:1.0: USB hub found
[    2.465348] hub 1-2.1:1.0: 5 ports detected
[    2.752384] usb 1-2.1.1: new high-speed USB device number 4 using exynos-ehci
[    2.857846] usb 1-2.1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.859253] usb 1-2.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.869235] smsc95xx v1.0.4
[    2.917039] smsc95xx 1-2.1.1:1.0 eth0: register 'smsc95xx' at usb-12580000.ehci-2.1.1, smsc95xx USB 2.0 Ethernet, 26:39:dc:28:51:4f


This is my boot.scr (I also tried with fdt_addr "0x44000000")

Code: Select all
# kernel image and dtb load addresses
setenv zimg_addr "0x40008000"
setenv fdt_addr "0x41f00000"
setenv initrd_addr "0x42000000"
setenv fdt_high "0xffffffff"
setenv initrd_high "0xffffffff"
   
# video config: 1280x720M@50, 1920x1080M@60
# console config
# rootfs config
setenv vid_config "video=HDMI-A-1:1280x720M@60"
setenv con_config "console=tty1 console=ttySAC1,115200n8"
setenv rfs_config "rootwait imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh"
   
setenv zimg_file "zImage"
setenv fdt_file "exynos4412-odroidx2.dtb"
setenv initrd_file "uInitrd"
setenv bootargs "${vid_config} ${con_config} ${rfs_config}"
   
setenv uloadcmd "fatload mmc 0:1 ${zimg_addr} ${zimg_file}; fatload mmc 0:1 ${initrd_addr} ${initrd_file}; fatload mmc 0:1 ${fdt_addr} ${fdt_file}"
setenv bootcmd "run uloadcmd; fdt addr ${fdt_addr}; fdt resize; bootz ${zimg_addr} ${initrd_addr} ${fdt_addr}"
boot
User avatar
gkkpch
 
Posts: 237
Joined: Mon Feb 25, 2013 11:47 pm
Location: Switzerland
languages_spoken: english, dutch, german
ODROIDs: Odroid-C1+, Odroid-C1+ HiFi shield, Odroid-C1, Odroid-X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Mar 30, 2016 2:11 am

u-boot might read the file, but the kernel certainly doesn't (no "Unpacking initramfs..." message).
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby gkkpch » Wed Mar 30, 2016 4:52 am

:oops: blind as a bat, really overlooked that one.
Without initramfs/ initrd support enabled in the kernel, I wasn't going to get far...
Corrected, works :D
User avatar
gkkpch
 
Posts: 237
Joined: Mon Feb 25, 2013 11:47 pm
Location: Switzerland
languages_spoken: english, dutch, german
ODROIDs: Odroid-C1+, Odroid-C1+ HiFi shield, Odroid-C1, Odroid-X2

Re: Playing with upstream (Exynos4412)

Unread postby Slade87 » Mon Apr 11, 2016 12:34 am

sorry to bother but could somebody provide me please with a link to u-boot-bin which is able to boot the new kernels? I would like building kernel 4.4.6 for my odroid and have done so, but it seems my u-boot has an issue since it also doesnt even boot the old kernel. Not sure what I did wrong.

Thanks alot!
Slade87
 
Posts: 10
Joined: Wed Mar 23, 2016 3:58 pm
languages_spoken: english
ODROIDs: U3,C2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Mon Apr 11, 2016 10:30 pm

Slade87 wrote:I would like building kernel 4.4.6 for my odroid and have done so, but it seems my u-boot has an issue since it also doesnt even boot the old kernel. Not sure what I did wrong.

You won't be able to boot Hardkernel's odroid-3.8.y kernel with a recent u-boot (different MPLL clock). Apart from that I have no idea. I guess you need to provide more information.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby Julius » Wed Apr 13, 2016 11:13 am

Awesome... I just noticed this now that this is actually working on a X2.

Any chance this could be made available for meverics Debian Jessie version: viewtopic.php?f=16&t=17920 or as another easy to flash ubuntu/debian image file?
Julius
 
Posts: 51
Joined: Wed Apr 30, 2014 5:59 am
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed Apr 13, 2016 5:10 pm

Julius wrote:Any chance this could be made available for meverics Debian Jessie version: viewtopic.php?f=16&t=17920 or as another easy to flash ubuntu/debian image file?

No, like I said before this thread is about kernel development. I have zero interest in providing any binaries and/or image files.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Fri Apr 22, 2016 1:22 am

I have pushed odroid-4.5.y (currently based on stable/linux-4.5.2) to linux-odroid-public. It took a bit longer, but I first wanted to (semi) finish my G2D command list submission rewrite. Multiple bitblts are now possible in one command list block, and the kernel driver should be more resilient against misuse (previously it was easy to lockup the system by submitting a list which used certain registers like mask and pattern).
The rewrite is still ongoing, since I have yet some functionality of the block left to make use of (clipping window and rotation).
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Sun May 08, 2016 8:02 am

Nothing too spectacular:
- odroid-4.4.y rebased on stable/linux-4.4.9
- odroid-4.5.y rebased on stable/linux-4.5.3
- odroid-4.6.y is still cooking...
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: Playing with upstream (Exynos4412)

Unread postby LiquidAcid » Wed May 25, 2016 7:47 am

odroid-4.6.y pushed to linux-odroid-public. Working (debug) config can be found at the usual place.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

PreviousNext

Return to The Ideas

Who is online

Users browsing this forum: Exabot [Bot] and 4 guests