All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Julia Lawall <julia.lawall@inria.fr>, outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Mon, 20 Mar 2023 03:02:16 -0700	[thread overview]
Message-ID: <20230320100216.GD126429@sumitra.com> (raw)
In-Reply-To: <ZBglD5yEm2Qb40qf@ubun2204.myguest.virtualbox.org>

On Mon, Mar 20, 2023 at 02:49:11PM +0530, Deepak R Varma wrote:
> On Sun, Mar 19, 2023 at 01:45:20AM -0700, Sumitra Sharma wrote:
> > On Sat, Mar 18, 2023 at 09:38:23PM +0530, Deepak R Varma wrote:
> > > On Sat, Mar 18, 2023 at 06:02:11AM -0700, Sumitra Sharma wrote:
> > > > 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:
> > > > > 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.
> > > 
> > > Did you follow Sanjaya's instruction on cleaning your source directory? Once
> > > that is done, I suggest enabling necessary configurations using the arch
> > > specific config file and then run a full build. Make sure the build is all
> > > successful and the module's .ko file is generated.
> > >
> > 
> > Hi deepak,
> > 
> > Yes I did the cleanup. But I am unable to enable the below driver as
> > module 'M' when running the command 'make menuconfig' or 'make
> > menuconfig ~/git/kernels/staging/arch/arm64/configs/defconfig'. It is
> > because I am not able to locate it under staging drivers.
> 
> what is your Linux distro and host architecture?
>

VM linux distro = Ubuntu 20.04 64-bit version
Host architecture = windows 11 x64

REgards,
SUmitra

> > 
> >   │                                                                                                                  │
> >   │ 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])
> > 
> > > Deepak.
> > > 
> > > > 
> > > > It will be of much help. Thank you.
> > > > 
> > > > Regards,
> > > > 
> > > > Sumitra
> > > > 
> > > > > Deepak.
> > > > > 
> > > > > 
> > > > > 
> > > > > > 
> > > > > >   Regards,
> > > > > >   
> > > > > >   Sumitra
> > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > > 
> > 
> 
> 

  reply	other threads:[~2023-03-20 10: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
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 [this message]
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=20230320100216.GD126429@sumitra.com \
    --to=sumitraartsy@gmail.com \
    --cc=drv@mailo.com \
    --cc=julia.lawall@inria.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.