From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Vas Dias Date: Thu, 14 Apr 2011 22:56:03 +0000 Subject: Re: why does udev-167 break /lib64/udev/firmware ? Message-Id: <201104142356.05092.jason.vas.dias@gmail.com> List-Id: References: <201104141753.22335.jason.vas.dias@gmail.com> In-Reply-To: <201104141753.22335.jason.vas.dias@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thursday 14 April 2011 22:26:58 Kay Sievers wrote: > > Maybe the libusb message I was seeing was an artefact, but really, why are you using an executable to do a shell script's job ? > > Because we need to encode filenames in that binary. > ever heard of cpio ? the kernel understands that. Why do you need to encode filenames ? surely /sys/devices/.../ etc is "trusted" ? In what way are filenames encoded ? or do you mean "encrypted" - why ? b43 / ssb / /usr/src/linux/drivers/base/firmware_class.c doesn't seem to mention "encoded" or "encrypted" filenames and seem to work fine without any filenames being sent ? Why isn't this "filename encoding" interface to drivers/base/class/firmware* documented anywhere ?