unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Mark H Weaver" <mhw@netris.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 31447@debbugs.gnu.org
Subject: [bug#31447] [PATCH] linux-libre: Add aarch64-linux.
Date: Thu, 17 May 2018 15:05:35 -0700	[thread overview]
Message-ID: <87vabmsztc.fsf@aikidev.net> (raw)
In-Reply-To: <87d0xu5dgu.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]

On 2018-05-17, Mark H Weaver wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>>> From b9e48a787b6b151b5c7df6036eb75752d3c4db24 Mon Sep 17 00:00:00 2001
>>> From: Vagrant Cascadian <vagrant@debian.org>
>>> Date: Mon, 14 May 2018 03:20:17 +0000
>>> Subject: [PATCH] gnu: linux-libre: Enable build for aarch64-linux.
>>>
>>> * gnu/packages/linux.scm (%linux-compatible-systems): Add aarch64-linux.
>>> * gnu/packages/aux-files/linux-libre/4.16-arm64.conf: New file.
>>
>> I think we should add the .conf file to gnu/local.mk, but apart from
>> that it LGTM.
>>
>> Mark, WDYT?
>
> %linux-compatible-systems is also used as the 'supported-systems' field
> of linux-libre-4.14, but there's no '4.14-arm64.conf' file added here.
> We should either add that file, or else somehow arrange for
> 'aarch64-linux' to be omitted from linux-libre-4.14's
> 'supported-systems' field.

I briefly thought about weather to add support for older kernels, but
figured only adding a new architecture to the current version of
linux-libre would be simpler... guess that requires a little more
patching...


> As Ludovic mentioned, the new .conf file needs to be added to
> gnu/local.mk.

I don't see any of the existing linux-libre/*.conf files added there;
maybe Ludovic meant Makefile.am ?


> Otherwise, it looks good to me.

Since submitting, I did notice that the way .dtb files are installed, it
doesn't preserve the subdirectory structure. Unlike the "arm"
architecture, where .dtb files are all placed in a single directory, on
"arm64" there are sub-directories for each soc family:

  allwinner/sun50i-a64-pine64-plus.dtb

It looks like the linux Makefile supports setting INSTALL_DTBS_PATH
variable, and both "arm" and "arm64" architectures have a "dtbs_install"
target, which may simply do "the right thing".

U-boot on arm64 platforms typically sets a variable "fdtfile" to load,
and so fails to boot without manual intervention. Could work around it
in the bootloader configuration, but I think it would be better to fix
in the linux-libre packages.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-05-17 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  3:40 [bug#31447] [PATCH] linux-libre: Add aarch64-linux Vagrant Cascadian
2018-05-17  8:53 ` Ludovic Courtès
2018-05-17 18:44   ` Mark H Weaver
2018-05-17 22:05     ` Vagrant Cascadian [this message]
2018-05-18  4:38       ` Mark H Weaver
2018-05-18 22:31       ` Vagrant Cascadian
2018-05-19 23:33         ` Vagrant Cascadian
2018-05-20 22:11           ` Ludovic Courtès
2018-05-20 22:26             ` Vagrant Cascadian
2018-05-20 22:12         ` bug#31447: " Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vabmsztc.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=31447@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).