Re: [PATCH] Fix sleep/wakeup problems on iBook G3
Hi! < Le jeudi 31 mars 2005 ï 00:31:30 +0200 (CEST), Benjamin Herrenschmidt écrivit :> > Ok, I've updated the patch on gate. Try applying this on top of a fresh > kernel and tell me if that works: Tried on 2.6.11.6: Hunk #4 failed at 139 Do I can apply manually ? Jean-Paul Vincent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Accessing LogWatch via web
On Tue, 29 Mar 2005 22:03:53 +0100, Lee Braiden <[EMAIL PROTECTED]> wrote: > On Tuesday 29 March 2005 21:51, Mehul Sanghvi wrote: > > Does anyone know how to get LogWatch to create web based reports ? > > If I understand it > > You could filter it through a script via procmail or some other filter, use a > web-based email server, or just have it redirected to a remote email address. > > I think there are a few front-ends to logwatch though, and some of the larger > IDS systems support it too, if I recall correctly. > Actually what I was looking for was http://awstats.sourceforge.net/ which provides what I want mostly. cheers, mehul -- Mehul N. Sanghvi email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apple trackpad driver update
On Thu, 2005-03-31 at 08:35 +1000, Benjamin Herrenschmidt wrote: > > I've made a few updates today. Notable is the addition of yet another > > USB product ID for the 12" series and a fix for some trackpads that send > > 81 bytes in interrupt go as opposed to mine which sends 64 and 17 in two > > consecutive interrupts. > > Hrm ? Isn't 64 the max for an USB interrupt pipe ? Hm. Yes. (page 43 following of the USB 1.1 specs) There are two possibilities now: * Apple ignores that * behaviour difference between 2.6.10 (which he was using) and 2.6.11 (which I am using) But in the latter case, my driver still only allocates MAX(64,driver reported packet size) bytes for the buffer so I have no clue how that would work... johannes signature.asc Description: This is a digitally signed message part
Re: PowerPC's APM emulation dependant upon PMU feature?
> Unless you want to make it generic enough to apply to all > non-x86 systems, it's also not very worthwhile to put a ton > of effort into this. If you want that, it's probably better > to take the official APM driver and split it into a front > end (just the device node stuff) and a back end (hardware > interface) so that anyone can write a new back end. Well, the ARM folks did a good job at doing a more generic APM emulation, I'd rather go from their implementation if I had to do anything. > Any non-PMU Mac has only minimal power management. The cuda > based models have some stuff around scheduled powerup and > server mode and can reboot the box using a cuda command. Yes, but nothing that fits in the APM API anyway. > Older models can do poweroff and (in most cases) a clean > reset but not much else. > > I'm not sure what your goal is. Do you just want X to shutup > about not being able to open an APM device? > > Brad Boyer > [EMAIL PROTECTED] > > -- Benjamin Herrenschmidt <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
> I also want applications that expect to be able to interact with APM to > succeed at this. Why ? there is no APM, and there is nothing to tell them, afaik. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, 2005-03-30 at 19:49 +0300, Martin-Ãric Racine wrote: > On Wed, 30 Mar 2005, Johannes Berg wrote: > > > On Wed, 2005-03-30 at 15:40 +0300, Martin-Ãâric Racine wrote: > > > > > I wanted to enable the APM emulation to calm down XFree's warning about > > > the missing APM device, but I notice that it's currently dependant upon > > > the PMU support. Could this be changed into a generic platform option? > > > > Maybe I'm misunderstanding, but how should it then get at the relevant > > data to emulate APM? > > There are power management architectures predating PMU. Not on Macs, at least, not relevant here. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apple trackpad driver update
> Also: > (page 43) > All Host Controllers are required to have support for up to 64-byte > maximum data payload sizes for full-speed interrupt endpoints and eight > bytes or less maximum data payload sizes for low-speed interrupt > endpoints. No Host Controller is required to support larger maximum data > payload sizes. > > I'd read that as: "if the host controller does it it doesn't hurt to > try" I'm pretty sure they don't tho ... but I may be wrong. > Maybe I'll try compiling/installing his kernel version and testing my > driver with it. I'll be collecting some data and moving this to > linux-usb-devel. > > johannes -- Benjamin Herrenschmidt <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
POWER3 install CD
Hi, I was looking for a POWER3 debian install CD and came across the installer ports status page: http://www.debian.org/devel/debian-installer/ports-status It mentions these as working: powerpc IBM RS6000 power3 IBM RS6000 power4 IBM RS6000 It turns out these targets overlap with the next two: IBM pSeries IBM iseries Which are marked as unavailable. I also tried booting the CD image on a POWER3 box and it did not work. What options are used to build the ISO? Anton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apple trackpad driver update
On Thu, 2005-03-31 at 09:15 +1000, Benjamin Herrenschmidt wrote: Apple can't "ignore" that, it's simply not possible, > unless they actually send two packets and the USB stack itself is > coalescing them... I wouldn't be too sure about that, quoting the specs: (page 44) The bus frequency and frame timing limit the maximum number of successful interrupt transactions within a frame for any USB system to less than 108 full-speed one-byte data payloads or 14 low-speed one-byte data payloads. A Host Controller, for various implementation reasons, may not be able to provide the above maximum number of interrupt transactions per frame. (so 81 bytes fit since I think the kb/trackpad is connected via it's own controller -- which is really necessary even at 64 bytes/msec) Also: (page 43) All Host Controllers are required to have support for up to 64-byte maximum data payload sizes for full-speed interrupt endpoints and eight bytes or less maximum data payload sizes for low-speed interrupt endpoints. No Host Controller is required to support larger maximum data payload sizes. I'd read that as: "if the host controller does it it doesn't hurt to try" Maybe I'll try compiling/installing his kernel version and testing my driver with it. I'll be collecting some data and moving this to linux-usb-devel. johannes signature.asc Description: This is a digitally signed message part
Re: apple trackpad driver update
On Thu, 2005-03-31 at 00:50 +0200, Johannes Berg wrote: > On Thu, 2005-03-31 at 08:35 +1000, Benjamin Herrenschmidt wrote: > > > > I've made a few updates today. Notable is the addition of yet another > > > USB product ID for the 12" series and a fix for some trackpads that send > > > 81 bytes in interrupt go as opposed to mine which sends 64 and 17 in two > > > consecutive interrupts. > > > > Hrm ? Isn't 64 the max for an USB interrupt pipe ? > > Hm. Yes. (page 43 following of the USB 1.1 specs) > There are two possibilities now: > * Apple ignores that > * behaviour difference between 2.6.10 (which he was using) >and 2.6.11 (which I am using) > > But in the latter case, my driver still only allocates > MAX(64,driver reported packet size) > bytes for the buffer so I have no clue how that would work... It might be something with the USB stack, you should ask on the usb-devel list, Apple can't "ignore" that, it's simply not possible, unless they actually send two packets and the USB stack itself is coalescing them... Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apple trackpad driver update
On Wed, 2005-03-30 at 22:47 +0200, Johannes Berg wrote: > Hi, > > I've made a few updates today. Notable is the addition of yet another > USB product ID for the 12" series and a fix for some trackpads that send > 81 bytes in interrupt go as opposed to mine which sends 64 and 17 in two > consecutive interrupts. Hrm ? Isn't 64 the max for an USB interrupt pipe ? > I simply multiplex that the userspace driver now so anyone wanting to > hack should use that to start from (and probably not touch the main > routine) > > Have fun, > johannes -- Benjamin Herrenschmidt <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] sleep & cpufreq problems
On Tue, 2005-03-29 at 13:28 +1000, Benjamin Herrenschmidt wrote: > Hi ! > > Here are a couple of patches against current linus bk (one was already > posted to this list) that should fix a number issues related to sleep > and wakeup, especially in conjunction with cpufreq transitions. > > Please test and let me know if it fixes a problem you had, it adds a new > problem, or it has no effect, stuff still doesn't work (if it used to > work and still work, no need to bug me). > > Thanks ! > > Patches are at: > > http://gate.crashing.org/~benh/ppc32-pmac-sleep-fix.diff > http://gate.crashing.org/~benh/ppc32-cpufreq-gpio-off.diff Ok, I re-updated them, if you have sleep, cpufreq or both problems, try and let me know. THe first one should apply on 2.6.11, the second one applies only on top of current bk. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Fix sleep/wakeup problems on iBook G3
> kernel 2.6.11.5 (test #3 at the end of mail) > > Test 1 (patch and first change) : the ibook wakes up. But... > > ~$ sudo reboot > Erreur de segmentation Ok, I've updated the patch on gate. Try applying this on top of a fresh kernel and tell me if that works: http://gate.crashing.org/~benh/ppc32-pmac-sleep-fix.diff Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, 2005-03-30 at 15:40 +0300, Martin-Éric Racine wrote: > Hello Ben, > > I wanted to enable the APM emulation to calm down XFree's warning about > the missing APM device, but I notice that it's currently dependant upon > the PMU support. Could this be changed into a generic platform option? No. APM emulation is entirely built on top of the PMU driver. XFree is complaining in it's log but that's harmless, it does so for every ACPI (non-APM) x86 machine too :) Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd 0.6.8beta1 has been released for testing
Matthias Grimm <[EMAIL PROTECTED]> wrote: > On Fri, 25 Mar 2005 15:35:11 + (UTC) > Joerg Sommer <[EMAIL PROTECTED]> wrote: > >> Matthias Grimm <[EMAIL PROTECTED]> wrote: >> > >> > Hi, >> > >> > As consequence of the high number of critical bugs in the last release I >> > publish a beta release first this time: >> > >> > PBButtonsd 0.6.8beta1 >> > available at: http://pbbuttons.sourceforge.net >> >> I've build it and started it (not installed), but the touchpad suspend >> doesn't work. I can type and use the touchpas. How to enable this new >> feature? > > In this beta realease the function is always enabled. To track if the trackpad > tap is currently en- or disabled, you could compile with --enable-debug. > > The tapping is only disabled for 0.6 seconds and key repetition is not > covered. > Only normal key strokes will disable trackpad tapping. To continously disable > the tapping you need constant typing. Pressing one single key for a while is > not the same. This was how I tested it. Now I hit a key many times and the trackpad doesn't work. The feature works for at me. Now I will see if it work in practice. I hat it to type a text and the cursor jumps away. Jörg. BTW: I use the pbbuttonsd from experimental -- no problems -- Damit das Mögliche entsteht, muß immer wieder das Unmögliche versucht werden. (Hermann Hesse) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apple trackpad driver update
On Wed, 2005-03-30 at 22:59 +0200, Antonio-M. Corbi Bellot wrote: > 1) The device created user/group are root:root, I suppose that once this > gets into a driver-only code this will not matter. I am not sure the driver has any influence on that. You can instruct udev to give it other permissions. > 2) The mouse movement is a bit jerky, and in some times it moves > alone :), but you mentioned a bit of this before. Yes, this is because my driver.c program is really simple. I encourage you to find better algorithms, I haven't really had time to look for something better yet. johannes signature.asc Description: This is a digitally signed message part
Re: apple trackpad driver update
El mié, 30-03-2005 a las 22:47 +0200, Johannes Berg escribió: > I've made a few updates today. Notable is the addition of yet another > USB product ID for the 12" series and a fix for some trackpads that send > 81 bytes in interrupt go as opposed to mine which sends 64 and 17 in two > consecutive interrupts. Hi Johannes: Saw your mail with the patch you sent me just minutes before this last update, so I downloaded the update (up to and including patch 14) and now the trackpad works on the 12", thanks a lot! Only two things I've noticed: 1) The device created user/group are root:root, I suppose that once this gets into a driver-only code this will not matter. 2) The mouse movement is a bit jerky, and in some times it moves alone :), but you mentioned a bit of this before. Antonio Corbi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apple trackpad driver update
Hi, I've made a few updates today. Notable is the addition of yet another USB product ID for the 12" series and a fix for some trackpads that send 81 bytes in interrupt go as opposed to mine which sends 64 and 17 in two consecutive interrupts. I simply multiplex that the userspace driver now so anyone wanting to hack should use that to start from (and probably not touch the main routine) Have fun, johannes signature.asc Description: This is a digitally signed message part
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, 30 Mar 2005, Brad Boyer wrote: > On Wed, Mar 30, 2005 at 07:49:06PM +0300, Martin-?ric Racine wrote: > > On Wed, 30 Mar 2005, Johannes Berg wrote: > > > Maybe I'm misunderstanding, but how should it then get at the relevant > > > data to emulate APM? > > > > There are power management architectures predating PMU. > > While that is true, the current version of apm_emu.c is heavily > dependent on via-pmu.c. It would be nice to make it a little > more generic so that the features that can be used on other > models could be exposed. That's a fair amount of work. > Any non-PMU Mac has only minimal power management. The cuda > based models have some stuff around scheduled powerup and > server mode and can reboot the box using a cuda command. This iMac CRT indeed is a CUDA box. It does poweroffs; I'm not sure what else it is capable of. > I'm not sure what your goal is. Do you just want X to shutup > about not being able to open an APM device? I also want applications that expect to be able to interact with APM to succeed at this. -- Martin-Éric Racine http://www.iki.fi/q-funk/
Re: pbbutons wont put my PB to sleep
On Wed, 30 Mar 2005, Matthias Grimm wrote: Please check out the configuration file. There is an option that tells pbbuttonsd what to to when the lid has been closed. It's named onAC_CoverAction and onBattery_CoverAction. See man pbbuttonsd.conf for detailed description. I have checked that, and the action is suspend-to-ram... I also tried suspend-to-disk with same results... Best Regards Matthias regards, -- Rolando Abarca M. [EMAIL PROTECTED] "Tam pro papa quam pro rege bibunt omnes sine lege." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
booting from USB/Firewire
Hi all, I have been following the list for a while and would like to try debian on my Powerbook G4. My internal HD is partitioned as when I bought it (one big HFS+ partition) and I don't want to repartition it at the moment (real estate is too expensive on the internal hard drive). So I am thinking of acquiring a Firewire/USB external HD to put debian on. Looking at the archives of the list, I see nothing very encouraging, though there are no recent posts on the subject. Does anyone have a success story of booting from such a device? Or links to useful info? Thanks. -- Arnaud -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: BLK_DEV_IDEDMA_PMAC && !BLK_DEV_IDEPCI
On Mar 29, 2005, at 11:12 PM, Benjamin Herrenschmidt wrote: On Tue, 2005-03-29 at 23:06 -0800, [EMAIL PROTECTED] wrote: Unfortunately I dunno in which direction to proceed - I dunno whether BLK_DEV_IDEDMA_PMAC should build without BLK_DEV_IDEPCI, or whether it's a problem with Kconfig - thanks for any help! ide pmac shares code with the normal PCI DMA driver and thus requires BLK_DEV_IDEPCI. It's a bug in Kconfig not to show that dependency. Cool - many thanks for your help, Ben! Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, Mar 30, 2005 at 07:49:06PM +0300, Martin-?ric Racine wrote: > On Wed, 30 Mar 2005, Johannes Berg wrote: > > Maybe I'm misunderstanding, but how should it then get at the relevant > > data to emulate APM? > > There are power management architectures predating PMU. While that is true, the current version of apm_emu.c is heavily dependent on via-pmu.c. It would be nice to make it a little more generic so that the features that can be used on other models could be exposed. That's a fair amount of work. Unless you want to make it generic enough to apply to all non-x86 systems, it's also not very worthwhile to put a ton of effort into this. If you want that, it's probably better to take the official APM driver and split it into a front end (just the device node stuff) and a back end (hardware interface) so that anyone can write a new back end. Any non-PMU Mac has only minimal power management. The cuda based models have some stuff around scheduled powerup and server mode and can reboot the box using a cuda command. Older models can do poweroff and (in most cases) a clean reset but not much else. I'm not sure what your goal is. Do you just want X to shutup about not being able to open an APM device? Brad Boyer [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, 30 Mar 2005, Johannes Berg wrote: > On Wed, 2005-03-30 at 15:40 +0300, Martin-Ãric Racine wrote: > > > I wanted to enable the APM emulation to calm down XFree's warning about > > the missing APM device, but I notice that it's currently dependant upon > > the PMU support. Could this be changed into a generic platform option? > > Maybe I'm misunderstanding, but how should it then get at the relevant > data to emulate APM? There are power management architectures predating PMU. -- Martin-Éric Racine http://www.iki.fi/q-funk/
Re: Linux PPC Java development
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lee Braiden wrote: | On Tuesday 29 March 2005 21:03, Barry Hawkins wrote: | |>~Hello and welcome. If you would like, you can use the gcjwebplugin; |>that is about your only option for applets. | | | Marcellus: Just to give you an informed decision, the gcj plugin had SERIOUS | security issues last time I looked at it. | | (Is that still the case, Barry?) | Lee, ~I think you are right, though I must admit I do not follow it closely. Regards, - -- Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCSsZtHuKcDICy0QoRAm20AKCsIcJ/rp8ZEi2eqNtiWH+PMQR3cgCguwx+ ULk0niSGD0N1fkUA1LqhRIo= =wIz4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new powerbook touchpad
On Wed, 2005-03-30 at 17:10 +0200, Antonio-M. Corbi Bellot wrote:
>
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=05ac ProdID=030a Rev= 0.06
> S: Manufacturer=Apple Computer
> S: Product=Apple Internal Trackpad
> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 40mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=1ms
Is that all? Mine reads:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=05ac ProdID=020e Rev= 0.28
S: Manufacturer=Apple Computer
S: Product=Apple Internal Keyboard/Trackpad
C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr= 40mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=AppleTrackpad
E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=84(I) Atr=03(Int.) MxPS= 1 Ivl=10ms
I take it then your keyboard is not connected via USB. Well, try the
attached patch and test program (to compile just run 'make ,,test').
Then insmod the changed driver, and run the test program as follows:
./,,test > /tmp/dump
wait a few seconds, maybe press touchpad button a bit and move the
finger over the touchpad, kill the program with ctrl-c, bzip2 the file
and send it to me (privately please, not on list).
johannes
--- orig/appletrackpad.c
+++ mod/appletrackpad.c
@@ -29,6 +29,7 @@
#define APPLE_VENDOR_ID 0x05AC
#define TP_PRODUCT_ID1 0x020E
#define TP_PRODUCT_ID2 0x020F
+#define TP_12INCH_ID 0x030A
#define TP_DRIVER_VERSION 0x0001 /* 00.01 */
@@ -42,6 +43,7 @@
static struct usb_device_id apple_tp_table [] = {
{ TP_DEVICE(TP_PRODUCT_ID1) },
{ TP_DEVICE(TP_PRODUCT_ID2) },
+ { USB_DEVICE(APPLE_VENDOR_ID, TP_12INCH_ID) },
{ } /* Terminating entry */
};
MODULE_DEVICE_TABLE (usb, apple_tp_table);
/*
* Apple TrackPad test program
*
* Copyright (C) 2005 Johannes Berg ([EMAIL PROTECTED])
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation, version 2.
*
* arch-tag: 2586e5ef-0be6-4240-a50e-49bcb0f188ac
*/
#include
#include
#include
#include
#include
#include
#include
#define DEVICE "/dev/apple_trackpad0"
int main() {
int fd = open(DEVICE, O_RDWR);
char buffer[1024];
if (fd == -1) {
perror ("open failed");
return -1;
}
while (1) {
int len = read(fd, buffer, sizeof(buffer));
printf("%d:", len);
if (len >= 0)
for (int i=0; i
signature.asc
Description: This is a digitally signed message part
Re: new powerbook touchpad
El mié, 30-03-2005 a las 16:38 +0200, Johannes Berg escribió: > On Wed, 2005-03-30 at 16:31 +0200, Antonio-M. Corbi Bellot wrote: > No need, udev should be fine. The driver doesn't recognize your trackpad > apparently. Check /var/log/kern.log, it should say: > Mar 30 16:38:23 localhost kernel: > /home/johannes/sys/kmod/tp/=build/appletrackpad.c: USB Trackpad device now > attached to USBAppleTrackpad-0 > Mar 30 16:38:23 localhost kernel: usbcore: registered new driver AppleTrackpad Nope :( tail -f /var/log/kern.log says: Mar 30 17:06:21 localhost kernel: usbcore: registered new driver AppleTrackpad And nothing else... > Maybe your trackpad has a yet different USB device ID? Send me the > relevant part of /proc/bus/usb/device (or the full file if you want) Probably, here you are: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05ac ProdID=030a Rev= 0.06 S: Manufacturer=Apple Computer S: Product=Apple Internal Trackpad C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 40mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=1ms Thanks for your help. A. Corbi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new powerbook touchpad
On Wed, 2005-03-30 at 16:31 +0200, Antonio-M. Corbi Bellot wrote: > I'm trying the kernel driver in a post-feb'05 pbook 12" and I'm not > having luck with the trackpad. > > I'm using udev+2.6.11.6 (ubuntu-hoary), after compiling the driver I can > insmod it but nothing else happens...no /dev/apple_trackpad0 device is > created. 'lsmod' says that the driver is inserted but syslog only gets > this and nothing else: > > "Mar 30 15:26:59 localhost kernel: usbcore: registered new driver > AppleTrackpad" > > I have also tried debian-unstable udev packages also without luck. No need, udev should be fine. The driver doesn't recognize your trackpad apparently. Check /var/log/kern.log, it should say: Mar 30 16:38:23 localhost kernel: /home/johannes/sys/kmod/tp/=build/appletrackpad.c: USB Trackpad device now attached to USBAppleTrackpad-0 Mar 30 16:38:23 localhost kernel: usbcore: registered new driver AppleTrackpad > Maybe there are small differences between trackpads in 15" and 12" > models? Maybe your trackpad has a yet different USB device ID? Send me the relevant part of /proc/bus/usb/device (or the full file if you want) johannes signature.asc Description: This is a digitally signed message part
Re: new powerbook touchpad
El mar, 29-03-2005 a las 17:53 +0200, Johannes Berg escribió: > On Tue, 2005-03-29 at 17:44 +0200, Marco Vignati wrote: > > Great! > > my trackpad now works, thanks johannes! > > welcome :) I'm trying the kernel driver in a post-feb'05 pbook 12" and I'm not having luck with the trackpad. I'm using udev+2.6.11.6 (ubuntu-hoary), after compiling the driver I can insmod it but nothing else happens...no /dev/apple_trackpad0 device is created. 'lsmod' says that the driver is inserted but syslog only gets this and nothing else: "Mar 30 15:26:59 localhost kernel: usbcore: registered new driver AppleTrackpad" I have also tried debian-unstable udev packages also without luck. Maybe there are small differences between trackpads in 15" and 12" models? Any help is welcome. I also can try any patch you want. Antonio Corbi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Fix sleep/wakeup problems on iBook G3
Hi! < Le mercredi 30 mars 2005 ï 00:21:22 +0200 (CEST), Benjamin Herrenschmidt écrivit :> > Yes, but lis r4,2 not lis r3,2 > kernel 2.6.11.5 (test #3 at the end of mail) Test 1 (patch and first change) : the ibook wakes up. But... ~$ sudo reboot Erreur de segmentation and I cant log in root -> hard reboot syslog: -- Mar 30 14:32:06 ogma kernel: kernel BUG in page_remove_rmap at mm/rmap.c:482! Mar 30 14:32:06 ogma kernel: Oops: Exception in kernel mode, sig: 5 [#1] Mar 30 14:32:06 ogma kernel: NIP: C004DDAC LR: C0046944 SP: C2B7BC40 REGS: c2b7bb90 TRAP: 0700Not tainted Mar 30 14:32:06 ogma kernel: MSR: 00029032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 Mar 30 14:32:06 ogma kernel: TASK = c4ce4c10[2037] 'hotplug' THREAD: c2b7a000 Mar 30 14:32:06 ogma kernel: Last syscall: 6 Mar 30 14:32:06 ogma kernel: GPR00: C043A528 C2B7BC40 C4CE4C10 C043A520 0FF61000 01D38D84 0001 4000 Mar 30 14:32:06 ogma kernel: GPR08: 003E9840 0001 9032 003D67B0 100C21FC C2B7BD9C Mar 30 14:32:06 ogma kernel: GPR16: C6C52540 0001 C035 C035 0001 0FF61000 01D29787 0FF61000 Mar 30 14:32:06 ogma kernel: GPR24: C034EAD8 C043A520 3000 FFFD C1D38D84 Mar 30 14:32:06 ogma kernel: NIP [c004ddac] __vmalloc+0x54/0x68 Mar 30 14:32:06 ogma kernel: LR [c0046944] zap_pte_range+0x1a4/0x2f4 Mar 30 14:32:06 ogma kernel: Call trace: Mar 30 14:32:06 ogma kernel: [c0046944] zap_pte_range+0x1a4/0x2f4 Mar 30 14:32:06 ogma kernel: [c0046adc] zap_pmd_range+0x48/0x84 Mar 30 14:32:06 ogma kernel: [c0046b58] zap_pud_range+0x40/0x78 Mar 30 14:32:06 ogma kernel: [c0046c38] unmap_page_range+0xa8/0xc8 Mar 30 14:32:06 ogma kernel: [c0046da8] unmap_vmas+0x150/0x210 Mar 30 14:32:06 ogma kernel: [c004be6c] __anon_vma_link+0x64/0x13c Mar 30 14:32:06 ogma kernel: [c0017130] mmput+0x50/0xd4 Mar 30 14:32:06 ogma kernel: [c001b0dc] exit_mm+0x148/0x1a8 Mar 30 14:32:06 ogma kernel: [c001ba38] do_exit+0xb0/0x310 Mar 30 14:32:06 ogma kernel: [c001bd18] do_group_exit+0x38/0x90 Mar 30 14:32:06 ogma kernel: [c002629c] get_signal_to_deliver+0x15c/0x2a8 Mar 30 14:32:06 ogma kernel: [c00083cc] do_signal+0x3c/0x22c Mar 30 14:32:06 ogma kernel: [c0004af4] do_user_signal+0x7c/0xcc Mar 30 14:32:06 ogma kernel: adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f Mar 30 14:32:06 ogma kernel: ADB keyboard at 2, handler 1 Mar 30 14:32:06 ogma kernel: ADB mouse at 3, handler set to 4 (trackpad) Mar 30 14:32:06 ogma kernel: adb: finished probe task... Mar 30 14:32:06 ogma pmud[1833]: system awake again Mar 30 14:32:06 ogma pmud[1833]: running /etc/power/pwrctl wakeup ac Mar 30 14:32:06 ogma kernel: swap_free: Unused swap offset entry 0040 Mar 30 14:32:06 ogma pmud[1833]: /etc/power/pwrctl got signal 11 Mar 30 14:32:06 ogma pmud[1833]: running /etc/power/pwrctl lid-opened ac Mar 30 14:32:06 ogma kernel: swap_free: Unused swap offset entry 0040 Mar 30 14:32:06 ogma pmud[1833]: /etc/power/pwrctl got signal 11 --- Test 3 (patch+ change #1 and #2): the ibook wakes up and all seems to be well. Now I will test the patch for the cpufreq. Do I enable the cpufreq support ? Thanks. Jean-Paul Vincent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC's APM emulation dependant upon PMU feature?
On Wed, 2005-03-30 at 15:40 +0300, Martin-Ãric Racine wrote: > I wanted to enable the APM emulation to calm down XFree's warning about > the missing APM device, but I notice that it's currently dependant upon > the PMU support. Could this be changed into a generic platform option? Maybe I'm misunderstanding, but how should it then get at the relevant data to emulate APM? johannes signature.asc Description: This is a digitally signed message part
PowerPC's APM emulation dependant upon PMU feature?
Hello Ben, I wanted to enable the APM emulation to calm down XFree's warning about the missing APM device, but I notice that it's currently dependant upon the PMU support. Could this be changed into a generic platform option? Thanks! -- Martin-Éric Racine http://www.iki.fi/q-funk/
re: msnbc_auto_response: thank you for contacting today with katie couric and matt lauer
Charlene Scott 267 W Main St Ridgway PA 15853 814-776-6681 [EMAIL PROTECTED] I am writing because of your contest of "What do you want to accomplish". My only thing to do is help my 86 year old dad find his brother. They were seperated when he was around 3 and he wants to find him. My Dad's name is Gilbert Barboza and he was born Feb 26, 1919. His brother George Barboza was born in1920 or 1921, he is not sure. They were born on 80th Avenue in Oakland Ca. My dad served in WWII and he thinks George did to but was never able to find out anything for sure. If you can help me, I would greatly appreciate it. Thank you for your time. Charlene Scott [EMAIL PROTECTED] EarthLink Revolves Around You.
Re: pbbuttonsd 0.6.8beta1 has been released for testing
On 30 Mar 2005 at 12h03, Matthias Grimm wrote: Hi, > The tapping is only disabled for 0.6 seconds and key repetition is > not covered. Only normal key strokes will disable trackpad tapping. > To continously disable the tapping you need constant typing. Pressing > one single key for a while is not the same. In mouseemu i (think to remember) used key _press_ to disable trackpad until key _release_ + delta. So that handles either constant typing or constant press. Maybe you can do like that too? -- Colin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd 0.6.8beta1 has been released for testing
On Fri, 25 Mar 2005 15:35:11 + (UTC) Joerg Sommer <[EMAIL PROTECTED]> wrote: > Matthias Grimm <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > As consequence of the high number of critical bugs in the last release I > > publish a beta release first this time: > > > > PBButtonsd 0.6.8beta1 > > available at: http://pbbuttons.sourceforge.net > > I've build it and started it (not installed), but the touchpad suspend > doesn't work. I can type and use the touchpas. How to enable this new > feature? In this beta realease the function is always enabled. To track if the trackpad tap is currently en- or disabled, you could compile with --enable-debug. The tapping is only disabled for 0.6 seconds and key repetition is not covered. Only normal key strokes will disable trackpad tapping. To continously disable the tapping you need constant typing. Pressing one single key for a while is not the same. The best way to test this feature is to type constantly on the keyboard while trying to activate another window with a tap on the trackpad. This should not be possible. But keep in mind: 0.6 seconds are really short so don't type too slowly :-). In the main release this time value has been increades to 0,8 seconds. Best Regrads Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbutons wont put my PB to sleep
On Sun, 27 Mar 2005 22:02:06 -0400 (CLT) Rolando Abarca <[EMAIL PROTECTED]> wrote: > I have a lombard with kernel 2.6.11.5 (recently compiled) I thought that > pbbutons will work now, but it's doing the same thing that before, it > won't put my PB to sleep if I close the lid (only turn off the screen). Do > I have to include some special module/option for this to work?... > thanks! Please check out the configuration file. There is an option that tells pbbuttonsd what to to when the lid has been closed. It's named onAC_CoverAction and onBattery_CoverAction. See man pbbuttonsd.conf for detailed description. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RTC_PIE possible using via-pmu?
> > Oh, those periodic interrupt things are features of x86 RTC chips, they > > aren't available on other architectures, at least not all of them, > > definitely not on pmac. > > Well I was wondering if I could use the via-pmu timer to implement such > a periodic interrupt. I wouldn't recommend doing that, and I wouldn't recommend touching the via-pmu driver at all anyway, it's enough of a mess. Also, the VIA timers tend not to be very well calibrated on modern HW. > > Why not just normal timers ? > > Not sure what exactly you mean by "normal". I created a genrtc patch [1] for > the ioctls above using add_timer(). > But the resulting timer responses using a simple test program [2] are not > that good (the last percentage is the accuracy), and above 1024Hz completely > unusable: Yah, you would probably need the high res timer. It would be possible to do something with the KeyLargo timer maybe... > Oddly enough (well, odd to me :), 1024Hz is quite good. I have been able > to do some latency tests with that setting [3] which point to latency issues > with the radeon and/or drm modules. > If I get those figured out (video is NOT my area) I'll be kinda stuck. The kernel is running internally it's scheduler at 1000Hz on ppc, and thus that's the best precision you'll get, around the ms. You may want to look into the high resolution timers patches. > Hints/tips/suggestions welcome... Must say 2.6.11 looks better than 2.6.8. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RTC_PIE possible using via-pmu?
On Wed, Mar 30, 2005 at 10:36:15AM +1000, Benjamin Herrenschmidt wrote: > On Tue, 2005-03-29 at 13:17 +0100, Martin Habets wrote: > > RTC_IRQP_SET sets the periodic interrupt rate. > > RTC_PIE_ON turns on periodic interrupts. > > RTC_PIE_OFF turns off periodic interrupts. > > > > There are similar ioctls for setting alarms, but I don't see those > > used very often. > > > > I've pasted the relevant part of my dmesg below. It seems the OpenPIC > > timer frequency will limit the usability of above iotctls to 4.16MHz. > > Is that right? > > Oh, those periodic interrupt things are features of x86 RTC chips, they > aren't available on other architectures, at least not all of them, > definitely not on pmac. Not on Motorola PowerPlus based boards either. The funny thing is that these have a standard PC RTC, but the missing link (literally) is that the interrupt line of the chip is not connected anywhere. > > Why not just normal timers ? For some of these applications, the high resolution timers will come handy. Gabriel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RTC_PIE possible using via-pmu?
On Wed, Mar 30, 2005 at 10:36:15AM +1000, Benjamin Herrenschmidt wrote: > On Tue, 2005-03-29 at 13:17 +0100, Martin Habets wrote: > > RTC_IRQP_SET sets the periodic interrupt rate. > > RTC_PIE_ON turns on periodic interrupts. > > RTC_PIE_OFF turns off periodic interrupts. > > > > There are similar ioctls for setting alarms, but I don't see those > > used very often. > > > > I've pasted the relevant part of my dmesg below. It seems the OpenPIC > > timer frequency will limit the usability of above iotctls to 4.16MHz. > > Is that right? > > Oh, those periodic interrupt things are features of x86 RTC chips, they > aren't available on other architectures, at least not all of them, > definitely not on pmac. Well I was wondering if I could use the via-pmu timer to implement such a periodic interrupt. > Why not just normal timers ? Not sure what exactly you mean by "normal". I created a genrtc patch [1] for the ioctls above using add_timer(). But the resulting timer responses using a simple test program [2] are not that good (the last percentage is the accuracy), and above 1024Hz completely unusable: $ ./rtctest2 20 loops at 2Hz = 9997669 usec, 499883 usec/loop. deviation is 117 usec (0%). 20 loops at 4Hz = 4999186 usec, 249959 usec/loop. deviation is 41 usec (0%). 20 loops at 8Hz = 2499566 usec, 124978 usec/loop. deviation is 22 usec (0%). 20 loops at 16Hz = 1239760 usec, 61988 usec/loop. deviation is 512 usec (0%). 20 loops at 32Hz = 619856 usec, 30992 usec/loop. deviation is 258 usec (0%). 20 loops at 64Hz = 299902 usec, 14995 usec/loop. deviation is 630 usec (4%). 20 loops at 128Hz = 139931 usec, 6996 usec/loop. deviation is 816 usec (10%). 20 loops at 256Hz = 59947 usec, 2997 usec/loop. deviation is 909 usec (23%). 20 loops at 512Hz = 21003 usec, 1050 usec/loop. deviation is 903 usec (46%). 20 loops at 1024Hz = 19906 usec, 995 usec/loop. deviation is 19 usec (1%). 20 loops at 2048Hz = 19954 usec, 997 usec/loop. deviation is 509 usec (104%). 20 loops at 4096Hz = 19955 usec, 997 usec/loop. deviation is 753 usec (308%). 20 loops at 8192Hz = 19956 usec, 997 usec/loop. deviation is 875 usec (717%). Oddly enough (well, odd to me :), 1024Hz is quite good. I have been able to do some latency tests with that setting [3] which point to latency issues with the radeon and/or drm modules. If I get those figured out (video is NOT my area) I'll be kinda stuck. Hints/tips/suggestions welcome... Must say 2.6.11 looks better than 2.6.8. Thanks, -- Martin Signed-off-by: Martin Habets <[EMAIL PROTECTED]> [1] http://www.mph.eclipse.co.uk/pub/linux/patches/2.6.11/genrtc.c.patch [2] http://www.mph.eclipse.co.uk/pub/linux/patches/rtctest2.c [3] http://www.mph.eclipse.co.uk/pub/linux/latency/test3/index.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
