Date: Mon, 18 Mar 2019 20:57:28 +0000 From: Kaya Saman <kayasaman@optiplex-networks.com> To: freebsd-arm@freebsd.org Subject: Re: Options for FBSD support with LCD device - new project Message-ID: <35b3045f-817c-5645-d78b-f20b08671850@optiplex-networks.com> In-Reply-To: <ac7d434f16f3a89f5ef247678d6becdbeded5c3f.camel@freebsd.org> References: <ad61a598-53af-02a5-41db-0128da7d1a34@optiplex-networks.com> <CAF19XBLAjP4yKtGSBzA4QdT346Bnbnr8MutQNZgmERLbJkWAyA@mail.gmail.com> <8df902f6-20a3-31c4-71ac-91f5d5fdf50d@optiplex-networks.com> <0ecf23e129ca7ac6a92a01bbb34c03f1ac8c6dc8.camel@freebsd.org> <e5d42c67-e1f2-ede1-965f-c89226de46da@optiplex-networks.com> <89f5b8d1ab0614ac8d88b5d5f1afc63e640c3c17.camel@freebsd.org> <4EB5C6C1-7DB9-4DEE-BB23-CD1259581271@jeditekunum.com> <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <C68D7E6E-03C1-448F-8638-8BD1717DBF44@jeditekunum.com> <ac7d434f16f3a89f5ef247678d6becdbeded5c3f.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<snip> >>> I'm not sure what would give you that impression about i2c and >>> spi. I >>> belive they're well-supported on virtually every arm SOC we have >>> any >>> support for at all (except maybe amlogic/odroid and exynos, both of >>> which are rapidly bitrootting from neglect). We have command-line >>> tools to read and write data to i2c and spi devices from userland, >>> as >>> well as programmatic interfaces using ioctl() for higher- >>> performance >>> needs like a rasterized spi display. >>> >>> I'm the person who does most of the i2c and spi driver work for all >>> of >>> freebsd (not just arm), and it's something we use heavily in our >>> products at $work, so I tend to stay on top of it. >>> >>> To enable i2c or spi on any given platform, you usually do have to >>> touch some FDT code along the way. That's because almost always, >>> the >>> pins used by i2c or spi can be used for other things as well, so >>> the >>> default config (which we get by importing fdt source code from >>> linux) >>> usually isn't set up to enable those devices. >>> >>> To enable them you typically have to write and compile a small dts >>> overlay and set a variable in /boot/loader.conf to have that >>> overlay >>> loaded at boot time. None of that is hard, but there is quite a >>> bit to >>> explain, more than I can do right here in this email in the middle >>> of a >>> $work day. I guess maybe I should write a wiki page for it. >>> >>> -- Ian >> Finding this thread: https://forum.pine64.org/showthread.php?tid=6232 It seems that there is an official image for pine64 platform: http://ftp.freebsd.org/pub/FreeBSD/releases/arm64/aarch64/ISO-IMAGES/12.0/ Would anyone recommend the Pine64? Also which model as there are several: http://wiki.pine64.org/index.php/Main_Page#PINE64_Devices I could go with A64 or H64, though I wonder if there is a mode basic model out there? I don't need 4k or even HD graphics, or 'desktop' related stuff. A serial console would be fine or even vga just as long as the board is stable and robust and won't crash or hang often. Regards, Kaya
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35b3045f-817c-5645-d78b-f20b08671850>