Date: Sat, 14 Jan 2012 11:45:05 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: Mykhaylo Yehorov <yehorov@gmail.com> Cc: freebsd-gnats-submit@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/164090: [umodem] [patch] Add sysctl with ucom unit number Message-ID: <201201141145.05813.hselasky@c2i.net> In-Reply-To: <CAH=XtiS%2B%2BMncwZoMgtj3aXB4tV%2BSgPQe=gRkX%2Bev6FQgRKHt=w@mail.gmail.com> References: <201201131705.q0DH5Tko030020@red.freebsd.org> <201201132154.01815.hselasky@c2i.net> <CAH=XtiS%2B%2BMncwZoMgtj3aXB4tV%2BSgPQe=gRkX%2Bev6FQgRKHt=w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 14 January 2012 10:51:07 Mykhaylo Yehorov wrote: > On Fri, Jan 13, 2012 at 22:54, Hans Petter Selasky <hselasky@c2i.net> wrote: > > Hi, > > > > Could you patch ucom_set_pnpinfo_usb() instead, so that such a sysctl is > > created for all ucom devices, not only umodem? > > I guess it will be necessary to remove a sysctl oid from a parent > sysctl tree before destroying ucom structures. > It's would be better to do in ucom_detach() but now there is no a > pointer to a parent device structure from there. > > Now all drivers that use ucom pass a pointer to parent softc structure > to ucom_attach(). > Is there any reason for this? > May be it's would be more useful to pass a pointer to a parent device > structure. > > > Can you explain a bit more how you use this information in your scripts? > > I've got a gps receiver and a mobile phone that supported by the umodem > driver. I can attach its in any order. > So I use sysctl to generate gpsd and ppp configs with appropriate > values of serial port. Ok, I see. And you cannot use the information passed through devd by ucom_set_pnpinfo_usb()? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201141145.05813.hselasky>