On Tue, 2011-01-18 at 14:25 -0500, Daniel Dickinson wrote: > On Mon, 17 Jan 2011 23:01:36 -0800 > Philip Prindeville <philipp_s...@redfish-solutions.com> wrote: > > > On 1/17/11 1:17 AM, Imre Kaloz wrote: > > > On Mon, 17 Jan 2011 10:15:19 +0100, Philip Prindeville > > > <philipp_s...@redfish-solutions.com> wrote: > > > > > >> The soloscli utility is useful for setting parameters on the FPGA > > >> that aren't accessible via module parameters. > > >> > > >> It doesn't do much good to have the kernel driver without this > > >> utility. > > > > > > Sure, but a kernel module should never depend on a userspace > > > program. Make it the other way around, and include it in the > > > profile. > > > > > > Imre > > > > Thinking about this some more... The Solos chips come on a PCI card, > > so any device with a PCI slot could have the solos card as well (the > > Geos happens to have it on the SBC). > > > > So I could build a net5501 (which has PCI) with the kmod-solos and > > still forget to include soloscli. > > > > It would be nice to specify that all solos h/w support also pulls in > > the soloscli user utility. > > Sorry Philip, I've been talking about it with the other devs the change > has been reverted. This is really a user knowledge issue, not a true > dependency (conceivably other userspace tools could be created and used > as well). In addition it creates a circular dependency because the > soloscli already depends on the module. > > The real answer here to educate users or fix the driver. >
The most common attributes are available through sysfs: /sys/class/atm/solos-pci0/parameters/.. The driver is definitely usable without soloscli. If you need more attributes through sysfs, they can be added to solos-attrlist.c. Regards, Nathan _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
