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: Ludwig 'K. N. <lu...@no...> - 2008-05-30 05:40:36
|
Jerome Flesch a écrit :
> Hello,
Hi,
>
> In kernel/mactel-patches-2.6.24/hid-add-new-apple-keyboard.patch , two
> keys seem to be missing in the array "apple_keyboard_fn_keys":
> { KEY_F5, KEY_KBDILLUMDOWN, POWERBOOK_FLAG_FKEY },
> { KEY_F6, KEY_KBDILLUMUP, POWERBOOK_FLAG_FKEY },
>
> Without these two lines, it's not possible for me on my macbook pro
> 4.1 to adjust the light of the keyboard with pommed, but with them, it
> works fine.
Indeed, I just recompile with those two lines above and it works, thanx
a lot :) BTW, do you know what KEY_CYCLEWINDOWS (F3) and KEY_CONFIG (F4)
refer to ? pommed returns "KBD: inhibit clear 0x08 -> 0x00" for both of
them, which have no result on keyboard backlight.
>
> I'm also wondering : Is there any plan to integrate your patches to
> the mainstream linux kernel ?
Regards,
--
Ludwig 'Kn' Noujarret
lu...@no...
|
|
From: Jerome F. <jf...@gm...> - 2008-05-29 07:21:07
|
Hello,
In kernel/mactel-patches-2.6.24/hid-add-new-apple-keyboard.patch , two
keys seem to be missing in the array "apple_keyboard_fn_keys":
{ KEY_F5, KEY_KBDILLUMDOWN, POWERBOOK_FLAG_FKEY },
{ KEY_F6, KEY_KBDILLUMUP, POWERBOOK_FLAG_FKEY },
Without these two lines, it's not possible for me on my macbook pro
4.1 to adjust the light of the keyboard with pommed, but with them, it
works fine.
I'm also wondering : Is there any plan to integrate your patches to
the mainstream linux kernel ?
|
|
From: Sven A. <an...@an...> - 2008-04-24 07:43:06
|
Hello!
Here is the update of the appletouch driver addtions for the 2.6.25 linux kernel.
Please report any problems.
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: Dr. Thomas Träger
|
|
From: Steffen S. <pe...@gm...> - 2008-04-06 22:05:41
|
On 080406 at 22:53, Chris Nolan wrote:
> Steffen Schulz wrote:
>> So the goal is to get the laptop into s2ram without polling the
>> battery status..
> "[If the battery doesn't support alarms...] the ACPI specification
> requires the OS to poll the battery to check its remaining capacity".
>
> Certainly on my Macbook 3,1 under Fedora, the laptop shuts down when the
> battery reaches a critical level.
"...It appears that Linux does not yet do this."
So its a missing hardware feature. Unbelievable that neither the
battery module nor acpid or laptop-mode can handle this problem..
Thanks for the info! *running yet another deamon*
/steffen
--
_----------------
(o< ·-_ Less CO2 | _o) +49/1781384223
//\ | for more ice! | /\\ .o) .o) gpg --recv-key A04D7875
V_/_ --------------- _\_V _(\)_(\) mailto: pe...@cb...
|
|
From: Steffen S. <pe...@gm...> - 2008-04-06 20:38:00
|
On 080406 at 21:44, Soeren Sonnenburg wrote: > On Sun, 2008-04-06 at 20:29 +0200, Steffen Schulz wrote: > > cat /proc/acpi/battery/BAT0/alarm > > alarm: unsupported > > what is battery alarm? It seems to be mandatory to let acpi do something when the battery status gets critical. I don't get acpi events, acpid doesn't put the macbook to sleep. So the goal is to get the laptop into s2ram without polling the battery status.. |
|
From: Soeren S. <mac...@nn...> - 2008-04-06 19:44:07
|
On Sun, 2008-04-06 at 20:29 +0200, Steffen Schulz wrote: > Hi, > > A few days ago I noticed that the battery alarm on my Santa Rosa Macbook > Pro is not working. > > When 'battery' is loaded: > > cat /proc/acpi/battery/BAT0/alarm > alarm: unsupported what is battery alarm? > Any hints on this? If this is not supported yet, how difficult would > that be? note that this is also not supported on mbp1,1's Soeren |
|
From: Steffen S. <pe...@gm...> - 2008-04-06 18:29:40
|
Hi, A few days ago I noticed that the battery alarm on my Santa Rosa Macbook Pro is not working. When 'battery' is loaded: cat /proc/acpi/battery/BAT0/alarm alarm: unsupported Witch sbshc and sbs do not even recognise a battery(no BAT0 dir). The module help says sbs uses SMBus, so I activated i2c-core and i2c-i801, but nothing.. Any hints on this? If this is not supported yet, how difficult would that be? /steffen |
|
From: Marvin S. <ma...@de...> - 2008-04-03 10:24:19
|
On Tuesday 01 April 2008 14:56:30 you wrote: > Hi, Hi, > > You should not use the user-space executable anymore, as there is a > kernel driver for that now. thanks I didn't know that. > > You can read the temperature in > /sys/devices/platform/coretemp.0/temp1_input (or coretemp.1). > > It seems something has been added to coretemp in 2.6.25-rc7 > (drivers/hwmon/coretemp.c), so maybe it supports reading the values you > are interested in. Yes this is true. I had a look at the patches. beside this facts, the coretemp code in the svn tree should also be updated or removed because it returns wrong values (reads more bits than needed). > > Thanks, > > Best regards, > > Nicolas [...] Cheers, -- .""`. Marvin Stark <ma...@de...> : :" : Homepage: www.der-marv.de `. `"` `- Debian - when you have better things to do than fix a system |
|
From: Marvin S. <ma...@de...> - 2008-03-30 20:39:44
|
Hi, as the C2D processor has two TJunction values (model dependent), I added them to the coretemp code. Furthermore I added some code improvements. Please have a look at the code and commit it to svn, if the code is ok. Thanks, -- .""`. Marvin Stark <ma...@de...> : :" : Homepage: www.der-marv.de `. `"` `- Debian - when you have better things to do than fix a system |
|
From: James V. <ja...@va...> - 2008-03-16 03:39:09
|
So does this patch do anything special with 2 or 3 finger movements? It
would be nice to apply the capability of this hardware to interface with
compiz or something, for example, 3 finger swipe rotates my cube in a
given direction.
Or are we not there yet?
James
On Mon, 2008-03-10 at 12:51 +0100, Sven Anders wrote:
> Hello!
>
> The is an update of the appletouch, which fixes one wrong Product-ID.
> It also replaces the "appletouch-add-macbook3-trackpad.patch" patch.
>
> Please update the SVN...
>
> Regards
> Sven
>
> plain text document attachment (appletouch.patch-2.6.24)
> --- appletouch.c.orig-2.6.24 2008-01-28 17:50:52.000000000 +0100
> +++ appletouch.c 2008-02-29 20:15:33.000000000 +0100
> @@ -8,6 +8,7 @@
> * Copyright (C) 2005 Peter Osterlund (pe...@te...)
> * Copyright (C) 2005 Michael Hanselmann (lin...@ha...)
> * Copyright (C) 2006 Nicolas Boichat (ni...@bo...)
> + * Copyright (C) 2007-2008 Sven Anders (an...@an...)
> *
> * Thanks to Alex Harper <bas...@fo...> for his inputs.
> *
> @@ -38,16 +39,18 @@
> #define APPLE_VENDOR_ID 0x05AC
>
> /* These names come from Info.plist in AppleUSBTrackpad.kext */
> +
> +/* PowerBooks Feb 2005 / iBooks */
> #define FOUNTAIN_ANSI_PRODUCT_ID 0x020E
> #define FOUNTAIN_ISO_PRODUCT_ID 0x020F
> -
> #define FOUNTAIN_TP_ONLY_PRODUCT_ID 0x030A
>
> #define GEYSER1_TP_ONLY_PRODUCT_ID 0x030B
>
> -#define GEYSER_ANSI_PRODUCT_ID 0x0214
> -#define GEYSER_ISO_PRODUCT_ID 0x0215
> -#define GEYSER_JIS_PRODUCT_ID 0x0216
> +/* PowerBooks Oct 2005 */
> +#define GEYSER2_ANSI_PRODUCT_ID 0x0214
> +#define GEYSER2_ISO_PRODUCT_ID 0x0215
> +#define GEYSER2_JIS_PRODUCT_ID 0x0216
>
> /* MacBook devices */
> #define GEYSER3_ANSI_PRODUCT_ID 0x0217
> @@ -58,9 +61,14 @@
> * Geyser IV: same as Geyser III according to Info.plist in AppleUSBTrackpad.kext
> * -> same IOClass (AppleUSBGrIIITrackpad), same acceleration tables
> */
> -#define GEYSER4_ANSI_PRODUCT_ID 0x021A
> -#define GEYSER4_ISO_PRODUCT_ID 0x021B
> -#define GEYSER4_JIS_PRODUCT_ID 0x021C
> +#define GEYSER4_ANSI_PRODUCT_ID 0x021A
> +#define GEYSER4_ISO_PRODUCT_ID 0x021B
> +#define GEYSER4_JIS_PRODUCT_ID 0x021C
> +
> +/* Macbook3,1 devices */
> +#define GEYSER4_HF_ANSI_PRODUCT_ID 0x0229
> +#define GEYSER4_HF_ISO_PRODUCT_ID 0x022A
> +#define GEYSER4_HF_JIS_PRODUCT_ID 0x022B
>
> #define ATP_DEVICE(prod) \
> .match_flags = USB_DEVICE_ID_MATCH_DEVICE | \
> @@ -73,15 +81,17 @@
>
> /* table of devices that work with this driver */
> static struct usb_device_id atp_table [] = {
> +
> + /* PowerBooks Feb 2005, iBooks G4 */
> { ATP_DEVICE(FOUNTAIN_ANSI_PRODUCT_ID) },
> { ATP_DEVICE(FOUNTAIN_ISO_PRODUCT_ID) },
> { ATP_DEVICE(FOUNTAIN_TP_ONLY_PRODUCT_ID) },
> { ATP_DEVICE(GEYSER1_TP_ONLY_PRODUCT_ID) },
>
> /* PowerBooks Oct 2005 */
> - { ATP_DEVICE(GEYSER_ANSI_PRODUCT_ID) },
> - { ATP_DEVICE(GEYSER_ISO_PRODUCT_ID) },
> - { ATP_DEVICE(GEYSER_JIS_PRODUCT_ID) },
> + { ATP_DEVICE(GEYSER2_ANSI_PRODUCT_ID) },
> + { ATP_DEVICE(GEYSER2_ISO_PRODUCT_ID) },
> + { ATP_DEVICE(GEYSER2_JIS_PRODUCT_ID) },
>
> /* Core Duo MacBook & MacBook Pro */
> { ATP_DEVICE(GEYSER3_ANSI_PRODUCT_ID) },
> @@ -93,6 +103,11 @@
> { ATP_DEVICE(GEYSER4_ISO_PRODUCT_ID) },
> { ATP_DEVICE(GEYSER4_JIS_PRODUCT_ID) },
>
> + /* Core2 Duo MacBook3,1 */
> + { ATP_DEVICE(GEYSER4_HF_ANSI_PRODUCT_ID) },
> + { ATP_DEVICE(GEYSER4_HF_ISO_PRODUCT_ID) },
> + { ATP_DEVICE(GEYSER4_HF_JIS_PRODUCT_ID) },
> +
> /* Terminating entry */
> { }
> };
> @@ -136,12 +151,21 @@
> #define ATP_GEYSER_MODE_REQUEST_INDEX 0
> #define ATP_GEYSER_MODE_VENDOR_VALUE 0x04
>
> +/*
> + * Meaning of the status bits (only Geyser 3/4?)
> + */
> +#define ATP_STATUS_BIT_BUTTON 0x01 /* The button was pressed */
> +#define ATP_STATUS_BIT_UNKNOWN1 0x02 /* Unknown or unused */
> +#define ATP_STATUS_BIT_BASE_UPDATE 0x04 /* Update of the base values (untouched pad) */
> +#define ATP_STATUS_BIT_UNKNOWN2 0x08 /* Unknown or unused */
> +#define ATP_STATUS_BIT_FROM_RESET 0x10 /* Reset previously performed */
> +
> /* Structure to hold all of our device specific stuff */
> struct atp {
> char phys[64];
> struct usb_device * udev; /* usb device */
> struct urb * urb; /* usb request block */
> - signed char * data; /* transferred data */
> + u8 * data; /* transferred data */
> struct input_dev * input; /* input dev */
> unsigned char open; /* non-zero if opened */
> unsigned char valid; /* are the sensors valid ? */
> @@ -156,8 +180,8 @@
> /* accumulated sensors */
> int xy_acc[ATP_XSENSORS + ATP_YSENSORS];
> int datalen; /* size of an USB urb transfer */
> - int idlecount; /* number of empty packets */
> - struct work_struct work;
> + int idle_counter; /* number of empty packets */
> + struct work_struct work; /* kernel workqueue entry (for re-init) */
> };
>
> #define dbg_dump(msg, tab) \
> @@ -174,8 +198,12 @@
> if (debug) printk(KERN_DEBUG format, ##a); \
> } while (0)
>
> -MODULE_AUTHOR("Johannes Berg, Stelian Pop, Frank Arnold, Michael Hanselmann");
> -MODULE_DESCRIPTION("Apple PowerBooks USB touchpad driver");
> +MODULE_AUTHOR("Johannes Berg");
> +MODULE_AUTHOR("Stelian Pop");
> +MODULE_AUTHOR("Frank Arnold");
> +MODULE_AUTHOR("Michael Hanselmann");
> +MODULE_AUTHOR("Sven Anders");
> +MODULE_DESCRIPTION("Apple PowerBook and MacBook USB touchpad driver");
> MODULE_LICENSE("GPL");
>
> /*
> @@ -185,7 +213,7 @@
> module_param(threshold, int, 0644);
> MODULE_PARM_DESC(threshold, "Discards any change in data from a sensor (trackpad has hundreds of these sensors) less than this value");
>
> -static int debug = 1;
> +static int debug;
> module_param(debug, int, 0644);
> MODULE_PARM_DESC(debug, "Activate debugging output");
>
> @@ -203,12 +231,12 @@
> {
> u16 productId = le16_to_cpu(dev->udev->descriptor.idProduct);
>
> - return (productId == GEYSER_ANSI_PRODUCT_ID) ||
> - (productId == GEYSER_ISO_PRODUCT_ID) ||
> - (productId == GEYSER_JIS_PRODUCT_ID);
> + return (productId == GEYSER2_ANSI_PRODUCT_ID) ||
> + (productId == GEYSER2_ISO_PRODUCT_ID) ||
> + (productId == GEYSER2_JIS_PRODUCT_ID);
> }
>
> -static inline int atp_is_geyser_3(struct atp *dev)
> +static inline int atp_is_geyser_3_4(struct atp *dev)
> {
> u16 productId = le16_to_cpu(dev->udev->descriptor.idProduct);
>
> @@ -217,7 +245,10 @@
> (productId == GEYSER3_JIS_PRODUCT_ID) ||
> (productId == GEYSER4_ANSI_PRODUCT_ID) ||
> (productId == GEYSER4_ISO_PRODUCT_ID) ||
> - (productId == GEYSER4_JIS_PRODUCT_ID);
> + (productId == GEYSER4_JIS_PRODUCT_ID) ||
> + (productId == GEYSER4_HF_ANSI_PRODUCT_ID) ||
> + (productId == GEYSER4_HF_ISO_PRODUCT_ID) ||
> + (productId == GEYSER4_HF_JIS_PRODUCT_ID);
> }
>
> /*
> @@ -229,7 +260,7 @@
> {
> char data[8];
> int size;
> -
> +
> size = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
> ATP_GEYSER_MODE_READ_REQUEST_ID,
> USB_DIR_IN | USB_TYPE_CLASS | USB_RECIP_INTERFACE,
> @@ -237,6 +268,13 @@
> ATP_GEYSER_MODE_REQUEST_INDEX, &data, 8, 5000);
>
> if (size != 8) {
> + if (debug)
> + {
> + int i;
> + printk("appletouch atp_geyser_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 Raw mode)");
> return -EIO;
> @@ -252,6 +290,13 @@
> ATP_GEYSER_MODE_REQUEST_INDEX, &data, 8, 5000);
>
> if (size != 8) {
> + if (debug)
> + {
> + int i;
> + printk("appletouch atp_geyser_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 Raw mode)");
> return -EIO;
> @@ -269,8 +314,7 @@
> struct usb_device *udev = dev->udev;
> int retval;
>
> - dev->idlecount = 0;
> -
> + dprintk("appletouch: putting appletouch to sleep (reinit)\n");
> atp_geyser_init(udev);
>
> retval = usb_submit_urb(dev->urb, GFP_ATOMIC);
> @@ -385,7 +429,7 @@
> }
>
> /* reorder the sensors values */
> - if (atp_is_geyser_3(dev)) {
> + if (atp_is_geyser_3_4(dev)) {
> memset(dev->xy_cur, 0, sizeof(dev->xy_cur));
>
> /*
> @@ -442,13 +486,20 @@
> dbg_dump("sample", dev->xy_cur);
>
> if (!dev->valid) {
> - /* first sample */
> + /* first sample after init or resume */
> dev->valid = 1;
> dev->x_old = dev->y_old = -1;
> memcpy(dev->xy_old, dev->xy_cur, sizeof(dev->xy_old));
> + dev->idle_counter = 0;
> +
> + /* store first sample on older Geyser */
> + if ((dev->data[dev->datalen-1] & ATP_STATUS_BIT_BASE_UPDATE) ||
> + !atp_is_geyser_3_4(dev))
> + memcpy(dev->xy_old, dev->xy_cur, sizeof(dev->xy_old));
> +
>
> if (dev->size_detect_done ||
> - atp_is_geyser_3(dev)) /* No 17" Macbooks (yet) */
> + atp_is_geyser_3_4(dev)) /* No 17" Macbooks (yet) */
> goto exit;
>
> /* 17" Powerbooks have extra X sensors */
> @@ -474,26 +525,47 @@
> goto exit;
> }
>
> + /* Just update the base values (i.e. touchpad in untouched state) */
> + if (dev->data[dev->datalen-1] & ATP_STATUS_BIT_BASE_UPDATE)
> + {
> + if (debug > 0) printk("appletouch: updated base values\n");
> +
> + memcpy(dev->xy_old, dev->xy_cur, sizeof(dev->xy_old));
> + goto exit;
> + }
> +
> for (i = 0; i < ATP_XSENSORS + ATP_YSENSORS; i++) {
> - /* accumulate the change */
> - signed char change = dev->xy_old[i] - dev->xy_cur[i];
> - dev->xy_acc[i] -= change;
> + /* calculate the change */
> + dev->xy_acc[i] = dev->xy_cur[i] - dev->xy_old[i];
> +
> + /* this is a round-robin value, so couple with that */
> + if (dev->xy_acc[i] > 127)
> + dev->xy_acc[i] -= 256;
> +
> + if (dev->xy_acc[i] < -127)
> + dev->xy_acc[i] += 256;
> +
> + /* Needed for the older Geyser */
> + if (!atp_is_geyser_3_4(dev))
> + {
> + /* store new 'untouched' value, if any new */
> + if (dev->xy_acc[i] < -1)
> + dev->xy_old[i] = dev->xy_cur[i];
> + }
>
> /* prevent down drifting */
> if (dev->xy_acc[i] < 0)
> dev->xy_acc[i] = 0;
> }
>
> - memcpy(dev->xy_old, dev->xy_cur, sizeof(dev->xy_old));
> -
> dbg_dump("accumulator", dev->xy_acc);
>
> x = atp_calculate_abs(dev->xy_acc, ATP_XSENSORS,
> ATP_XFACT, &x_z, &x_f);
> y = atp_calculate_abs(dev->xy_acc + ATP_XSENSORS, ATP_YSENSORS,
> ATP_YFACT, &y_z, &y_f);
> - key = dev->data[dev->datalen - 1] & 1;
> -
> + key = dev->data[dev->datalen - 1] & ATP_STATUS_BIT_BUTTON;
> +
> if (x && y) {
> if (dev->x_old != -1) {
> x = (dev->x_old * 3 + x) >> 2;
> @@ -538,16 +610,28 @@
> * work on Fountain touchpads.
> */
> if (!atp_is_fountain(dev)) {
> +
> + /* Button must not be pressed when entering suspend,
> + otherwise we will never release the button. */
> if (!x && !y && !key) {
> - dev->idlecount++;
> - if (dev->idlecount == 10) {
> - dev->valid = 0;
> +
> + /* Idle counter */
> + dev->idle_counter++;
> +
> + /* Wait for 10 more packages before suspending */
> + if (dev->idle_counter > 10) {
> +
> + /* Reset counter */
> + dev->idle_counter = 0;
> +
> + /* Prepare for device reset */
> schedule_work(&dev->work);
> +
> /* Don't resubmit urb here, wait for reinit */
> return;
> }
> } else
> - dev->idlecount = 0;
> + dev->idle_counter = 0;
> }
>
> exit:
> @@ -615,7 +699,7 @@
> dev->udev = udev;
> dev->input = input_dev;
> dev->overflowwarn = 0;
> - if (atp_is_geyser_3(dev))
> + if (atp_is_geyser_3_4(dev))
> dev->datalen = 64;
> else if (atp_is_geyser_2(dev))
> dev->datalen = 64;
> @@ -658,7 +742,7 @@
>
> set_bit(EV_ABS, input_dev->evbit);
>
> - if (atp_is_geyser_3(dev)) {
> + if (atp_is_geyser_3_4(dev)) {
> /*
> * MacBook have 20 X sensors, 10 Y sensors
> */
> @@ -701,6 +785,7 @@
> /* save our data pointer in this interface device */
> usb_set_intfdata(iface, dev);
>
> + /* initialize kernel work queue for re-init out of interrupt context */
> INIT_WORK(&dev->work, atp_reinit);
>
> return 0;
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ Mactel-linux-devel mailing list Mac...@li... https://lists.sourceforge.net/lists/listinfo/mactel-linux-devel
|
|
From: Scott D. D. <da...@4p...> - 2008-03-11 22:45:25
|
>From: David Elliott <df...@tg...> >To: "Scott D. Davilla" <da...@4p...> >Subject: Re: darwin and friends >Date: Tue, 11 Mar 2008 14:46:07 -0400 > >Hi Scott, > >I suspect you are looking in IODeviceTree:/options and/or looking at >the NVRAM directly. That, as you have found out, is the blessed >device not the one that actually booted. > >The one that actually booted is found in IODeviceTree:/chosen and >the key you want from that device tree node is most likely >boot-device-path which appears to be an EFI binary device path. >Somewhere here I've got a program I wrote to decode >device-properties from IODeviceTree:/efi because at the time >Netkas's boot loader was including this blob for different machines >to make the graphics work. I wondered what exactly was in there. >Since then someone else wrote a decoder but I've never released mine >since I don't particularly agree with filling in this info at the >bootloader level when it can be done just as well in a kext (see >Titan/Natit which have existed for quite a while). > >As it turns out, I didn't find what I was looking for in >device-properties which was to see if this same scheme was used for >other pieces of hardware. It is, but at least on the dumps I've >processed it appears that it's mostly the graphics card and then the >overall system volume (which is how the machine knows how loud to >chime at startup). > >So nothing came of it other than writing a decoder for the binary >format which necessarily includes a decoder for EFI device paths. >Unfortunately I can't find the code at the moment and it wouldn't be >of too much use to you anyway other than to know which header files >to look through in TianoCore to find the device path structures. >Decoding them is fairly trivial if you just read the comments in >those headers. > >But I suppose that if you've already determined that the NVRAM >contains the blessed boot device then you probably already know how >to decode it so you can actually read it. So hopefully knowing that >the real boot device is in IODeviceTree:/chosen should be enough. > >Also do you have any sort of public mailing list for your project? >If so please forward this message to it so that others may benefit. > >-Dave > > >On Mar 11, 2008, at 3:00 PM, Scott D. Davilla wrote: > >>Nice stuff; >> >> Quick question, I' working on an AppleTV bootloader that >>makes it much easier to boot Linux and friends. The AppleTV is >>special, pure EFI, no BIOS and efi firmware will only load a signed >>boot.efi so using other efi bootloaders are not possible. We get >>around that by creating a fake mach_kernel that is a secondary >>bootloader which does the actual boot of Linux. I've extended the >>original work to convert EFI memmaps into e820 memmap and relocate >>ACPI and SMBIOS table pointers to where Linux can find them. This >>and the standard vesafb as a linear framebuffer lets me boot >>non-efi unpatched linux kernels. This all works great and I'm >>moving into auto boot by searching for the various linux boot confs >>(grub, syslinux, etc), extracting the boot params and then using >>kexec to boot the real kernel. >> >> So the question, I'd like to know which device I was booted >>from at the bootloader level. It's a swing point on the initial >>search patch for the real kernel. So this is at entry into a mach >>kernel. I've got the passed boot params and limited EFI info (EFI >>is gone at this point). It there are way to retrieve the boot >>device info. boot.efi knows it as I can see it as the fake mach >>kernel loads, but is this information present somewhere that can be >>assessed. EFI vars will only contain the blessed boot device not >>the real boot device (USB pen for example). >> >> Any information you can point me to would be appreciated. I >>have grep'd xnu source but I have not found anything using this >>type of info. >> >>Thanks >>Scott -- ----------------------------------------------------------------------- Scott D. Davilla Phone: 919 489-1757 ext 13 (tel) 4pi Analysis, Inc. Fax: 919 489-1487 (fax) 3500 Westgate Drive, Suite 403 email: da...@4p... Durham, North Carolina 27707-2534 web: http://www.4pi.com |
|
From: Sven A. <an...@an...> - 2008-03-10 11:52:09
|
Hello!
The is an update of the appletouch, which fixes one wrong Product-ID.
It also replaces the "appletouch-add-macbook3-trackpad.patch" patch.
Please update the SVN...
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: Dr. Thomas Träger
|
|
From: gimli <gi...@da...> - 2008-03-03 08:03:34
|
Hi, updated status on the MacBookAir1,1 : pommed 1.16 adds proper support for the MacbOkkAir1,1 kernel hid patch updated with the missing usb ids happy penguin Edgar (gimli) Hucek |
|
From: gimli <gi...@da...> - 2008-02-29 09:36:22
|
Hi, the trackpad is not supported by the appletouchpad driver. i use the stock in kernel hid driver for it. happy penguin Edgar (gimli) Hucek > > also, does the new trackpad work OK? is it jumpy or anything? > > does it do anything weird when you move more than one finger across it? > > i would like to play with the driver when I get one to see if > multi-touch can be taken advantage of very easily... > > On Thu, 2008-02-28 at 22:32 +0100, gimli wrote: >> Hi, >> >> my status report on the Macbook Air : >> Installed Ubuntu gutsy with kernel 2.6.24.3 and mactel patches >> WLAN work with ndiswrapper >> Bluetooth work >> Speedstep work >> Suspen/Resume work >> 3D acceleration work >> Applesmc partialy work >> Sound works with the mbp3 option >> Display backlight work with a pommed patch. >> >> happy penguin >> >> Edgar /gimli) Hucek >> >> > James Vautin a dit: >> >> There are some hints someone has Ubuntu running: >> >> >> >> http://www.flickr.com/photos/isriya/2265405622/ >> >> >> >> http://www.flickr.com/photos/isriya/2264613881/ >> >> >> >> but not much more than that. I'm going to try to get in touch with >> >> this guy. >> > >> > Please report back here - I'd definitely like to know as well! >> > >> > Cheers, >> > >> > -- >> > mike dentifrice <fl...@po...> >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > 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 >> > >> > >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> 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: gimli <gi...@da...> - 2008-02-29 09:33:26
|
------------------------ Ursprüngliche Nachricht ------------------------- Betreff: Macbook Air updated pommed patch Von: "gimli" <gi...@da...> Datum: Fr, 29.02.2008, 10:18 An: "Jeffrey Gardner" <je...@ge...> Cc: gi...@da... -------------------------------------------------------------------------- Hi, attached you find an updated patch for pommed. the added usbid is for my german keyboard. happy penguin Edgar (gimli) Hucek > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > gimli wrote: > > | Display backlight work with a pommed patch. > > Hello gimli, > May I ask what pommed patch you used, and which version of pommed you're > using? > > Thanks, > je_fro > > - -- > Jeffrey Gardner > Gentoo Developer > Public PGP Key ID: 4A5D8F23 > hkp://pgpkeys.mit.edu > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHx15liR2KxEpdjyMRAicJAKCpJZCUThnVNF5CV16+tF1HwipBegCeOs7r > QV2WReG6SnDbmL/xoiMOB4c= > =tI/w > -----END PGP SIGNATURE----- > > > |
|
From: gimli <gi...@da...> - 2008-02-24 20:03:30
|
Indeed, my patch is wrong ;)
> gimli wrote:
>> Attached is a patch for the debian pommed unstable package.
>
> This section of the patch is incorrect:
>
> diff -uNr pommed-1.15~dfsg/pommed/evdev.c
> pommed-1.15~dfsg.macbookair/pommed/evdev.c
> --- pommed-1.15~dfsg/pommed/evdev.c 2007-12-07 13:39:59.000000000 +0100
> +++ pommed-1.15~dfsg.macbookair/pommed/evdev.c 2008-02-24
> 11:52:17.000000000 +0100
> @@ -608,7 +608,8 @@
>
> if ((product == USB_PRODUCT_ID_GEYSER4HF_ANSI)
> || (product == USB_PRODUCT_ID_GEYSER4HF_ISO)
> - || (product == USB_PRODUCT_ID_GEYSER4HF_JIS))
> + || (product == USB_PRODUCT_ID_GEYSER4HF_JIS)
> + || USB_PRODUCT_ID_GEYSER5HF_ANSI)
> {
> logdebug(" -> Geyser IV-HF USB keyboard\n");
>
>
> It should be:
>
> diff -uNr pommed-1.15~dfsg/pommed/evdev.c
> pommed-1.15~dfsg.macbookair/pommed/evdev.c
> --- pommed-1.15~dfsg/pommed/evdev.c 2007-12-07 13:39:59.000000000 +0100
> +++ pommed-1.15~dfsg.macbookair/pommed/evdev.c 2008-02-24
> 11:52:17.000000000 +0100
> @@ -608,7 +608,8 @@
>
> if ((product == USB_PRODUCT_ID_GEYSER4HF_ANSI)
> || (product == USB_PRODUCT_ID_GEYSER4HF_ISO)
> - || (product == USB_PRODUCT_ID_GEYSER4HF_JIS))
> + || (product == USB_PRODUCT_ID_GEYSER4HF_JIS)
> + || (product == USB_PRODUCT_ID_GEYSER5HF_ANSI))
> {
> logdebug(" -> Geyser IV-HF USB keyboard\n");
>
>
> -- Jay
> --
> Jay Schuster <ja...@pc...> The Physician's Computer Company
>
>
>
|
|
From: gimli <gi...@da...> - 2008-02-24 11:27:01
|
Hi, some progress report for linux on MacbookAir1,1. I run ubuntu gutsy on it. Basic HID keyboard support is in svn. At least it works with my german keyboard ;) Wlan should work with ndiswrapper and this windows driver : http://www.versiontracker.com/dyn/moreinfo/win/151020. The filename is sp37950.exe which contains the Broadcom drivers in version 4.170.25.12. The driver gets loaded and i see a wlan interface. Have no AP here to test it. Sound works with "modprobe snd-hda-intel model=mbp3". Suspend/Resume works out of the box. Bluetooth is detected. I have no clue how to make applesmc and appletouch work corectly. Attached is a patch for the debian pommed unstable package. Last but not least a lspci output ;) 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 02:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 05) As allways, happy penguin Edgar (gimli) Hucek |
|
From: Scott D. D. <da...@4p...> - 2008-02-21 22:17:52
|
>On Wed, 20 Feb 2008 04:01:40 pm Scott D. Davilla wrote:
>> I think I've resolved the hang/green video corruption under xvmc
>> decode of 1080i mpeg2 content with the AppleTV.
>>
>> enable Coolbit is xorg.config then;
>>
>> nvidia-settings -a GPUOverclockingState=1
>> nvidia-settings -a GPU2DClockFreqs=200,800
>
>Could you please post your xorg.conf file?
This is my testing config, it's setup right now for HD480i over
component which is my development tv. Outputing to a real HDTV over
component or hdmi makes no difference. For hdmi, replace "TV-0" with
"CRT-0" and comment out the option "TVOutFormat".
__________________________xorg.config--------------------
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Thu Oct 4
10:33:51 PDT 2007
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
RgbPath "/usr/lib/X11/rgb"
EndSection
Section "Module"
Load "glx"
Load "dbe"
Load "extmod"
#Load "fbdevhw"
#Load "record"
Load "freetype"
Load "type1"
EndSection
Section "ServerFlags"
Option "blank time" "0"
Option "standby time" "0"
Option "suspend time" "0"
Option "off time" "0"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
#Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
#Option "DPMS"
Option "DPMS" "false"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
EndSection
Section "Device"
Option "NvAGP" "0"
Option "RenderAccel" "true"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Option "UseEDID" "FALSE"
Option "TVStandard" "HD480i"
Option "metamodes" "TV-0: 720x480 +0+0"
#--------------480p Group-----------------------------
#Option "TVStandard" "HD480p"
#Option "metamodes" "TV-0: 720x480 +0+0"
#--------------720p Group-----------------------------
#Option "TVStandard" "HD1080i"
#Option "metamodes" "TV-0: 1920x1080 +0+0"
#--------------1080p Group-----------------------------
#Option "TVStandard" "HD1080p"
#Option "metamodes" "TV-0: 1920x1080 +0+0"
#
#Option "XvmcUsesTextues" "True"
#Option "AddARGBVisuals" "True"
#Option "AddARGBGLXVisuals" "True"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "UseDisplayDevice" "TV-0"
Option "TVOverScan" "0.5"
Option "TVOutFormat" "COMPONENT"
#--------------480i Group-----------------------------
#Option "TVStandard" "HD720p"
#Option "metamodes" "TV-0: 1280x720 +0+0"
#--------------1080i Group-----------------------------
#Option "ConnectToAcpid" "False"
Option "EnableACPIHotkeys" "False"
Option "UseEvents" "True"
Option "Coolbits" "1"
Option "DPI" "100x100"
#Option "TripleBuffer" "True"
#Option "DynamicTwinView" "False"
SubSection "Display"
Depth 24
Modes "1920x1080" "1280x720" "1024x768" "720x480" "640x480"
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
|
|
From: Daniel R. F. <da...@el...> - 2008-02-21 01:55:42
|
On Wed, 20 Feb 2008 04:01:40 pm Scott D. Davilla wrote: > I think I've resolved the hang/green video corruption under xvmc > decode of 1080i mpeg2 content with the AppleTV. > > enable Coolbit is xorg.config then; > > nvidia-settings -a GPUOverclockingState=1 > nvidia-settings -a GPU2DClockFreqs=200,800 Could you please post your xorg.conf file? Thanks - Daniel -- ************************************************************************* * Daniel Franklin - Lecturer in Computer Engineering * University of Wollongong, NSW, Australia * d.f...@ie... ************************************************************************* |
|
From: Scott D. D. <da...@4p...> - 2008-02-20 05:02:01
|
I think I've resolved the hang/green video corruption under xvmc decode of 1080i mpeg2 content with the AppleTV. enable Coolbit is xorg.config then; nvidia-settings -a GPUOverclockingState=1 nvidia-settings -a GPU2DClockFreqs=200,800 This underclocks the gpu and overclocks the vram for 2D which is what xvmc uses. Glitches are gone for both mplayer and myth (both of which use ffmpeg). I've had mplayer running for over 12 hours continuous doing xvmc 1080i mpeg2 decode and it's still going strong. Underclocking the gpu from 360MHz to 200MHz is primary. I've overclocked the vram from 720MHz to 800MHz as xvmc decode seems more sensitive to this parameter. I don't notice any differences in decode performance by underclocking the gpu. Scott |
|
From: Florian K. <fl...@gm...> - 2008-02-12 07:52:38
|
Hello! Any chance of getting this into the mactel-patchset for kernel 2.6.24 or into 2.6.25? -- florian Chris Irwin wrote: > This is a followup to Martin Szulecki post on 2007-10-22 with the apple > aluminum keyboard patch. > > I have updated the patch with the keycodes for the macbook3,1 (the new > "Santa Rosa" one), as well as a few keycodes that were handy and present > on the "powerbook" keyboard, such as delete, pgup/down, and home/end. > > Thanks Martin for posting the patch, I would not have known where to > start otherwise. > > Also sorry for not replying to the thread in progress, but I just > subscribed to this list. > > |
|
From: Jean-Baka Domelevo-E. <dom...@gm...> - 2008-02-08 08:36:32
|
Hi, I have a MacBook Pro C2C (Santa Rosa, bought durins last october), and I have the same floodings of messages from applesmc : "wait status failed", with alternatively "5 != 50" (flood), "c != 58" or "5 != 54" (sporadic). This occurs with both kernels 2.6.23-9 and 2.6.24-git13, both patched with mactel. And also: my machine sometimes halts suddenly (powering off without any warning). it occurs at moments when fans run at their highest speed, without any reason (I'm not using the CPU). Thanks for any answer. On Feb 8, 2008 6:19 AM, Lucas C. Villa Real <lu...@go...> wrote: > Hi, > > I'm setting up my MacBook and it seems like applesmc.ko can't get the > expected values from __wait_status(). After being flooded by a few > messages like this, the driver decides to ignore the accelerometer and > keeps going on: > > applesmc: wait status failed: c != 58 > applesmc: Cannot set motion sensor min/max norm parameters, might not > receive some interrupts. > applesmc: wait status failed: c != 58 > applesmc: wait status failed: c != 58 > > I'm just getting started to this hardware, so I have no clues about > the protocol and the like. Do you have some scripts (dtrace?) set to > aid in the reverse engineering of the Mac drivers or some pointers > that could help me fix this? > > Thanks a lot, > > -- > Lucas > powered by /dev/dsp > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mactel-linux-devel mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-devel > |
|
From: Lucas C. V. R. <lu...@go...> - 2008-02-08 06:44:51
|
I just realized that I sent this patch before. Sorry for the duplicate! On Feb 7, 2008 9:09 PM, Lucas C. Villa Real <lu...@go...> wrote: > Hi, > > This patch makes sure that apple_smc is unregistered at rmmod time > (that's necessary to reload the driver). > Diff against 2.6.24 vanilla. > > Cheers, > > -- > Lucas > powered by /dev/dsp > -- Lucas powered by /dev/dsp |
|
From: Lucas C. V. R. <lu...@go...> - 2008-02-08 05:19:09
|
Hi, I'm setting up my MacBook and it seems like applesmc.ko can't get the expected values from __wait_status(). After being flooded by a few messages like this, the driver decides to ignore the accelerometer and keeps going on: applesmc: wait status failed: c != 58 applesmc: Cannot set motion sensor min/max norm parameters, might not receive some interrupts. applesmc: wait status failed: c != 58 applesmc: wait status failed: c != 58 I'm just getting started to this hardware, so I have no clues about the protocol and the like. Do you have some scripts (dtrace?) set to aid in the reverse engineering of the Mac drivers or some pointers that could help me fix this? Thanks a lot, -- Lucas powered by /dev/dsp |
|
From: Lucas C. V. R. <lu...@go...> - 2008-02-08 05:09:18
|
Hi, This patch makes sure that apple_smc is unregistered at rmmod time (that's necessary to reload the driver). Diff against 2.6.24 vanilla. Cheers, -- Lucas powered by /dev/dsp |
71 messages has been excluded from this view by a project administrator.
