Rick Mann <rmann@...> writes:
>>> remoteproc just loads the firmware and set's up the initial
>> Is the fact that my dmesg showing a failure to load firmware a
problem? I thought the way you used the PRU was
to load the firmware you wrote at the time you want to use it.
> That's firmware for your to create. If you copy your pru firmware to
> /lib/firmware/ with those two file names it'll load it..
>> I've enable CONFIG_UIO_PRUSS in the kernel you had me build a while
back (dealing with the USB audio
issues), and am re-building that. Hopefully I won't completely bork
what I have going on.
> I thought i had that enabled in v3.14.x
Doesn't seem like it:
$ ./scripts/config --state CONFIG_UIO_PRUSS
Also, I tried enabling it, then re-ran the fakeroot make command (with
a new local version name), and tried
installing those .debs, but I still don't have a uio_pruss module or
the /dev/uio devices. I actually used
--enable, not --module, so I didn't expect it to build a module, but I
don't have /dev/ui*, so I'm not sure
what I'm supposed to do.
I then tried changing the config to --module, re-ran the fakeroot
make, but I still didn't get a module
built. Then I checked the state again, and it's "undef" again.
Something is unsetting it?
I am experiencing the same problems with PRU on 3.14 kernel. Has some
progress been made? Thanks