Re: Patch to add usbmon

[Pete Zaitcev]

On Tue, 01 Feb 2005 12:13:03 +0100, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:

> By accident I removed the debugfs option from my kernel config and this
> makes usbmon totally useless. So I think the module approach is wrong
> from my point of view. Why not compile it always and if debugfs is
> available, then enable it when the usbcore gets loaded?

This may be a good idea, but I'm too lazy to think in trinary. Care to
send a patch?

> And btw don't you think that you split your code into too much separate
> files? I count less than 900 lines of code.

What does it hurt? I think the split was rather clean, along well defined
functional lines, with minimum dependencies. They may even be separate
modules later.

> However it works fine for me, but I can't find a document that describes
> the information (without looking at the code) you get, when running cat
> on a specific bus.

I'm sorry about that. I will add a file in Documentation/ .

> control urb endpoint 0x00 flags 0x00 buflen 3 actlen 0
> bRequestType 0x20 bRequest 0x00 wValue 0 wIndex 0 wLength 3
> pipe 0x80003900 flags 0x00 buffer f7f2e4e0 length 3 setup f64895a0 start 0 packets 0 interval 0
> data 36 fc 00

You are right, the current text format (0t) is not easily readable.

My plan calls for the parsing of control messages and things like SCSI
commands to be placed in user mode applications, like USBMon. This is how
tcpdump and Ethereal operate. I don't like to keep too much of this in
kernel. Do you think it's a wrong approach?

> [...] I think it makes sense to present the device number of that device.

When I read dumps, I mentally fetch the device number from the pipe.
Just use that for now, please.

But if you or someone else were to hack on something like usbdump(1),
it would be peachy, I think.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/