From info at pleasureholidayz.com Sat Aug 15 09:48:11 2009 From: info at pleasureholidayz.com (pleasureholidayz) Date: Sat Aug 15 09:48:17 2009 Subject: Happy Independence Day Message-ID: Dear Friends HAPPY INDEPENDENCE DAY!!! Slums to Skyscrapers... Crowded yet spacious... Where peace entails... Never losing hope...Unity in diversity... Striving for peace...Realzing the dream... Thats Our India... Where enchanment persist against all odds........ Jai Hind ************************** Please contact us at Pleasure Holidayz, 1st Floor, Pallath Business Center, Kurishupally Road, Ravipuram, Cochin, Kerala ? 682 015, India. Mob: +91 9961040050, +91 9539040906 Phone: +91 484 3077234, Fax: +91 484 3061977 Website : www.pleasureholidayz.com email:pleasureholidayz@gmail.com, info@pleasureholidayz.com Chat Id: pleasureholidayz (Msn/Yahoo/gmail/skype) -- If you do not want to receive any more newsletters, http://www.pleasureholidayz.com/phplist/?p=unsubscribe&uid=a798d3fe7ab539531adb5e8d615442e3 To update your preferences and to unsubscribe visit http://www.pleasureholidayz.com/phplist/?p=preferences&uid=a798d3fe7ab539531adb5e8d615442e3 Forward a Message to Someone http://www.pleasureholidayz.com/phplist/?p=forward&uid=a798d3fe7ab539531adb5e8d615442e3&mid=48 -- Powered by PHPlist, www.phplist.com -- From rgrover1 at gmail.com Wed Aug 19 13:42:33 2009 From: rgrover1 at gmail.com (Rohit Grover) Date: Wed Aug 19 13:42:39 2009 Subject: introducing a FreeBSD driver for the Apple Touchpad; and a few questions.. Message-ID: <426bed110908190616m21d39e9bm95a60f624b831418@mail.gmail.com> Hello, I have developed a driver for the Touchpad device on Apple Macbooks. Mine is a Macbook 3,1, and I run FreeBSD7.2 on it--so testing has sor far been limited to this configuration. In its present state, the driver supports multi-tap, edge detection, and movement smothening. The driver creates a pseudo device: /dev/atp, which expects to be read from moused. You can setup moused to work with it by adding the following to /etc/rc.conf: moused_port="/dev/atp" and then you would also need to tell your X-server to get mouse data from /dev/sysmouse. You may get the driver from git://github.com/rgrover/freebsd-atp.git. The git command is: "git clone git://github.com/rgrover/freebsd-atp.git". I have been using this driver for a while now. It is stable. Please help me test this driver for a wider range of hardware. There is more work to be done in the area of movement smoothening. I am also going to add support for detecting gestures. For this I need to track strokes. For my algorithms, I would like to allocate memory dynamically out of a small pool of fixed sized structures. I have read a bit about UMA; is UMA a good alternative for managing a small pool (~20) of buffers (of around 20 bytes in size)? regards, From rgrover1 at gmail.com Wed Aug 19 21:16:12 2009 From: rgrover1 at gmail.com (Rohit Grover) Date: Wed Aug 19 21:16:17 2009 Subject: introducing a FreeBSD driver for the Apple Touchpad; and a few questions.. In-Reply-To: <20090819194426.3bf401d9@baby-jane.lamaiziere.net> References: <426bed110908190616m21d39e9bm95a60f624b831418@mail.gmail.com> <20090819194426.3bf401d9@baby-jane.lamaiziere.net> Message-ID: <426bed110908191416q35cf8613ue912b741d6285f1c@mail.gmail.com> On Thu, Aug 20, 2009 at 1:44 AM, Patrick Lamaiziere wrote: > Le Wed, 19 Aug 2009 21:16:06 +0800, > Rohit Grover a ?crit : > > > I have developed a driver for the Touchpad device on Apple Macbooks. > > Mine is a Macbook 3,1, and I run FreeBSD7.2 > > Cool! Shall it work on a MacBookPro 3,1? Please give it a try. The number of Y sensors on a MacBookPro might be different. On my MacBook, I've got 20 X sensors and 10 Y sensors; but that is with a mouse-button at the bottom of the touch-sensitive area. The button has been replaced with additional touchpad surface in the MacBookPro. So it will require a bit of experimentation, and even some reverse-engineering. The key to interpreting data from the device is atp_read_sensors(). That might have to change to support newer models. If someone is willing to contribute with testing, I can create a version of the driver which logs additional detail to help us with the reverse engineering. > Do you plan a version to the new usb stack on 8.0? > Certainly. I can't yet run 8.0 on my MacBook. ACPI panics the kernel right at the beginning of boot, and even if I disable ACPI, the kernel is still unable to mount the root partition. I have tried compiling my driver against 8.0, and I see that I will need to adapt to the new USB stack. I'm very keen on moving to 8.0 once it can boot on my laptop. I'd be happy to maintain support for multiple versions of FreeBSD. > > > For my algorithms, I would like to allocate memory dynamically out of > > a small pool of fixed sized structures. I have read a bit about UMA; > > is UMA a good alternative for managing a small pool (~20) of buffers > > (of around 20 bytes in size)? > > I'm not sure for this, IMHO UMA does not care about the size of the > buffers, and malloc uses UMA for the allocation. > But is UMA a very heavy-weight approach to managing a small pool of fixed sized buffers whose total footprint is under 512 bytes? > I've read a bit the source, you should not use spl on 7.x, they are > no-ops. Instead use some mutexes. And you should not use the giant lock. > Thanks for pointing this out. I will research the use of SMP primitives. The 'ums' driver, which is what I am replacing, also uses splx(). Could you tell me which giant lock I am using in my code? Is there any documentation I can refer to for SMP synchronization under FreeBSD? regards, Rohit. From mrkotfw at gmail.com Sun Aug 23 00:39:04 2009 From: mrkotfw at gmail.com (Israel Jacques) Date: Sun Aug 23 00:39:11 2009 Subject: Dell USB keyboard Message-ID: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> Hello all. I have the following keyboard: http://support.dell.com/support/edocs/acc/P76379/sk8135.jpg and I would like to add support for the hot keys and the multimedia buttons including the knob. dmesg: uhub1: on uhub0 uhub1: 3 ports with 2 removable, bus powered ukbd0: on uhub1 kbd2 at ukbd0 uhid0: on uhub1 usbdevs -v: port 2 addr 3: full speed, power 100 mA, config 1, Dell USB Keyboard Hub(0x1003), Dell(0x413c), rev 2.00 port 1 addr 4: full speed, power 50 mA, config 1, Dell USB Keyboard(0x2010), Dell(0x413c), rev 2.00 I tried xev and nothing worked. My question is, how do I go about writing a userland application to access the extra buttons? Would I have to use ioctl(2) to poll /dev/ukbd0? I would like to write the userland application in order to map them to: XF86Back XF86Forward XF86Stop XF86Refresh XF86HomePage XF86Mail XF86MyComputer XF86Calculator XF86AudioMute XF86AudioStop XF86AudioPrev XF86AudioNext XF86AudioPlay XF86AudioLowerVolume XF86AudioRaiseVolume Any suggestions? From freebsd at sopwith.solgatos.com Sun Aug 23 04:20:04 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sun Aug 23 04:20:56 2009 Subject: Dell USB keyboard In-Reply-To: Your message of "Sat, 22 Aug 2009 17:13:41 PDT." <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> Message-ID: <200908230216.CAA12582@sopwith.solgatos.com> > My question is, how do I go about writing a userland application to > access the extra buttons? Would I have to use ioctl(2) to poll > /dev/ukbd0? I would like to write the userland application in order to > map them to: > XF86Back ... > XF86AudioRaiseVolume > > Any suggestions? Can xmodmap(1) do what you need? Appears to be in ports. From henry.hu.sh at gmail.com Sun Aug 23 06:32:16 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Sun Aug 23 06:32:22 2009 Subject: Dell USB keyboard In-Reply-To: <200908230216.CAA12582@sopwith.solgatos.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> Message-ID: <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >> My question is, how do I go about writing a userland application to >> access the extra buttons? Would I have to use ioctl(2) to poll >> /dev/ukbd0? I would like to write the userland application in order to >> map them to: >> XF86Back > ... >> XF86AudioRaiseVolume >> >> Any suggestions? > > Can xmodmap(1) do what you need? ?Appears to be in ports. > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > You might try usbhidaction and usbhidctl on the uhid device. Once I was using a microsoft keyboard, and I hacked the programs a bit, and wrote a configuration file for usbhidaction, and finally I can use the multimedia keys. These programs have problems parsing the Report ID field. You might have to refer to the HID standard to modify them a bit. Good luck. From mrkotfw at gmail.com Mon Aug 24 05:10:34 2009 From: mrkotfw at gmail.com (Israel Jacques) Date: Mon Aug 24 05:10:41 2009 Subject: Dell USB keyboard In-Reply-To: <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> Message-ID: <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> I have the following in my ~/.xmodmaprc: keycode 234 = XF86Back keycode 233 = XF86Forward keycode 232 = XF86Stop keycode 231 = XF86Refresh keycode 130 = XF86HomePage keycode 236 = XF86Mail keycode 198 = XF86MyComputer keycode 161 = XF86Calculator keycode 160 = XF86AudioMute keycode 164 = XF86AudioStop keycode 144 = XF86AudioPrev keycode 153 = XF86AudioNext keycode 162 = XF86AudioPlay keycode 129 = XF86AudioMedia keycode 174 = XF86AudioLowerVolume keycode 176 = XF86AudioRaiseVolume And it doesn't work with my WM. Thanks for the tip. So far, I ran (as root): # usbhidctl -anrv -f /dev/uhid0 Report descriptor: Total input size 0 bytes Total output size 1 bytes Total feature size 1 bytes On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: > On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>> My question is, how do I go about writing a userland application to >>> access the extra buttons? Would I have to use ioctl(2) to poll >>> /dev/ukbd0? I would like to write the userland application in order to >>> map them to: >>> XF86Back >> ... >>> XF86AudioRaiseVolume >>> >>> Any suggestions? >> >> Can xmodmap(1) do what you need? ?Appears to be in ports. >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >> > You might try usbhidaction and usbhidctl on the uhid device. > Once I was using a microsoft keyboard, and I hacked the programs a > bit, and wrote a configuration file for usbhidaction, and finally I > can use the multimedia keys. > These programs have problems parsing the Report ID field. You might > have to refer to the HID standard to modify them a bit. > > Good luck. > From henry.hu.sh at gmail.com Tue Aug 25 05:02:38 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Tue Aug 25 05:02:45 2009 Subject: Dell USB keyboard In-Reply-To: <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> Message-ID: <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> On Mon, Aug 24, 2009 at 1:10 PM, Israel Jacques wrote: > I have the following in my ~/.xmodmaprc: > > keycode 234 = XF86Back > keycode 233 = XF86Forward > keycode 232 = XF86Stop > keycode 231 = XF86Refresh > keycode 130 = XF86HomePage > keycode 236 = XF86Mail > keycode 198 = XF86MyComputer > keycode 161 = XF86Calculator > keycode 160 = XF86AudioMute > keycode 164 = XF86AudioStop > keycode 144 = XF86AudioPrev > keycode 153 = XF86AudioNext > keycode 162 = XF86AudioPlay > keycode 129 = XF86AudioMedia > keycode 174 = XF86AudioLowerVolume > keycode 176 = XF86AudioRaiseVolume > > And it doesn't work with my WM. If the messages of the multimedia keys are sent through the uhid device, then you need to write a configuration file for the usbhidaction, specify the keys and corresponding commands, and run usbhidaction when keyboard inserted. Can you see anything when a key is pressed with usbhidctl -alrv -f /dev/uhid0 ? > > Thanks for the tip. > > So far, I ran (as root): > > # usbhidctl -anrv -f /dev/uhid0 > Report descriptor: > Total ? input size 0 bytes > Total ?output size 1 bytes > Total feature size 1 bytes > > On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: >> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>>> My question is, how do I go about writing a userland application to >>>> access the extra buttons? Would I have to use ioctl(2) to poll >>>> /dev/ukbd0? I would like to write the userland application in order to >>>> map them to: >>>> XF86Back >>> ... >>>> XF86AudioRaiseVolume >>>> >>>> Any suggestions? >>> >>> Can xmodmap(1) do what you need? ?Appears to be in ports. >>> _______________________________________________ >>> freebsd-drivers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>> >> You might try usbhidaction and usbhidctl on the uhid device. >> Once I was using a microsoft keyboard, and I hacked the programs a >> bit, and wrote a configuration file for usbhidaction, and finally I >> can use the multimedia keys. >> These programs have problems parsing the Report ID field. You might >> have to refer to the HID standard to modify them a bit. >> >> Good luck. >> > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > From mrkotfw at gmail.com Tue Aug 25 06:03:13 2009 From: mrkotfw at gmail.com (Israel Jacques) Date: Tue Aug 25 06:03:21 2009 Subject: Dell USB keyboard In-Reply-To: <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> Message-ID: <5cd4c4cd0908242303q16031125m62d1122f7a024bd2@mail.gmail.com> Hi Henry. After about a minute of running: usbhidctl -alrv -f /dev/uhid0 > dump, I get: 00000000 52 65 70 6f 72 74 20 64 65 73 63 72 69 70 74 6f |Report descripto| 00000010 72 3a 0a 54 6f 74 61 6c 20 20 20 69 6e 70 75 74 |r:.Total input| 00000020 20 73 69 7a 65 20 30 20 62 79 74 65 73 0a 54 6f | size 0 bytes.To| 00000030 74 61 6c 20 20 6f 75 74 70 75 74 20 73 69 7a 65 |tal output size| 00000040 20 31 20 62 79 74 65 73 0a 54 6f 74 61 6c 20 66 | 1 bytes.Total f| 00000050 65 61 74 75 72 65 20 73 69 7a 65 20 31 20 62 79 |eature size 1 by| 00000060 74 65 73 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a |tes.............| 00000070 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a |................| * 0b675000 There is an option in the BIOS that allows me to disable BIOS support for USB. I'll reboot and report back on whether or not it makes a difference. As with usbhidaction, I'm assuming I would need to be able to get output from /dev/uhid0 in order to write a configuration file. Correct? On Mon, Aug 24, 2009 at 10:02 PM, Henry Hu wrote: > On Mon, Aug 24, 2009 at 1:10 PM, Israel Jacques wrote: >> I have the following in my ~/.xmodmaprc: >> >> keycode 234 = XF86Back >> keycode 233 = XF86Forward >> keycode 232 = XF86Stop >> keycode 231 = XF86Refresh >> keycode 130 = XF86HomePage >> keycode 236 = XF86Mail >> keycode 198 = XF86MyComputer >> keycode 161 = XF86Calculator >> keycode 160 = XF86AudioMute >> keycode 164 = XF86AudioStop >> keycode 144 = XF86AudioPrev >> keycode 153 = XF86AudioNext >> keycode 162 = XF86AudioPlay >> keycode 129 = XF86AudioMedia >> keycode 174 = XF86AudioLowerVolume >> keycode 176 = XF86AudioRaiseVolume >> >> And it doesn't work with my WM. > If the messages of the multimedia keys are sent through the uhid > device, then you need to write a configuration file for the > usbhidaction, specify the keys and corresponding commands, and run > usbhidaction when keyboard inserted. > Can you see anything when a key is pressed with usbhidctl -alrv -f /dev/uhid0 ? >> >> Thanks for the tip. >> >> So far, I ran (as root): >> >> # usbhidctl -anrv -f /dev/uhid0 >> Report descriptor: >> Total ? input size 0 bytes >> Total ?output size 1 bytes >> Total feature size 1 bytes >> >> On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: >>> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>>>> My question is, how do I go about writing a userland application to >>>>> access the extra buttons? Would I have to use ioctl(2) to poll >>>>> /dev/ukbd0? I would like to write the userland application in order to >>>>> map them to: >>>>> XF86Back >>>> ... >>>>> XF86AudioRaiseVolume >>>>> >>>>> Any suggestions? >>>> >>>> Can xmodmap(1) do what you need? ?Appears to be in ports. >>>> _______________________________________________ >>>> freebsd-drivers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>> >>> You might try usbhidaction and usbhidctl on the uhid device. >>> Once I was using a microsoft keyboard, and I hacked the programs a >>> bit, and wrote a configuration file for usbhidaction, and finally I >>> can use the multimedia keys. >>> These programs have problems parsing the Report ID field. You might >>> have to refer to the HID standard to modify them a bit. >>> >>> Good luck. >>> >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >> > From henry.hu.sh at gmail.com Tue Aug 25 07:51:37 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Tue Aug 25 07:51:47 2009 Subject: Dell USB keyboard In-Reply-To: <5cd4c4cd0908242303q16031125m62d1122f7a024bd2@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> <5cd4c4cd0908242303q16031125m62d1122f7a024bd2@mail.gmail.com> Message-ID: <53a1e0710908250051k297cff18l25daeb1e27656ac5@mail.gmail.com> On Tue, Aug 25, 2009 at 2:03 PM, Israel Jacques wrote: > Hi Henry. > > After about a minute of running: usbhidctl -alrv -f /dev/uhid0 > dump, I get: > 00000000 ?52 65 70 6f 72 74 20 64 ?65 73 63 72 69 70 74 6f ?|Report descripto| > 00000010 ?72 3a 0a 54 6f 74 61 6c ?20 20 20 69 6e 70 75 74 ?|r:.Total ? input| > 00000020 ?20 73 69 7a 65 20 30 20 ?62 79 74 65 73 0a 54 6f ?| size 0 bytes.To| > 00000030 ?74 61 6c 20 20 6f 75 74 ?70 75 74 20 73 69 7a 65 ?|tal ?output size| > 00000040 ?20 31 20 62 79 74 65 73 ?0a 54 6f 74 61 6c 20 66 ?| 1 bytes.Total f| > 00000050 ?65 61 74 75 72 65 20 73 ?69 7a 65 20 31 20 62 79 ?|eature size 1 by| > 00000060 ?74 65 73 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|tes.............| > 00000070 ?0a 0a 0a 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|................| > * > 0b675000 > > There is an option in the BIOS that allows me to disable BIOS support > for USB. I'll reboot and report back on whether or not it makes a > difference. > > As with usbhidaction, I'm assuming I would need to be able to get > output from /dev/uhid0 in order to write a configuration file. > Correct? I'm sorry. After googling more, I find out that most multimedia keys are sent through the normal keyboard device, it seems like only the volume control information is sent through other devices. So if you run xev, and press the multimedia keys, you would see these keycodes, right? Which WM are you using? For compiz, you may specify the program to run in the CCSM. I'm not familiar with metacity, but I know at least you may specify it in gconf-editor. > > On Mon, Aug 24, 2009 at 10:02 PM, Henry Hu wrote: >> On Mon, Aug 24, 2009 at 1:10 PM, Israel Jacques wrote: >>> I have the following in my ~/.xmodmaprc: >>> >>> keycode 234 = XF86Back >>> keycode 233 = XF86Forward >>> keycode 232 = XF86Stop >>> keycode 231 = XF86Refresh >>> keycode 130 = XF86HomePage >>> keycode 236 = XF86Mail >>> keycode 198 = XF86MyComputer >>> keycode 161 = XF86Calculator >>> keycode 160 = XF86AudioMute >>> keycode 164 = XF86AudioStop >>> keycode 144 = XF86AudioPrev >>> keycode 153 = XF86AudioNext >>> keycode 162 = XF86AudioPlay >>> keycode 129 = XF86AudioMedia >>> keycode 174 = XF86AudioLowerVolume >>> keycode 176 = XF86AudioRaiseVolume >>> >>> And it doesn't work with my WM. >> If the messages of the multimedia keys are sent through the uhid >> device, then you need to write a configuration file for the >> usbhidaction, specify the keys and corresponding commands, and run >> usbhidaction when keyboard inserted. >> Can you see anything when a key is pressed with usbhidctl -alrv -f /dev/uhid0 ? >>> >>> Thanks for the tip. >>> >>> So far, I ran (as root): >>> >>> # usbhidctl -anrv -f /dev/uhid0 >>> Report descriptor: >>> Total ? input size 0 bytes >>> Total ?output size 1 bytes >>> Total feature size 1 bytes >>> >>> On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: >>>> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>>>>> My question is, how do I go about writing a userland application to >>>>>> access the extra buttons? Would I have to use ioctl(2) to poll >>>>>> /dev/ukbd0? I would like to write the userland application in order to >>>>>> map them to: >>>>>> XF86Back >>>>> ... >>>>>> XF86AudioRaiseVolume >>>>>> >>>>>> Any suggestions? >>>>> >>>>> Can xmodmap(1) do what you need? ?Appears to be in ports. >>>>> _______________________________________________ >>>>> freebsd-drivers@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>>> >>>> You might try usbhidaction and usbhidctl on the uhid device. >>>> Once I was using a microsoft keyboard, and I hacked the programs a >>>> bit, and wrote a configuration file for usbhidaction, and finally I >>>> can use the multimedia keys. >>>> These programs have problems parsing the Report ID field. You might >>>> have to refer to the HID standard to modify them a bit. >>>> >>>> Good luck. >>>> >>> _______________________________________________ >>> freebsd-drivers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>> >> > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > From mrkotfw at gmail.com Tue Aug 25 16:32:21 2009 From: mrkotfw at gmail.com (Israel Jacques) Date: Tue Aug 25 16:32:28 2009 Subject: Dell USB keyboard In-Reply-To: <53a1e0710908250051k297cff18l25daeb1e27656ac5@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> <5cd4c4cd0908242303q16031125m62d1122f7a024bd2@mail.gmail.com> <53a1e0710908250051k297cff18l25daeb1e27656ac5@mail.gmail.com> Message-ID: <5cd4c4cd0908250932o10abd2d0n32a3425c1e1f5fca@mail.gmail.com> Hello. Yeah, I'm starting to see that. Well, It's a good thing. At least there is a difference between the volume knob and the keyboard. Maybe usbhidctl isn't what I need since I receive no output. I use Openbox as my WM. Using xev with or without LinEAK still produces no results. I just tried running lineakd and no go. The keyboard is indeed supported by LinEAK, but I get no output. At first, I was getting Xlib errors but after restarting it stopped. This is very odd. I did try: Section "InputDevice" Identifier "Keyboard" Driver "kbd" Option "XkbLayout" "dvorak,us" Option "XkbOptions" "grp:alt_caps_toggle" Option "XkbModel" "pc104" Option "XkbRules" "dellsk8125" Option "CustomKeycodes" "False" EndSection The settings above gets me: (**) Option "CoreKeyboard" (**) Keyboard: always reports core events (**) Option "Protocol" "standard" (**) Keyboard: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "dellsk8125" (**) Keyboard: XkbRules: "dellsk8125" (**) Option "XkbModel" "pc104" (**) Keyboard: XkbModel: "pc104" (**) Option "XkbLayout" "dvorak,us" (**) Keyboard: XkbLayout: "dvorak,us" (**) Option "XkbOptions" "grp:alt_caps_toggle" (**) Keyboard: XkbOptions: "grp:alt_caps_toggle" (**) Option "CustomKeycodes" "False" (**) Keyboard: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard" (type: KEYBOARD) (EE) XKB: Couldn't open rules file /usr/local/share/X11/xkb/rules/dellsk8125 (EE) XKB: No components provided for device Keyboard (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap Apparently I don't know what device X.org is using. I tried the following (Option "Device" "/dev/foo" after calling ls /dev/*kbd*): /dev/atkbd0 /dev/kbd0 /dev/kbd1 /dev/kbd2 /dev/kbdmux0 /dev/ukbd0 Which none worked. Could the only solution be to use a USB to PS/2 adapter or to simply hack away at the ukbd(4) driver? Since X.org doesn't use any of the devices, what could it be using? On Tue, Aug 25, 2009 at 12:51 AM, Henry Hu wrote: > On Tue, Aug 25, 2009 at 2:03 PM, Israel Jacques wrote: >> Hi Henry. >> >> After about a minute of running: usbhidctl -alrv -f /dev/uhid0 > dump, I get: >> 00000000 ?52 65 70 6f 72 74 20 64 ?65 73 63 72 69 70 74 6f ?|Report descripto| >> 00000010 ?72 3a 0a 54 6f 74 61 6c ?20 20 20 69 6e 70 75 74 ?|r:.Total ? input| >> 00000020 ?20 73 69 7a 65 20 30 20 ?62 79 74 65 73 0a 54 6f ?| size 0 bytes.To| >> 00000030 ?74 61 6c 20 20 6f 75 74 ?70 75 74 20 73 69 7a 65 ?|tal ?output size| >> 00000040 ?20 31 20 62 79 74 65 73 ?0a 54 6f 74 61 6c 20 66 ?| 1 bytes.Total f| >> 00000050 ?65 61 74 75 72 65 20 73 ?69 7a 65 20 31 20 62 79 ?|eature size 1 by| >> 00000060 ?74 65 73 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|tes.............| >> 00000070 ?0a 0a 0a 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|................| >> * >> 0b675000 >> >> There is an option in the BIOS that allows me to disable BIOS support >> for USB. I'll reboot and report back on whether or not it makes a >> difference. >> >> As with usbhidaction, I'm assuming I would need to be able to get >> output from /dev/uhid0 in order to write a configuration file. >> Correct? > > I'm sorry. After googling more, I find out that most multimedia keys > are sent through the normal keyboard device, it seems like only the > volume control information is sent through other devices. > So if you run xev, and press the multimedia keys, you would see these > keycodes, right? > Which WM are you using? For compiz, you may specify the program to run > in the CCSM. I'm not familiar with metacity, but I know at least you > may specify it in gconf-editor. > >> >> On Mon, Aug 24, 2009 at 10:02 PM, Henry Hu wrote: >>> On Mon, Aug 24, 2009 at 1:10 PM, Israel Jacques wrote: >>>> I have the following in my ~/.xmodmaprc: >>>> >>>> keycode 234 = XF86Back >>>> keycode 233 = XF86Forward >>>> keycode 232 = XF86Stop >>>> keycode 231 = XF86Refresh >>>> keycode 130 = XF86HomePage >>>> keycode 236 = XF86Mail >>>> keycode 198 = XF86MyComputer >>>> keycode 161 = XF86Calculator >>>> keycode 160 = XF86AudioMute >>>> keycode 164 = XF86AudioStop >>>> keycode 144 = XF86AudioPrev >>>> keycode 153 = XF86AudioNext >>>> keycode 162 = XF86AudioPlay >>>> keycode 129 = XF86AudioMedia >>>> keycode 174 = XF86AudioLowerVolume >>>> keycode 176 = XF86AudioRaiseVolume >>>> >>>> And it doesn't work with my WM. >>> If the messages of the multimedia keys are sent through the uhid >>> device, then you need to write a configuration file for the >>> usbhidaction, specify the keys and corresponding commands, and run >>> usbhidaction when keyboard inserted. >>> Can you see anything when a key is pressed with usbhidctl -alrv -f /dev/uhid0 ? >>>> >>>> Thanks for the tip. >>>> >>>> So far, I ran (as root): >>>> >>>> # usbhidctl -anrv -f /dev/uhid0 >>>> Report descriptor: >>>> Total ? input size 0 bytes >>>> Total ?output size 1 bytes >>>> Total feature size 1 bytes >>>> >>>> On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: >>>>> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>>>>>> My question is, how do I go about writing a userland application to >>>>>>> access the extra buttons? Would I have to use ioctl(2) to poll >>>>>>> /dev/ukbd0? I would like to write the userland application in order to >>>>>>> map them to: >>>>>>> XF86Back >>>>>> ... >>>>>>> XF86AudioRaiseVolume >>>>>>> >>>>>>> Any suggestions? >>>>>> >>>>>> Can xmodmap(1) do what you need? ?Appears to be in ports. >>>>>> _______________________________________________ >>>>>> freebsd-drivers@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>>>> >>>>> You might try usbhidaction and usbhidctl on the uhid device. >>>>> Once I was using a microsoft keyboard, and I hacked the programs a >>>>> bit, and wrote a configuration file for usbhidaction, and finally I >>>>> can use the multimedia keys. >>>>> These programs have problems parsing the Report ID field. You might >>>>> have to refer to the HID standard to modify them a bit. >>>>> >>>>> Good luck. >>>>> >>>> _______________________________________________ >>>> freebsd-drivers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>> >>> >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >> > From mrkotfw at gmail.com Fri Aug 28 07:32:25 2009 From: mrkotfw at gmail.com (Israel Jacques) Date: Fri Aug 28 08:25:51 2009 Subject: Dell USB keyboard In-Reply-To: <53a1e0710908271101q75f6379fkabec2d3b5776c084@mail.gmail.com> References: <5cd4c4cd0908221713y5d396946h5e4000ee11a48e0c@mail.gmail.com> <200908230216.CAA12582@sopwith.solgatos.com> <53a1e0710908222309x78b04000t40e31fbee495355c@mail.gmail.com> <5cd4c4cd0908232210p61f1b56aw660aad2bb4e53fbb@mail.gmail.com> <53a1e0710908242202n1345eb1fj53a7a2bf1d3672f@mail.gmail.com> <5cd4c4cd0908242303q16031125m62d1122f7a024bd2@mail.gmail.com> <53a1e0710908250051k297cff18l25daeb1e27656ac5@mail.gmail.com> <5cd4c4cd0908250932o10abd2d0n32a3425c1e1f5fca@mail.gmail.com> <53a1e0710908271101q75f6379fkabec2d3b5776c084@mail.gmail.com> Message-ID: <5cd4c4cd0908271620s4339ab3ck1917f3ecba58f253@mail.gmail.com> None whatsoever. It could also be because the ports are legacy USB ports. I'm stumped. What other options do I have? On Thu, Aug 27, 2009 at 11:01 AM, Henry Hu wrote: > Is there any key event when you press the multimedia keys in the xev window? > > On Wed, Aug 26, 2009 at 12:32 AM, Israel Jacques wrote: >> Hello. >> Yeah, I'm starting to see that. Well, It's a good thing. At least >> there is a difference between the volume knob and the keyboard. Maybe >> usbhidctl isn't what I need since I receive no output. >> >> I use Openbox as my WM. Using xev with or without LinEAK still >> produces no results. >> >> I just tried running lineakd and no go. The keyboard is indeed >> supported by LinEAK, but I get no output. At first, I was getting Xlib >> errors but after restarting it stopped. >> >> This is very odd. >> >> I did try: >> Section "InputDevice" >> ? ? ? ?Identifier ? "Keyboard" >> ? ? ? ?Driver ? ? ? "kbd" >> ? ? ? ?Option ? ? ? "XkbLayout" "dvorak,us" >> ? ? ? ?Option ? ? ? "XkbOptions" "grp:alt_caps_toggle" >> ? ? ? ?Option ? ? ? "XkbModel" "pc104" >> ? ? ? ?Option ? ? ? "XkbRules" "dellsk8125" >> ? ? ? ?Option ? ? ? "CustomKeycodes" "False" >> EndSection >> >> The settings above gets me: >> (**) Option "CoreKeyboard" >> (**) Keyboard: always reports core events >> (**) Option "Protocol" "standard" >> (**) Keyboard: Protocol: standard >> (**) Option "AutoRepeat" "500 30" >> (**) Option "XkbRules" "dellsk8125" >> (**) Keyboard: XkbRules: "dellsk8125" >> (**) Option "XkbModel" "pc104" >> (**) Keyboard: XkbModel: "pc104" >> (**) Option "XkbLayout" "dvorak,us" >> (**) Keyboard: XkbLayout: "dvorak,us" >> (**) Option "XkbOptions" "grp:alt_caps_toggle" >> (**) Keyboard: XkbOptions: "grp:alt_caps_toggle" >> (**) Option "CustomKeycodes" "False" >> (**) Keyboard: CustomKeycodes disabled >> (II) XINPUT: Adding extended input device "Keyboard" (type: KEYBOARD) >> (EE) XKB: Couldn't open rules file /usr/local/share/X11/xkb/rules/dellsk8125 >> (EE) XKB: No components provided for device Keyboard >> (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap >> >> Apparently I don't know what device X.org is using. I tried the >> following (Option "Device" "/dev/foo" after calling ls /dev/*kbd*): >> /dev/atkbd0 >> /dev/kbd0 >> /dev/kbd1 >> /dev/kbd2 >> /dev/kbdmux0 >> /dev/ukbd0 >> >> Which none worked. Could the only solution be to use a USB to PS/2 >> adapter or to simply hack away at the ukbd(4) driver? >> >> Since X.org doesn't use any of the devices, what could it be using? >> >> On Tue, Aug 25, 2009 at 12:51 AM, Henry Hu wrote: >>> On Tue, Aug 25, 2009 at 2:03 PM, Israel Jacques wrote: >>>> Hi Henry. >>>> >>>> After about a minute of running: usbhidctl -alrv -f /dev/uhid0 > dump, I get: >>>> 00000000 ?52 65 70 6f 72 74 20 64 ?65 73 63 72 69 70 74 6f ?|Report descripto| >>>> 00000010 ?72 3a 0a 54 6f 74 61 6c ?20 20 20 69 6e 70 75 74 ?|r:.Total ? input| >>>> 00000020 ?20 73 69 7a 65 20 30 20 ?62 79 74 65 73 0a 54 6f ?| size 0 bytes.To| >>>> 00000030 ?74 61 6c 20 20 6f 75 74 ?70 75 74 20 73 69 7a 65 ?|tal ?output size| >>>> 00000040 ?20 31 20 62 79 74 65 73 ?0a 54 6f 74 61 6c 20 66 ?| 1 bytes.Total f| >>>> 00000050 ?65 61 74 75 72 65 20 73 ?69 7a 65 20 31 20 62 79 ?|eature size 1 by| >>>> 00000060 ?74 65 73 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|tes.............| >>>> 00000070 ?0a 0a 0a 0a 0a 0a 0a 0a ?0a 0a 0a 0a 0a 0a 0a 0a ?|................| >>>> * >>>> 0b675000 >>>> >>>> There is an option in the BIOS that allows me to disable BIOS support >>>> for USB. I'll reboot and report back on whether or not it makes a >>>> difference. >>>> >>>> As with usbhidaction, I'm assuming I would need to be able to get >>>> output from /dev/uhid0 in order to write a configuration file. >>>> Correct? >>> >>> I'm sorry. After googling more, I find out that most multimedia keys >>> are sent through the normal keyboard device, it seems like only the >>> volume control information is sent through other devices. >>> So if you run xev, and press the multimedia keys, you would see these >>> keycodes, right? >>> Which WM are you using? For compiz, you may specify the program to run >>> in the CCSM. I'm not familiar with metacity, but I know at least you >>> may specify it in gconf-editor. >>> >>>> >>>> On Mon, Aug 24, 2009 at 10:02 PM, Henry Hu wrote: >>>>> On Mon, Aug 24, 2009 at 1:10 PM, Israel Jacques wrote: >>>>>> I have the following in my ~/.xmodmaprc: >>>>>> >>>>>> keycode 234 = XF86Back >>>>>> keycode 233 = XF86Forward >>>>>> keycode 232 = XF86Stop >>>>>> keycode 231 = XF86Refresh >>>>>> keycode 130 = XF86HomePage >>>>>> keycode 236 = XF86Mail >>>>>> keycode 198 = XF86MyComputer >>>>>> keycode 161 = XF86Calculator >>>>>> keycode 160 = XF86AudioMute >>>>>> keycode 164 = XF86AudioStop >>>>>> keycode 144 = XF86AudioPrev >>>>>> keycode 153 = XF86AudioNext >>>>>> keycode 162 = XF86AudioPlay >>>>>> keycode 129 = XF86AudioMedia >>>>>> keycode 174 = XF86AudioLowerVolume >>>>>> keycode 176 = XF86AudioRaiseVolume >>>>>> >>>>>> And it doesn't work with my WM. >>>>> If the messages of the multimedia keys are sent through the uhid >>>>> device, then you need to write a configuration file for the >>>>> usbhidaction, specify the keys and corresponding commands, and run >>>>> usbhidaction when keyboard inserted. >>>>> Can you see anything when a key is pressed with usbhidctl -alrv -f /dev/uhid0 ? >>>>>> >>>>>> Thanks for the tip. >>>>>> >>>>>> So far, I ran (as root): >>>>>> >>>>>> # usbhidctl -anrv -f /dev/uhid0 >>>>>> Report descriptor: >>>>>> Total ? input size 0 bytes >>>>>> Total ?output size 1 bytes >>>>>> Total feature size 1 bytes >>>>>> >>>>>> On Sat, Aug 22, 2009 at 11:09 PM, Henry Hu wrote: >>>>>>> On Sun, Aug 23, 2009 at 10:16 AM, Dieter wrote: >>>>>>>>> My question is, how do I go about writing a userland application to >>>>>>>>> access the extra buttons? Would I have to use ioctl(2) to poll >>>>>>>>> /dev/ukbd0? I would like to write the userland application in order to >>>>>>>>> map them to: >>>>>>>>> XF86Back >>>>>>>> ... >>>>>>>>> XF86AudioRaiseVolume >>>>>>>>> >>>>>>>>> Any suggestions? >>>>>>>> >>>>>>>> Can xmodmap(1) do what you need? ?Appears to be in ports. >>>>>>>> _______________________________________________ >>>>>>>> freebsd-drivers@freebsd.org mailing list >>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>>>>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>>>>>> >>>>>>> You might try usbhidaction and usbhidctl on the uhid device. >>>>>>> Once I was using a microsoft keyboard, and I hacked the programs a >>>>>>> bit, and wrote a configuration file for usbhidaction, and finally I >>>>>>> can use the multimedia keys. >>>>>>> These programs have problems parsing the Report ID field. You might >>>>>>> have to refer to the HID standard to modify them a bit. >>>>>>> >>>>>>> Good luck. >>>>>>> >>>>>> _______________________________________________ >>>>>> freebsd-drivers@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>>>> >>>>> >>>> _______________________________________________ >>>> freebsd-drivers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >>>> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" >>>> >>> >> >