Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jul 2019 19:03:47 +0300
From:      Stefan Parvu <sparvu@kronometrix.org>
To:        freebsd-arm@freebsd.org
Subject:   Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0
Message-ID:  <EF94BC84-4B8D-455C-952F-4FD1CC5557CE@kronometrix.org>
In-Reply-To: <d71fc4e3db26242ffa817814d6cd92b8899fc2ab.camel@freebsd.org>
References:  <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <AB510253-52D9-469C-B06E-5EC73C5F188E@kronometrix.org> <fd9991c4e6aaccb812a59ff86c9c8564ebd1d767.camel@freebsd.org> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <c52f9d9ab358ac0dc09af411bf97625945579b4e.camel@freebsd.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <BE321299-8569-4B2E-98FD-FD5210E1B6AF@kronometrix.org> <A9FD7D2B-9382-4EAE-B245-5F4DE643DBB7@gromit.dlib.vt.edu> <C93E2C64-6280-464D-AB5F-B1E968690CEF@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <BD0BE075-9E69-4CB0-826A-5DF2D160E9B1@kronometrix.org> <d71fc4e3db26242ffa817814d6cd92b8899fc2ab.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I copied the ko file under /boot/kernel . I just copied the nxprtc.ko =
nothing else
no linker.hints=20

But does not work. I cannot see the driver after reboot. I have of =
course all things in config.txt.

root@k1:/boot/kernel # kldstat=20
Id Refs Address                Size Name
 1    9 0xffff000000000000  13d1480 kernel
 3    1 0xffff000001415000    40f10 nxprtc.ko
 4    1 0xffff000053600000    41000 tmpfs.ko
 5    1 0xffff000053641000    31000 mac_ntpd.ko
root@k1:/boot/kernel #=20

root@k1:/boot/kernel # dmesg | grep nxp
root@k1:/boot/kernel #=20

> That's why I have been lifelong-skeptical about the whole concept of
> trying to build a single module separate from the kernel.  Maybe it
> mostly works for amd64, but I've never thought it was a safe thing to
> do on arm systems.
>=20
> You might be able to work around it by hand-editing that file and then
> rebuilding the module.  The file will be in
>=20
> =
/usr/obj/arm64.aarch64/usr/src/sys/GENERIC/modules/i2c/nxprtc/opt_platform=
.h

okay. let me try that.

Stefan=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF94BC84-4B8D-455C-952F-4FD1CC5557CE>