All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Carl Karsten <carl@personnelware.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] firewire: do not expose globally unique IDs in the kernel log
Date: Wed, 21 Dec 2011 00:10:31 +0100	[thread overview]
Message-ID: <20111221001031.539ef397@stein> (raw)
In-Reply-To: <CADmzSSjfFgrAroh8jZfC-q0dNuDgsyoNcUfTik6gBx75zrngFw@mail.gmail.com>

On Dec 20 Carl Karsten wrote:
> grumble.
> 
> I use those guids like so:
> 
> plug in dv cam, dmesg, cut guid to clipboard, run:
> dvgrab -guid (paste)

How about:

	#!/bin/sh
	guid=$(cat /sys/bus/firewire/devices/$1/guid)
	shift
	dvgrab -guid $guid "$@"

To be called as "dvgrab-wrapper fw3 [more dvgrab options]", with fw3 being
the device of your choice, e.g. the one that just scrolled by in syslog.

Or you run "grep . /sys/bus/firewire/devices/*/guid | sed s/\\/guid:/\\t/"
before dvgrab, and you get a list of GUIDs from which you can copy and
paste.

> It also kinda helps me keep track of what devices are misbehaving, but
> this alone isn't very important.
> 
> Any chance of making this configurable?

So far the configuration of the "new" firewire drivers were kept at an
essential minimum, and I am hesitant to add more baroque ones.  I would
rather drop this patch now that there was negative feedback, unless there
is going to be positive feedback as well.
-- 
Stefan Richter
-=====-==-== ==-- =-=--
http://arcgraph.de/sr/

  reply	other threads:[~2011-12-20 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 20:30 [PATCH 0/3] firewire: some simple kernel log changes Stefan Richter
2011-12-20 20:31 ` [PATCH 1/3] firewire: do not expose globally unique IDs in the kernel log Stefan Richter
2011-12-20 20:58   ` Carl Karsten
2011-12-20 23:10     ` Stefan Richter [this message]
2011-12-20 23:42       ` Carl Karsten
2011-12-20 23:43       ` Stefan Richter
2011-12-20 23:50         ` Carl Karsten
2011-12-20 20:32 ` [PATCH 2/3] firewire: ohci: use dev_printk API Stefan Richter
2011-12-20 20:34 ` [PATCH 3/3] firewire: sbp2: " Stefan Richter

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=20111221001031.539ef397@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=carl@personnelware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.