Hi, Yes, I'm interested in the patch.
Thanks, Graeme. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jesper Smith Sent: Friday, 28 October 2011 04:02 To: [email protected] Subject: Re: [etherlab-users] Problem reading SII configuration from slave Hello, Because the supplier of our slaves told us that their SII information will never fit in the slave (the SII binary is 3kb and the slave only has a 2kb memory location) and we're stuck with 14 of them I've cleaned up the hack to read the SII information from a binary file and made it work in combination with other slaves. If someone is interested I can make a patch to the most recent master code. I've adjusted the fsm_slave_scan state machine to works as follows - Read vendor id + product code from slave - Use the kernels firmware_request to load ec_${vendor_id}_${product_code}.bin /lib/firmware/${uname -r}/ethercat (or whatever path your distribution uses) If firmware is found, use that to load the SII information else read SII information from the slave I think this can be used as starting point for reading XML files. I'm thinking of the following solutions - Make a separate user space program that compiles the XML files to SII binaries and stores them in /lib/firmware - Store the XML file in /lib/firmware and parse it in the master module - Create a separate communication between the kernel and user space that requests slave information from a daemon/udev. Maybe someone on this list can voice their opinion what would be the neatest way to do it. Regards, Jesper _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
