* Switching Odroid C1 boot partition to FAT
U-boot FAT driver is very unstable and there is no wish to dig into u-boot. Seems like a sane workaround @plntyk
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Add notes for separate boot partitions
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Typo
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Bugfix: use zImage for converting to uImage since on FAT partitions we use move
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Cleanup C1 boot scripts
We have no plans to ever support legacy kernel again. Removing related things
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* A bit more radical change. Moving meson current to (new) legacy, current to 5.6.y and dev to some development branch / commit.
* Remove unneded patch
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Kernel install image is broken on VFAT images since it unmounts directory in preinstall and doesn't mount back. We used to have this for NAND / FAT install which fixes this in the postinst script. Removing since we have no more support for NAND anyway. Tested on Odroid C1. @the-going
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* [ mvebu ] Switch fake-hwclock to hardware RTC AR-159
* remove fake-hwclock dpkg
* tweak /lib/udev/hwclock-set to be executed even if systemd present
* move helios4 bsp file under mvebu folder for tidiness
* Fixing desktop install on Ubuntu Focal / Eean
Changed dependencies for Network manager automatically install Gnome3 desktop unless certain packages are installed first. Fixing with pre-depends package feature. Tested on arm64, desktop install on top of CLI image
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Prepping for N2 move to mainline I stumbled upon the missed variables when I tried to use this on g12b.
@igorpecovnik or @superna9999 I just want a second set of eyes, I think it's obvious, but that's where I always make the mistakes.
* Rework packages install that they can be installed from repository instead of local compile. Handy for making releases.
* Don't build ATF if you don't build u-boot
odroidc1 can fail to boot probably depending
on features of the ext4 rootfs that is created
during the build process
serial log error:
Loading file "/boot/uInitrd" from mmc device 0:1 xxa1
invalid extent block
since there is no support for that board in upstream u-boot
backport the patch from
upstream commit:b5bbac1a9b07016602559ff483df265fef6c1f83
see also [1]
[1] https://lists.denx.de/pipermail/u-boot/2014-January/170802.html
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
Enable DMC for roc-rk3328-cc (renegade) in current
No stability issues with this enabled, no reason not to merge, enables higher clockrates via manual setting for now.
* enable and change odroidc1 config
remove EOS
enable current and dev config
meson-current: update config
meson-dev: update config
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* meson-current meson-dev: reduce Kernel size
with default loading locations in u-boot
the uImage can be too large and will be partly overwritten
with the loaded dtb leading to boot failues due to wrong checksum
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* odroid-c1: change default loglevel
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* meson: fix odroidc1 boot and create uImage
without uImage the board will not boot
take the already used hack (?) from
general-kernel-odroidn2-current.patch
since KERNEL_IMAGE_TYPE does not work as expected
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* Update targets.conf
* Update targets.conf
* Update targets.conf
* Making a bigger diff
* Removing build_minimal
One can choose what to build, while build targets are defined elsewhere
* Governor interactive n/a
* Updating config
Cause of changes in boot.ini we don't need to worry about size. After few tests, no problems sighted.
Tested running Docker.
* Adjust dev config too
Tested.
* Update odroidc1.conf
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
deleted activation of i2s1 - 1c2240, because it isnt necessary for the corect operation of audio-analog and sound_hdmi
USB isnt affected.
i2s2 is right, because its needed for sound_hdmi 1c22800
User overlays are working fine on this boards (I have already tested on rock64).
Added the possibility to use on rockchip64 based boards.
Changed "if" to "case" to facilitate adding more supported boards.
