From: Deepak R Varma <mh12gx2825@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Julia Lawall <julia.lawall@inria.fr>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Need help building a driver: mt7621-pci
Date: Tue, 20 Oct 2020 09:08:36 +0530 [thread overview]
Message-ID: <20201020033836.GA78621@ubuntu204> (raw)
In-Reply-To: <20201019191803.GV20115@casper.infradead.org>
On Mon, Oct 19, 2020 at 08:18:03PM +0100, Matthew Wilcox wrote:
> On Mon, Oct 19, 2020 at 07:01:50PM +0200, Julia Lawall wrote:
> > On Mon, 19 Oct 2020, Deepak R Varma wrote:
> > > Hello,
> > > I have made a change to drivers/staging/mt7621-pci/pci-mt7621.c file and
> > > now trying to build to ensure the driver builds fine. However, this file
> > > doesn't get included in the build process.
> > >
> > > I tried looking for driver dependencies and am not able to locate RALINK
> > > in my driver tree [in menuconfig] to enable it.
> > >
> > > Can you please suggest what may be wrong here?
> >
> > A colleague of mine, Paul Gazzillo, makes a tool called klocalizer that
> > figures out how to compile Linux kernel files. It suggests:
> >
> > make.cross ARCH=mips olddefconfig; make.cross ARCH=mips clean drivers/staging/mt7621-pci/pci-mt7621.o
>
> It's useful for drivers to build on all architectures by depending
> on COMPILE_TEST. You will probably have to provide a lot of dummy
> interfaces; the only requirement is that the code build, not work,
> since it almost certainly needs to access hardware that only exists on
> the Mediatek platform.
Thank you. Tried a couple of times with different selections however,
not able to get across this error:
make[4]: *** No rule to make target
'drivers/staging/mt7621-pci/pci-mt7621.o'. Stop.
make[3]: *** [scripts/Makefile.build:475: __build] Error 2
make[2]: *** [scripts/Makefile.build:500: drivers/staging] Error 2
make[1]: *** [Makefile:1777: drivers] Error 2
make: *** [Makefile:335: __build_one_by_one] Error 2
It looks like a generic error message and lot of possibilities while I
try to explore it myself. Any quick suggestion on what is wrong will
be time saving.
Thank you,
Deepak.
next prev parent reply other threads:[~2020-10-20 3:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 16:20 Need help building a driver: mt7621-pci Deepak R Varma
2020-10-19 17:01 ` [Outreachy kernel] " Julia Lawall
2020-10-19 17:17 ` Deepak R Varma
2020-10-19 19:18 ` Matthew Wilcox
2020-10-20 3:38 ` Deepak R Varma [this message]
2020-10-20 11:32 ` Matthew Wilcox
2020-10-20 11:52 ` Deepak R Varma
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=20201020033836.GA78621@ubuntu204 \
--to=mh12gx2825@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy-kernel@googlegroups.com \
--cc=willy@infradead.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.
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.