* [Buildroot] Compiled in kernel drivers.
@ 2020-10-02 13:31 LWATCDR
2020-10-06 18:55 ` Arnout Vandecappelle
0 siblings, 1 reply; 2+ messages in thread
From: LWATCDR @ 2020-10-02 13:31 UTC (permalink / raw)
To: buildroot
I have written a driver that must be compiled into the kernel. It can not
work as a loadable. It is in my br_external and I have changed the make
file to make it build in the kernel. vs a loadable. The problem is that it
just does not seem to work in build root. Does anyone know how to make it
work? I can get it to build and work as a loadable but only if I remove
some needed functionality so it must be compiled into the kernel. It works
just fine if I copy it into the drivers folder of the kernel and do a
traditional kconfig kernel build. also does anyone know how to search the
mailing list? I did not see a search. .
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20201002/c0678f2e/attachment.html>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] Compiled in kernel drivers.
2020-10-02 13:31 [Buildroot] Compiled in kernel drivers LWATCDR
@ 2020-10-06 18:55 ` Arnout Vandecappelle
0 siblings, 0 replies; 2+ messages in thread
From: Arnout Vandecappelle @ 2020-10-06 18:55 UTC (permalink / raw)
To: buildroot
Hi LWATCDR,
On 02/10/2020 15:31, LWATCDR wrote:
> I have written a driver that must be compiled into the kernel. It can not
> work as a loadable. It is in my br_external and I have changed the make
> file to make it build in the kernel. vs a loadable.
AFAIK there is no way with the kernel build system to have an out-of-tree
module built into the kernel binary, so how did you do this?
> The problem is that it
> just does not seem to work in build root. Does anyone know how to make it
> work? I can get it to build and work as a loadable but only if I remove
> some needed functionality so it must be compiled into the kernel. It works
> just fine if I copy it into the drivers folder of the kernel and do a
> traditional kconfig kernel build.
That's the only way to do it AFAIK: patch the kernel itself.
The normal approach would be to make a git clone of the kernel, make your
modifications in it, push it somewhere, and then refer to that one as
BR2_LINUX_KERNEL_CUSTOM_GIT.
> also does anyone know how to search the
> mailing list? I did not see a search. .
The mailing list archive on buildroot.org is pretty primitive. People usually
use a plain web search engine, or marc.info or nabble.org.
Regards,
Arnout
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-10-06 18:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-02 13:31 [Buildroot] Compiled in kernel drivers LWATCDR
2020-10-06 18:55 ` Arnout Vandecappelle
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.