USB Todo's - Revision history

Erdmann at 16:26, 25 March 2018

2018-03-25T16:26:40Z

← Older revision		Revision as of 18:26, 25 March 2018
Line 30:		Line 30:


	There's a daemon package called [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmount&stype=all&sort=type&dir=%2F USBMOUNT] on Hobbes for automatically mounting USB disks. It uses USBRES to monitor for new devices and runs ~~rediscoverdrives~~.exe ~~(or however it's called)~~ after attaching of a USB device. Source code is included. This package may be easily extended to support cameras and other stuff. With a REXX interface user written REXX procedures may be executed on every mount.		There's a daemon package called [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmount&stype=all&sort=type&dir=%2F USBMOUNT] on Hobbes for automatically mounting USB disks. It uses USBRES to monitor for new devices and runs lvm.exe /rediscoverprm after attaching of a USB device. Source code is included. This package may be easily extended to support cameras and other stuff. With a REXX interface user written REXX procedures may be executed on every mount.

	* status reports should pop up in xCenter a bit like what we have on Windows		* status reports should pop up in xCenter a bit like what we have on Windows

Lewisr: /* USB driver */ Updated Hobbes links, as they were broken (pointing to cgi-bin/h-search.php instead of just /h-search.php) - LGR

2013-06-04T18:54:17Z

USB driver: Updated Hobbes links, as they were broken (pointing to cgi-bin/h-search.php instead of just /h-search.php) - LGR

← Older revision		Revision as of 20:54, 4 June 2013
Line 15:		Line 15:
	====USB driver====		====USB driver====
	At the moment there are several different USB drivers available, each one supports some features more or less:		At the moment there are several different USB drivers available, each one supports some features more or less:
	* [http://hobbes.nmsu.edu~~/cgi-bin~~/h-search?sh=1&button=Search&key=cw-usbmsd&stype=all&sort=~~type~~&dir=%2F CW-USBMSD], the driver from Chris Wohlgemuth. Supports more devices than the IBM one, especially Archos Jukebox and other external hard disks.		* [http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=cw-usbmsd&stype=all&sort=type_name&dir=%2F CW-USBMSD], the driver from Chris Wohlgemuth. Supports more devices than the IBM one, especially Archos Jukebox and other external hard disks.
	* USBD.SYS included in [http://hobbes.nmsu.edu~~/cgi-bin~~/h-search?key=mmport&~~pushbutton~~=~~Search~~ MMPORT] by Martin Kiewitz. This driver implements the enumeration of devices like Windows does so it should be more compatible with devices than the original one by IBM.		* USBD.SYS included in [http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=mmport&stype=all&sort=type_name&dir=%2F MMPORT] by Martin Kiewitz. This driver implements the enumeration of devices like Windows does so it should be more compatible with devices than the original one by IBM.
	* [http://hobbes.nmsu.edu~~/cgi-bin~~/h-search?sh=1&button=Search&key=usbmsd13b&stype=all&sort=~~type~~&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.		* [http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=usbmsd13b&stype=all&sort=type_name&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.
	* [http://home.hccnet.nl/w.m.brul/usbprobe/index.html USB 1.1 Expanded Control Driver for OS/2] by Wim Brul.		* [http://home.hccnet.nl/w.m.brul/usbprobe/index.html USB 1.1 Expanded Control Driver for OS/2] by Wim Brul.
	*PCMCIA driver for USB2.0 cards for laptops. Right now, laptops with USB1.0 built in cannot be upgraded to USB2.0 with PCMCIA cards.		*PCMCIA driver for USB2.0 cards for laptops. Right now, laptops with USB1.0 built in cannot be upgraded to USB2.0 with PCMCIA cards.

Ktk at 03:06, 29 December 2006

2006-12-29T03:06:55Z

← Older revision		Revision as of 05:06, 29 December 2006
Line 1:		Line 1:
			[[Category:Ideas]]
	==USB on OS/2 and eCS==		==USB on OS/2 and eCS==
	There are several efforts working on USB related issues for OS/2. Most of the work is based on IBM's USB stack which is unfortunately not always the best known solution because it is based on official standards. For sure Microsoft did it different so many devices are not recognized correctly on OS/2 or eCS. IBM itself seems not to be interested in following the Microsoft way, which makes the USB stack useless for quite some devices.		There are several efforts working on USB related issues for OS/2. Most of the work is based on IBM's USB stack which is unfortunately not always the best known solution because it is based on official standards. For sure Microsoft did it different so many devices are not recognized correctly on OS/2 or eCS. IBM itself seems not to be interested in following the Microsoft way, which makes the USB stack useless for quite some devices.

Ktk: /* Java interfaces on OS/2 and eCS */

2006-06-07T09:19:35Z

Java interfaces on OS/2 and eCS

← Older revision		Revision as of 11:19, 7 June 2006
Line 54:		Line 54:

	The jSyncManager's [http://viewcvs.jsyncmanager.org CVS tree] contains a prototype transport plug-in for USB acccess on OS/2 (see the contrib/os2-usb directory). This is built upon Markus Montkowski's Ring 3 library, however it is in need of very serious debugging. As of the last testing, the code was able to (at times) receive data from the handheld device, but would cause a trap 0006 shortly after connecting. Debugging this code could bring us the ability to sync USB handhelds on OS/2 rapidly while javax.usb is ported.		The jSyncManager's [http://viewcvs.jsyncmanager.org CVS tree] contains a prototype transport plug-in for USB acccess on OS/2 (see the contrib/os2-usb directory). This is built upon Markus Montkowski's Ring 3 library, however it is in need of very serious debugging. As of the last testing, the code was able to (at times) receive data from the handheld device, but would cause a trap 0006 shortly after connecting. Debugging this code could bring us the ability to sync USB handhelds on OS/2 rapidly while javax.usb is ported.

			The same could be done for SyncML, there are some good libraries available at http://www.funambol.com/ - see SyncML and ''Push Mail''

	====USB Resource Manager====		====USB Resource Manager====

Ktk: /* USB driver */

2005-07-11T13:07:23Z

USB driver

← Older revision		Revision as of 15:07, 11 July 2005
Line 18:		Line 18:
	* [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmsd13b&stype=all&sort=type&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.		* [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmsd13b&stype=all&sort=type&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.
	* [http://home.hccnet.nl/w.m.brul/usbprobe/index.html USB 1.1 Expanded Control Driver for OS/2] by Wim Brul.		* [http://home.hccnet.nl/w.m.brul/usbprobe/index.html USB 1.1 Expanded Control Driver for OS/2] by Wim Brul.
			*PCMCIA driver for USB2.0 cards for laptops. Right now, laptops with USB1.0 built in cannot be upgraded to USB2.0 with PCMCIA cards.
			*USB driver for enabling RSJ to talk to external CDRW drives.

			Note: It is better to make some changes in OS2CDROM.DMD code, so that it will allow to issue SCSI commands without need to open device. I made some checks, and found that it is possible to get CDROM Id control, open/close tray via OS2CDROM SCSI interface, but drive must have loaded media for the first to obtain device handle.

	====PM/WPS integration====		====PM/WPS integration====

147.87.65.205: /* USB driver */

2005-03-18T13:48:27Z

USB driver

← Older revision		Revision as of 15:48, 18 March 2005
Line 17:		Line 17:
	* USBD.SYS included in [http://hobbes.nmsu.edu/cgi-bin/h-search?key=mmport&pushbutton=Search MMPORT] by Martin Kiewitz. This driver implements the enumeration of devices like Windows does so it should be more compatible with devices than the original one by IBM.		* USBD.SYS included in [http://hobbes.nmsu.edu/cgi-bin/h-search?key=mmport&pushbutton=Search MMPORT] by Martin Kiewitz. This driver implements the enumeration of devices like Windows does so it should be more compatible with devices than the original one by IBM.
	* [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmsd13b&stype=all&sort=type&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.		* [http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=usbmsd13b&stype=all&sort=type&dir=%2F USBMSD13b] by Yuri Dario. Supports Olympus digital cameras.
			* [http://home.hccnet.nl/w.m.brul/usbprobe/index.html USB 1.1 Expanded Control Driver for OS/2] by Wim Brul.

	====PM/WPS integration====		====PM/WPS integration====

24.102.205.150: /* Java interfaces on OS/2 and eCS */

2004-12-22T04:04:36Z

Java interfaces on OS/2 and eCS

← Older revision		Revision as of 06:04, 22 December 2004
Line 47:		Line 47:

	This library is also in use by the [http://www.jsyncmanager.org/ JSyncManager]. So long as the implementation is sufficiently complete to detect the addition and removal of USB devices, the configuration of devices, the aquisition of the interface endpoints, and the tools to do bulk transport communications, it will permit USB-dock based PalmOS handhelds to sync on OS/2.		This library is also in use by the [http://www.jsyncmanager.org/ JSyncManager]. So long as the implementation is sufficiently complete to detect the addition and removal of USB devices, the configuration of devices, the aquisition of the interface endpoints, and the tools to do bulk transport communications, it will permit USB-dock based PalmOS handhelds to sync on OS/2.

			The jSyncManager's [http://viewcvs.jsyncmanager.org CVS tree] contains a prototype transport plug-in for USB acccess on OS/2 (see the contrib/os2-usb directory). This is built upon Markus Montkowski's Ring 3 library, however it is in need of very serious debugging. As of the last testing, the code was able to (at times) receive data from the handheld device, but would cause a trap 0006 shortly after connecting. Debugging this code could bring us the ability to sync USB handhelds on OS/2 rapidly while javax.usb is ported.

	====USB Resource Manager====		====USB Resource Manager====

24.102.205.150: /* Java interfaces on OS/2 and eCS */

2004-12-22T03:57:14Z

Java interfaces on OS/2 and eCS

← Older revision		Revision as of 05:57, 22 December 2004
Line 43:		Line 43:

	IBM's "proposal" is [http://www.jcp.org/en/jsr/detail?id=80 JSR-080], inhabiting the [http://javax-usb.org javax.usb] namespace. Final approval ballot for this proposed specification ends on December 20th, 2004, at which time the proposal is expected to become a finalized standard.		IBM's "proposal" is [http://www.jcp.org/en/jsr/detail?id=80 JSR-080], inhabiting the [http://javax-usb.org javax.usb] namespace. Final approval ballot for this proposed specification ends on December 20th, 2004, at which time the proposal is expected to become a finalized standard.

			(Note: JSR-080 passed on Dec 20th, 2004, and thus has been ratified as an official Java standard).

	This library is also in use by the [http://www.jsyncmanager.org/ JSyncManager]. So long as the implementation is sufficiently complete to detect the addition and removal of USB devices, the configuration of devices, the aquisition of the interface endpoints, and the tools to do bulk transport communications, it will permit USB-dock based PalmOS handhelds to sync on OS/2.		This library is also in use by the [http://www.jsyncmanager.org/ JSyncManager]. So long as the implementation is sufficiently complete to detect the addition and removal of USB devices, the configuration of devices, the aquisition of the interface endpoints, and the tools to do bulk transport communications, it will permit USB-dock based PalmOS handhelds to sync on OS/2.

Ktk: /* Installation tool */

2004-12-15T12:10:56Z

Installation tool

← Older revision		Revision as of 14:10, 15 December 2004
Line 79:		Line 79:


	====Installation tool====		===Installation tool===
	A working installation program (may just be CLI) for the USB drivers is needed, which automatically queries the controllers in the system and adds the right drivers acordingly. Often people not even get the base USB stuff to run for yet unknown reasons.		A working installation program (may just be CLI) for the USB drivers is needed, which automatically queries the controllers in the system and adds the right drivers acordingly. Often people not even get the base USB stuff to run for yet unknown reasons.

Ktk: /* USB Resource Manager */

2004-12-15T12:10:04Z

USB Resource Manager

← Older revision		Revision as of 14:10, 15 December 2004
Line 53:		Line 53:
	* Check hub ports if unused/or if a hub is attached to it to detect hub de/attachmement		* Check hub ports if unused/or if a hub is attached to it to detect hub de/attachmement
	* General Hotplug demon with DLLs for the supported busses (USB/IR/Bluetooth/PCMCIA/Firewire)		* General Hotplug demon with DLLs for the supported busses (USB/IR/Bluetooth/PCMCIA/Firewire)
	The demon loads the bus DLLs and starts notification threads for each bus.		** The demon loads the bus DLLs and starts notification threads for each bus.
	When a new device is attached the DLL returns a uniqe name for the device f.i. in the form of		** When a new device is attached the DLL returns a uniqe name for the device f.i. in the form of BUS:NR:V-VENDORID:D-DEVICEID:SERIAL.
	BUS:NR:V-VENDORID:D-DEVICEID:SERIAL.		** The demon looks up if a WPS object with the Name exists and if notifies it.
	The demon looks up if a WPS object with the Name exists and if notifies it.		** If not it creates an object for it in the folder of it's bus.
	If not it creates an object for it in the folder of it's bus.
	* General Hotplug-Bus WPS Class		* General Hotplug-Bus WPS Class
	Each Hostdriver gets represented as an WPS Object as it implements.		** Each Hostdriver gets represented as an WPS Object as it implements.
	With optional statistics pages.		** With optional statistics pages.
	* General Hotplug WPS Device Class		* General Hotplug WPS Device Class
	Gives info about the device in properties : BUS, BUS ID etc.		** Gives info about the device in properties : BUS, BUS ID etc.
	Allows addion of Programobject for Plug/Unplug events.		** Allows addion of Programobject for Plug/Unplug events.
	Shows BUS spec. Property pages implemented by the BUS-DLLs.		** Shows BUS spec. Property pages implemented by the BUS-DLLs.

	====GENMAC and USB devices====		====GENMAC and USB devices====