Re: Where is this device attached?
Jonathan, this looks promising. David Coppa had said It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1 The dmesg now shows: moscom0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 ucom0 at moscom0 portno 0 How do I relate this to a filename? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
See ucom(4) man page. Short answer: /dev/ttyU0 (ucom? should match up with /dev/ttyU?) -Adam On March 24, 2014 12:58:20 PM CDT, John Long codeb...@inbox.lv wrote: Jonathan, this looks promising. David Coppa had said It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1 The dmesg now shows: moscom0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 ucom0 at moscom0 portno 0 How do I relate this to a filename? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Where is this device attached?
John Long codeb...@inbox.lv wrote: Jonathan, this looks promising. David Coppa had said It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1 The dmesg now shows: moscom0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 ucom0 at moscom0 portno 0 How do I relate this to a filename? That would be /dev/ttyU0 and /dev/cuaU0 as the FILES section of ucom(4) shows. It is always a good idea to read device manual pages, as they usually contain a lot of helpful information. - Martin
Re: Where is this device attached?
On Mon, Mar 24, 2014 at 01:23:32PM -0500, Adam Thompson wrote: See ucom(4) man page. Short answer: /dev/ttyU0 (ucom? should match up with /dev/ttyU?) -Adam Thank you! /jl
Re: Where is this device attached?
On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: It seems this needs a new driver, here is a quick test that modifies an existing one that might work: snip Your patch works great. Kermit is talking to the device. Thank you so much for the help! /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On Fri, Mar 21, 2014 at 02:50:17PM +1100, Jonathan Gray wrote: On Thu, Mar 20, 2014 at 04:33:01PM +, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? You need to build and install a new kernel. After checking out the src tree via cvs and saving the patch to a file. cd /usr/src/sys/dev/usb patch -p0 /path/to/file then build and install a kernel as described in http://www.openbsd.org/faq/faq5.html#BldKernel Thanks. I didn't know how much of the system had to be rebuilt to get your changes in. It takes a full day or more to rebuild the kernel and userland on this box, so knowing I only have to rebuild the kernel will be a big help. I'll get back to you. Thanks a lot, Jonathan! /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Where is this device attached?
Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 and the usbdevs -vd output is Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x1022), rev 1.00 uhub0 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x1022), rev 1.00 uhub1 port 1 powered port 2 powered port 3 addr 2: full speed, power 50 mA, config 1, HPx9G+ Device(0x0121), HP Company(0x03f0), rev 1.00 ugen0 port 4 powered How do I correlate this info to a /dev filename so I can tell Kermit which line to open? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote: Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 Is this a usb-to-serial thingie? If this is the case, then it's not properly recognized by the kernel. It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1
Re: Where is this device attached?
David- sorry, I meant to reply to the list, here it is again for public consumption with the topic threading borked, probably. On Thu, Mar 20, 2014 at 04:14:13PM +0100, David Coppa wrote: On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote: Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 Is this a usb-to-serial thingie? I don't think so, but I don't know if it is a standard USB device either. It comes up as /dev/ttyUSB0 on that _other_ OS and will talk to Kermit but I can't get it working on OpenBSD yet. I would prefer to use it with the Loongson box if possible. If this is the case, then it's not properly recognized by the kernel. It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1 Any other ideas? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 03:31:37PM +, John Long wrote:
David- sorry, I meant to reply to the list, here it is again for public
consumption with the topic threading borked, probably.
On Thu, Mar 20, 2014 at 04:14:13PM +0100, David Coppa wrote:
On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote:
Hi,
I am trying to use a USB device with a Loongson 5.3 stable box.
The line from dmesg for the device is
ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2
Is this a usb-to-serial thingie?
I don't think so, but I don't know if it is a standard USB device either.
It comes up as /dev/ttyUSB0 on that _other_ OS and will talk to Kermit but I
can't get it working on OpenBSD yet. I would prefer to use it with the
Loongson box if possible.
If this is the case, then it's not properly recognized by the kernel.
It should expose a ucom*, e.g.:
ucom0 at uftdi0 portno 1
Any other ideas?
It seems this needs a new driver, here is a quick test that modifies
an existing one that might work:
Index: moscom.c
===
RCS file: /cvs/src/sys/dev/usb/moscom.c,v
retrieving revision 1.19
diff -u -p -r1.19 moscom.c
--- moscom.c15 Nov 2013 08:25:30 - 1.19
+++ moscom.c20 Mar 2014 16:01:34 -
@@ -150,17 +150,17 @@ int moscom_cmd(struct moscom_softc *, in
struct ucom_methods moscom_methods = {
NULL,
- moscom_set,
- moscom_param,
NULL,
- moscom_open,
+ NULL,
+ NULL,
+ NULL,
NULL,
NULL,
NULL,
};
static const struct usb_devno moscom_devs[] = {
- { USB_VENDOR_MOSCHIP, USB_PRODUCT_MOSCHIP_MCS7703 }
+ { 0x03f0, 0x0121 }
};
int moscom_match(struct device *, void *, void *);
Re: Where is this device attached?
On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On 03/20/14 16:33, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl http://www.openbsd.org/faq/faq5.html should answer most of your questions. hth Fred
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 04:45:12PM +, Fred wrote: On 03/20/14 16:33, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl http://www.openbsd.org/faq/faq5.html should answer most of your questions. Nah, most of my questions have nothing to do with OpenBSD. The one you responded to could be clarified. My bad. Do I need to go through steps of rebuilding all of the kernel, userland, etc.? Since I don't know what has to happen to get this into the system. I figured Jonathan would know since he's the one who was nice enough to offer a test patch. hth Don't get too far ahead of yourself ;-) /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 04:33:01PM +, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? You need to build and install a new kernel. After checking out the src tree via cvs and saving the patch to a file. cd /usr/src/sys/dev/usb patch -p0 /path/to/file then build and install a kernel as described in http://www.openbsd.org/faq/faq5.html#BldKernel
