From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>, outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Sat, 18 Mar 2023 16:14:06 +0700 [thread overview]
Message-ID: <ZBWA3rb9nVP8ho05@debian.me> (raw)
In-Reply-To: <20230318084048.GC4434@sumitra.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Sat, Mar 18, 2023 at 01:40:48AM -0700, Sumitra Sharma wrote:
> │ Symbol: NVEC_PAZ00 [=n] │
> │ Type : tristate │
> │ Defined at drivers/staging/nvec/Kconfig:45 │
> │ Prompt: Support for OEM specific functions on Compal PAZ00 based devices │
> │ Depends on: STAGING [=y] && MFD_NVEC [=n] && LEDS_CLASS [=y] │
Hi,
MFD_NVEC depends on ARCH_TEGRA, which requires arm64
(aarch64-*-linux-gnu) cross-compiler. If don't have it yet, you can
build one with crosstool-NG. When the cross-compiler have been successfully
built and installed, add <cross-compiler prefix>/bin to PATH.
Now in order to cross-compile the kernel (to arm64 in this case),
you need to pass `ARCH=arm64 and CROSS_COMPILE=aarch64-<vendor>-linux-gnu-`
to each invocation of `make`.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-18 9:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 8:40 Unable to find module location Sumitra Sharma
2023-03-18 9:13 ` Deepak R Varma
2023-03-18 13:02 ` Sumitra Sharma
2023-03-18 16:08 ` Deepak R Varma
2023-03-19 8:45 ` Sumitra Sharma
2023-03-20 9:19 ` Deepak R Varma
2023-03-20 10:02 ` Sumitra Sharma
2023-03-20 10:16 ` Deepak R Varma
2023-03-20 10:21 ` Deepak R Varma
2023-03-22 4:12 ` Sumitra Sharma
2023-03-18 9:14 ` Bagas Sanjaya [this message]
2023-03-18 12:15 ` Sumitra Sharma
2023-03-18 12:34 ` Bagas Sanjaya
2023-03-18 12:49 ` Sumitra Sharma
2023-03-18 13:01 ` Bagas Sanjaya
2023-03-18 17:57 ` Sumitra Sharma
2023-03-19 2:08 ` Bagas Sanjaya
2023-03-19 8:32 ` Sumitra Sharma
2023-03-19 8:40 ` Julia Lawall
2023-03-19 8:56 ` Julia Lawall
2023-03-19 12:10 ` Sumitra Sharma
2023-03-19 12:36 ` Julia Lawall
2023-03-20 8:46 ` Sumitra Sharma
2023-03-20 8:56 ` Julia Lawall
2023-03-20 8:59 ` Bagas Sanjaya
2023-03-20 9:04 ` Julia Lawall
2023-03-20 9:03 ` Julia Lawall
2023-03-20 9:53 ` Sumitra Sharma
2023-03-20 13:04 ` Julia Lawall
2023-03-22 4:10 ` Sumitra Sharma
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=ZBWA3rb9nVP8ho05@debian.me \
--to=bagasdotme@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=sumitraartsy@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox