linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: scott <scott@waye.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: How to configure the tty with a usb serial device
Date: Sun, 26 Nov 2006 23:50:15 +0000	[thread overview]
Message-ID: <456A2837.7050109@waye.co.uk> (raw)

Hello,

Is hotplug the right place to set up (e.g. stty ispeed 4800) a USB 
serial device?  I can see that after udev runs and creates the 
/dev/tts/USB0, the only call left to hotplug is with a type of tty.  But 
I have no tty.agent (of course I can cp usb.agent tty.agent which I've 
done), but what would be the equivalent of usbmodules?  Also how can 
hotplug "know" the /dev/tts/USBx device that was created by the udev 
rule, there doesn't seem to be any environment variable for that?

kernel 2.6.15.4

Here is a section of debug:

Nov 26 20:34:32 calera default.hotplug[7676]: no runnable 
/etc/hotplug/usb-serial.agent is installed
Nov 26 20:34:32 calera kernel: drivers/usb/serial/usb-serial.c: USB 
Serial support registered for pl2303
Nov 26 20:34:32 calera kernel: pl2303 1-1:1.0: pl2303 converter detected
Nov 26 20:34:32 calera kernel: usb 1-1: pl2303 converter now attached to 
ttyUSB0
Nov 26 20:34:32 calera kernel: usbcore: registered new driver pl2303
Nov 26 20:34:32 calera kernel: drivers/usb/serial/pl2303.c: Prolific 
PL2303 USB to serial adaptor driver
Nov 26 20:34:32 calera default.hotplug[7689]: testing debug
Nov 26 20:34:32 calera udev[7695]: udev_rules.c: rule applied, 'ttyUSB0' 
becomes 'tts/USB0'
Nov 26 20:34:32 calera udev[7695]: udev_add.c: creating device node 
'/dev/tts/USB0'
Nov 26 20:34:32 calera default.hotplug[7689]: arguments (tty) env 
(PHYSDEVPATH=/devices/pci0000:00/0000:00:10.0/usb1/1-1/1-1:1.0/ttyUSB0
SUBSYSTEM=tty OLDPWD=/ DEVPATH=/class/tty/ttyUSB0 MINOR=0 
PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION­d PWD=/etc/hotplug MAJOR\x188 
HOME=/
 SHLVL=2 PHYSDEVDRIVER=pl2303 DEBUG=yes PHYSDEVBUS=usb-serial SEQNUMf1 
_=/usr/bin/env)
Nov 26 20:34:32 calera default.hotplug[7689]: invoke 
/etc/hotplug/tty.agent ()
Nov 26 20:34:32 calera tty.agent[7689]: testing debug
Nov 26 20:34:32 calera tty.agent[7689]: load_drivers for tty and module
Nov 26 20:34:32 calera tty.agent[7689]: lister is /sbin/ttymodules
Nov 26 20:34:32 calera tty.agent[7689]: mapfile is /etc/hotplug/usb.usermap
Nov 26 20:34:32 calera tty.agent[7689]: device is
Nov 26 20:34:32 calera tty.agent[7689]: drivers is
Nov 26 20:34:32 calera tty.agent[7689]: ... no modules for USB product


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2006-11-26 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 23:50 scott [this message]
2006-11-28  8:24 ` How to configure the tty with a usb serial device Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=456A2837.7050109@waye.co.uk \
    --to=scott@waye.co.uk \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).