Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Aug 2016 15:43:59 +0200
From:      Bernd Walter <ticso@cicely7.cicely.de>
To:        freebsd-arm@freebsd.org
Cc:        Bernd Walter <ticso@cicely7.cicely.de>
Subject:   out of tree kernel modules (was: compiling modules and FDT define)
Message-ID:  <20160805134358.GN18406@cicely7.cicely.de>
In-Reply-To: <20160805005433.GL18406@cicely7.cicely.de>
References:  <20160805005433.GL18406@cicely7.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 05, 2016 at 02:54:34AM +0200, Bernd Walter wrote:
> I compile a driver as module and it seems that FDT isn't defined
> on a rpi.

When compiling kernel with modules you get an opt_platform.h containing
#define FDT 1

For my out of tree module all I get is an empty file.
I assume that also happens when you just manually compile anything in
sys/modules.

Do I really need to integrate the driver into the kernel source tree
and always compile everything?

The symptoms of missing FDT support is subtile, because everything
may seem to work, the device probing just accepts more devices than
it is supposed to handle.

On a side note, the ofw_bus_is_compatible and ofw_bus_search_compatible
functions are undocumented.
At least they don't have a manpage.
My only option was to blindly copy from another driver, without really
understanding the differences between those two functions.

-- 
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160805134358.GN18406>