patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Jamie McClymont <jamie@kwiius.com>
Cc: devel@spectrum-os.org
Subject: Re: [RFC PATCH 2/8] chromiumOSPackages.cros_linux: fix config
Date: Fri, 02 Apr 2021 15:35:58 +0000	[thread overview]
Message-ID: <87y2e08zs1.fsf@alyssa.is> (raw)
In-Reply-To: <0100017891d36eab-b33cd88c-2b79-4848-8f7b-29cf7ea42e93-000000@email.amazonses.com>

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

Jamie McClymont <jamie@kwiius.com> writes:

> The ANALOGIX_ANX7625 option no longer exists, but  VIDEO_INTEL_IPU6 is
> now a source of build errors.
> ---
>  pkgs/os-specific/linux/kernel/linux-cros.nix | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/pkgs/os-specific/linux/kernel/linux-cros.nix b/pkgs/os-specific/linux/kernel/linux-cros.nix
> index 789a9fb6fd2..d292fe2c54a 100644
> --- a/pkgs/os-specific/linux/kernel/linux-cros.nix
> +++ b/pkgs/os-specific/linux/kernel/linux-cros.nix
> @@ -29,6 +29,10 @@ buildLinux (args // rec {
>      # Enabling this (the default) caused a build failure.  If you can
>      # archieve a successful build with this enabled, go ahead and
>      # enable it.
> -    ANALOGIX_ANX7625 = no;
> +    VIDEO_INTEL_IPU6 = no;
> +
> +    # RTW88_8822*E were being selected as Y when N/m/? are the only valid options
> +    RTW88_8822BE = lib.mkForce no;
> +    RTW88_8822CE = lib.mkForce no;

What do you think about setting these to "modules" instead of "no"?
It looks like that's what we do in Nixpkgs for more recent kernels that
behave the same way (not allowing Y).

>    } // (args.structuredExtraConfig or {});
>  } // (args.argsOverride or {}))
> -- 
> 2.31.1

Patch LGTM other than that.

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

  reply	other threads:[~2021-04-02 15:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210402090042.2020627-1-jamie@kwiius.com>
2021-04-02  9:04 ` [RFC PATCH 1/8] chromiumOSPackages: update 83->89 Jamie McClymont
2021-04-02 14:58   ` Alyssa Ross
2021-04-02  9:04 ` [RFC PATCH 2/8] chromiumOSPackages.cros_linux: fix config Jamie McClymont
2021-04-02 15:35   ` Alyssa Ross [this message]
2021-04-02  9:04 ` [RFC PATCH 4/8] chromiumOSPackages.common-mk: update patches Jamie McClymont
2021-04-02 15:47   ` Alyssa Ross
2021-04-02  9:04 ` [RFC PATCH 3/8] chromiumOSPackages.vm_protos: drop GN patch Jamie McClymont
2021-04-02 15:53   ` Alyssa Ross
2021-04-02  9:04 ` [RFC PATCH 5/8] chromiumOSPackages.common-mk: disable clang-only warnings Jamie McClymont
2021-04-02 15:54   ` Alyssa Ross
2021-04-02  9:04 ` [RFC PATCH 6/8] chromiumOSPackages.sommelier: drop unneeded patches Jamie McClymont
2021-04-02 16:11   ` Alyssa Ross
2021-04-02 17:28     ` Alyssa Ross
2021-04-02 17:18       ` Thomas Leonard
2021-04-02 21:00       ` [PATCH platform2] Revert "Revert "vm_tools: sommelier: Switch to the stable version of xdg-shell"" Alyssa Ross
2021-04-02  9:04 ` [RFC PATCH 8/8] chromiumOSPackages.crosvm: bump cargoSha256 Jamie McClymont
2021-04-02  9:04 ` [RFC PATCH 7/8] chromiumOSPackages.crosvm: add platform2 dep Jamie McClymont

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

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

  git send-email \
    --in-reply-to=87y2e08zs1.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=devel@spectrum-os.org \
    --cc=jamie@kwiius.com \
    /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://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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 NNTP newsgroup(s).