| |
| |
| |
|
Comments:
<0> have an issue with hal, I while back I could pop in a dvd and it would mount with the "dvd title" name
<0> know it just "pops in" my desktop as dvdrecorder
<0> what fdi file would I have to edit?
<1> Hi anholt. Do you happen to know how to work the magic LDAP user-management bits?
<2> and maybe why it never responds to my email commands?
<1> Actually, I meant the admin side of the LDAP bits, to create and manage users.
<1> ds: Do you have a GPG key registered?
<2> yes
<3> JoshTriplett: it's on the sitewranglers wiki
<2> is there any way to check what key is attached to my account?
<2> (gpg)
<1> anholt: Ah, good to know. keithp tried to help with what I've now reported as #9782, but he said he didn't know how to work the LDAP magic.
<4> Hello, does anyone know a way to connect two monitors on tow computers that they act liek xinerama. i mean like one physical desktop ?
<5> that's pretty much what Xdmx is for
<4> DrNick : thanks i will look for it .
<4> DrNick : that's exactly what i meant :)
<6> hi there
<6> I have a problem with my radeon mergedfb with xserver-1.2.0 and I've done a git bisect to find what's the culprit
<6> commit d89fee68d0e49211871cd9eb3893ed55c1d478a6 seems to be the culprit
<6> should I report a bug or is it a know issue ?
<7> weird, does anyone know, where the wheel information comes from in kernel?
<7> i mean morepercise down or up direction
<8> drivers/input/mouse/psmouse*, I suspect
<7> hmm ok and it should not be sent via /dev/input/mice?
<8> Yes
<7> mjg59: hmm weird, how will i be able to read those then? mouse is usb not ps2
<8> Wait. What precisely do you want to know?
<7> mjg59: how can i read wheel direction from /dev/input/mice
<8> Open it, read it, parse the datastream
<8> ?
<8> It'll appear as the PS/2 mouse protocol, I believe
<7> yeah but here the same thing happens like in this thread
<7> http://kerneltrap.org/node/6786
<7> mjg59: that way it really generates the same information regardless if moving wheel mouse up or down, need to know where it p***es the info up or down
<8> IIRC, you need to send it a byte to tell it that you want the 4-byte protocol stream
<7> mjg59: ok how a bit closer can you explain?
<7> mjg59:http://rsim.cs.uiuc.edu/~sachs/tp-scroll/tp-scroll-1.0.tgz there i need to reconize the wheel, perhaps you can take a look
<8> Write 0xf3, 200, 0xf3, 100, 0xf3, 80
<8> Then it'll feed you the 4-byte protocol
<7> mjg59:yeah this should be the key, but how i write it? to /dev/input/mice?
<8> Yes
<7> mjg59: yeah interesting how would you form this in a fwrite function or similar?
<7> mjg59: tried that writing to /dev/input/mice though it seems to have no affect
<7> static unsigned char mousedev_imps_seq[] = { 0xf3, 200, 0xf3, 100, 0xf3, 80 };
<7> out = fopen(indev, "w");
<7> fwrite(mousedev_imps_seq,1,6*sizeof(unsigned char), out);
<7> whould do the trick yes?
<7> anyways seems it does not do much here,wonder why
Return to
#freedesktop
or
Go to some related
logs:
vesafb unrecognized mtrr
inter-tel backdoor
#css
gentoo glxgears api mismatch
#fedora
#ai
#suse
#debian
#perl
aliien ubuntu
|
|