'Twas brillig, and Richard Hughes at 27/11/13 09:31 did gyre and
gimble: Hi all,
I've been porting a lot of the gnome-packagekit functionality to
gnome-software these last few months. One thing that used to work
well, but I've not seen a bugreport about in *years* is the
On Wed, Nov 27, 2013 at 10:31 AM, Richard Hughes hughsi...@gmail.com wrote:
I've been porting a lot of the gnome-packagekit functionality to
gnome-software these last few months. One thing that used to work
well, but I've not seen a bugreport about in *years* is the
On Wed, Nov 27, 2013 at 12:53 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Kay Sievers [2013-11-27 12:47 +0100]:
All of that is gone and will not come back, udev has no idea about
device firmware and does no longer want to know about it. There is no
way to tell these days what firmware was
On Wed, Nov 27, 2013 at 12:53 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Kay Sievers [2013-11-27 12:47 +0100]:
All of that is gone and will not come back, udev has no idea about
device firmware and does no longer want to know about it. There is no
way to tell these days what firmware was
On Wed, Nov 27, 2013 at 1:02 PM, Tom Gundersen t...@jklm.no wrote:
Couldn't the kernel simply log (one of these new fance structured log
messages it now supports) whenever it fails to load a piece of
firmware?
Yes, drivers could explicitly log fatal failures, ones they cannot
recover from
On Wed, 2013-11-27 at 13:11 +0100, Kay Sievers wrote:
It would need a MESSSAGE_ID= and a few key/value pairs with the file
name, the driver name and such to send out. The journal could get a
service activation feature by message id ...
Where does that stand, btw ? Hasn't
On Wed, Nov 27, 2013 at 5:04 PM, Matthias Clasen mcla...@redhat.com wrote:
On Wed, 2013-11-27 at 13:11 +0100, Kay Sievers wrote:
It would need a MESSSAGE_ID= and a few key/value pairs with the file
name, the driver name and such to send out. The journal could get a
service activation feature
