From: Marcel Holtmann <marcel@holtmann.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@suse.cz>,
gregkh@suse.de, Paolo Abeni <paolo.abeni@email.it>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] usbmon: add binary interface
Date: Mon, 16 Oct 2006 12:07:38 +0200 [thread overview]
Message-ID: <1160993258.5498.10.camel@localhost> (raw)
In-Reply-To: <20061011142941.3c599e16.zaitcev@redhat.com>
Hi Pete,
> > Would relayfs be a better choice than debugfs for exporting potentially
> > large quantities of binary data?
>
> I'm sick of mounting them, so for the binary API I was going to
> create a bunch of character devices with a dynamic major.
> With udev, I do not even need to read /proc/devices myself.
>
> Curiously enough, Marcel Holtmann argued for a device because he
> did NOT want to run udev. Funny how that works.
can't remember that I said that. My concern was that distros might not
compile debugfs and so usbmon would have been useless. Some character
devices seems the right approach to me. The only concern with a dynamic
major might be USB debugging in an early time of the boot process, but
that seems to be really rare.
Regards
Marcel
next prev parent reply other threads:[~2006-10-16 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 8:57 [PATCH] usbmon: add binary interface Paolo Abeni
2006-10-11 14:09 ` [linux-usb-devel] " Alan Stern
2006-10-11 19:44 ` Pavel Machek
2006-10-11 20:43 ` Pete Zaitcev
2006-10-11 20:51 ` [linux-usb-devel] " Alan Stern
2006-10-11 21:01 ` Greg KH
2006-10-11 21:29 ` Pete Zaitcev
2006-10-16 10:07 ` Marcel Holtmann [this message]
2006-10-12 8:17 ` [linux-usb-devel] " Duncan Sands
2006-10-12 15:13 ` Pete Zaitcev
2006-10-18 4:48 ` Pete Zaitcev
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=1160993258.5498.10.camel@localhost \
--to=marcel@holtmann.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=paolo.abeni@email.it \
--cc=pavel@suse.cz \
--cc=stern@rowland.harvard.edu \
--cc=zaitcev@redhat.com \
/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