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, URIBL_BLOCKED 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 419FFC43331 for ; Tue, 12 Nov 2019 06:23:25 +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 028BD20674 for ; Tue, 12 Nov 2019 06:23:24 +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="SBI/SvWy" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 028BD20674 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 1iUPZu-0000Dz-FM; Tue, 12 Nov 2019 01:23:02 -0500 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1iUPZr-0000Dt-RZ for kernelnewbies@kernelnewbies.org; Tue, 12 Nov 2019 01:23:00 -0500 Received: by mail-io1-xd32.google.com with SMTP id x21so17457866iol.2 for ; Mon, 11 Nov 2019 22:22:58 -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=hOFoZnHu2QMKIYK9kZlAhAW9S8zzlSMqG4YuCPuQ9sw=; b=SBI/SvWytPvxlM5iyM7nrBJnR55NOsz4rlMTP4RdEgnx1GCdPZ+2QauT4UV071G2zw k73lf9OLOp+ZYAnbOZiisLGHrlS9Vd6mGEFl8/O+JxCv4xlC3iiImspB1UkhXDK+L5ur 1J3qL1PhxQHDAJ8s6poX3nQrUAsaO2nKHhpasOB/NoOd9g6KAkA30HGufBEY6uMr0aUF SxXNkXRumJdxG+qXTROND0axl/E8oGwJVJYUgqfyYQs33btUuV0X8p6dBAMol6iY0MCZ hu/tVEhwr7cVJ3MJdTx3DpKFrQA1ep+c+rIzh4p0E1mXPlbcnsXCiCkjYT334z8OTwAM WkmQ== 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=hOFoZnHu2QMKIYK9kZlAhAW9S8zzlSMqG4YuCPuQ9sw=; b=eVucC8GaJg+GjC6UMVmfJDsDoFTZLCEp0pZJ9wxNq+LqfnOKfu+iy+1bcB+f1ZMhqk 2jtkjNuxZAmOvLR2xJ3ZNrinf/WKPPiH31YQP+2AshVFybzLj4Iv1QMKJQw15uLrSKp2 zqp80bGv4XxKDzbw7ToNAHwC0+woC4U1TRSNcOIKX8vGgPalg51lSbl83WDOSkVRERdz t02/1K/XnpMb8sBzFt8tcA5g4m1oqios5SI7hCUU+aKEh8Z00cdC+XECYW4GFSoOQiA5 0f8XpdUVUkGS7whC8fN6p4bUIyhENp0rz2qaCAwxOp0dyxm9jLOPlTsUBYS6GSP/3kRn 2Acg== X-Gm-Message-State: APjAAAX3FEI5FEjMsSCSdh07RGnC6zbAC2Bp7ZbaaJULEuitKSgYdO80 ulwLVEd8Fr7FRA/3+jawM5j90lUXu35v7EhOQ23qTQ== X-Google-Smtp-Source: APXvYqx+lygWpqAQ25jAbtY2a8GpDCB5BL/8bxR5LzegduCqj+41ue87+dbukQU49sdkym0QsOuC7roWX8NoBltXmx0= X-Received: by 2002:a02:aa0c:: with SMTP id r12mr4320643jam.75.1573539717919; Mon, 11 Nov 2019 22:21:57 -0800 (PST) MIME-Version: 1.0 References: <20191111163131.GB1017642@kroah.com> <20191111172442.GC1077444@kroah.com> <20191112053754.GB1210104@kroah.com> In-Reply-To: <20191112053754.GB1210104@kroah.com> From: Jeffrey Walton Date: Tue, 12 Nov 2019 01:20:43 -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 Tue, Nov 12, 2019 at 12:37 AM Greg KH wrote: > ... > > > Here's why I want to specify a device number: > > > > $ cat /sys/kernel/debug/usb/devices | grep -i -c 'Bus=01' > > 13 > > > > It is too much information for me to sift through. I'll do it if I > > have to, but I prefer the tools do the work for me (rather than me do > > the work of the tools). > > That explains why you only want one device's data, but does not answer > why you want that data at all :) I have a pet project like NoMoRobo. It is essentially a call blocking service that depends on Caller ID. My pet project takes things a step further by initiating a call trace on suspicious numbers, and also files FCC and FTC complaints. The program works well with Conexant, Accura/Hayes and MultiTech modems. The program chokes on USR modems. For USR I get the RING message, but not the Caller ID information. From my program's perspective, it looks like the Caller ID information is never sent. So I want to perform some low level traces to understand why I am mishandling things. The GNU screen program receives the information as expected. The problem is, GNU screen does not show me individual messages. I don't know where one message ends and another begins. (One of my theories is the USR modem is batching RING and Caller ID into a single message). Jeff _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies