Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Deepak R Varma <drv@mailo.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Sat, 18 Mar 2023 06:02:11 -0700	[thread overview]
Message-ID: <20230318130211.GB39892@sumitra.com> (raw)
In-Reply-To: <ZBWAsdC5UOEkbedF@ubun2204.myguest.virtualbox.org>

On Sat, Mar 18, 2023 at 02:43:21PM +0530, Deepak R Varma wrote:
> On Sat, Mar 18, 2023 at 01:40:48AM -0700, Sumitra Sharma wrote:
> > Hi,
> > 
> > I was trying to recopmile the driver using the command "make menuconfig".
> > This opens the text-based UI and I wanted to locate and make NVEC_PAZ00
> > as a module whose location is as follows:
> > 
> >   │                                                                                                                  │
> >   │ 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]                                                   │
> >   │   Location:                                                                                                      │
> >   │     -> Device Drivers                                                                                            │
> >   │ (3)   -> Staging drivers (STAGING [=y])                                                                          │
> >   │         -> NV Tegra Embedded Controller SMBus Interface (MFD_NVEC [=n])                                          │
> >   │           -> Support for OEM specific functions on Compal PAZ00 based devices (NVEC_PAZ00 [=n])
> > 
> >   But under "Staging drivers" there is no such thing called "NV Tegra Embedded Controller SMBus Interface (MFD_NVEC [=n])".
> > 
> >   --- Staging drivers                                                                       │ │
> >   │ │                    < >   RealTek RTL8192U Wireless LAN NIC driver                                            │ │
> >   │ │                    < >   Support for rtllib wireless devices                                                 │ │
> >   │ │                    < >   Realtek PCI-E Card Reader RTS5208/5288 support                                      │ │
> >   │ │                    < >   Silicon Motion SM750 framebuffer support                                            │ │
> >   │ │                    [*]   Media staging drivers  ----                                                         │ │
> >   │ │                    < >   GCT GDM724x LTE support                                                             │ │
> >   │ │                    < >   Support for small TFT LCD display modules  ----                                     │ │
> >   │ │                    < >   KeyStream KS7010 SDIO support                                                       │ │
> >   │ │                    <M>   Pi433 - a 433MHz radio module for Raspberry Pi                                      │ │
> >   │ │                    < >   Fieldbus Device Support  ----                                                       │ │
> >   │ │                    <M>   QLogic QLGE 10Gb Ethernet Driver Support                                            │ │
> >   │ │                    [*]   VME bridge support  --->
> >   
> > 
> >   Kindly guide me through this.
> 
> Hi Sumitra,
> You will need to use a arch specific config file and cross compile to configure
> and build this driver module.
> I just tried it with arch/arm64/configs/defconfig file and the
> aarch64-linux-gnu- compiler for my host system and was able to configure the
> driver for build.
>

Hi deepak,

Can you tell me command you are using because when adding the
arch/arm64/configs/defconfig file. I am receiving the invalid options
error.

It will be of much help. Thank you.

Regards,

Sumitra

> Deepak.
> 
> 
> 
> > 
> >   Regards,
> >   
> >   Sumitra
> > 
> > 
> 
> 

  reply	other threads:[~2023-03-18 13:02 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 [this message]
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
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=20230318130211.GB39892@sumitra.com \
    --to=sumitraartsy@gmail.com \
    --cc=drv@mailo.com \
    --cc=outreachy@lists.linux.dev \
    /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