From owner-freebsd-usb@freebsd.org Sun Oct 1 22:06:22 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15542E2FB1B for ; Sun, 1 Oct 2017 22:06:22 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BABDE70CE0; Sun, 1 Oct 2017 22:06:21 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-vk0-x243.google.com with SMTP id b5so350361vkf.1; Sun, 01 Oct 2017 15:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=a4NctLZGbGfhxivAHL0HxbwjpJCAe5nIOdf78tDkK+8=; b=bC2B7GNxhVF2K/ULfcdB3j88P/bE3lqTv//BrgNkqUtKon/hCBayJjfANUg9m10ZZB 3t7AfuveZ1bM9L/LL7YBQx4j37ct1KpRd3kbSus1DoDQw2G4yErZtu6Ky4Pkn0IM6yPR 5D9qp0/YK7FJoIMuxqxNt88H3fsXgc5lpQq0P3YrqAJHJxGKU2rNgUT3bLgLvKeeAnXp KnA9Z9iNW+1+FPAtU8K/PqSxWk6YQE7s3CE9WwJ+8XHT1jVS/OTSioxoo6rndroCwPIy mcLDwNZYPkt+VTd+aKHPO4bZCzU0mGRU+8NssJvQd7TsvoTNWmxSndzsy9y1+ASi4LEG kKHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=a4NctLZGbGfhxivAHL0HxbwjpJCAe5nIOdf78tDkK+8=; b=MTi4ox5SWlMpayKot4hn669lnVz6Lr9Fq8Sl5d0lyRmDngRSjwwFumpwW71z/ls4R7 3TKAthehcsjusUlYJ8QpHH3vZbMtmyIbAAf3scHZzpRNPca2Q3swkPW2xaF05VprG7D9 k8ccoBE2WsrmkSXRYrDGqzSvzRVV3QxgsSjqP7o5d+ig2+wN79HGUO99re7kPN0A5WaC A5KaUJx+tl8+hujQkda9EYO26OSdRa8+nNW/JltxIWKpblwowXbzxaVSCeeodyKB5NFT 5to1KjLpuJRUoBbeGLLExzj7AccAg2ESuIC0p/A5nbgdxheEjFn+E4cgzGYwYVorMjKw MFRg== X-Gm-Message-State: AHPjjUjASEr3GP8KDEe3tQiHeXzR/tk8ACL/W4CNPpxTzX10Xd+u2dqd XbXEpb5qr96MYm2o1ThBQC9d7lITOETkQnMd/nRxDSpN X-Google-Smtp-Source: AOwi7QBUEDCTwYwA6sryU09XtizPq/6IOr5pUz4nTX8a7l6P0pIHGyxkjYcPGQsvmqI0OPmc25xp+pwsfYZoD3bJXAk= X-Received: by 10.31.167.71 with SMTP id q68mr7085926vke.49.1506895580433; Sun, 01 Oct 2017 15:06:20 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.159.53.237 with HTTP; Sun, 1 Oct 2017 15:05:59 -0700 (PDT) In-Reply-To: <1506891559.22078.50.camel@freebsd.org> References: <1506465459.73082.168.camel@freebsd.org> <165556bc-c011-bebd-feee-5bbd4cb5943e@selasky.org> <1506876055.22078.24.camel@freebsd.org> <87d62aba-0b35-8b20-cf1f-9fd2de2d301a@selasky.org> <1506882193.22078.32.camel@freebsd.org> <1506886709.22078.43.camel@freebsd.org> <1506891559.22078.50.camel@freebsd.org> From: Tomasz CEDRO Date: Mon, 2 Oct 2017 00:05:59 +0200 X-Google-Sender-Auth: qUI_fx0dsjKMLLxxZLpFUa0AQL0 Message-ID: Subject: Re: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module To: Ian Lepore Cc: Hans Petter Selasky , "freebsd-usb@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 22:06:22 -0000 On Sun, Oct 1, 2017 at 10:59 PM, Ian Lepore wrote: > On Sun, 2017-10-01 at 22:20 +0200, Tomasz CEDRO wrote: >> On Sun, Oct 1, 2017 at 9:38 PM, Ian Lepore wrote: >> > >> > On Sun, 2017-10-01 at 20:59 +0200, Tomasz CEDRO wrote: >> > > >> > > On Sun, Oct 1, 2017 at 8:23 PM, Ian Lepore >> > > wrote: >> > > > >> > > > >> > > > On Sun, 2017-10-01 at 20:17 +0200, Tomasz CEDRO wrote: >> > > > > >> > > > > >> > > > > [...old stuff...] >> > > I have verified on uath device (more on that below) and it turns >> > > out >> > > $cdev works fine.. but it returns /dev/usb/X.Y.Z not the >> > > /dev/cuaU0 >> > > which does not work with this "gobi_loader" utility which >> > > requires >> > > /dev/cuaU0 (CDC / serial port device)... any clues how to replace >> > > $cdev with cuaUX? :-) >> > > >> > > Regarding the UATH, I have TP-LINK TL-WN822N Ver2.0 based on >> > > Atheros >> > > 9002[1] and it seems to work with modified /dev/devd/uath.conf >> > > but >> > > the >> > > uathload returns "Operation not permitted" when executed as root >> > > and >> > > during boot.. >> > > >> > > [1] https://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2 >> > > >> > Hmmm. I think we need to key off the tty 'attach' event instead of >> > the >> > devfs 'create' event. The tty attach for a usb device is the one >> > event >> > that has all the info we need in one message. This is assuming the >> > device name in dmesg on attach is u3g0 or u3g1 or whatever. >> > >> > attach 100 { >> > device-name "(u3g)[0-9]+"; >> > match "vendor" "0x04da"; >> > match "product" "0x250e"; >> > action "/usr/local/bin/gobi_loader /dev/cua$ttyname >> > /boot/firmware/gobi/"; >> > }; >> > >> > The way I arrived at this conclusion was to first look in the devd >> > source to figure out/remind myself that devd creates variables from >> > all >> > the tag=value tuples it finds in the events coming from the kernel. >> > Then I connected to devd using netcat so I could watch the events >> > as >> > they happen: >> > >> > nc -U /var/run/devd.pipe >> > >> > then I plugged in a usb-serial adapter (I have no u3g stuff), which >> > creates a whole lot of events. The last one was the tty attach: >> > >> > +uplcom0 at bus=1 hubaddr=1 port=1 devaddr=2 interface=0 >> > ugen=ugen1.2 >> > vendor=0x067b product=0x2303 devclass=0x00 devsubclass=0x00 >> > devproto=0x00 sernum="" release=0x0300 mode=host intclass=0xff >> > intsubclass=0x00 intprotocol=0x00 ttyname=U0 ttyports=1 on uhub1 >> > >> > The '+' means it's an attach, the "device-name" variable is set >> > from >> > the space-delimited word after the +, and then vars are created >> > from >> > all the tag=value tuples between 'at' and 'on'. So that gives us >> > the >> > info to match product and vendor, and ttyname is the suffix to >> > append >> > to /dev/cua to make the cdev name. >> > >> > -- Ian >> Awsome! That works!! Thank you Ian!! Thank you for pointing out how >> that was achieved! :-) >> >> Is there any way to echo something out to the console to notify user >> that firmware is being updated? This takes some time and it would be >> nice to see something happens in the background.. I cannot see >> anything with action "logging blah"; maybe no need for that? >> > > I think you can use logger(1) in the action, like: > > action "logger -p kern.crit Loading firmware to cua$ttyname ; > /usr/local/bin/gobi_loader etc etc" > > The 'kern.crit' should be a high enough priority to ensure it comes out > on the console, but it depends on syslog.conf of course. If > gobi_loader outputs a nice message it could be piped to logger(1) > instead of putting the message in the command. > > -- Ian Logger works with syslog which is loaded after modules and firmware, this is why I could not see the message.. but additional action with /bin/echo seems to do the job :-) Thank you guys! You are the best! FreeBSD ROX!!! =) https://github.com/freebsd/freebsd/pull/115 -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info