[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131023110618.7bd07899@ipc1.ka-ro>
Date: Wed, 23 Oct 2013 11:06:18 +0200
From: Lothar Waßmann <LW@...O-electronics.de>
To: linux-kernel@...r.kernel.org
Cc: Ming Lei <ming.lei@...onical.com>,
linux-arm-kernel@...ts.infradead.org
Subject: userspace firmware load fails with current linux-next
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@...o-electronics.de
___________________________________________________________
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists