Menu
▾
▴
mactel-linux-devel — mactel-linux Development
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
(4) |
Mar
(135) |
Apr
(130) |
May
(82) |
Jun
(101) |
Jul
(75) |
Aug
(37) |
Sep
(28) |
Oct
(45) |
Nov
(114) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(22) |
Feb
(60) |
Mar
(81) |
Apr
(120) |
May
(29) |
Jun
(50) |
Jul
(67) |
Aug
(41) |
Sep
(36) |
Oct
(4) |
Nov
(4) |
Dec
|
| 2008 |
Jan
(5) |
Feb
(17) |
Mar
(5) |
Apr
(6) |
May
(5) |
Jun
(9) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: gela <que...@gm...> - 2007-07-21 08:41:30
|
Hi, I have been in nvnews forums, checking for the updates... http://www.nvnews.net/vbulletin/showthread.php?t=92980&page=5 but in the meantime, the latest xorg nv drivers should work (agh...) - today I am going to test it with mine.. regards. 2007/7/20, Clive Saldanha <cli...@gm...>: > > Does anyone know if the drivers are out for the new NVIDIA card on the MBP > V3. > > As of now im getting crazy colour for some older version of the driver. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > |
|
From: Clive S. <cli...@gm...> - 2007-07-20 19:08:36
|
Does anyone know if the drivers are out for the new NVIDIA card on the MBP V3. As of now im getting crazy colour for some older version of the driver. |
|
From: <ma...@mi...> - 2007-07-19 20:01:40
|
Hi Thomas! On Thu, 19 Jul 2007 17:33:23 +0200, Thomas Besser <tho...@ar...> wrote: > Hi Marek, > > > Still no working microphone (intern nor extern via headset). > Could you please send me your output of amixer?! Well, the output of amixer is attached. It was a bit surprise for me, that when I tried to record something, my microphone was not working too. Fortunately, I was able to set the mixer so that the microphone works now:) I think the important things are setting the "Digital" and "MUX" controls. It is a good idea to tune this settings for better record. Probably there are more things, which are significant for recording. Just look to my mixer settings. I read somwhere, that it would be necessary to switch between "Line" and "Mic" as input source on startup. Well, I am not sure, if the _hack_ is necessary, because, when trying to setup correctly the mixer, I switched it. And I don't want to restart my computer now to test if it is really necessary. > How (which software) do you test working microphone? I used arecord/aplay > > Perhaps silly question, but is the microphone a separate device node? If > yes, do you know which? Well, I don't know, what you are writing about:-) marek |
|
From: Roscoe M. <ros...@tc...> - 2007-07-19 07:56:14
|
Save up to 80% on your prescription drugs!!! We're #1 OnlinePharmacy. You can buy prescription drugs WITHOUT PRESCRIPTION or buy online prescription drugs without prescription or buy discount prescription drugs WITHOUT A PRESCRIPTION. == please click either links below to view what we have to save you 80% == http://kqu3gry112ev7.abplacewhen.com http://kh9d02y1evyvu0.abplacewhen.com between truly son lady. page lady hurrying page your ten bread; iqg3ch2x8qh2gb 4tr4xt209i |
|
From: <nbo...@us...> - 2007-07-17 18:50:43
|
Revision: 135
http://svn.sourceforge.net/mactel-linux/?rev=135&view=rev
Author: nboichat
Date: 2007-07-17 11:50:21 -0700 (Tue, 17 Jul 2007)
Log Message:
-----------
- Remove appleir.patch and unblacklist Apple IR from usbhid, not needed anymore, as lirc supports the remote using the driver "macmini".
- Latest update of the appletouch patch.
Modified Paths:
--------------
trunk/kernel/mactel-patches-2.6.22/appletouch-shut-up-when-it-has-nothing-to-say.patch
trunk/kernel/mactel-patches-2.6.22/series
Added Paths:
-----------
trunk/kernel/mactel-patches-2.6.22/appleir-undo-hid-blacklist.patch
Removed Paths:
-------------
trunk/kernel/mactel-patches-2.6.22/appleir.patch
trunk/kernel/mactel-patches-2.6.22/appletouch-fix-run-amok-problem.patch
Added: trunk/kernel/mactel-patches-2.6.22/appleir-undo-hid-blacklist.patch
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/appleir-undo-hid-blacklist.patch (rev 0)
+++ trunk/kernel/mactel-patches-2.6.22/appleir-undo-hid-blacklist.patch 2007-07-17 18:50:21 UTC (rev 135)
@@ -0,0 +1,30 @@
+Undo USB HID blacklisting of Apple IR, as it is support by lirc now.
+
+From: Nicolas Boichat <ni...@bo...>
+
+
+---
+
+ drivers/hid/usbhid/hid-quirks.c | 2 --
+ 1 files changed, 0 insertions(+), 2 deletions(-)
+
+diff --git a/drivers/hid/usbhid/hid-quirks.c b/drivers/hid/usbhid/hid-quirks.c
+index f6c4145..3e64d56 100644
+--- a/drivers/hid/usbhid/hid-quirks.c
++++ b/drivers/hid/usbhid/hid-quirks.c
+@@ -61,7 +61,6 @@
+ #define USB_DEVICE_ID_APPLE_GEYSER4_JIS 0x021c
+ #define USB_DEVICE_ID_APPLE_FOUNTAIN_TP_ONLY 0x030a
+ #define USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY 0x030b
+-#define USB_DEVICE_ID_APPLE_IR 0x8240
+
+ #define USB_VENDOR_ID_ATEN 0x0557
+ #define USB_DEVICE_ID_ATEN_UC100KM 0x2004
+@@ -300,7 +299,6 @@ static const struct hid_blacklist {
+ { USB_VENDOR_ID_AIPTEK, USB_DEVICE_ID_AIPTEK_24, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_AIRCABLE, USB_DEVICE_ID_AIRCABLE1, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ALCOR, USB_DEVICE_ID_ALCOR_USBRS232, HID_QUIRK_IGNORE },
+- { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IR, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_BERKSHIRE, USB_DEVICE_ID_BERKSHIRE_PCWD, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_CIDC, 0x0103, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_CYPRESS, USB_DEVICE_ID_CYPRESS_HIDCOM, HID_QUIRK_IGNORE },
Deleted: trunk/kernel/mactel-patches-2.6.22/appleir.patch
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/appleir.patch 2007-07-12 13:56:52 UTC (rev 134)
+++ trunk/kernel/mactel-patches-2.6.22/appleir.patch 2007-07-17 18:50:21 UTC (rev 135)
@@ -1,429 +0,0 @@
-Apple IR patch.
-
-From: James McKenzie <ma...@ma...>
-
-
----
-
- drivers/input/misc/Kconfig | 5 +
- drivers/input/misc/Makefile | 1
- drivers/input/misc/appleir.c | 379 ++++++++++++++++++++++++++++++++++++++++++
- 3 files changed, 385 insertions(+), 0 deletions(-)
-
-diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig
-index 88e2907..d2d629a 100644
---- a/drivers/input/misc/Kconfig
-+++ b/drivers/input/misc/Kconfig
-@@ -113,6 +113,10 @@ config INPUT_ATI_REMOTE2
- To compile this driver as a module, choose M here: the module will be
- called ati_remote2.
-
-+config USB_APPLEIR
-+ tristate "Apple Mac Mini USB IR receiver (built in)"
-+ depends on USB && INPUT
-+
- config INPUT_KEYSPAN_REMOTE
- tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
- depends on EXPERIMENTAL
-@@ -179,3 +183,4 @@ config HP_SDC_RTC
- of the HP SDC controller.
-
- endif
-+
-diff --git a/drivers/input/misc/Makefile b/drivers/input/misc/Makefile
-index 3585b50..f73f139 100644
---- a/drivers/input/misc/Makefile
-+++ b/drivers/input/misc/Makefile
-@@ -13,6 +13,7 @@ obj-$(CONFIG_INPUT_WISTRON_BTNS) += wistron_btns.o
- obj-$(CONFIG_INPUT_ATLAS_BTNS) += atlas_btns.o
- obj-$(CONFIG_INPUT_ATI_REMOTE) += ati_remote.o
- obj-$(CONFIG_INPUT_ATI_REMOTE2) += ati_remote2.o
-+obj-$(CONFIG_USB_APPLEIR) += appleir.o
- obj-$(CONFIG_INPUT_KEYSPAN_REMOTE) += keyspan_remote.o
- obj-$(CONFIG_INPUT_POWERMATE) += powermate.o
- obj-$(CONFIG_INPUT_YEALINK) += yealink.o
-diff --git a/drivers/input/misc/appleir.c b/drivers/input/misc/appleir.c
-new file mode 100644
-index 0000000..3ff46fc
---- /dev/null
-+++ b/drivers/input/misc/appleir.c
-@@ -0,0 +1,379 @@
-+/*
-+ * drivers/usb/input/appleir.c - driver for Apple Intel-based Macs IR Receiver
-+ *
-+ * Copyright (C) 2006 James McKenzie <ma...@ma...>
-+ *
-+ * This program is free software; you can redistribute it and/or modify it
-+ * under the terms of the GNU General Public License v2 as published by the
-+ * Free Software Foundation.
-+ *
-+ * This program is distributed in the hope that it will be useful, but WITHOUT
-+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-+ * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
-+ * more details.
-+ *
-+ * You should have received a copy of the GNU General Public License along with
-+ * this program; if not, write to the Free Software Foundation, Inc.,
-+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-+ */
-+
-+#include <linux/kernel.h>
-+#include <linux/slab.h>
-+#include <linux/input.h>
-+#include <linux/module.h>
-+#include <linux/init.h>
-+#include <linux/usb.h>
-+#include <linux/usb/input.h>
-+#include <linux/mutex.h>
-+#include <asm/unaligned.h>
-+#include <asm/byteorder.h>
-+
-+#define DRIVER_VERSION "v1.2"
-+#define DRIVER_AUTHOR "James McKenzie"
-+#define DRIVER_DESC "USB Apple MacIntel IR Receiver driver"
-+#define DRIVER_LICENSE "GPL"
-+
-+MODULE_AUTHOR(DRIVER_AUTHOR);
-+MODULE_DESCRIPTION(DRIVER_DESC);
-+MODULE_LICENSE(DRIVER_LICENSE);
-+
-+#define USB_VENDOR_ID_APPLE 0x05ac
-+#define USB_DEVICE_ID_APPLE_IR 0x8240
-+
-+#define URB_SIZE 32
-+
-+#define MAX_KEYS 8
-+#define MAX_KEYS_MASK (MAX_KEYS - 1)
-+
-+static int debug = 1;
-+
-+struct appleir {
-+ struct input_dev *dev;
-+ uint8_t *data;
-+ dma_addr_t dma_buf;
-+ struct usb_device *usbdev;
-+ struct urb *urb;
-+ struct timer_list key_up_timer;
-+ int current_key;
-+ char phys[32];
-+};
-+
-+
-+static struct usb_device_id appleir_ids[] = {
-+ {
-+ USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IR),
-+ .driver_info = 0
-+ },
-+ {}
-+};
-+
-+MODULE_DEVICE_TABLE(usb, appleir_ids);
-+
-+/*
-+ * Devices report the following, where XX depends on the remote and/or the
-+ * receiver (at least 2a, 83, ca, ee have been reported as possible values, it
-+ * looks like it is remote control dependent).
-+ * The fifth byte's LSB also depends on the hardware.
-+ * 25 87 ee XX 0a/0b +
-+ * 25 87 ee XX 0c/0d -
-+ * 25 87 ee XX 09/08 <<
-+ * 25 87 ee XX 06/07 >>
-+ * 25 87 ee XX 05/04 >"
-+ * 25 87 ee 83 03/02 menu
-+ * 26 00 00 00 00 for key repeat
-+ *
-+ * Thomas Glanzmann also observes the following event sometimes sent after a key
-+ * is released, which I interpret as a flat battery message:
-+ * 25 87 e0 ca 06 flat battery
-+ */
-+
-+static int keymap[MAX_KEYS] = {
-+ KEY_RESERVED, KEY_MENU,
-+ KEY_PLAYPAUSE, KEY_NEXTSONG,
-+ KEY_PREVIOUSSONG, KEY_VOLUMEUP,
-+ KEY_VOLUMEDOWN, KEY_RESERVED
-+};
-+
-+static void dump_packet(struct appleir *appleir, char *msg,
-+ uint8_t *data, int len)
-+{
-+ int i;
-+
-+ printk(KERN_ERR "appleir: %s (%d bytes)", msg, len);
-+
-+ for (i = 0; i < len; ++i) {
-+ printk(" %02x", data[i]);
-+ }
-+
-+ printk("\n");
-+}
-+
-+
-+static void key_up(struct appleir *appleir, int key)
-+{
-+ if (debug)
-+ printk (KERN_DEBUG "key %d up\n", key);
-+
-+ input_report_key(appleir->dev, key, 0);
-+ input_sync(appleir->dev);
-+}
-+
-+static void key_down(struct appleir *appleir, int key)
-+{
-+ if (debug)
-+ printk (KERN_DEBUG "key %d down\n", key);
-+
-+ input_report_key(appleir->dev, key, 1);
-+ input_sync(appleir->dev);
-+}
-+
-+static void battery_flat(struct appleir *appleir)
-+{
-+ printk(KERN_WARNING "appleir: possible flat battery?\n");
-+}
-+
-+static void key_up_tick(unsigned long data)
-+{
-+ struct appleir *apple_ir = (struct appleir *)data;
-+
-+ if (apple_ir->current_key) {
-+ key_up(apple_ir, apple_ir->current_key);
-+ apple_ir->current_key = 0;
-+ }
-+}
-+
-+static void parse_data(struct appleir *apple_ir, uint8_t *data, int len)
-+{
-+ static const uint8_t keydown[] = { 0x25, 0x87, 0xee };
-+ static const uint8_t keyrepeat[] = { 0x26, 0x00, 0x00, 0x00, 0x00 };
-+ static const uint8_t flatbattery[] = { 0x25, 0x87, 0xe0 };
-+
-+ if (debug)
-+ dump_packet(apple_ir, "received", data, len);
-+
-+ if (len != 5)
-+ return;
-+
-+ if (!memcmp(data, keydown, sizeof(keydown))) {
-+ /*
-+ * If we already have a key down, take it up before marking
-+ * this one down.
-+ */
-+ if (apple_ir->current_key)
-+ key_up(apple_ir, apple_ir->current_key);
-+ apple_ir->current_key = keymap[(data[4] >> 1) & MAX_KEYS_MASK];
-+
-+ key_down(apple_ir, apple_ir->current_key);
-+
-+ /*
-+ * Remote doesn't do key up, either pull them up, in the test
-+ * above, or here set a timer which pulls them up after 1/8 s
-+ */
-+ mod_timer(&apple_ir->key_up_timer, jiffies + HZ / 8);
-+
-+ return;
-+ }
-+
-+ if (!memcmp(data, keyrepeat, sizeof(keyrepeat))) {
-+ key_down(apple_ir, apple_ir->current_key);
-+
-+ /*
-+ * Remote doesn't do key up, either pull them up, in the test
-+ * above, or here set a timer which pulls them up after 1/8 s
-+ */
-+ mod_timer(&apple_ir->key_up_timer, jiffies + HZ / 8);
-+ return;
-+ }
-+
-+ if (!memcmp(data, flatbattery, sizeof(flatbattery))) {
-+ battery_flat(apple_ir);
-+ /* Fall through */
-+ }
-+
-+ dump_packet(apple_ir, "unknown packet", data, len);
-+}
-+
-+static void appleir_urb(struct urb *urb)
-+{
-+ struct appleir *appleir = urb->context;
-+ int retval;
-+
-+ switch (urb->status) {
-+ case 0:
-+ parse_data(appleir, urb->transfer_buffer, urb->actual_length);
-+ break;
-+ case -ECONNRESET:
-+ case -ENOENT:
-+ case -ESHUTDOWN:
-+ /* this urb is terminated, clean up */
-+ dbg("%s - urb shutting down with status: %d",
-+ __FUNCTION__, urb->status);
-+ return;
-+ default:
-+ dbg("%s - nonzero urb status received: %d",
-+ __FUNCTION__, urb->status);
-+ }
-+
-+ retval = usb_submit_urb(urb, GFP_ATOMIC);
-+ if (retval)
-+ err("%s - usb_submit_urb failed with result %d",
-+ __FUNCTION__, retval);
-+}
-+
-+
-+static int appleir_open(struct input_dev *dev)
-+{
-+ struct appleir *appleir = dev->private;
-+
-+ if (usb_submit_urb(appleir->urb, GFP_KERNEL))
-+ return -EIO;
-+
-+ return 0;
-+}
-+
-+static void appleir_close(struct input_dev *dev)
-+{
-+ struct appleir *appleir = dev->private;
-+ usb_kill_urb(appleir->urb);
-+ del_timer_sync(&appleir->key_up_timer);
-+}
-+
-+static int appleir_probe(struct usb_interface *intf,
-+ const struct usb_device_id *id)
-+{
-+ struct usb_device *dev = interface_to_usbdev(intf);
-+ struct usb_endpoint_descriptor *endpoint;
-+ struct appleir *appleir = NULL;
-+ struct input_dev *input_dev;
-+ int i;
-+ int ret = -ENOMEM;
-+
-+ appleir = kzalloc(sizeof(struct appleir), GFP_KERNEL);
-+ if (!appleir)
-+ goto fail;
-+
-+ memset(appleir, 0, sizeof(struct appleir));
-+
-+ appleir->data =
-+ usb_buffer_alloc(dev, URB_SIZE, GFP_KERNEL, &appleir->dma_buf);
-+ if (!appleir->data)
-+ goto fail_appleir;
-+
-+ appleir->urb = usb_alloc_urb(0, GFP_KERNEL);
-+ if (!appleir->urb)
-+ goto fail_buffer;
-+
-+ appleir->usbdev = dev;
-+
-+ input_dev = input_allocate_device();
-+ if (!input_dev)
-+ goto fail_urb;
-+
-+ appleir->dev = input_dev;
-+
-+ if (usb_make_path(dev, appleir->phys, sizeof(appleir->phys)) < 0)
-+ goto fail_input_device;
-+
-+ strlcpy(appleir->phys, "/input0", sizeof(appleir->phys));
-+
-+ input_dev->name = "Apple MacIntel infrared remote control driver";
-+ input_dev->phys = appleir->phys;
-+ usb_to_input_id(dev, &input_dev->id);
-+ input_dev->cdev.dev = &intf->dev;
-+ input_dev->private = appleir;
-+
-+ input_dev->evbit[0] = BIT(EV_KEY) | BIT(EV_REP);
-+ input_dev->ledbit[0] = 0;
-+
-+ for (i = 0; i < MAX_KEYS; i++) {
-+ set_bit(keymap[i], input_dev->keybit);
-+ }
-+
-+ clear_bit(0, input_dev->keybit);
-+
-+ input_dev->open = appleir_open;
-+ input_dev->close = appleir_close;
-+
-+ endpoint = &intf->cur_altsetting->endpoint[0].desc;
-+
-+ usb_fill_int_urb(appleir->urb, dev,
-+ usb_rcvintpipe(dev, endpoint->bEndpointAddress),
-+ appleir->data, 8,
-+ appleir_urb, appleir, endpoint->bInterval);
-+
-+ appleir->urb->transfer_dma = appleir->dma_buf;
-+ appleir->urb->transfer_flags |= URB_NO_TRANSFER_DMA_MAP;
-+
-+ usb_set_intfdata(intf, appleir);
-+
-+ init_timer(&appleir->key_up_timer);
-+
-+ appleir->key_up_timer.function = key_up_tick;
-+ appleir->key_up_timer.data = (unsigned long) appleir;
-+
-+ ret = input_register_device(appleir->dev);
-+ if (ret < 0)
-+ goto fail_timer;
-+
-+ return 0;
-+
-+fail_timer:
-+ del_timer_sync(&appleir->key_up_timer);
-+
-+fail_input_device:
-+ input_free_device(appleir->dev);
-+
-+fail_urb:
-+ usb_free_urb(appleir->urb);
-+
-+fail_buffer:
-+ usb_buffer_free(dev, URB_SIZE, appleir->data, appleir->dma_buf);
-+
-+fail_appleir:
-+ kfree(appleir);
-+
-+fail:
-+ return ret;
-+}
-+
-+static void appleir_disconnect(struct usb_interface *intf)
-+{
-+ struct appleir *appleir = usb_get_intfdata(intf);
-+
-+ usb_set_intfdata(intf, NULL);
-+ if (appleir) {
-+ input_unregister_device(appleir->dev);
-+ del_timer_sync(&appleir->key_up_timer);
-+ usb_kill_urb(appleir->urb);
-+ usb_free_urb(appleir->urb);
-+ usb_buffer_free(interface_to_usbdev(intf), URB_SIZE,
-+ appleir->data, appleir->dma_buf);
-+ kfree(appleir);
-+ }
-+}
-+
-+static struct usb_driver appleir_driver = {
-+ .name = "appleir",
-+ .probe = appleir_probe,
-+ .disconnect = appleir_disconnect,
-+ .id_table = appleir_ids,
-+};
-+
-+static int __init appleir_init(void)
-+{
-+ int retval;
-+ retval = usb_register(&appleir_driver);
-+ if (retval)
-+ goto out;
-+ info(DRIVER_VERSION ":" DRIVER_DESC);
-+out:
-+ return retval;
-+}
-+
-+static void __exit appleir_exit(void)
-+{
-+ usb_deregister(&appleir_driver);
-+}
-+
-+module_init(appleir_init);
-+module_exit(appleir_exit);
Deleted: trunk/kernel/mactel-patches-2.6.22/appletouch-fix-run-amok-problem.patch
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/appletouch-fix-run-amok-problem.patch 2007-07-12 13:56:52 UTC (rev 134)
+++ trunk/kernel/mactel-patches-2.6.22/appletouch-fix-run-amok-problem.patch 2007-07-17 18:50:21 UTC (rev 135)
@@ -1,32 +0,0 @@
-The attached patch tries to resolve the 'appletouch runs amok' problem.
-
-From: Soeren Sonnenburg <mac...@nn...>
-
-
----
-
- drivers/input/mouse/appletouch.c | 10 +++++++++-
- 1 files changed, 9 insertions(+), 1 deletions(-)
-
-diff --git a/drivers/input/mouse/appletouch.c b/drivers/input/mouse/appletouch.c
-index 724bcd4..6b7aefe 100644
---- a/drivers/input/mouse/appletouch.c
-+++ b/drivers/input/mouse/appletouch.c
-@@ -502,8 +502,16 @@ static void atp_complete(struct urb* urb)
- several hundred times a second */
- if (atp_is_geyser_3(dev)) {
- dev->idlecount++;
-- if (dev->idlecount == 10)
-+ if (dev->idlecount == 10) {
-+ if (dev->data[dev->datalen-1] != 20)
-+ input_report_key(dev->input, BTN_LEFT,
-+ !!dev->data[dev->datalen - 1]);
-+
-+ input_sync(dev->input);
- schedule_work (&dev->work);
-+
-+ goto exit;
-+ }
- }
- }
-
Modified: trunk/kernel/mactel-patches-2.6.22/appletouch-shut-up-when-it-has-nothing-to-say.patch
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/appletouch-shut-up-when-it-has-nothing-to-say.patch 2007-07-12 13:56:52 UTC (rev 134)
+++ trunk/kernel/mactel-patches-2.6.22/appletouch-shut-up-when-it-has-nothing-to-say.patch 2007-07-17 18:50:21 UTC (rev 135)
@@ -1,42 +1,82 @@
-The appletouch devices found in the Intel Macs (and possibly some later PPC ones?) send a constant stream of packets after the first touch. This results in the kernel waking up around once every couple of milliseconds to process them, making it almost impossible to spend any significant period of time in C3 state on a dynamic HZ kernel. Sending the mode initialisation code makes the device shut up until it's touched again. This patch does so after receiving 10 packets with no interesting content.
+The attached minimally intrusive patch is based on Matthew Garret's
-From: Matthew Garrett <mj...@sr...>
+From: Soeren Sonnenburg <ke...@nn...>
+patch 'Make appletouch shut up when it has nothing to say' patches (e.g.
+http://lkml.org/lkml/2007/5/13/117): Matthews description follows /
+second paragraph lists my additional changes.
+The appletouch geyser3 devices found in the Intel Macs (and possibly some later
+PPC ones?) send a constant stream of packets after the first touch. This
+results in the kernel waking up around once every couple of milliseconds
+to process them, making it almost impossible to spend any significant
+period of time in C3 state on a dynamic HZ kernel. Sending the mode
+initialization code makes the device shut up until it's touched again.
+This patch does so after receiving 10 packets with no interesting
+content.
+
+In addition it now empties the work queue via cancel_work_sync on module
+exit, keeps all error checking and only reports BTN_LEFT presses if bit
+1 in the status byte (last byte in packet) is set. This fixes the random
+left clicks issue. Furthermore it invalidates touchpad data before the
+mode switch, which fixes the touchpad runs amok issue.
+
+Credits:
+Sven Anders found out that one should only check for bit 1 for BTN_LEFT.
+Matthew Garrett did the initial 'Make appletouch shut up when it has
+nothing to say' so I am adding him to the signed-off lines (hope that is
+the correct way).
+
+Patch follows inline and attached.
+
+Soeren.
+
+Signed-off-by: Soeren Sonnenburg <ke...@nn...>
+Signed-off-by: Matthew Garrett <mj...@sr...>
---
- drivers/input/mouse/appletouch.c | 93 ++++++++++++++++++++++++++------------
- 1 files changed, 63 insertions(+), 30 deletions(-)
+ drivers/input/mouse/appletouch.c | 112 ++++++++++++++++++++++++++------------
+ 1 files changed, 77 insertions(+), 35 deletions(-)
diff --git a/drivers/input/mouse/appletouch.c b/drivers/input/mouse/appletouch.c
-index c26af96..724bcd4 100644
+index c26af96..22182a7 100644
--- a/drivers/input/mouse/appletouch.c
+++ b/drivers/input/mouse/appletouch.c
@@ -155,6 +155,8 @@ struct atp {
int xy_acc[ATP_XSENSORS + ATP_YSENSORS];
int overflowwarn; /* overflow warning printed? */
int datalen; /* size of an USB urb transfer */
-+ int idlecount; /* number of empty packets */
++ int idlecount; /* number of empty packets */
+ struct work_struct work;
};
#define dbg_dump(msg, tab) \
-@@ -208,6 +210,51 @@ static inline int atp_is_geyser_3(struct atp *dev)
+@@ -208,6 +210,63 @@ static inline int atp_is_geyser_3(struct atp *dev)
(productId == GEYSER4_JIS_PRODUCT_ID);
}
++/*
++ * By default Geyser 3 device sends standard USB HID mouse
++ * packets (Report ID 2). This code changes device mode, so it
++ * sends raw sensor reports (Report ID 5).
++ */
+static int atp_geyser3_init(struct usb_device *udev)
+{
+ char data[8];
+ int size;
++ int i;
+
+ size = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
-+ ATP_GEYSER3_MODE_READ_REQUEST_ID,
-+ USB_DIR_IN | USB_TYPE_CLASS | USB_RECIP_INTERFACE,
-+ ATP_GEYSER3_MODE_REQUEST_VALUE,
-+ ATP_GEYSER3_MODE_REQUEST_INDEX, &data, 8, 5000);
-+
++ ATP_GEYSER3_MODE_READ_REQUEST_ID,
++ USB_DIR_IN | USB_TYPE_CLASS | USB_RECIP_INTERFACE,
++ ATP_GEYSER3_MODE_REQUEST_VALUE,
++ ATP_GEYSER3_MODE_REQUEST_INDEX, &data, 8, 5000);
++
+ if (size != 8) {
++ printk("appletouch atp_geyser3_init READ error\n");
++ for (i=0; i<8; i++)
++ printk("appletouch[%d]: %d\n", i, (int) data[i]);
++
+ err("Could not do mode read request from device"
+ " (Geyser 3 mode)");
+ return -EIO;
@@ -44,15 +84,17 @@
+
+ /* Apply the mode switch */
+ data[0] = ATP_GEYSER3_MODE_VENDOR_VALUE;
-+
++
+ size = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
-+ ATP_GEYSER3_MODE_WRITE_REQUEST_ID,
-+ USB_DIR_OUT | USB_TYPE_CLASS |
-+ USB_RECIP_INTERFACE,
-+ ATP_GEYSER3_MODE_REQUEST_VALUE,
-+ ATP_GEYSER3_MODE_REQUEST_INDEX, &data, 8, 5000);
-+
++ ATP_GEYSER3_MODE_WRITE_REQUEST_ID,
++ USB_DIR_OUT | USB_TYPE_CLASS | USB_RECIP_INTERFACE,
++ ATP_GEYSER3_MODE_REQUEST_VALUE,
++ ATP_GEYSER3_MODE_REQUEST_INDEX, &data, 8, 5000);
++
+ if (size != 8) {
++ printk("appletouch atp_geyser3_init WRITE error\n");
++ for (i=0; i<8; i++)
++ printk("appletouch[%d]: %d\n", i, (int) data[i]);
+ err("Could not do mode write request to device"
+ " (Geyser 3 mode)");
+ return -EIO;
@@ -73,42 +115,48 @@
static int atp_calculate_abs(int *xy_sensors, int nb_sensors, int fact,
int *z, int *fingers)
{
-@@ -441,7 +488,6 @@ static void atp_complete(struct urb* urb)
- dev->y_old = y;
- }
- else if (!x && !y) {
--
- dev->x_old = dev->y_old = -1;
- input_report_key(dev->input, BTN_TOUCH, 0);
- input_report_abs(dev->input, ABS_PRESSURE, 0);
-@@ -449,10 +495,21 @@ static void atp_complete(struct urb* urb)
+@@ -449,11 +508,21 @@ static void atp_complete(struct urb* urb)
/* reset the accumulator on release */
memset(dev->xy_acc, 0, sizeof(dev->xy_acc));
-+
+- }
+
+- input_report_key(dev->input, BTN_LEFT,
+- !!dev->data[dev->datalen - 1]);
+ /* Geyser 3 will continue to send packets continually after
+ the first touch unless reinitialised. Do so if it's been
+ idle for a while in order to avoid waking the kernel up
+ several hundred times a second */
+ if (atp_is_geyser_3(dev)) {
+ dev->idlecount++;
-+ if (dev->idlecount == 10)
++ if (dev->idlecount == 10) {
++ dev->valid=0;
+ schedule_work (&dev->work);
++ }
+ }
- }
++ }
-- input_report_key(dev->input, BTN_LEFT,
-- !!dev->data[dev->datalen - 1]);
-+ if (dev->data[dev->datalen-1] != 20)
-+ input_report_key(dev->input, BTN_LEFT,
-+ !!dev->data[dev->datalen - 1]);
-
++ input_report_key(dev->input, BTN_LEFT, dev->data[dev->datalen-1] & 1);
input_sync(dev->input);
-@@ -533,35 +590,9 @@ static int atp_probe(struct usb_interface *iface, const struct usb_device_id *id
- * packets (Report ID 2). This code changes device mode, so it
- * sends raw sensor reports (Report ID 5).
- */
+ exit:
+@@ -480,6 +549,7 @@ static void atp_close(struct input_dev *input)
+ struct atp *dev = input_get_drvdata(input);
+
+ usb_kill_urb(dev->urb);
++ cancel_work_sync(&dev->work);
+ dev->open = 0;
+ }
+
+@@ -528,40 +598,10 @@ static int atp_probe(struct usb_interface *iface, const struct usb_device_id *id
+ dev->datalen = 81;
+
+ if (atp_is_geyser_3(dev)) {
+- /*
+- * By default Geyser 3 device sends standard USB HID mouse
+- * packets (Report ID 2). This code changes device mode, so it
+- * sends raw sensor reports (Report ID 5).
+- */
- char data[8];
- int size;
-
@@ -121,10 +169,11 @@
- if (size != 8) {
- err("Could not do mode read request from device"
- " (Geyser 3 mode)");
++ /* switch to raw sensor mode */
+ if (atp_geyser3_init(udev))
goto err_free_devs;
- }
-
+-
- /* Apply the mode switch */
- data[0] = ATP_GEYSER3_MODE_VENDOR_VALUE;
-
@@ -133,7 +182,7 @@
- USB_DIR_OUT | USB_TYPE_CLASS | USB_RECIP_INTERFACE,
- ATP_GEYSER3_MODE_REQUEST_VALUE,
- ATP_GEYSER3_MODE_REQUEST_INDEX, &data, 8, 5000);
--
+
- if (size != 8) {
- err("Could not do mode write request to device"
- " (Geyser 3 mode)");
@@ -142,11 +191,11 @@
printk("appletouch Geyser 3 inited.\n");
}
-@@ -636,6 +667,8 @@ static int atp_probe(struct usb_interface *iface, const struct usb_device_id *id
+@@ -636,6 +676,8 @@ static int atp_probe(struct usb_interface *iface, const struct usb_device_id *id
/* save our data pointer in this interface device */
usb_set_intfdata(iface, dev);
-+ INIT_WORK(&dev->work, atp_reinit);
++ INIT_WORK(&dev->work, atp_reinit);
+
return 0;
Modified: trunk/kernel/mactel-patches-2.6.22/series
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/series 2007-07-12 13:56:52 UTC (rev 134)
+++ trunk/kernel/mactel-patches-2.6.22/series 2007-07-17 18:50:21 UTC (rev 135)
@@ -5,6 +5,5 @@
sigmatel_audio3.patch
applesmc_int.patch
appletouch.patch
-appleir.patch
+appleir-undo-hid-blacklist.patch
appletouch-shut-up-when-it-has-nothing-to-say.patch
-appletouch-fix-run-amok-problem.patch
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: Daniel M. N. <dmn...@po...> - 2007-07-17 08:12:04
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>on 17/07/07 16:44 Soeren Sonnenburg said the following:</tt>
<blockquote cite="mid:1184654670.14051.16.camel@localhost" type="cite">
<pre wrap="">On Tue, 2007-07-17 at 09:16 +1000, Daniel M. Newman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">on 16/07/07 15:33 Soeren Sonnenburg said the following:
</pre>
<blockquote type="cite">
<pre wrap="">On Mon, 2007-07-16 at 10:32 +1000, Daniel M. Newman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Using kernel 2.6.22 and the mactel-linux revision 133 patch set from svn
on a Macbook Pro 15in, there seem to be a couple of peculiarities in the
trackpad behaviour.
</pre>
</blockquote>
<pre wrap="">please try the attached kernel patch and make sure that you are using a
new X synaptics driver (e.g. 0.14.7~git20070517 )...
</pre>
</blockquote>
<pre wrap="">I tried building the 0.14.7~git20070517 driver from source. It built
fine, but it didn't play well with my Ubuntu distribution version
2:1.3.0.0.dfsg-6ubuntu2, failing with:
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
dlopen: /usr/lib/xorg/modules/input//synaptics_drv.so: undefined symbol: __stack_chk_fail_local
(EE) Failed to load /usr/lib/xorg/modules/input//synaptics_drv.so
so I reverted to the 0.14.6-0ubuntu7 driver, which was working ok.
</pre>
</blockquote>
<pre wrap=""><!---->
too bad... this newer driver really resolved a couple of issues for me.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">1. During boot-up, the appletouch module always loads normally.
However, as X (using the fglrx driver 8.38.6) starts up I sometimes
(about one time in five) get an error that the core pointer is
unavailable. When this happens, the following shows up in syslog:
kernel: BUG: scheduling while atomic: Xorg/0x00000001/2826
kernel: [schedule+1267/2448] schedule+0x4f3/0x990
kernel: [_spin_unlock+13/48] _spin_unlock+0xd/0x30
kernel: [__wake_up_common+57/112] __wake_up_common+0x39/0x70
kernel: [__wake_up+56/80] __wake_up+0x38/0x50
kernel: [<f89d8f81>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx]
kernel: [<f89c9f45>] firegl_takedown+0x625/0xc50 [fglrx]
kernel: [proc_delete_inode+0/96] proc_delete_inode+0x0/0x60
kernel: [<f89c900f>] firegl_release+0x12f/0x190 [fglrx]
kernel: [<f89bd44f>] ip_firegl_release+0xf/0x20 [fglrx]
kernel: [__fput+151/368] __fput+0x97/0x170
kernel: [filp_close+73/128] filp_close+0x49/0x80
kernel: [put_files_struct+156/192] put_files_struct+0x9c/0xc0
kernel: [do_exit+314/2016] do_exit+0x13a/0x7e0
kernel: [<f8a14be9>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89d8d2e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [kernel_thread_helper+13/20] kernel_thread_helper+0xd/0x14
Removing and re-inserting appletouch generally fixes this, although
sometimes I have to do the remove and reinsert twice.
</pre>
</blockquote>
<pre wrap="">this sounds more like a bug in fglrx... but I've yet to see this to
happen...
</pre>
</blockquote>
<pre wrap="">No, I'm fairly sure it is to do with the appletouch, since it can be
fixed by removing and re-inserting it. I think the fglrx component of
the failure happens after the appletouch fails to provide a pointer
device. Also, the bug seems to have some connection to the usb
system, since it happens much more often if the machine is booted up
with large numbers of usb devices connected, particularly if a usb hub
is used. Maybe there is some sort of race in the allocation of usb
devices ?
</pre>
</blockquote>
<pre wrap=""><!---->
Could be, but as I've never seen it and I am also regularly connecting
my machine to a usb hub. So it would be great if you could isolate it a
bit more...
One last idea: is appletouch really loaded before you start X ? It could
be that X just does not find the touchpad device starts/stops X
triggering a bug in fglrx...
So you could try to explicitly load the appletouch module on startup and
also it might help to use this as the appletouch device line...
Option "Device" "/dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-mouse"
Any appletouch errors in dmesg ?
</pre>
</blockquote>
<tt>I'm already explicitly loading appletouch, as the first item in
/etc/modules. I have regularly checked dmesg and never seen any
appletouch problems. I'm using udev to set up a link to the device,
and have tried both _Trackpad-mouse and _Trackpad-event-mouse with
similar results (the problem happens only occasionally in each case).
I'll keep experimenting and see what else I can find out ...</tt>
<blockquote cite="mid:1184654670.14051.16.camel@localhost" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">2. I have my screen set to blank after a period of non-usage. When
waking up after this happens, the trackpad cursor no longer follows
finger movements reliably. Removing and re-inserting the appletouch
module fixes this, but does not re-enable response to two- and three-
finger taps. Restarting gdm fixes both problems.
</pre>
</blockquote>
<pre wrap="">that should be fixed by the patch.
</pre>
</blockquote>
<pre wrap="">Your patch fixed the problem, although sometimes it seems to slightly
affect the sensitivity of the multi-finger taps after wakeup. It also
prevents the svn patch
"appletouch-shut-up-when-it-has-nothing-to-say.patch" from applying
cleanly.
</pre>
</blockquote>
<pre wrap=""><!---->
well the patch I sent you already includes the
appletouch-shut-up-when-it-has-nothing-to-say.patch + small fixes. and
it definitely does not change anything regarding multi-finger taps... so
that is a heisen-bug :-)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">3. Trackpad button presses sometimes do not generate an immediate
response. However, if the trackpad button is pressed and no response
happens, a small movement of the cursor will cause the response to
occur. It seems that the button press input is being queued, but the
queue is not checked until trackpad motion is detected. I thought this
might be due to my xorg.conf settings, but these seem to be in
accordance with the various recommendations (see below).
</pre>
</blockquote>
<pre wrap="">strange...
Please report back whether it still happens with the attached patch and
a newer synaptics xorg driver...
</pre>
</blockquote>
<pre wrap="">This doesn't seem to happen now - maybe because the
"appletouch-shut-up-when-it-has-nothing-to-say.patch" didn't install ?
</pre>
</blockquote>
<pre wrap=""><!---->
well the shut-up patch could have triggered this, but as I said my patch
included that one + a fix when the touchpad 'wakes up' so it might have
been fixed by that patch too...
Soeren
</pre>
</blockquote>
<tt>OK, with the new patch installed I've done some experimenting with
synclient and now have what seems (for me, anyway) is a good response
to multi-fingered touches. The revised xorg.conf element is:<br>
<br>
Section "InputDevice"<br>
Identifier "Synaptics Touchpad"<br>
Driver "synaptics"<br>
Option "Device" "/dev/input/appletouchpad"<br>
Option "Protocol" "event"<br>
Option "CorePointer"<br>
Option "SHMConfig" "on"<br>
Option "LeftEdge" "0"<br>
Option "RightEdge" "850"<br>
Option "TopEdge" "0"<br>
Option "BottomEdge" "310"<br>
Option "FingerLow" "25"<br>
Option "FingerHigh" "30"<br>
Option "MaxTapTime" "350"<br>
Option "MaxTapMove" "0"<br>
Option "MaxDoubleTapTime" "180"<br>
Option "HorizEdgeScroll" "true"<br>
Option "VertEdgeScroll" "true"<br>
Option "VertTwoFingerScroll" "false"<br>
Option "HorizTwoFingerScroll" "false"<br>
Option "VertScrollDelta" "7"<br>
Option "HorizScrollDelta" "7"<br>
Option "MinSpeed" "0.6"<br>
Option "MaxSpeed" "1.0"<br>
Option "AccelFactor" "0.02"<br>
Option "TapButton1" "0"<br>
Option "TapButton2" "2"<br>
Option "TapButton3" "3"<br>
EndSection<br>
<br>
<br>
So, I'd say your patch has definitely fixed most of my touchpad
problems and the remaining one only happens occasionally and
irregularly. Thanks for all the help.<br>
<br>
Dan<br>
<br>
</tt><br>
</body>
</html>
|
|
From: Soeren S. <mac...@nn...> - 2007-07-17 06:44:39
|
On Tue, 2007-07-17 at 09:16 +1000, Daniel M. Newman wrote:
> on 16/07/07 15:33 Soeren Sonnenburg said the following:
> > On Mon, 2007-07-16 at 10:32 +1000, Daniel M. Newman wrote:
> >
> > > Using kernel 2.6.22 and the mactel-linux revision 133 patch set from svn
> > > on a Macbook Pro 15in, there seem to be a couple of peculiarities in the
> > > trackpad behaviour.
> > >
> >
> > please try the attached kernel patch and make sure that you are using a
> > new X synaptics driver (e.g. 0.14.7~git20070517 )...
> >
> >
> I tried building the 0.14.7~git20070517 driver from source. It built
> fine, but it didn't play well with my Ubuntu distribution version
> 2:1.3.0.0.dfsg-6ubuntu2, failing with:
>
> (II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
> dlopen: /usr/lib/xorg/modules/input//synaptics_drv.so: undefined symbol: __stack_chk_fail_local
> (EE) Failed to load /usr/lib/xorg/modules/input//synaptics_drv.so
> so I reverted to the 0.14.6-0ubuntu7 driver, which was working ok.
too bad... this newer driver really resolved a couple of issues for me.
> > > 1. During boot-up, the appletouch module always loads normally.
> > > However, as X (using the fglrx driver 8.38.6) starts up I sometimes
> > > (about one time in five) get an error that the core pointer is
> > > unavailable. When this happens, the following shows up in syslog:
> > >
> > > kernel: BUG: scheduling while atomic: Xorg/0x00000001/2826
> > > kernel: [schedule+1267/2448] schedule+0x4f3/0x990
> > > kernel: [_spin_unlock+13/48] _spin_unlock+0xd/0x30
> > > kernel: [__wake_up_common+57/112] __wake_up_common+0x39/0x70
> > > kernel: [__wake_up+56/80] __wake_up+0x38/0x50
> > > kernel: [<f89d8f81>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx]
> > > kernel: [<f89c9f45>] firegl_takedown+0x625/0xc50 [fglrx]
> > > kernel: [proc_delete_inode+0/96] proc_delete_inode+0x0/0x60
> > > kernel: [<f89c900f>] firegl_release+0x12f/0x190 [fglrx]
> > > kernel: [<f89bd44f>] ip_firegl_release+0xf/0x20 [fglrx]
> > > kernel: [__fput+151/368] __fput+0x97/0x170
> > > kernel: [filp_close+73/128] filp_close+0x49/0x80
> > > kernel: [put_files_struct+156/192] put_files_struct+0x9c/0xc0
> > > kernel: [do_exit+314/2016] do_exit+0x13a/0x7e0
> > > kernel: [<f8a14be9>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx]
> > > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
> > > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
> > > kernel: [<f89d8d2e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx]
> > > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
> > > kernel: [kernel_thread_helper+13/20] kernel_thread_helper+0xd/0x14
> > >
> > > Removing and re-inserting appletouch generally fixes this, although
> > > sometimes I have to do the remove and reinsert twice.
> > >
> >
> > this sounds more like a bug in fglrx... but I've yet to see this to
> > happen...
> >
> >
> No, I'm fairly sure it is to do with the appletouch, since it can be
> fixed by removing and re-inserting it. I think the fglrx component of
> the failure happens after the appletouch fails to provide a pointer
> device. Also, the bug seems to have some connection to the usb
> system, since it happens much more often if the machine is booted up
> with large numbers of usb devices connected, particularly if a usb hub
> is used. Maybe there is some sort of race in the allocation of usb
> devices ?
Could be, but as I've never seen it and I am also regularly connecting
my machine to a usb hub. So it would be great if you could isolate it a
bit more...
One last idea: is appletouch really loaded before you start X ? It could
be that X just does not find the touchpad device starts/stops X
triggering a bug in fglrx...
So you could try to explicitly load the appletouch module on startup and
also it might help to use this as the appletouch device line...
Option "Device" "/dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-mouse"
Any appletouch errors in dmesg ?
> > > 2. I have my screen set to blank after a period of non-usage. When
> > > waking up after this happens, the trackpad cursor no longer follows
> > > finger movements reliably. Removing and re-inserting the appletouch
> > > module fixes this, but does not re-enable response to two- and three-
> > > finger taps. Restarting gdm fixes both problems.
> > >
> >
> > that should be fixed by the patch.
> >
> >
> Your patch fixed the problem, although sometimes it seems to slightly
> affect the sensitivity of the multi-finger taps after wakeup. It also
> prevents the svn patch
> "appletouch-shut-up-when-it-has-nothing-to-say.patch" from applying
> cleanly.
well the patch I sent you already includes the
appletouch-shut-up-when-it-has-nothing-to-say.patch + small fixes. and
it definitely does not change anything regarding multi-finger taps... so
that is a heisen-bug :-)
> > > 3. Trackpad button presses sometimes do not generate an immediate
> > > response. However, if the trackpad button is pressed and no response
> > > happens, a small movement of the cursor will cause the response to
> > > occur. It seems that the button press input is being queued, but the
> > > queue is not checked until trackpad motion is detected. I thought this
> > > might be due to my xorg.conf settings, but these seem to be in
> > > accordance with the various recommendations (see below).
> > >
> >
> > strange...
> >
> > Please report back whether it still happens with the attached patch and
> > a newer synaptics xorg driver...
> >
> This doesn't seem to happen now - maybe because the
> "appletouch-shut-up-when-it-has-nothing-to-say.patch" didn't install ?
well the shut-up patch could have triggered this, but as I said my patch
included that one + a fix when the touchpad 'wakes up' so it might have
been fixed by that patch too...
Soeren
|
|
From: Daniel M. N. <dmn...@po...> - 2007-07-16 23:17:15
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>on 16/07/07 15:33 Soeren Sonnenburg said the following:</tt>
<blockquote cite="mid:1184564024.4181.75.camel@localhost" type="cite">
<pre wrap="">On Mon, 2007-07-16 at 10:32 +1000, Daniel M. Newman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Using kernel 2.6.22 and the mactel-linux revision 133 patch set from svn
on a Macbook Pro 15in, there seem to be a couple of peculiarities in the
trackpad behaviour.
</pre>
</blockquote>
<pre wrap=""><!---->
please try the attached kernel patch and make sure that you are using a
new X synaptics driver (e.g. 0.14.7~git20070517 )...
</pre>
</blockquote>
<tt>I tried building the 0.14.7~git20070517 driver from source. It
built fine, but it didn't play well with my Ubuntu distribution version
2:1.3.0.0.dfsg-6ubuntu2, failing with:<br>
<br>
</tt><tt>(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so<br>
dlopen: /usr/lib/xorg/modules/input//synaptics_drv.so: undefined
symbol: __stack_chk_fail_local<br>
(EE) Failed to load /usr/lib/xorg/modules/input//synaptics_drv.so<br>
<br>
so I reverted to the 0.14.6-0ubuntu7 driver, which was working ok.</tt>
<blockquote cite="mid:1184564024.4181.75.camel@localhost" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">1. During boot-up, the appletouch module always loads normally.
However, as X (using the fglrx driver 8.38.6) starts up I sometimes
(about one time in five) get an error that the core pointer is
unavailable. When this happens, the following shows up in syslog:
kernel: BUG: scheduling while atomic: Xorg/0x00000001/2826
kernel: [schedule+1267/2448] schedule+0x4f3/0x990
kernel: [_spin_unlock+13/48] _spin_unlock+0xd/0x30
kernel: [__wake_up_common+57/112] __wake_up_common+0x39/0x70
kernel: [__wake_up+56/80] __wake_up+0x38/0x50
kernel: [<f89d8f81>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx]
kernel: [<f89c9f45>] firegl_takedown+0x625/0xc50 [fglrx]
kernel: [proc_delete_inode+0/96] proc_delete_inode+0x0/0x60
kernel: [<f89c900f>] firegl_release+0x12f/0x190 [fglrx]
kernel: [<f89bd44f>] ip_firegl_release+0xf/0x20 [fglrx]
kernel: [__fput+151/368] __fput+0x97/0x170
kernel: [filp_close+73/128] filp_close+0x49/0x80
kernel: [put_files_struct+156/192] put_files_struct+0x9c/0xc0
kernel: [do_exit+314/2016] do_exit+0x13a/0x7e0
kernel: [<f8a14be9>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89d8d2e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [kernel_thread_helper+13/20] kernel_thread_helper+0xd/0x14
Removing and re-inserting appletouch generally fixes this, although
sometimes I have to do the remove and reinsert twice.
</pre>
</blockquote>
<pre wrap=""><!---->
this sounds more like a bug in fglrx... but I've yet to see this to
happen...
</pre>
</blockquote>
<tt>No, I'm fairly sure it is to do with the appletouch, since it can
be fixed by removing and re-inserting it. I think the fglrx component
of the failure happens after the appletouch fails to provide a pointer
device. Also, the bug seems to have some connection to the usb system,
since it happens much more often if the machine is booted up with large
numbers of usb devices connected, particularly if a usb hub is used.
Maybe there is some sort of race in the allocation of usb devices ?<br>
</tt>
<blockquote cite="mid:1184564024.4181.75.camel@localhost" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">2. I have my screen set to blank after a period of non-usage. When
waking up after this happens, the trackpad cursor no longer follows
finger movements reliably. Removing and re-inserting the appletouch
module fixes this, but does not re-enable response to two- and three-
finger taps. Restarting gdm fixes both problems.
</pre>
</blockquote>
<pre wrap=""><!---->
that should be fixed by the patch.
</pre>
</blockquote>
<tt>Your patch fixed the problem, although sometimes it seems to
slightly affect the sensitivity of the multi-finger taps after wakeup.
It also prevents the svn patch
"appletouch-shut-up-when-it-has-nothing-to-say.patch" from applying
cleanly.</tt><br>
<blockquote cite="mid:1184564024.4181.75.camel@localhost" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">3. Trackpad button presses sometimes do not generate an immediate
response. However, if the trackpad button is pressed and no response
happens, a small movement of the cursor will cause the response to
occur. It seems that the button press input is being queued, but the
queue is not checked until trackpad motion is detected. I thought this
might be due to my xorg.conf settings, but these seem to be in
accordance with the various recommendations (see below).
</pre>
</blockquote>
<pre wrap=""><!---->
strange...
Please report back whether it still happens with the attached patch and
a newer synaptics xorg driver...
</pre>
</blockquote>
<tt>This doesn't seem to happen now - maybe because the </tt><tt>"appletouch-shut-up-when-it-has-nothing-to-say.patch"
didn't install ?<br>
</tt>
<blockquote cite="mid:1184564024.4181.75.camel@localhost" type="cite">
<pre wrap="">
Thanks,
Soeren
</pre>
</blockquote>
<tt>Thanks for all your help,<br>
Dan <br>
</tt><br>
</body>
</html>
|
|
From: Thomas B. <tho...@ar...> - 2007-07-16 07:07:52
|
Hi Marek, ma...@mi... wrote: > On Fri, 13 Jul 2007 11:48:40 +0200, Thomas Besser > <tho...@ar...> wrote: > First at all, it is a good idea to determine, which version of macbook, or > more precisely which audio subsystem is used in your macbook. You can do > it by the command > > # cat /proc/asound/card0/codec\#0 | grep Subsystem > > If your output is an other number than 0x106b2200, there no chance that > this patch will work for you. Ok, I have the right version ;-) Subsystem Id: 0x106b2200 > But, it seems, your mixer is not set correctly. Your input source is > set to "Line" and not for "Mic". I don't know if you tried some other > possibilities, but setting the input source as "Mic" would be necessary. Oh thats right, I oversaw also the hints on http://wiki.debian.org/MacBook#head-d374bb9e1b7183c133759a8c6877a34c50c4ba7d Will give it a try soon. Thanx... Thomas |
|
From: Soeren S. <mac...@nn...> - 2007-07-16 05:34:19
|
On Mon, 2007-07-16 at 10:32 +1000, Daniel M. Newman wrote: > Using kernel 2.6.22 and the mactel-linux revision 133 patch set from svn > on a Macbook Pro 15in, there seem to be a couple of peculiarities in the > trackpad behaviour. please try the attached kernel patch and make sure that you are using a new X synaptics driver (e.g. 0.14.7~git20070517 )... > 1. During boot-up, the appletouch module always loads normally. > However, as X (using the fglrx driver 8.38.6) starts up I sometimes > (about one time in five) get an error that the core pointer is > unavailable. When this happens, the following shows up in syslog: > > kernel: BUG: scheduling while atomic: Xorg/0x00000001/2826 > kernel: [schedule+1267/2448] schedule+0x4f3/0x990 > kernel: [_spin_unlock+13/48] _spin_unlock+0xd/0x30 > kernel: [__wake_up_common+57/112] __wake_up_common+0x39/0x70 > kernel: [__wake_up+56/80] __wake_up+0x38/0x50 > kernel: [<f89d8f81>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx] > kernel: [<f89c9f45>] firegl_takedown+0x625/0xc50 [fglrx] > kernel: [proc_delete_inode+0/96] proc_delete_inode+0x0/0x60 > kernel: [<f89c900f>] firegl_release+0x12f/0x190 [fglrx] > kernel: [<f89bd44f>] ip_firegl_release+0xf/0x20 [fglrx] > kernel: [__fput+151/368] __fput+0x97/0x170 > kernel: [filp_close+73/128] filp_close+0x49/0x80 > kernel: [put_files_struct+156/192] put_files_struct+0x9c/0xc0 > kernel: [do_exit+314/2016] do_exit+0x13a/0x7e0 > kernel: [<f8a14be9>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx] > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx] > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx] > kernel: [<f89d8d2e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx] > kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx] > kernel: [kernel_thread_helper+13/20] kernel_thread_helper+0xd/0x14 > > Removing and re-inserting appletouch generally fixes this, although > sometimes I have to do the remove and reinsert twice. this sounds more like a bug in fglrx... but I've yet to see this to happen... > 2. I have my screen set to blank after a period of non-usage. When > waking up after this happens, the trackpad cursor no longer follows > finger movements reliably. Removing and re-inserting the appletouch > module fixes this, but does not re-enable response to two- and three- > finger taps. Restarting gdm fixes both problems. that should be fixed by the patch. > 3. Trackpad button presses sometimes do not generate an immediate > response. However, if the trackpad button is pressed and no response > happens, a small movement of the cursor will cause the response to > occur. It seems that the button press input is being queued, but the > queue is not checked until trackpad motion is detected. I thought this > might be due to my xorg.conf settings, but these seem to be in > accordance with the various recommendations (see below). strange... Please report back whether it still happens with the attached patch and a newer synaptics xorg driver... Thanks, Soeren |
|
From: Daniel M. N. <dmn...@po...> - 2007-07-16 00:32:21
|
Using kernel 2.6.22 and the mactel-linux revision 133 patch set from svn
on a Macbook Pro 15in, there seem to be a couple of peculiarities in the
trackpad behaviour.
1. During boot-up, the appletouch module always loads normally.
However, as X (using the fglrx driver 8.38.6) starts up I sometimes
(about one time in five) get an error that the core pointer is
unavailable. When this happens, the following shows up in syslog:
kernel: BUG: scheduling while atomic: Xorg/0x00000001/2826
kernel: [schedule+1267/2448] schedule+0x4f3/0x990
kernel: [_spin_unlock+13/48] _spin_unlock+0xd/0x30
kernel: [__wake_up_common+57/112] __wake_up_common+0x39/0x70
kernel: [__wake_up+56/80] __wake_up+0x38/0x50
kernel: [<f89d8f81>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx]
kernel: [<f89c9f45>] firegl_takedown+0x625/0xc50 [fglrx]
kernel: [proc_delete_inode+0/96] proc_delete_inode+0x0/0x60
kernel: [<f89c900f>] firegl_release+0x12f/0x190 [fglrx]
kernel: [<f89bd44f>] ip_firegl_release+0xf/0x20 [fglrx]
kernel: [__fput+151/368] __fput+0x97/0x170
kernel: [filp_close+73/128] filp_close+0x49/0x80
kernel: [put_files_struct+156/192] put_files_struct+0x9c/0xc0
kernel: [do_exit+314/2016] do_exit+0x13a/0x7e0
kernel: [<f8a14be9>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [<f89d8d2e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx]
kernel: [<f89bab90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
kernel: [kernel_thread_helper+13/20] kernel_thread_helper+0xd/0x14
Removing and re-inserting appletouch generally fixes this, although
sometimes I have to do the remove and reinsert twice.
2. I have my screen set to blank after a period of non-usage. When
waking up after this happens, the trackpad cursor no longer follows
finger movements reliably. Removing and re-inserting the appletouch
module fixes this, but does not re-enable response to two- and three-
finger taps. Restarting gdm fixes both problems.
3. Trackpad button presses sometimes do not generate an immediate
response. However, if the trackpad button is pressed and no response
happens, a small movement of the cursor will cause the response to
occur. It seems that the button press input is being queued, but the
queue is not checked until trackpad motion is detected. I thought this
might be due to my xorg.conf settings, but these seem to be in
accordance with the various recommendations (see below).
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "Device" "/dev/input/appletouchpad"
Option "Protocol" "event"
Option "CorePointer"
Option "LeftEdge" "0"
Option "RightEdge" "850"
Option "TopEdge" "0"
Option "BottomEdge" "645"
Option "MinSpeed" "0.4"
Option "MaxSpeed" "1"
Option "AccelFactor" "0.02"
Option "FingerLow" "0"
Option "FingerHigh" "30"
Option "MaxTapMove" "0"
Option "MaxTapTime" "180"
Option "EmulateMidButtonTime" "75"
Option "HorizScrollDelta" "0"
Option "VertScrollDelta" "30"
Option "SHMConfig" "true"
EndSection
Any suggestions about any of the above ?
|
|
From: Sven A. <an...@an...> - 2007-07-14 12:33:58
|
Hello!
Since I upgraded to kernel 2.6.22.1 with the mactel patches, the applesmc isn't
loaded automatically any longer. Have you changed anything?
If I load it manually, anything works fine...
I own an MacBookPro C2D 2,33Ghz (Dec '06).
And... Did you received my last mail regarding the problems with failed
sensors readings?
Regards
Sven
--
Sven Anders <an...@an...> () Ascii Ribbon Campaign
/\ Support plain text e-mail
ANDURAS service solutions AG
Innstraße 71 - 94036 Passau - Germany
Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55
Rechtsform: Aktiengesellschaft - Sitz: Passau - Amtsgericht Passau HRB 6032
Mitglieder des Vorstands: Sven Anders, Marcus Junker
Vorsitzender des Aufsichtsrats: Dipl. Kfm. Thomas Träger
|
|
From: <ma...@mi...> - 2007-07-14 01:50:12
|
Hi Thomas! On Fri, 13 Jul 2007 11:48:40 +0200, Thomas Besser <tho...@ar...> wrote: > Tried it today with 2.6.21.1 and mactel patches. > I think patching was successful (?!): Yes, from the output you wrote, it seems, the patching was successful. > But integrated microphone or with headset does always not. > How to debug this problem? Starting point? > Output of 'amixer' is attached. First at all, it is a good idea to determine, which version of macbook, or more precisely which audio subsystem is used in your macbook. You can do it by the command # cat /proc/asound/card0/codec\#0 | grep Subsystem If your output is an other number than 0x106b2200, there no chance that this patch will work for you. But, it seems, your mixer is not set correctly. Your input source is set to "Line" and not for "Mic". I don't know if you tried some other possibilities, but setting the input source as "Mic" would be necessary. The last thing is, that I'm not an alsa developper. So I really don't know much about alsa subsystem. This patch only provides some pinout settings, which I actually took from the windows driver inf file. Regards marek |
|
From: Thomas B. <tho...@ar...> - 2007-07-13 09:49:12
|
Hi Marek, Thomas Besser wrote: > ma...@mi... wrote: >> on my second generanion non-pro MacBook the microphone >> (and probbably some ohter soundcard stuff) did not work. > > Great, I have such one for two weeks now and microphone does not. > >> The patch should be applied after sigmatel_audio2.patch >> and sigmatel_audio3.patch. > > I'm running 2.6.22-rc3 with mactel patches. I will try it next days. Tried it today with 2.6.21.1 and mactel patches. I think patching was successful (?!): sissymobil:/usr/src/linux-2.6.22.1# patch -p1 < ../macbook_v2_audio.patch patching file sound/pci/hda/patch_sigmatel.c Hunk #1 succeeded at 61 with fuzz 1 (offset 1 line). Hunk #2 succeeded at 562 (offset 25 lines). Hunk #3 succeeded at 592 with fuzz 1 (offset 31 lines). Hunk #4 succeeded at 604 with fuzz 1 (offset 32 lines). Hunk #5 succeeded at 2049 with fuzz 1 (offset 125 lines). But integrated microphone or with headset does always not. How to debug this problem? Starting point? Output of 'amixer' is attached. Thanx in advance... Thomas |
|
From: <nbo...@us...> - 2007-07-12 13:56:55
|
Revision: 134
http://svn.sourceforge.net/mactel-linux/?rev=134&view=rev
Author: nboichat
Date: 2007-07-12 06:56:52 -0700 (Thu, 12 Jul 2007)
Log Message:
-----------
Minor change in applesmc_int.patch
Modified Paths:
--------------
trunk/kernel/mactel-patches-2.6.22/applesmc_int.patch
trunk/kernel/mactel-patches-2.6.22/series
Modified: trunk/kernel/mactel-patches-2.6.22/applesmc_int.patch
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/applesmc_int.patch 2007-06-27 13:14:46 UTC (rev 133)
+++ trunk/kernel/mactel-patches-2.6.22/applesmc_int.patch 2007-07-12 13:56:52 UTC (rev 134)
@@ -1,4 +1,4 @@
-Interrupt support for the accelerometer.
+Add interrupt support for the accelerometer. A message is printed in dmesg when an interrupt occurs, but no further handling is done.
From: Nicolas Boichat <ni...@bo...>
@@ -9,7 +9,7 @@
1 files changed, 298 insertions(+), 23 deletions(-)
diff --git a/drivers/hwmon/applesmc.c b/drivers/hwmon/applesmc.c
-index 232cbad..933a72d 100644
+index 232cbad..c022c98 100644
--- a/drivers/hwmon/applesmc.c
+++ b/drivers/hwmon/applesmc.c
@@ -39,14 +39,20 @@
@@ -255,7 +255,7 @@
+static int applesmc_remove(struct platform_device *dev)
+{
-+ free_irq(6, NULL);
++ free_irq(APPLESMC_IRQ, NULL);
+ return 0;
+}
+
Modified: trunk/kernel/mactel-patches-2.6.22/series
===================================================================
--- trunk/kernel/mactel-patches-2.6.22/series 2007-06-27 13:14:46 UTC (rev 133)
+++ trunk/kernel/mactel-patches-2.6.22/series 2007-07-12 13:56:52 UTC (rev 134)
@@ -1,4 +1,4 @@
-# This series applies on GIT commit 48d8d7ee5dd17c64833e0343ab4ae8ef01cc2648
+# This series applies on GIT commit f44bba1a92e01bbab6ca9817b86ddf9e1744a616
applesmc-use-input-polldev.patch
applesmc-add-macbook-temperature-keys.patch
sigmatel_audio2.patch
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <fa...@dg...> - 2007-07-11 02:57:56
|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TTT企业培训师培训
开课日期：2007年7月20-22日 地点：上海
开课日期：2007年8月10-12日 地点：深圳
开课日期：2007年11月2-4日 地点：广州
【培训费用】3600元
【主办公司】 众 人 行 管 理 咨 询 机 构
深圳总部电话：0755-26075265 26075429 26075365 22008632 81069646
上海办事处电话：021-51875149
北京办事处电话：010-51293353
传真： 0755-61351396 82129209
联系人：彭小姐 曾小姐
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
课程背景
本课程通过对学习理论、培训方式、培训技巧、课程设计、培训游戏的讲授、
研讨、练习、演练等形式多样的互动教学来帮助学员理解、观摩、练习并掌
握讲师的基本技能，以帮助学员更快更有效地成长为优秀讲师。
培训目标：
? 掌握学习原理与培训原理，并能创造性地在培训中加以应用；
? 理解、练习并掌握培训常见演讲技巧及与学员互动方法；
? 掌握培训游戏组织的技巧与方法；
? 掌握课程设计方法并能有效运用；
? 掌握培训讲师成长路径与成长经验。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【课程内容】
第一天上午:
学习原理及和培训师的角色定位
1、 为何要成为一名讲师
3C时代，知识更新速度，挑战舒适区，培训终身受益
2、最主流的学习理论分析
培训与学习之关系，学习的信息加工模型：建构主义
3、 1分钟培训体验
压力转换技巧训练：如何克服培训中的紧张想象
4、培训师的角色定位
定义：什么是现代意义上的培训
企业发展与培训的关系
培训与教育的不同之处
培训讲师的使命与角色
5、培训师的风格选型
第一天下午:
培训需求定义
（需求、环境、备课、开场白技巧）
1、 培训技能自检测试
2、 定义需求和培训准备
如何确定培训需求的：不同性质的需求
学员、组织者、总经理对需求的区别
培训环境（教室、道具、提示纲要）
备课与自我状态（备课CHECKLIST、仪表与仪态、上课前注意事项）
4、 培训演讲的两大原则（结构化3T原则；AIDA原则）
5、 开场白的技巧
3I-O（自我介绍；激起兴趣与注意；破冰；主题预览）
技巧一：立即切入故事；
技巧二：让听众吃惊
技巧三：制造悬念
技巧四：拿学员来打比方
技巧五：提问吊胃口
成人学习原理
1、 注意力原理及其在培训中的应用
鸡尾酒会现象；大胖子效应；注意力保持曲线；注意力分配
2、 记忆力原理及其在培训中的应用
3、 成人学习原理
动机、策略、应用、成人经验、疲劳度
4、 大脑的在培训中的应用
思维脑与创造脑；意识与潜意识；学习音乐；情绪脑与创造学习氛围
演讲技巧演练
（语言表达技巧）
1、 语言表达技巧
准确流畅；具体化技巧；多用故事、类比、排比、对比、比喻；设置悬念；
少用专业术语；多用短句；运用对白；多用亮词，少用抽象词；去掉冗余词汇；
标志性语言应用；停顿技巧；声音抑扬顿挫；如何才能打动人；故事联结技巧；
分层设计技巧
2、演练与分组演练
第二天上午:
课程设计与课件制作
1、明确课程设计的目的与效果
2、 课程设计的步骤
3、 课程设计的建构主义原则
4、课程内容的金字塔组织
5、课程内容的衔接与过渡
6、幻灯版制作的原则与技巧（美学原则、版面、颜色、图形、风格、详简）
7、教案制作技巧（简单制作）
8、学员手册制作技巧（原则、样板）
第二天下午:
演讲技巧（肢体语言技巧、提问互动技巧、）
1、肢体语言技巧与观摩
2、倾听与观察技巧
3、提问与答疑技巧
4、控场能力技巧
5、鼓励参与与分组研讨的技巧
6、仪器道具使用技巧
7、时间控制技巧
8、培训结束技巧
9、培训评估与辅导
第三天上午:
企业培训体系的构建
1、 培训体系的组成部分
2、 培训课程开发与管理体系
3、 培训师甑选与培养体系
4、 培训实施与效果评估体系
5、 三明治培训课程设计体系
6、 典型的员工培训课程体系设计
7、 培训效果的评估体系
8、 国外培训管理的经验介绍
9、 企业培训体系案例研讨
10、 企业培训管理组织机构的建设
? 不同层级的培训管理机构
? 不同层级的培训管理
机构的分工
? 人力资源部、培训部、
其它部门的协调的分工
? 企业培训部以及培训
经理主要工作
第三天下午:
游戏百宝箱与讲师的自我修炼成长
1、游戏在培训中的作用
2、游戏组织的要点与技巧
3、常见游戏类型、特点及其现场示范
1）破冰型游戏；2）认识型游戏；3）分组型游戏
4）团队型游戏；5）测试型游戏；6）充能型游戏
7）宴会型游戏；8）其他类型游戏
4、 如何自己设计游戏
1）明确游戏目的；
2）界定游戏范围；
3）游戏改造与创新；
4）练习：现场设计游戏
5、 如何建立自己的游戏百宝箱
1、 讲师的八大素质要求与讲师的层次
2、 讲师的五练与五功
8、培训讲师进步的六个阶梯
9、培训讲师必看的书与网站
10、培训讲师的素养与职业道德
11、讲师的目标计划系统练习
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【顾问介绍】张见明（Jay Zhang ）先生
资深人力资源管理咨询师、培训师，美国麻省大学MBA， 2003年度深圳市
优秀咨询顾问，深圳市企业协会咨询业专业委员会专家团顾问，《中国人力资
源网》专家,《中国培训师大联盟》特约培训师、欧中美联国际教育集团咨询
培训专家委员会委员。张先生拥有10余年培训与咨询经验，先后在大型国有外
贸企业、知名高科技企业和专业咨询公司担任过销售经理、培训经理、人力资
源总监、咨询总监、副总裁等职务,积累了丰富的人力资源管理实操及咨询培
训经验。张先生擅长于战略性人力资源管理方案的设计，包括基于BSC和KPI的
绩效体系、目标管理、组织设计、营销体系设计、员工素质模型设计、薪酬体
系设计等领域。
其服务过的培训客户包括，中国电信东莞公司、佛山电信、久隆地产集团、
卓越地产集团、中国移动辽宁省公司、中国电信深大电话、键桥通信、润讯科技、
深圳市机场集团、广东证券、三和国际、恒丰酒店、同城置业、汉哲科技、
博思堂广告、龙岗留学生创业园、元征科技、天健信德、神威药业、四川工商银行、
深圳市商业银行、都都文具、正合电子、广东高科技产业商会、汇天源汽贸公司、
UT斯达康通信、EDAW、ITT、云南电力网、广西电网、河池供电局、柳州供电局、
杭州海关、浙江大学《医院院长高级培训班》等。
核心培训课程有《TTT－企业培训师培训》、《团队建设训练营》（英文版本）、
《目标管理与计划管理》、《现代人力资源管理实务》、《基于KPI的绩效管理》、
《BSC的导入实操演练》、《有效沟通技能》、《时间管理》、
《工作分析与职位评估》、《医院人力资源管理》、《企业文化与组织持续发展》、
《基于积极心态下的敬业精神和敬业心》等。
其培训课程将西方管理理论与国内管理咨询实践高度融合，授课风格以案例丰富、
轻松诙谐、互动性好、给人思维启迪而受到广泛好评。
张先生发表过的著作有：《从后台走向前台――人力资源管理新模式》、
《绩效评估的前提与目标管理》、《咨询的角色与定位》、
《人力资源管理的角色与定位》、 《人性假设与人力资源管理》 、
《明确绩效考核的目的》、《绩效管理的盲区》、《战略规划部的定位》、
《闻到的企业文化》等。
|
|
From: Clive S. <cli...@gm...> - 2007-07-10 17:51:52
|
Hi I just wanted to know if I can install FC 7 on the new macbook pro , Intel C2D , NVIDIA 8600M GT Thanks Clive |
|
From: Nadine H. <Jas...@ya...> - 2007-07-10 16:03:32
|
As a business you have been preapproved to receive 45293 USD TODAY! No hassle at all, completely unsecured. There are no hidden costs or fees. Worried that your credit is less than perfect? Not an issue. As long as your business is based in the US and processes over ten thousand a month. Give us a ring, now.. +18777679308 Turn your dream, into a reality, is that not worth two minutes of your time? +18777679308 Had she sat there in her as-yet-unseen-by-him parlor with her mouth open and her eyes wide as Misery finally realized the truth and made her decision and sneaked off to Geoffrey? He fled to that well now, like a thirsty animal finding a waterhole at dusk, and he drank from it; which is to say he found the hole in the paper and fell thankfully through it. Dianna Lange |
|
From: gimli <gi...@da...> - 2007-07-10 07:38:28
|
Hi, the latest oss nvidia driver from http://gitweb.freedsektop.org works on my 15" Macbook Pro V3. Happy Penguin Edgar (gimli) Hucek |
|
From: M.S. <ma...@su...> - 2007-07-09 13:59:32
|
Created a page on the WIKI for further investigation: http://www.mactel-linux.org/wiki/AppleSMC Cheers --- M.S. |
|
From: Steffen S. <pe...@gm...> - 2007-07-09 07:54:17
|
On 070709 at 08:40, Thomas Besser wrote: > Steffen Schulz wrote: > > I installed debian/unstable with vanilla 2.6.22-rc6 plus your patches. > > > When I do a suspend2ram, the display stays dark. vbetool save/restore > > did not help, > Same here with 'suspend' (s2ram) and 'suspend2' (hibernate-ram). > suspend2disk (hibernate, suspend2) works for me. > > I'm using the current binary nvidia driver, the display stays dark if I > > try the free one from xorg. > > MacBook with nvidia graphics? Thats new for me. I have Intel GM 945. Yes, I'm talking about the Macbook Pro rev3, they have an 8600M GT chip. I've seen intel and ati to work, nvidia however does not. I got s2ram working in X. The console is dead after wakeup and 2D acceleration seems to be gone in X. Never tried s2disk. My biggest problem is the backlight, the LED is much to bright and sucks on the battery of course.. stan: The 'fan-situation' is just fine. You'll have to use a little hack to get the current nvidia driver to work, it'll be fixed in the next version: https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro The binary driver also seems to enable the throttling, or maybe it's throttled all the time, I don't know. Don't have any complex games for Linux. /pepe |
|
From: Thomas B. <tho...@ar...> - 2007-07-09 06:29:27
|
Steffen Schulz wrote: > I installed debian/unstable with vanilla 2.6.22-rc6 plus your patches. Debian Etch, vanilla 2.6.22-rc6 + mactel + suspend2 on MacBook (rev2?) > I don't know how I can enable the apple ir receiver. The module loads > and I get an input device for it, but nothing happens when I do 'cat' > on the event-device and push buttons. Works. > There is also no support for display backlight control. Can I do > something to help you get it working? I'm using 'pommed' without problems > When I do a suspend2ram, the display stays dark. vbetool save/restore > did not help, Same here with 'suspend' (s2ram) and 'suspend2' (hibernate-ram). suspend2disk (hibernate, suspend2) works for me. > I'm using the current binary nvidia driver, the display stays dark if I > try the free one from xorg. MacBook with nvidia graphics? Thats new for me. I have Intel GM 945. Regards Thomas |
|
From: Steffen S. <pe...@gm...> - 2007-07-07 17:59:53
|
Hi, I installed debian/unstable with vanilla 2.6.22-rc6 plus your patches. Sensors and keyboard backlight seem to work finde, the macbook-led and hdaps-gl applications work too, but there are some things missing: I don't know how I can enable the apple ir receiver. The module loads and I get an input device for it, but nothing happens when I do 'cat' on the event-device and push buttons. There is also no support for display backlight control. Can I do something to help you get it working? When I do a suspend2ram, the display stays dark. vbetool save/restore did not help, someone said it is the LED brightness that needs tweaking here. Maybe one could use that as a starting point, read out memory(which one? how?) and compare.. I'm using the current binary nvidia driver, the display stays dark if I try the free one from xorg. /pepe -- ,''`, : :' : +49/1781384223 `. `' gpg --recv-key A04D7875 `- www.debian.org mailto: pe...@cb... |
|
From: <ma...@mi...> - 2007-07-06 01:43:23
|
Well, I really don't know, if my macbook is the second generation. Now I found out, that there is probably a third generation of macbooks. My macbook is the latest generation. So don't stone me if I wrote a bad generation:-) marek |
|
From: Thomas B. <tho...@ar...> - 2007-07-05 06:35:11
|
Hi Marek, ma...@mi... wrote: > on my second generanion non-pro MacBook the microphone > (and probbably some ohter soundcard stuff) did not work. Great, I have such one for two weeks now and microphone does not. > this patch should fix the soundcard settings for this model: > > http://www.milimetr.org/patches/macbook_v2_audio.patch > > The patch should be applied after sigmatel_audio2.patch > and sigmatel_audio3.patch. I'm running 2.6.22-rc3 with mactel patches. I will try it next days. Regards Thomas |
71 messages has been excluded from this view by a project administrator.
