| Age | Commit message (Collapse) | Author |
|---|
|
Cleanup the package directory which is always used as intermediate step
to build in the default some xz compressed archives with all package
data. While reconfiguring the kernel mini.config or custom config
changes to the firmware did not happen always.
Some targets where redundant and the install step tries to compile, too.
Be more quiet with any cpio usage.
|
|
|
|
Most important is the fix in patch-src_journal_journald-server_c,
which breaks startup of systemd-journald when code is compiled
with -DNDEBUG.
A lot of base-files reorganizing to only install required files
on sysv systems.
|
|
Signed-off-by: Mario Haustein <mario.haustein@hrz.tu-chemnitz.de>
|
|
|
|
|
|
The new prereq check is completely implemented in
POSIX shell in scripts/prereq.sh.
It combines the old features from Makefile, scan-tools.sh,
scan-pkgs.sh, reloc.sh and some wrappers for tools.
The big benefit is to have all portability stuff in one place.
Furthermore we can compile GNU make and bash on the fly, for
systems lacking the required tools.
All changes on the host are detected on the fly, no make
prereq required anymore.
The build process is separated in following three phases:
1. small wrapper Makefile is used for BSD make or GNU make
2. prereq.sh is called, doing all checking, calling Makefile.adk
3. old logic in Makefile.adk or mk/build.mk is used
Tested successfully on Linux, MacOS X, Cygwin, FreeBSD, OpenBSD
and NetBSD.
An old depmaker bug was fixed, only optional host tools are compiled.
For example, even when a host provides xz, a local xz was compiled
in the past, because other packages had a build dependency on it.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
This reverts commit fba2ff31928b18364c1934654169806f5c800e23.
|
|
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
We do not need to manually set mini.config file anymore.
Every target system, even Qemu emulating different models get
it its own. Cleaner and simpler to add new targets.
|
|
|
|
|
|
Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
|
|
Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
|
|
Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
|
|
via serial console
|
|
The prepared kernel config wasn't copied to it's final place.
|
|
|
|
The Linux kernel can output messages to serial devices and
vga devices in parallel. The latest console= entry decides which
console output is used for init via /dev/console character device.
Let the developer configure what he wants. If you use f.e. Kodi,
be sure output/input is used for VGA, other wise kodi startsup,
but you end up with a black screen.
|
|
|
|
|
|
|
|
|
|
Use one place and not hard coded for each device.
There exist use cases where on a specific device
like raspberry pi, not the default 115200 baud rate
is used.
|
|
The Kernel need a trailer to be recognized as a device-tree
kernel. The overlay dir is called /boot/overlays.
Now my driver works fine.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to avoid namespace collisions in some packages, rename TOPDIR.
Sorry you need to make cleandir && make prereq && make
|
|
|
|
text after building
|
|
|
|
|
|
- always use /sbin/init, even for initramfs
- mount devtmpfs for initramfs automatically in kernel space
- fix armhf for adk-test-framework
- remove mdev -s on boot, I think it is unneeded, takes very long on
Qemu systems
- add alias for ro/rw remounts of /
- remove old /init and rc.shutdown, both unused
|
|
|
|
only miniconfig is used for all targets.
aranym support is still broken/experimental.
32 bit kernel support for 64 targets need to be fixed.
tested on usb boot on ibm-x40
|
|
not satisfying.
|
|
squashfs and jffs2 rootfs for qemu-microblaze, add support for both machine emulations
|
|
to new autotool infrastructure
|
|
dependency to libtirpc, disable inetd, add preliminary multilib support (not working right now),enable 32/64 bit kernel support for x86_64
|
|
|
|
This is more commonly known as 32bit userland support on 64bit
architectures.
For simplicity's sake though, this implementation works the other way
round: just build a 64bit-able linker and compiler, but no
64bit-libraries at all (i.e., no multilib). This is then just enough to
compile a 64bit kernel, as that doesn't link to anything. The
alternative would have been to build a native 64bit compiler with
multilib-support in order to cross-compile a 32bit userland, resulting
in a multilib system without need for it.
In order to allow compilation of a 64bit kernel for a given target
system, have it select ADK_TARGET_KERNEL_MAY_64BIT. Upon selection of
that target, the symbol ADK_64BIT_KERNEL will occur in the "Global
settings" menu. Since certain aspects of the 64bit kernel .config may
greatly differ from it's 32bit counterpart, it has to be shipped
separately: target/<arch>/kernel64.config is the place to be.
Conflicts:
target/Makefile
toolchain/gcc/Makefile
Untested, due to conflicts (original patch conflicts with
multiple kernel version support).
|
|
|
|
|
|
|
|
|
