From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.4 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 797A1C43331 for ; Mon, 11 Nov 2019 16:41:46 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3B47C2173B for ; Mon, 11 Nov 2019 16:41:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="hlh8/jV4" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3B47C2173B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1iUCkZ-0008C0-Ql; Mon, 11 Nov 2019 11:41:11 -0500 Received: from mail-il1-x141.google.com ([2607:f8b0:4864:20::141]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1iUCkX-0008Bt-EX for kernelnewbies@kernelnewbies.org; Mon, 11 Nov 2019 11:41:09 -0500 Received: by mail-il1-x141.google.com with SMTP id p6so12649452ilp.1 for ; Mon, 11 Nov 2019 08:41:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=cScbM0KF59yJJHKYleBKe43rwUiU6m1d5iDt+bOQ/0U=; b=hlh8/jV475SIgr4DZKK64r5MfmuDqy3LTtWl/tbhPnBDGK+Ew9jbTfEnCSYGsApIF8 oKi37mC8ZBkT0KONIDcgmqT23vmb75fCTR9a/cbj0UVbRUl68TTmNGkvES20lqunp6nm nOkKKD2Ic3Q4P08rO4TfadASg1I4hlhBXJQbfFEhm8XJE5OT4mUGakx5gBH7b+3wr109 J7SjWfVrwV5TzxnZIQEikhaLlvajyTX1myALWbXE6X0HQpNkjcEAnegKlDCYVDZ/gieu 44sbZuziUFUo6L7mqc4ODMksG30uuuUW/LU38FpDyP9Qrz/xREJCtqzwRHm0RlSLqmzS 55QA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=cScbM0KF59yJJHKYleBKe43rwUiU6m1d5iDt+bOQ/0U=; b=Mk7NvldTTiLp13PQTG08nuCYSifMX1//b4PCiJR1Uh/HG4b5x4AZGZXpa+SYweBVia +JTKM3hK1q4fxfuv6k24qTKxukfxVqsXcGj6eO3yyvXP6NLeCPL++SkTnZ40vMYbLIef jAuAnW2fj6p6GVl9uT/gRCEDP4oHlHWqjTkkTXMvpEnLUL1+nXdC8DvMBIgCsoqfaYoE knx4CuB3oHT1wA6232fOJOHntIRCE97xQPL6TQnuw8yPQl16RM05fZYBhFWf/zTKfu58 42wXNHRTcsBIlOQMbEHZE/BvzRXBD8wiuhAbw8ueFKTvZA5UScSnEE+RexFh9yx6ZdF8 yrkg== X-Gm-Message-State: APjAAAVRKT9dfeaTr3UtbxgsPDaoMQ3iKaMj7VIMK3yhm9C5i3+KWfN0 StzSV1ta+bfDjd5Y2DoYFlQTNnU3KQyG4pNXbe5pHQ== X-Google-Smtp-Source: APXvYqwdO6vKyEDSN8n9qczt9NZjI+LiB3lZ+OgKic9ZgFHm6HIVKFPRQH64rDieo8g4yfMY26juw7Adg63+INm5chU= X-Received: by 2002:a92:b70c:: with SMTP id k12mr27015307ili.55.1573490466611; Mon, 11 Nov 2019 08:41:06 -0800 (PST) MIME-Version: 1.0 References: <20191111163131.GB1017642@kroah.com> In-Reply-To: <20191111163131.GB1017642@kroah.com> From: Jeffrey Walton Date: Mon, 11 Nov 2019 11:40:51 -0500 Message-ID: Subject: Re: How to log USB modem data for a specific device? To: Greg KH Cc: kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: noloader@gmail.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Mon, Nov 11, 2019 at 11:31 AM Greg KH wrote: > > On Mon, Nov 11, 2019 at 11:11:06AM -0500, Jeffrey Walton wrote: > > Hi Everyone, > > > > I'm having trouble with a C application that opens a USB modem. The > > application is not receiving some data from a USR modem. Conexant > > modems are OK. > > > > I'm working through > > https://www.kernel.org/doc/Documentation/usb/usbmon.txt . I found the > > modem at Bus=01 Dev=24: > > > > T: Bus=01 Lev=03 Prnt=07 Port=00 Cnt=01 Dev#= 24 Spd=480 MxCh= 0 > > D: Ver= 2.00 Cls=02(comm.) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=0baf ProdID=0303 Rev= 2.00 > > S: Manufacturer=U.S.Robotics > > S: Product=USB Modem > > > > This is where my confusion lies. It is not clear to me how to > > determine which socket to use for step #3 in usbmon.txt. Step #3 says: > > > > # cat /sys/kernel/debug/usb/usbmon/3u > /tmp/1.mon.out > > > > How do I determine which socket to use for Bus=01 Dev=24? > > From the above documentation, it says to use "3u" for all devices on the > 3rd bus. You want the 1st bus, right? So did you try using "1u"? > > I think wireshark can intrepret usbmon output, so maybe just use that > instead and point it at the USB bus you want to watch? Thanks Greg. I want Bus 1, but I want Device 24 (not all devices). Jef _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies