ThinkWiki - User contributions [en]

Talk:HDAPS

2009-08-30T13:22:28Z

Oni: /* Question regarding the example udev rule ? */

== Question regarding the example udev rule ? ==
The example udev rule is as follows.
* KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1", ATTRS{modalias}=="input:b0019v1014p5054e4801-*", SYMLINK+="input/hdaps/accelerometer-event"

Where is the '''b0019v1014p5054e4801''' being taken from?

It is from "udevinfo --attribute-walk --name /dev/input/event9" (only with the tp_smapi module)

== Where can one find the recent hdapsd version mentioned in the article ? ==
The article mentions "New interface (requires hdapsd dated 2008-10-04 or newer)" without giving any clue about where one can find such a version, I looked in repositories, google and elsewhere in this very site and found an outdated http://www.dresco.co.uk/hdaps/ , as a newcomer here, it eludes me completely. [[User:Bugmenot1|Bugmenot1]] 21:38, 28 November 2008 (CET)

:I had the same problem, I think I found it via [[How_to_protect_the_harddisk_through_APS#Manual_compilation_from_source]], it links to a mailing list post at [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040] which has an attached source file at [http://cache.gmane.org//gmane/linux/drivers/hdaps/devel/1040-001.bin], this can be compiled easily with ''gcc -o hdapsd hdapsd.c''. Why this is not released cleanly on the original homepage eludes me as well... --[[User:Centic|Centic]] 12:34, 30 November 2008 (CET)

== "Reduced Power" hdapsd Consuming More Power ==

There is a link to a "reduced power" version of hdapsd, which is supposed to lower the number of timer interrupts (thereby reducing the power consumed by the daemon). From my experiments (using powertop), however, this program requires about twice as many interrupts to operate in "low power" mode as it does using the (older) sysfs interface. It also consumes enough CPU cycles to force my CPU back on periodically, consuming more power. Has anybody else had this experience?

--[[User:Mbsullivan|Mbsullivan]] 05:41, 24 August 2007 (UTC)

:Well, not really. With tp_smapi 0.31 and older hdapsd I had wakeups from hdapsd and from the hdaps module, now powertop only shows about 50wakeups from hdapsd (which are really from the module, but this is a bug in powertop, it tells who first called a function, not whose function it is [it's a function in the module code]). So I get a lower power consumption with the newer pair of tpsmapi and hdapsd
:--[[User:Zhenech|Zhenech]] 07:26, 24 August 2007 (UTC)

== I hawe a problem ==

I tray to start working my IBM x40 with hdaps function but I can't make it right.

The main problem is in a not hanging variables when I read
/sys/devices/platform/hdaps/position

==I also have this problem!==
Hi, I also have this problem that on my X40 the device/platform/hdaps/position does not give the right response. It is simply constant (128,1).
Does anyone have a clue? I use the suse kernel 2.6.16.13-4-default from suse10.1. the hdaps sources in that kernel are the same as in the original kernel.
thanks in advance,
----

Does the HDAPS sensor work under Windows (as observed from actual disk parking, or the graphical animation)?
Also, try loading [[tp_smapi]], it includes some patches for the hdaps driver. Does it help?

--[[User:Thinker|Thinker]] 16:45, 8 June 2006 (CEST)
----

HI Again,
HDAPS does work under windows. When I had windows running and then reboot the machine, hdaps is running under suse10.1 also. If I, however, turn off the machine and restart it, then, hdaps does *not* work anymore.
I remember that with suse 10.0 and the separate module, hdaps did work.
HDAPS now works with tp_smapi as suggested above.
Still, where does the problem derive from?

----

The hdaps in the vanilla kernel has some bugs (i.e., in doesn't talk to the hardware correctly) which tp_smapi fixes. Looks like you've hit one of these.

--[[User:Thinker|Thinker]] 18:05, 12 June 2006 (CEST)
----

==laptop acpi problem with hdaps==
 UPDATE: the problem seems fixed in the version 0.21 
<s>
My my both IBM T42/T43 laptops freezes time to times with the follow:

kernel 2.6.16/sata patch 
hdaps build as a module from the kernel.
tp_smapi 0.20/hdapsd

The freez is quite common then I access CD-ROM,but it also might freez without touching anything. 
After the freez keyboard doesn't work or priting some character,power button doesn't work, however mouse might continue to work. 
KDE battery systray shows discarchged batteries. 
Still under investigation that cases the problem. 
The related software:
khdapsmon 0.1.2 
ibm-acpi build-in as a module from the kernel(for ksensors)
modified ksensors without lm_sensors with a patch
http://bugs.gentoo.org/show_bug.cgi?id=116661

--noname 00:25, 13 June 2006 (CEST)Anton

----

You're the 2nd one reporting this. The fact you can reproduce it on two machines may be very helpful! Are these machines configured identically? Do they run the same software? Can you send your kernel .config, and precise kernel version + patches, to the e-mail address in the tp_smapi README? Please specify which hdaps or tp_smapi -related applications you're typically running.

BTW, if you have [[swsusp]] or [[Software Suspend 2]] installed, you can do a suspend-to-disk cycle to recover from the hang.

--[[User:Thinker|Thinker]] 11:53, 13 June 2006 (CEST)
----

I also have the follow
[[Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive]].
So I switched cdrom driver from IDE to ATA and it fixed the problem.
However HDAPS has stared to freez a machine if I shake it then HDD is active.
The issue might be not related to ACPI but I'll log it here for now.

I'll send configs. Thank you.
ps. 0.21 is out so let me try the new version.
--noname 08:34, 22 June 2006 (CEST)Anton
</s>

== hdaps and /sys ==

Hey Fellas,

I've just upgraded from 2.6.15.2, where the patches all dropped in ok and all was well, to 2.6.17.6, where hdaps is built into the kernel.
the hdapsd daemon referenced on thinkwiki looks in /sys/block/<drive>/queue/protect to get started.
The default drivers that come with 2.6.17.6 for hdaps apparently dont put anything in /queue there, so there is no 'protect' directory.
Has anyone else experienced this? I'd love to get my drive protection back :)
ON THE UPSIDE! - the Ricoh card reader in my z60m came to life, and I can read sd cards (but not sony memory sticks, oddly enough)
Any input would be awesome!
dan@itkinetix.com

----

You need an extra kernel patch for "protect". Please read the page more carefully.

--[[User:Thinker|Thinker]] 00:24, 22 July 2006 (CEST)
----

== Gnome HDAPS-Applet and the new interface ==

I just installed my first linux kernel with the new hdaps disk protection interface. Since the file that controls the (un)parking of the disk heads has changed with this interface, you have to edit the GNOME HDAPS applet source before compiling to make it work. Simply replace the lines 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/queue/protect"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/queue/protect"</nowiki> 
 
with these: 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/device/unload_heads"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/device/unload_heads"</nowiki> 
 
Then proceed with the instructions in the included INSTALL file. 
 
Another hint: On Ubuntu 8.10, install the hdapsd package, then compile the new version of hdapsd and replace the binary in /usr/sbin. Afterwards edit the /etc/init.d/hdapsd file so it looks for the new interface. Otherwise it will never start hdapsd bcause it's looking for the /sys/block/<device>/queue/protect file which simply doesn't exist. You may want to use the init script I posted at https://bugs.launchpad.net/ubuntu/+source/hdapsd/+bug/303915/comments/3 
And don't forget that udev-rule to create the symlink hdapsd needs to work!

Kind regards, 
--[[User:Gollo|Gollo]] 20:15, 18 December 2008 (CET)

== Older discussion ==

So, this is in the stable kernel now, but what userspace program do we need to actually park the heads?
--[[User:MrStaticVoid|MrStaticVoid]] 01:26, 30 Oct 2005 (CEST)
----
Yes the hdaps driver is in the 2.6.14 kernel, but support to park the heads quickly and freeze the disk queue (to prevent the heads from getting un-parked) is not. There is some disagreement into how that should be implemented.

In other words, the hdaps driver for the moment is rather useless, unless you want to use it to play games.

--[[User:Tonko|Tonko]] 02:10, 30 Oct 2005 (CEST)

----
I head rumours that you can make SDL handle this like a joystick, e.g. for playing Neverball. Can anyone confirm or deny that? Thanx --[[User:Nomeata|Nomeata]] 01:16, 16 Nov 2005 (CET)

Yes it is possible to use it as a joystick, as Tonko allready mentioned.
/dev/input/jsX modprobe joydev

Ozi

Thanks, I didn't have the joydev module. Rebuilding... --[[User:129.13.186.1|129.13.186.1]] 15:30, 16 Nov 2005 (CET)

----
Yeah, it's a pretty good party trick - set up the HDAPS joystick as xmame input. You can play Ms. Pac-man by tilting your laptop to make pac-man navigate the maze. You can imagine that the pac-man "rolls" downhill, just like those old wooden marble-puzzles that you see around. Heh, can actually clear a level or two.

Marble madness was strangely unsatisfying though, and just didn't work well (probably due to the diagonal nature of the screen in that game).

--[[User:gsmenden|gsmenden]] 20:10, 13 Jan 2006 (CEST)

----
Anyone got the queue freezing patch running on 2.6.16? I'm going to try to manually merge it but didn't want to duplicate someone else's work.

--[[User:Ajbarr|Ajbarr]] 19:12, 22 March 2006 (CET)

How to install MultiTouch from source

2008-09-19T12:14:21Z

Oni: /* Getting and compiling the code */

As things stand in August 2008 the latest packages of Ubuntu of the [http://linuxwacom.sourceforge.net/ linux-wacom-project] do not support MultiTouch for the X61 Tablet and X60 Tablet. However in the development packages MultiTouch is supported and work is going on there to improve things.

For the distribution Fedora Core 8 in [[Installing Fedora 8 (Werewolf) on an X61 Tablet]] a rpm based on the patch [http://sourceforge.net/tracker/index.php?func=detail&aid=1834901&group_id=69596&atid=525126 Usable Multitouch Support] has been created. As things change rapidly the patch has to be updated for every new version. Besides the patch is only applicable to the FC8 distribution.

In contrast to that the procedure in the present article tries to benefit from either the latest development version of the [http://linuxwacom.sourceforge.net/ linux-wacom-project] or the latest stable release. It describes how to get the sources via cvs, compile and install the drivers. It shows how to tweak the source code to get the calibration right.

The steps have been tested on a X61 Tablet MultiTouch with Ubuntu 8.04 (Hardy) distribution. Nevertheless it should work on other distributions as well.

== Removing old wacom-drivers ==

First remove all old wacom drivers and tools. In Ubuntu Hardy these are
* ''wacom-tools''
* ''xserver-xorg-input-wacom''

According to the installation manual [http://linuxwacom.sourceforge.net/index.php/howto/beforestart] remove or comment out all wacom related lines in the X-Server configuration file {{path|/etc/X11/xorg.conf}}. Restart the X-Server and test if everything has been removed by looking at {{path|/var/log/Xorg.0.log}}.

== Getting and compiling the code ==

We present here to ways: the first one is to get the latest developer release directly from the CVS server. However note that there might be errors. The other way is to download the latest stable release from [http://linuxwacom.sourceforge.net/ linux-wacom-project], which might be saver. However note, that a lot of work is currently (August 2008) going on to enhance the support for MultiTouch.

In either way we will first we have to get a few packages related with the Autotools. In Ubuntu Hardy these are
* ''automake''
* ''autoconf''
* ''libtool''
and dependencies. Furthermore we will need the development libraries ''ncurses'' and ''Xlib'' [[http://linuxwacom.sourceforge.net/index.php/howto/config]] as well as ''tcl/tk'', which are in Ubuntu Hardy
* ''xorg-dev''
* ''libncurses5''
* ''libncurses5-dev''
* ''libx11-6''
* ''libx11-dev''
* ''tcl8.4''
* ''tcl8.4-dev''
* ''tk8.4''
* ''tk8.4-dev''

=== Getting and preparing the latest development release ===

The [http://linuxwacom.sourceforge.net/ linux-wacom-project] is hosted on [[http://www.sourceforge.net Sourceforge]]. We will get the sources via CVS. Therefore we have to install the corresponding programs before. In Ubuntu Hardy this is just the ''cvs''-package.

Following the cvs instructions at [[http://sourceforge.net/cvs/?group_id=69596 Sourceforge CVS]] we first login as anonumous.
{{cmduser|cvs -d:pserver:anonymous@linuxwacom.cvs.sourceforge.net:/cvsroot/linuxwacom login}}

When prompted for a password just press enter. Now we are ready to download the development branch of the Wacom driver to the automatically created subdirectory {{path|linuxwacom-dev}} by issuing
{{cmduser|cvs -z3 -d:pserver:anonymous@linuxwacom.cvs.sourceforge.net:/cvsroot/linuxwacom co -P linuxwacom-dev}}

Change directory into {{path|linuxwacom-dev}} and issue
{{cmduser|autoreconf -i}}

=== Getting a stable release ===

Go to [http://linuxwacom.sourceforge.net/ linux-wacom-project] and download the latest stable release ({{path|linuxwacom-0.8.0-3.tar.bz2}} in August 2008). Untar the file and change directory.

=== Configuring and compiling the code (either way) ===

After that we can configure our linux-wacom tools. We just use the default options except for the request to build {{path|wacom.o}} by stating

{{cmduser|./configure --enable-wacom}}

After that we can compile the driver and install it by

{{cmduser|make}}
{{cmduser|sudo make install}}

== Editing {{path|/etc/X11/xorg.conf}} ==

After that we have to configure our X-server to recognize our new wacom input devices [[http://linuxwacom.sourceforge.net/index.php/howto/x11]]. First add the following input devices at the end of the file

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
# http://wiki.informatik.hu-berlin.de/nomads/index.php
Option "Button2" "3"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
# http://wiki.informatik.hu-berlin.de/nomads/index.php
Option "Button3" "2"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

# This section is for the TabletPC that supports touch
Section "InputDevice"
Driver "wacom"
Identifier "touch"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "touch"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

After that we have to add a few lines into the Section "Server Layout":
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Synaptics Touchpad"
# http://linuxwacom.sourceforge.net/index.php/howto/srvlayout
'''InputDevice "stylus" "SendCoreEvents"'''
'''InputDevice "eraser" "SendCoreEvents"'''
'''InputDevice "touch" "SendCoreEvents"'''
EndSection

Now restart the X-server. After that the X-Server should react on touching the screen. Note that if a stylus is near the screen it automatically disables MultiTouch input.

== Tweaking the driver ==

If you experience calibration problems first try
{{cmduser|wacomcpl}}
If it gives you an error we have to calibrate MultiTouch manually. For that we have to run
{{cmduser|xidump -u raw touch}}
Then try out the extreme x and y coordinates of your screen. After that edit the file {{path|src/xdrv/wcmISDV4.c}}. Find the function
static int isdv4Parse(LocalDevicePtr local, const unsigned char* data)
and in the function the part where the information about the touch event is parsed. In version 1.15 it should say starting from line 373
if (common->wcmPktLength == 5 ) /* a touch */
{
/* MultiTouch input only has 5 bytes of data */
ds->x = (((int)data[1]) << 7) | ((int)data[2]);
ds->y = (((int)data[3]) << 7) | ((int)data[4]);
ds->buttons = ds->proximity = data[0] & 0x01;
ds->device_type = TOUCH_ID;
ds->device_id = TOUCH_DEVICE_ID;
DBG(8, priv->debugLevel, ErrorF("isdv4Parse MultiTouch "
"%s proximity \n", ds->proximity ? "in" : "out of"));
}
Now remap the x and y coordinate by linearily transforming [xmin:xmax] to the full resolution [0:1024] and in the same manner [ymin:ymax] to [0:768]. Here xmin/xmax and ymin/ymax, respectively, are the measured minimal and maximal x-coordinates and y-coordinates of the touch events. In my case this is [41:927] and [80,738] so I write
if (common->wcmPktLength == 5 ) /* a touch */
{
/* MultiTouch input only has 5 bytes of data */
ds->x = (((int)data[1]) << 7) | ((int)data[2]);
'''// remapping from [41,927] to [0,1024]'''
'''ds->x = (ds->x - 41) * 1024 / (927-41);'''
ds->y = (((int)data[3]) << 7) | ((int)data[4]);
'''// remapping [80,738] to [0,768]'''
'''ds->y = (ds->y - 80) * 768 / (738-80);'''
ds->buttons = ds->proximity = data[0] & 0x01;
ds->device_type = TOUCH_ID;
ds->device_id = TOUCH_DEVICE_ID;
DBG(8, priv->debugLevel, ErrorF("isdv4Parse MultiTouch "
"%s proximity \n", ds->proximity ? "in" : "out of"));
}
If you find the values to be to inaccurate just reiterate until you are satisfied.

[[Category:X61 Tablet]]
[[Category:X60 Tablet]]

User:Oni

2008-03-17T18:00:34Z

Oni:

== Hi this is my page. ==

<nowiki> I'm sorry for my bad english and also for my not existing wiki-knowlege.</nowiki>

'''My ThinkPad'''
---------------------------------------
x30

'''current projects'''
--------------------------------------
getting my ThinkPad Dock completely running

'''former projects'''
--------------------------------------
the UltraPort pin layout

Talk:ThinkPad Dock

2008-03-17T17:57:36Z

Oni:

Which video cards have people put in the PCI slot?

What about USB in the Docking Station?

What about some usb-problems installing a new linux system with kernelversion 2.6?[[Problem with Dock USB Ports]]

== USB passthrough or PCI adapter? ==

The Dock has a single passthrough USB port.

But you should be able to install a USB 2.0 PCI-adapter in the PCI-slot.

== Referenced link ==

The referenced link is for the Dock II, not the original Dock, in addition it seems like it was a one-off event with a broken Dock that was replaced under warranty.

== Usage with unsupported Thinkpads ==

Does anyone know if the 2631 model will support T4x series, such as the T43p?

----
It will NOT physically fit.

The docking connector on the T40 series machines is in a different place then it was on the T20/30 machines.

And on the latest T60 machines, they moved it again.

--[[User:Tonko|Tonko]] 10:44, 5 May 2006 (CEST)

Physical incompatibility between the Dock I (2631) and the T40 series does not make sense to me. The Docking Station II is documented as supporting the T2x and T30 models as well as the T4x, so it would seem that they must use the same physical connector. Can someone clarify?

----

Ok, once more, the '''ThinkPad Dock''' is '''incompatible''' with the T40 series machines. 
And you are correct that the newer Dock II can support both the T40 series and the older T20/30 machines.

The reason for this is that the physical connector has not changed between the T20/30 series and the T40 series, but the location of the connector has. 
On the T20/30 machines the connector is placed more towards the back of the ThinkPad, while the T40 has it placed slightly more forward, because of the location of the battery. The Dock II (and also Port Replicator II) have an adjustable back that can be set for older (T20/30 series, etc), or for newer (T40, etc) series machines. This is not possible with the older Dock or Port Replicator.

--[[User:Tonko|Tonko]] 13:40, 4 June 2006 (CEST)

== Port problems ==
Hi,
I have a x30 with ubuntu and 2.6.23.8 kernel. My VGA,USB and ULTABAY Port is not running.
USB is running before the kernel is completely booted. Any ideas?

User:Oni

2006-02-10T18:02:25Z

Oni: /* Hi this is my page. */

== Hi this is my page. ==

<nowiki> I'm sorry for my bad english and also for my not existing wiki-knowlege.</nowiki>

'''My ThinkPad'''
---------------------------------------
x21

'''current projects'''
--------------------------------------
internal lan and wlan (lan ist realized with an "internal" usb-lancard)

an UltraPort usb-hub

the three undefined pins in the UltraPort

'''former projects'''
--------------------------------------
the UltraPort pin layout

User:Oni

2006-02-10T18:02:10Z

Oni: /* Hi this is my page. */

== Hi this is my page. ==

<nowiki> I'm sorry for my bad english and also for my not existing wiki-knowlege.</nowiki>

'''My ThinkPad'''
---------------------------------------
x21

'''current projects'''
--------------------------------------
internal lan and wlan (lan ist realized with an "internal" usb-lancrard)

an UltraPort usb-hub

the three undefined pins in the UltraPort

'''former projects'''
--------------------------------------
the UltraPort pin layout

Talk:How to build your own Ultrabay Plus device

2006-02-10T17:57:41Z

Oni:

witch thinkpads have an UltraBay plus port?

Talk:UltraPort

2006-02-08T20:57:00Z

Oni:

Yes, the UltraPort was available throughout all models of the T2x series. And yes, it was rarely found in models from the T30 series. But the location overview movie at the IBM web page shows the UltraPort and it mentions it on the page. So this seems to indicate that some T30 models still came with it.
[[User:Wyrfel|Wyrfel]] 03:57, 27 Nov 2004 (CET)

I have seen a lot of T30 models, and not one had the UltraPort. If the IBM webpage shows it does, that is simply a mistake. It certainly would not be the first time.

----
Please google for things like "T30 ultraport" or "A30p ultraport" and you will find a lot of pages indicating that there were models with ultraport. Either they all had wrong information or there were models including it. It is true that the mentioning on the locations overview page is a mistake and should obviously be UltraBay, but still you can see the ultraport in the movie picture. However, by writing "the time of the T30" i also refer to the models like the A30p and i think that there is very much stronger indication that there were A30p models with UltraPort.
[[User:Wyrfel|Wyrfel]] 04:14, 27 Nov 2004 (CET)

I double checked it in the T30 HMM, and it makes no mention of the Ultraport. 
ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/92p1840.pdf

I know because I had the UltraPort Camera II, and could no longer use it with my T30, so I gave it away. 
My wife has an X22 which does have the connector.

Doing some searches on the Internet and the IBM support pages, these should be all the machines with the UltraPort connector:

A20m 
A20p 
A21e 
A21m 
A21p 
A22e 
A22m 
A22p 
T20 
T21 
T22 
T23 
X21 
X22 
X23 
X24

I know the T30 and R31 no longer have the connector.

----
Ok, i changed it to A31p. Here are three links that indicate that it still had the connector...
*http://web.zdnet.de/mobile/artikel/notebooks/200205/ibm_thinkpad_a31p-wc.html
*http://www.sleeper-service.org/a31p/a31p.html
*http://www.karachinsky.com/roman/linux/a31p.html

And here is a ZDNet review that explicitly mentions the connetor for a T30...
*http://reviews-zdnet.com.com/IBM_ThinkPad_T30_2366___P4_M_1_8_GHz___14_1__TFT/4505-3121_16-20077786-2.html

However, i'll remove it from the T30 category as long as we don't have a proof.
[[User:Wyrfel|Wyrfel]] 04:41, 27 Nov 2004 (CET)

== why ultraports gone? ==

Hey guys,

Have you ever found any resources describing why IBM discontinued this very excellent device? I've come to find the integrated camera indispensible. BTW. I have an A31p and a22p and both have ultraports (although you had already pulled that to a pretty good conclusion)...

David

i thing it has gone because nobody has bought devices to connect to it

User:Oni

2006-02-08T20:53:43Z

Oni:

== Hi this is my page. ==

<nowiki> I'm sorry for my bad english and also for my not existing wiki-knowlege.</nowiki>

'''My ThinkPad'''
---------------------------------------
x21

'''current projects'''
--------------------------------------
internal lan and wlan

an UltraPort usb-hub

the three undefined pins in the UltraPort

'''former projects'''
--------------------------------------
the UltraPort pin layout

User talk:Oni

2006-02-08T18:40:55Z

Oni:

Hei,

what do you mean by "it works very well"? Did you actually mod any standard USB device to connect to the UltraBay connector?

[[User:Wyrfel|Wyrfel]] 02:30, 7 February 2006 (CET)
----

i have soldered an usb-port on it and an usb-lancard or mouse is working
also an usb-storage is working
----

You're talking about the Ultra'''Port''', not Ultra'''Bay''', right?

--[[User:Thinker|Thinker]] 01:06, 8 February 2006 (CET)
----

Yepp, that's what we mean. ;-) Thanks for the notion. [[User:Wyrfel|Wyrfel]] 03:32, 8 February 2006 (CET)
----

yes i talk about the UltraPort (the UltraBay has mutch more pins)

User talk:Oni

2006-02-07T18:55:33Z

Oni:

UltraPort

2006-02-06T22:33:16Z

Oni: /* Pin assignment */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ultraport.jpg|IBM Embedded Security Subsystem]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
===IBM UltraPort===
The UltraPort is a tiny connector sitting at the top edge of the display. It was introduced by IBM with the T20 series and other models of that time, but only continued onto some models from the time of the A31p. With the T30 type models it has vanished completely again.

On the controller side the UltraPort is nothing but a USB 1.1 port, so all UltraPort devices are usable on other computers as USB devices as well.
</div>
|}

==Devices==
There were 5 devices produced by IBM for this port:
*[[UltraPort Bluetooth Adapter]]
*[[UltraPort Camera & UltraPort Camera II]]
*[[UltraPort Compact Flash Adapter]]
*[[UltraPort Digital Array Microphone]]
*[[UltraPort Infrared Adapter]]

==Linux Support==
The UltraPort is recognised and driven by the kernels USB subsystem.

See the individual devices pages above for information on linux support for them.

==Pin assignment==
* {{X21}} :
|GND|0|VBUS|VBUS|GND|D+|D-|GND| o |?|?|?|0|GND|

{| border="1" cellspacing="0" cellpadding="2"
! Pin !! Name !! Description
|-
||1,5,8,13 ||GND || Ground
|-
||2,12 ||0 || probably not connected
|-
||3,4 ||VBUS || +5 VDC
|-
||6 ||D+ || Data +
|-
||7 ||D- || Data -
|-
||9,10,11 ||? || unidentified
|-
|| ||o || it is fastener not a pin
|}
These relusts are only measured and not well tested.
On my {{x21}} it works very well.

==Models featuring the UltraPort==
* {{A20p}}, {{A21p}}, {{A22p}}, {{A30p}}, {{A31p}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}

[[Category:Glossary]]

UltraPort

2006-02-06T22:25:27Z

Oni:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ultraport.jpg|IBM Embedded Security Subsystem]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
===IBM UltraPort===
The UltraPort is a tiny connector sitting at the top edge of the display. It was introduced by IBM with the T20 series and other models of that time, but only continued onto some models from the time of the A31p. With the T30 type models it has vanished completely again.

On the controller side the UltraPort is nothing but a USB 1.1 port, so all UltraPort devices are usable on other computers as USB devices as well.
</div>
|}

==Devices==
There were 5 devices produced by IBM for this port:
*[[UltraPort Bluetooth Adapter]]
*[[UltraPort Camera & UltraPort Camera II]]
*[[UltraPort Compact Flash Adapter]]
*[[UltraPort Digital Array Microphone]]
*[[UltraPort Infrared Adapter]]

==Linux Support==
The UltraPort is recognised and driven by the kernels USB subsystem.

See the individual devices pages above for information on linux support for them.

==Pin assignment==
* {{X21}} :
|GND|0|VBUS|VBUS|GND|D+|D-|GND| o |?|?|?|0|GND|

{| border="1" cellspacing="0" cellpadding="2"
! Pin !! Name !! Description
|-
||1,5,8,13 ||GND || Ground
|-
||2,12 ||0 || probably not connected
|-
||3,4 ||VBUS || +5 VDC
|-
||6 ||D+ || Data +
|-
||7 ||D- || Data -
|-
||9,10,11 ||? || unidentified
|-
|| ||o || it is fastener not a pin
|}
These relusts are only measured and not well tested.
On my {{x21}} it is working very well.
==Models featuring the UltraPort==
* {{A20p}}, {{A21p}}, {{A22p}}, {{A30p}}, {{A31p}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}

[[Category:Glossary]]

UltraPort

2006-02-06T21:53:57Z

Oni:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ultraport.jpg|IBM Embedded Security Subsystem]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
===IBM UltraPort===
The UltraPort is a tiny connector sitting at the top edge of the display. It was introduced by IBM with the T20 series and other models of that time, but only continued onto some models from the time of the A31p. With the T30 type models it has vanished completely again.

On the controller side the UltraPort is nothing but a USB 1.1 port, so all UltraPort devices are usable on other computers as USB devices as well.
</div>
|}

==Devices==
There were 5 devices produced by IBM for this port:
*[[UltraPort Bluetooth Adapter]]
*[[UltraPort Camera & UltraPort Camera II]]
*[[UltraPort Compact Flash Adapter]]
*[[UltraPort Digital Array Microphone]]
*[[UltraPort Infrared Adapter]]

==Linux Support==
The UltraPort is recognised and driven by the kernels USB subsystem.

See the individual devices pages above for information on linux support for them.

==Models featuring the UltraPort==
* {{A20p}}, {{A21p}}, {{A22p}}, {{A30p}}, {{A31p}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}

==Pin assignment==
* {{X21}} :
|GND|0|VBUS|VBUS|GND|D+|D-|GND| o |?|?|?|0|GND|

{| border="1" cellspacing="0" cellpadding="2"
! Pin !! Name !! Description
|-
||1,5,8,13 ||GND || Ground
|-
||2,12 ||0 || not connected
|-
||3,4 ||VBUS || +5 VDC
|-
||6 ||D+ || Data +
|-
||7 ||D- || Data -
|-
||9,10,11 ||? || unidentified
|-
|| ||o || it is fastener not a pin
|}
[[Category:Glossary]]