Messages in this thread | | | Date | Tue, 30 Aug 2022 19:21:35 +0100 | From | Mark Brown <> | Subject | Re: [PATCH -next 4/4] spi: mockup: Add documentation |
| |
On Fri, Aug 26, 2022 at 02:43:41PM +0000, Wei Yongjun wrote:
> +The typical use-case is like this: > + 1. load this module > + 2. use bpftool to load BPF program > + 3. load the target chip driver module
This needs to go into a bit more detail on how one is expected to obtain a copy of bpftool I think (or point to some good documentation, I can't seem to find any in tree right now), things may have changed since the last time I looked into this but in the past the userspace tooling for BPF had some extremely ambitious build dependencies which would be a fairly substantial barrier to entry.
> +Compile your copy of the kernel source. Make sure to configure the spi-mockup > +and the target chip driver as a module. Prepare a dts described the spi-mockup > +device.
As I said in another mail the DT part of this appears to be inappropriate, the driver should just allow the creation of virtual devices. [unhandled content-type:application/pgp-signature] | |