From: Jason Vas Dias <jason.vas.dias@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: why does udev-167 break /lib64/udev/firmware ?
Date: Thu, 14 Apr 2011 22:56:03 +0000 [thread overview]
Message-ID: <201104142356.05092.jason.vas.dias@gmail.com> (raw)
In-Reply-To: <201104141753.22335.jason.vas.dias@gmail.com>
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 ?
next prev parent reply other threads:[~2011-04-14 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 16:53 why does udev-167 break /lib64/udev/firmware ? Jason Vas Dias
2011-04-14 17:13 ` Kay Sievers
2011-04-14 19:03 ` Jason Vas Dias
2011-04-14 19:29 ` Jason Vas Dias
2011-04-14 21:26 ` Kay Sievers
2011-04-14 22:56 ` Jason Vas Dias [this message]
2011-04-14 23:00 ` Kay Sievers
2011-04-24 19:53 ` Matthias Schwarzott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201104142356.05092.jason.vas.dias@gmail.com \
--to=jason.vas.dias@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).