Caps Lock remapping not working
On 20.11 2005, Benjamin Herrenschmidt outgrape: On Sun, 2005-11-20 at 23:42 +, Jochen Voss wrote: > > Hello Benjamin, > > > > On Mon, Nov 21, 2005 at 10:23:53AM +1100, Benjamin Herrenschmidt wrote: > > > On the other hand, "Fn" is handled in hardware for ADB keyboards and by > > > the kernel (simulating hardware) afaik, in OS X, and I suspect it might > > > be a good idea to do the same, that is, have a translation map of the HW > > > keycodes when Fn is pressed in the kernel driver. > > > Why would this be a good idea? > > > > Disadvantage: Not passing fn-key presses to the X-server would prevent > > users from having their own mappings for fn-something combinations. > > 1) you could still pass it down > > 2) While the ability to customize mappings in weird ways is cool for > 0.1% of users who are "l33t", it's imho totally useless if the remaining > 99.9% of users end up by default with a non-working map I wonder if my problems remapping the Caps Lock key have something to do with this issue. I've remapped keycode 58 to Control_L for the console, but this has little effect. Caps Lock is nullified, but the key doesn't function as Control_L. Nevertheless, showkey and evdebug show key 58 getting pressed and released. It's a similar story for xorg & mol. Various tools tell me Key 58 is getting pressed, but Linux can't seem to do what it should with those keypresses. Other key remappings work fine, and the OS X remapping also works. This is on the Powerbook 6,8 1.5GHz G4 12" with Canadian French ADB keyboard. -- Guy Yasko -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Sun, 2005-11-20 at 23:42 +, Jochen Voss wrote: > Hello Benjamin, > > On Mon, Nov 21, 2005 at 10:23:53AM +1100, Benjamin Herrenschmidt wrote: > > On the other hand, "Fn" is handled in hardware for ADB keyboards and by > > the kernel (simulating hardware) afaik, in OS X, and I suspect it might > > be a good idea to do the same, that is, have a translation map of the HW > > keycodes when Fn is pressed in the kernel driver. > Why would this be a good idea? > > Disadvantage: Not passing fn-key presses to the X-server would prevent > users from having their own mappings for fn-something combinations. 1) you could still pass it down 2) While the ability to customize mappings in weird ways is cool for 0.1% of users who are "l33t", it's imho totally useless if the remaining 99.9% of users end up by default with a non-working map 3) guess what ? that is the case now (non working map) 4) it sucks big time to need different maps depending on wether your laptop has the ADB or the USB version of the keyboard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd and NoTapTyping option?
Hello Matthias, Matthias Grimm <[EMAIL PROTECTED]> wrote: > On Sun, 20 Nov 2005 12:30:31 +0100 (CET) > Michael Schmitz <[EMAIL PROTECTED]> wrote: > >> > does anybody use the NoTapTyping function of pbbuttonsd with success? >> > How much would you pay to keep it? ;-) >> >> I don't use that function - at least not in pbbuttonsd. moussemu takes >> care of that for me. > > That's what I thought. So there is no real need for that function in > pbbuttonsd anymore No, I use it and I can not say if it works, but I have not the problem like without and I do not have the problems like with mouseemu. Bye, Jörg. -- Wer einen Traum verwirklichen will, muss erst aufwachen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
Hello Benjamin, On Mon, Nov 21, 2005 at 10:23:53AM +1100, Benjamin Herrenschmidt wrote: > On the other hand, "Fn" is handled in hardware for ADB keyboards and by > the kernel (simulating hardware) afaik, in OS X, and I suspect it might > be a good idea to do the same, that is, have a translation map of the HW > keycodes when Fn is pressed in the kernel driver. Why would this be a good idea? Disadvantage: Not passing fn-key presses to the X-server would prevent users from having their own mappings for fn-something combinations. All the best, Jochen -- http://seehuhn.de/ signature.asc Description: Digital signature
Re: 2.6.15-rc2
> PS.: To answer the question you did not ask: the thing which is > "working" is (according to rumours, see the list archives), that with > an unpatched kernel and some super-secret (not yet in CVS?) versions > of Xorg you seemingly can get keyboard events from the fn-key under > X11. Afaik, current -git does emit KEY_FN. It might not be in the X.org default keycodes, but that's a userland fix I suppose... On the other hand, "Fn" is handled in hardware for ADB keyboards and by the kernel (simulating hardware) afaik, in OS X, and I suspect it might be a good idea to do the same, that is, have a translation map of the HW keycodes when Fn is pressed in the kernel driver. It may require some politics to get accepted by the input layer maintainer though. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Sun, 2005-11-20 at 22:46 +0100, Elimar Riesebieter wrote: > On Mon, 21 Nov 2005 the mental interface of > Benjamin Herrenschmidt told: > > > On Sun, 2005-11-20 at 22:30 +0100, Elimar Riesebieter wrote: > > > On Mon, 21 Nov 2005 the mental interface of > > > Benjamin Herrenschmidt told: > > > > > > > On Sun, 2005-11-20 at 14:51 +0100, Elimar Riesebieter wrote: > > > > > Hi all, > > > > > > > > > > please find attached fn-ky patch which works with 2.6.15-rc2. > > > > > > > > What is the point of this patch ? > > > > > > This patch is needed to get the fn-key working on powerbooks like > > > mine, which is a PowerBook5,6. > > > > Can you be more precise ? What is not "working" with the existing code ? > > Hmm, does the fn-key work with the vanilla one, which I didn't test? Well, it should send a KEY_FN to userland, but I don't have such a keyboard to test. I don't understand the point of your patch. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
Hello, On Mon, Nov 21, 2005 at 08:34:11AM +1100, Benjamin Herrenschmidt wrote: > Can you be more precise ? What is not "working" with the existing code ? I did not try 2.6.15, but with earlier kernels pressing "fn" was noticed neither by xev under X11 nor by showkeys on the console. Therefore you cannot map fn+something combinationsto anything useful, neither under X11 nor on the console. On PowerBooks the usual combinations to get pageup, pagedown etc. involve the fn-key and thus you have to do either without pageup, pagedown, home and end keys, or at least use key combinations which are different from the MacOS ones. Using, let's say, mutt under these conditions can be quite a challenge. I hope this helps, Jochen PS.: To answer the question you did not ask: the thing which is "working" is (according to rumours, see the list archives), that with an unpatched kernel and some super-secret (not yet in CVS?) versions of Xorg you seemingly can get keyboard events from the fn-key under X11. -- http://seehuhn.de/ signature.asc Description: Digital signature
mol and 2.6.15
Hi all, I hve a fresh new 2.6.15-rc2 running. Build mol via make-kpkg. $ startmol -X gives: insmod /lib/modules/2.6.15-rc2-aragorn/misc/mol.ko mol: Unknown symbol __flush_icache_range which was mentioned while building as well: LD [M] /usr/src/modules/mol/src/kmod/Linux/../build/mol.o Building modules, stage 2. MODPOST *** Warning: "__flush_icache_range" [/usr/src/modules/mol/src/kmod/Linux/../build/mol.ko] undefined! Elimar -- "Talking much about oneself can also be a means to conceal oneself." -Friedrich Nietzsche -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Sun, 20 Nov 2005 the mental interface of Elimar Riesebieter told: [...] > Hmm, does the fn-key work with the vanilla one, which I didn't test? No, it doesn't. Elimar -- The path to source is always uphill! -unknown- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Mon, 21 Nov 2005 the mental interface of Benjamin Herrenschmidt told: > On Sun, 2005-11-20 at 22:30 +0100, Elimar Riesebieter wrote: > > On Mon, 21 Nov 2005 the mental interface of > > Benjamin Herrenschmidt told: > > > > > On Sun, 2005-11-20 at 14:51 +0100, Elimar Riesebieter wrote: > > > > Hi all, > > > > > > > > please find attached fn-ky patch which works with 2.6.15-rc2. > > > > > > What is the point of this patch ? > > > > This patch is needed to get the fn-key working on powerbooks like > > mine, which is a PowerBook5,6. > > Can you be more precise ? What is not "working" with the existing code ? Hmm, does the fn-key work with the vanilla one, which I didn't test? Elimar -- .~. /V\ L I N U X /( )\ >Phear the Penguin< ^^-^^ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Sun, 2005-11-20 at 22:30 +0100, Elimar Riesebieter wrote: > On Mon, 21 Nov 2005 the mental interface of > Benjamin Herrenschmidt told: > > > On Sun, 2005-11-20 at 14:51 +0100, Elimar Riesebieter wrote: > > > Hi all, > > > > > > please find attached fn-ky patch which works with 2.6.15-rc2. > > > > What is the point of this patch ? > > This patch is needed to get the fn-key working on powerbooks like > mine, which is a PowerBook5,6. Can you be more precise ? What is not "working" with the existing code ? Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Mon, 21 Nov 2005 the mental interface of Benjamin Herrenschmidt told: > On Sun, 2005-11-20 at 14:51 +0100, Elimar Riesebieter wrote: > > Hi all, > > > > please find attached fn-ky patch which works with 2.6.15-rc2. > > What is the point of this patch ? This patch is needed to get the fn-key working on powerbooks like mine, which is a PowerBook5,6. Elimar -- We all know Linux is great... it does infinite loops in 5 seconds. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-rc2
On Sun, 2005-11-20 at 14:51 +0100, Elimar Riesebieter wrote: > Hi all, > > please find attached fn-ky patch which works with 2.6.15-rc2. What is the point of this patch ? Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Messaggio non Recapitato
Il sistema Antivirus della posta elettronica Rai non permette la consegna del messaggio con soggetto : Important Il messaggio inviato da : debian-powerpc@lists.debian.org é stato cancellato perchè l' estensione del file allegato non é accettata.
debian sarge on new iBook
Hi, I'm new in debian and last week I bought a new iBook G4. I installed debian sarge and I'm running on 2.6.8-powerpc kernel (the one coming with the installation). After installation I found some hints on the list and got my iBook run X (Kde) correctly; brightness and eject buttons work and sleep functionality seems to work too with pbbuttonsd_0.6.6-3_powerpc. Running lsmod I can see pmacsound modules loaded but Sound is not working at all [EMAIL PROTECTED]:~$ lsmod Module Size Used by ipv6 323928 17 appletalk 43456 20 uninorth_agp8544 1 agpgart42412 1 uninorth_agp tsdev 8640 0 joydev 12000 0 evdev 11968 3 eth139425480 0 ehci_hcd 37156 0 sungem 36836 0 crc32 4832 1 sungem sungem_phy 10240 1 sungem ohci1394 41924 0 therm_adt746x 12460 0 sr_mod 22884 0 snd_powermac 44304 1 snd_pcm 119800 2 snd_powermac snd_page_alloc 13480 1 snd_pcm snd_timer 29348 1 snd_pcm snd67800 4 snd_powermac,snd_pcm,snd_timer soundcore 11812 1 snd sbp2 28080 0 scsi_mod 113472 2 sr_mod,sbp2 ieee1394 448136 3 eth1394,ohci1394,sbp2 ide_cd 49764 0 cdrom 49660 2 sr_mod,ide_cd ext3 130736 1 jbd71576 1 ext3 mbcache10116 1 ext3 usbhid 53952 0 uhci_hcd 43792 0 ohci_hcd 26212 0 usbcore 139092 6 ehci_hcd,usbhid,uhci_hcd,ohci_hcd ide_disk 27072 3 unix 32088 244 Should I have to download another kernel version/patch or recompile the 2.6.8 kernel with other options? What about internal modem? Is there a way to make it work or is like the one coming with powerbooks (I think I read something on the list about soft modems on powerbooks). Thank you in advance for your help Matte -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd and NoTapTyping option?
On Sun, 20 Nov 2005 12:30:31 +0100 (CET) Michael Schmitz <[EMAIL PROTECTED]> wrote: > > does anybody use the NoTapTyping function of pbbuttonsd with success? > > How much would you pay to keep it? ;-) > > I don't use that function - at least not in pbbuttonsd. moussemu takes > care of that for me. That's what I thought. So there is no real need for that function in pbbuttonsd anymore (maybe never was), because mouseemu is much better in doing it. Thanks for your comment. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.6.15-rc2
Hi all,
please find attached fn-ky patch which works with 2.6.15-rc2.
Ciao
Elimar
--
The path to source is always uphill!
-unknown-
diff -Naur a/drivers/usb/input/hid-core.c b/drivers/usb/input/hid-core.c
--- a/drivers/usb/input/hid-core.c 2005-10-29 12:51:55.0 +0200
+++ b/drivers/usb/input/hid-core.c 2005-10-29 12:51:38.0 +0200
@@ -1452,6 +1452,9 @@
* Alphabetically sorted blacklist by quirk type.
*/
+#define USB_DEVICE_ID_POWERBOOK_KB_US 0x020E
+#define USB_DEVICE_ID_POWERBOOK_KB_UK 0x020F
+
static struct hid_blacklist {
__u16 idVendor;
__u16 idProduct;
@@ -1578,6 +1581,9 @@
{ USB_VENDOR_ID_SAITEK, USB_DEVICE_ID_SAITEK_RUMBLEPAD,
HID_QUIRK_BADPAD },
{ USB_VENDOR_ID_TOPMAX, USB_DEVICE_ID_TOPMAX_COBRAPAD, HID_QUIRK_BADPAD
},
+ { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_POWERBOOK_KB_US,
HID_QUIRK_POWERBOOK_FN_BUTTON },
+ { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_POWERBOOK_KB_UK,
HID_QUIRK_POWERBOOK_FN_BUTTON },
+
{ 0, 0 }
};
diff -Naur a/drivers/usb/input/hid-input.c b/drivers/usb/input/hid-input.c
--- a/drivers/usb/input/hid-input.c 2005-10-29 12:51:55.0 +0200
+++ b/drivers/usb/input/hid-input.c 2005-10-29 12:51:38.0 +0200
@@ -107,6 +107,10 @@
} else
map_key(KEY_UNKNOWN);
+ if ((device->quirks & HID_QUIRK_POWERBOOK_FN_BUTTON) &&
+ (hid_keyboard[usage->hid & HID_USAGE] ==
KEY_RIGHTCTRL))
+ map_key(KEY_UNKNOWN);
+
break;
case HID_UP_BUTTON:
@@ -320,15 +324,17 @@
case HID_UP_MSVENDOR:
goto ignore;
- case HID_UP_CUSTOM: /* Reported on Logitech and Powerbook USB
keyboards */
-
- set_bit(EV_REP, input->evbit);
- switch(usage->hid & HID_USAGE) {
- case 0x003: map_key_clear(KEY_FN);
break;
- default:goto ignore;
- }
- break;
-
+/* Who has shit who in his head for this? The need for XFree/Xorg to
change their
+ * input drivers? No thanks. (mcp)
+ * case HID_UP_CUSTOM:*/ /*Reported on Logitech and Powerbook USB
keyboards*/
+ /*
+ * set_bit(EV_REP, input->evbit);
+ * switch(usage->hid & HID_USAGE) {
+ * case 0x003: map_key_clear(KEY_FN);
break;
+ * default:goto ignore;
+ * }
+ * break;
+ */
case HID_UP_LOGIVENDOR: /* Reported on Logitech Ultra X Media
Remote */
set_bit(EV_REP, input->evbit);
@@ -380,6 +386,10 @@
default:
unknown:
+ if ((device->quirks & HID_QUIRK_POWERBOOK_FN_BUTTON) &&
(usage->hid == 0x00ff0003)) {
+ map_key_clear(KEY_RIGHTCTRL);
+ break;
+ }
if (field->report_size == 1) {
if (field->report->type == HID_OUTPUT_REPORT) {
map_led(LED_MISC);
diff -Naur a/drivers/usb/input/hid.h b/drivers/usb/input/hid.h
--- a/drivers/usb/input/hid.h 2005-10-29 12:51:55.0 +0200
+++ b/drivers/usb/input/hid.h 2005-10-29 12:51:38.0 +0200
@@ -246,6 +246,7 @@
#define HID_QUIRK_2WHEEL_MOUSE_HACK_5 0x100
#define HID_QUIRK_2WHEEL_MOUSE_HACK_ON 0x200
#define HID_QUIRK_2WHEEL_POWERMOUSE0x400
+#define HID_QUIRK_POWERBOOK_FN_BUTTON 0x800
/*
* This is the global environment of the parser. This information is
Re: glibc problem ?
On Nov 20 2005, Yves-Alexis Perez wrote: > It seems to be a "known" bug on gphoto2. The same thing occurs on a > vanilla 2.6.14 and on debian 2.6.14-2-powerpc But I don't use gphoto2. In fact, I have no digital camera. The problem must be somewhere else. I do have libc-i686 installed, though (which, AFAIK, has NPTL enabled). I don't know if that is a possible cause for the problem. Regards, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd and NoTapTyping option?
> does anybody use the NoTapTyping function of pbbuttonsd with success? > How much would you pay to keep it? ;-) I don't use that function - at least not in pbbuttonsd. moussemu takes care of that for me. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /dev/event0 missing
> > > So I think it's udev that is broken (version 0.074-2 from sid) > > > > Could you report a bug to udev's maintainer? > > I just upgraded to 0.074-3 and the problem seems to be fixed > > [EMAIL PROTECTED]:~$ ls -l /dev/input/ > total 0 > crw-rw 1 root root 13, 64 2005-11-19 11:30 event0 > crw-rw 1 root root 13, 65 2005-11-19 11:30 event1 > crw-rw 1 root root 13, 66 2005-11-19 11:30 event2 > crw-rw 1 root root 13, 67 2005-11-19 11:30 event3 > crw-rw 1 root root 13, 68 2005-11-19 11:30 event4 > crw-rw 1 root root 13, 63 2005-11-19 11:30 mice > crw-rw 1 root root 13, 32 2005-11-19 11:30 mouse0 > crw-rw 1 root root 13, 33 2005-11-19 11:30 mouse1 -2 did autoload the evdev module for me, -3 doesn't anymore. Both create the appropriate devices though. Should't udev watch for device open syscalls on /dev, and load the necessary modules? Doesn't work with i2c-dev and evdev for me... Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: temperature sensor powers off ibook?
Hallo Benjamin, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > On Sat, 2005-11-19 at 12:56 +, Joerg Sommer wrote: >> I have nothing changed in the kernel or the kernel itself before this >> problems start and I see it only when I was outdoor. I carry my iBook >> only in a second skin and a backpack. Did anyone have the same problems? > > Could be the movements causing a bad contact with the battery. Maybe, but I wouldn't expect it. I took my ibook so often under the arm and now this?! > Either that or causing the book to wakeup (lid a bit loose ?) and thus > causing it to empty it's battery or overhead in the backpack. No. The second skin doesn't leave the space to open the lid. Bye, Jörg. -- Eine Blume geht über eine Wiese, sieht einen schönen Menschen und reißt ihm den Kopf ab. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc problem ?
Rogério Brito wrote: > On Nov 20 2005, Benjamin Herrenschmidt wrote: > >>On Sat, 2005-11-19 at 13:34 +0100, Yves-Alexis Perez wrote: >> >>>*** glibc detected *** free(): invalid pointer: 0x108979f0 *** >> >>This has nothing to do with glibc itself. glibc is basically warning >>you that the application has corrupted memory. So something is wrong >>in the app / libraries you are using. > > > I don't remember exactly what caused it (it was three or four days ago), > but I saw this same message in a i386 box (which I am using right now). > > I have never seen this before and have not changed the system in any > drastic way that would cause programs to behave incorrectly regarding > memory allocation. > > Oh, wait. Perhaps I did. I enabled 4k stacks in my latest kernel > compilation (currently using 2.6.14.2). It seems to be a "known" bug on gphoto2. The same thing occurs on a vanilla 2.6.14 and on debian 2.6.14-2-powerpc -- Yves-Alexis Perez http://www.corsac.net signature.asc Description: OpenPGP digital signature
Re: glibc problem ?
On Nov 20 2005, Benjamin Herrenschmidt wrote: > On Sat, 2005-11-19 at 13:34 +0100, Yves-Alexis Perez wrote: > > *** glibc detected *** free(): invalid pointer: 0x108979f0 *** > > This has nothing to do with glibc itself. glibc is basically warning > you that the application has corrupted memory. So something is wrong > in the app / libraries you are using. I don't remember exactly what caused it (it was three or four days ago), but I saw this same message in a i386 box (which I am using right now). I have never seen this before and have not changed the system in any drastic way that would cause programs to behave incorrectly regarding memory allocation. Oh, wait. Perhaps I did. I enabled 4k stacks in my latest kernel compilation (currently using 2.6.14.2). Regards, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pbbuttonsd and NoTapTyping option?
Hi, does anybody use the NoTapTyping function of pbbuttonsd with success? How much would you pay to keep it? ;-) If this is not the case and due to the problems this function could cause, I would remove the function from pbbuttond again with the next release. Any comments? Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
