From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: userspace firmware load fails with current linux-next
Date: Wed, 23 Oct 2013 11:06:18 +0200 [thread overview]
Message-ID: <20131023110618.7bd07899@ipc1.ka-ro> (raw)
Hi,
with the current linux-next loading firmware from userspace fails
because when writing to /sys/class/firmware/*/data the return code is
always 0 (meaning to the userspace too that no data was written).
Thus the userspace tool (mdev) keeps writing the same block of data
over and over again.
A cursory check of the latest updates to /drivers/base/firmware* didn't
reveal anything that could be the cause of this misbehaviour.
Interestingly when changing the .size member of the
struct bin_attribute firmware_attr_data in drivers/base/firmware_class.c
(which is now '0') to e.g. PAGE_SIZE firmware loading works again.
Since .size was at '0' since the beginning of the .git universe there
must have been a fundamental change in the guts of the kernel handling
sysfs attribute files.
Is this behavioural change intended?
Do all sysfs attributes that are created with zero size need to be
changed?
Or is it an unintended side effect of some recent change?
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
next reply other threads:[~2013-10-23 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 9:06 Lothar Waßmann [this message]
2013-10-23 10:26 ` userspace firmware load fails with current linux-next Ming Lei
2013-10-23 10:43 ` Lothar Waßmann
2013-10-23 10:48 ` Ming Lei
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=20131023110618.7bd07899@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=linux-arm-kernel@lists.infradead.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