Re: cpufreq default governor
On 24/04/07, William Heimbigner <[EMAIL PROTECTED]> wrote: On Tue, 24 Apr 2007, Michal Piotrowski wrote: > On 24/04/07, William Heimbigner <[EMAIL PROTECTED]> wrote: >> On Tue, 24 Apr 2007, Michal Piotrowski wrote: >> >> > On 24/04/07, William Heimbigner <[EMAIL PROTECTED]> wrote: >> > > On Tue, 24 Apr 2007, Michal Piotrowski wrote: >> > > >> > > > Hi William, >> > > > >> > > > On 24/04/07, William Heimbigner <[EMAIL PROTECTED]> wrote: >> > > > >Question: is there some reason that kconfig does not allow for >> > > > >default >> > > > >governors of conservative/ondemand/powersave? >> > > > >> > > > Performance? >> > > > >> > > > >I'm not aware of any reason why one of those governors could not >> > > > >be >> > > > >used >> > > > >as default. >> > > > >> > > > My hardware doesn't work properly with ondemand governor. I hear >> > > > strange noises when frequency is changed. >> > > > >> > > >> > > That doesn't mean it isn't working, though. >> > >> > I didn't say that cpufreq ondemand is broken. It's a hardware problem. >> > >> > > I here weird noises if the cpu >> > > is clocked anywhere from 333MHz to 1GHz (sounds like an RD-D2 beeping >> > > noises in ultra high pitch?) >> > >> > Yes, something like that. >> >> Is it actually "not working" though, even at the hardware level? > > It works, but for me this sounds are very weird ;) > >> To my >> knowledge those noises are normal, and aren't even signs of a harware >> problem. I believe it is the natural result of changing frequencies at any >> time. If you change frequencies, especially in the low end of available >> frequencies, you should hear a very brief noise. A governor such as >> ondemand, which is rapidly switching the frequency from say, 333 MHz to >> 2.66 GHz, is likely to make this much more noticable. > > Ok, it might be normal behavior. I might be wrong, but IMO users > prefer speed and no strange sounds as default setting. I agree! My suggestion, however, is that if they do want a different scheduler as the default, they can choose one. There are some cases in which this could be very useful. A couple examples would be the processor with poor cooling that overheats easily, or a laptop with a poor battery. However, on second thought with regards to Kconfig, would it be feasible to have performance always be the default, unless a "cpufreqgov=conservative" arguement was specified on the command line? This would be less susceptible to users complaining that their cpu is chirping all of a sudden. I'm all for the ability to set the default to whatever governor the user wants. I _always_ run my laptops with the ondemand governor, my Pentium M-based PVR runs with ondemand too, and only my old P4 box doesn't because it's pointless. If you're running servers that _aren't_ going to be idle most of the time, then by all means set your default to performance, or just don't enable cpufreq at all, but give the rest of us the option. Particularily with laptops, I've always wanted the kernel to boot and immediately slow the CPU down, even if all I do is boot into single user mode, or even bypass init altogether. This will give best battery life and coolest operation out of the box without having to rely on userland whatsoever. I had an old laptop a while back that _would_ overheat and shutdown within a couple of minutes, even though idle, if booted to single user mode because the cpu freq wasn't slowed down. -- Ian Morgan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: cpufreq default governor
On 24/04/07, William Heimbigner [EMAIL PROTECTED] wrote: On Tue, 24 Apr 2007, Michal Piotrowski wrote: On 24/04/07, William Heimbigner [EMAIL PROTECTED] wrote: On Tue, 24 Apr 2007, Michal Piotrowski wrote: On 24/04/07, William Heimbigner [EMAIL PROTECTED] wrote: On Tue, 24 Apr 2007, Michal Piotrowski wrote: Hi William, On 24/04/07, William Heimbigner [EMAIL PROTECTED] wrote: Question: is there some reason that kconfig does not allow for default governors of conservative/ondemand/powersave? Performance? I'm not aware of any reason why one of those governors could not be used as default. My hardware doesn't work properly with ondemand governor. I hear strange noises when frequency is changed. That doesn't mean it isn't working, though. I didn't say that cpufreq ondemand is broken. It's a hardware problem. I here weird noises if the cpu is clocked anywhere from 333MHz to 1GHz (sounds like an RD-D2 beeping noises in ultra high pitch?) Yes, something like that. Is it actually not working though, even at the hardware level? It works, but for me this sounds are very weird ;) To my knowledge those noises are normal, and aren't even signs of a harware problem. I believe it is the natural result of changing frequencies at any time. If you change frequencies, especially in the low end of available frequencies, you should hear a very brief noise. A governor such as ondemand, which is rapidly switching the frequency from say, 333 MHz to 2.66 GHz, is likely to make this much more noticable. Ok, it might be normal behavior. I might be wrong, but IMO users prefer speed and no strange sounds as default setting. I agree! My suggestion, however, is that if they do want a different scheduler as the default, they can choose one. There are some cases in which this could be very useful. A couple examples would be the processor with poor cooling that overheats easily, or a laptop with a poor battery. However, on second thought with regards to Kconfig, would it be feasible to have performance always be the default, unless a cpufreqgov=conservative arguement was specified on the command line? This would be less susceptible to users complaining that their cpu is chirping all of a sudden. I'm all for the ability to set the default to whatever governor the user wants. I _always_ run my laptops with the ondemand governor, my Pentium M-based PVR runs with ondemand too, and only my old P4 box doesn't because it's pointless. If you're running servers that _aren't_ going to be idle most of the time, then by all means set your default to performance, or just don't enable cpufreq at all, but give the rest of us the option. Particularily with laptops, I've always wanted the kernel to boot and immediately slow the CPU down, even if all I do is boot into single user mode, or even bypass init altogether. This will give best battery life and coolest operation out of the box without having to rely on userland whatsoever. I had an old laptop a while back that _would_ overheat and shutdown within a couple of minutes, even though idle, if booted to single user mode because the cpu freq wasn't slowed down. -- Ian Morgan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Loud POP from sound system during module init w/ 2.6.19
Previous kernel was 2.6.18.3, which did not exhibit the problem. I was aware of udev setting the mixer at module load time, but I disabled that and the problem still exists. -- Ian E. Morgan [EMAIL PROTECTED] On 09/12/06, Jan Engelhardt <[EMAIL PROTECTED]> wrote: On Dec 8 2006 13:53, Ian E. Morgan wrote: >Subject: Loud POP from sound system during module init w/ 2.6.19 What kernel did you have before? What you see is the same I am experiencing on every boot - when the sound module is loaded, udev loads the previous volume settings. The volume settings are normal for me, but I guess the instant jump from 0-70% (for Master) and 0-61% (for PCM) is not taken too heartly by the soundcard. > Since upgrading to 2.6.19, two of my boxes (one workstation, one > notebook) started making a very loud (and scary) POP from the sound > system when the alsa modules are loaded. Unloading and reloading the > modules will generate another pop. > > Anybody else seeing this behaviour and know how to stop it? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Loud POP from sound system during module init w/ 2.6.19
Previous kernel was 2.6.18.3, which did not exhibit the problem. I was aware of udev setting the mixer at module load time, but I disabled that and the problem still exists. -- Ian E. Morgan [EMAIL PROTECTED] On 09/12/06, Jan Engelhardt [EMAIL PROTECTED] wrote: On Dec 8 2006 13:53, Ian E. Morgan wrote: Subject: Loud POP from sound system during module init w/ 2.6.19 What kernel did you have before? What you see is the same I am experiencing on every boot - when the sound module is loaded, udev loads the previous volume settings. The volume settings are normal for me, but I guess the instant jump from 0-70% (for Master) and 0-61% (for PCM) is not taken too heartly by the soundcard. Since upgrading to 2.6.19, two of my boxes (one workstation, one notebook) started making a very loud (and scary) POP from the sound system when the alsa modules are loaded. Unloading and reloading the modules will generate another pop. Anybody else seeing this behaviour and know how to stop it? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Loud POP from sound system during module init w/ 2.6.19
Since upgrading to 2.6.19, two of my boxes (one workstation, one notebook) started making a very loud (and scary) POP from the sound system when the alsa modules are loaded. Unloading and reloading the modules will generate another pop. I have removed any fiddling of mixer settings during module load/unload; same results. I have complied the kernel both with and without CONFIG_SND_AC97_POWER_SAVE; same results. The workstation uses snd_emu10k1, the notebook snd_intel8x0, so it's affecting more than a single driver. Anybody else seeing this behaviour and know how to stop it? -- Ian E. Morgan [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Loud POP from sound system during module init w/ 2.6.19
Since upgrading to 2.6.19, two of my boxes (one workstation, one notebook) started making a very loud (and scary) POP from the sound system when the alsa modules are loaded. Unloading and reloading the modules will generate another pop. I have removed any fiddling of mixer settings during module load/unload; same results. I have complied the kernel both with and without CONFIG_SND_AC97_POWER_SAVE; same results. The workstation uses snd_emu10k1, the notebook snd_intel8x0, so it's affecting more than a single driver. Anybody else seeing this behaviour and know how to stop it? -- Ian E. Morgan [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[WATCHDOG] Push SBC8360 driver upstream
I would like to ask that the SBC8360 watchdog driver be pushed upstream from -mm in time for the 2.6.14-rc series. I recognise that this driver, like a lot of the watchdog drivers, is for a piece of hardware this is present in only a very small percentage of hardware runnig Linux. I doubt that being in -mm for a long time will make any significant difference to it being more widely tested. The driver is working perfectly as expected on each of the machines we've tested it on. As a recap, the driver was submitted to akpm, was included in -mm1 (watchdog-new-sbc8360-driver.patch), offloaded to Wim's linux-2.6-watchdog-mm.git tree (commit 88b1f50923d14195ac1a50840fc4aa4066f067a9), and subsequently included in -mm2 by way of the combined git-watchdog.patch. Please consider merging this driver into 2.6.14-rc1. Thanks. Regards, Ian Morgan -- --- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[WATCHDOG] Push SBC8360 driver upstream
I would like to ask that the SBC8360 watchdog driver be pushed upstream from -mm in time for the 2.6.14-rc series. I recognise that this driver, like a lot of the watchdog drivers, is for a piece of hardware this is present in only a very small percentage of hardware runnig Linux. I doubt that being in -mm for a long time will make any significant difference to it being more widely tested. The driver is working perfectly as expected on each of the machines we've tested it on. As a recap, the driver was submitted to akpm, was included in -mm1 (watchdog-new-sbc8360-driver.patch), offloaded to Wim's linux-2.6-watchdog-mm.git tree (commit 88b1f50923d14195ac1a50840fc4aa4066f067a9), and subsequently included in -mm2 by way of the combined git-watchdog.patch. Please consider merging this driver into 2.6.14-rc1. Thanks. Regards, Ian Morgan -- --- Ian E. Morgan Vice President C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] New SBC8360 watchdog driver (revised)
On Mon, 29 Aug 2005, [EMAIL PROTECTED] wrote: The patch titled watchdog: new SBC8360 driver has been added to the -mm tree. Its filename is watchdog-new-sbc8360-driver.patch On Mon, 29 Aug 2005, [EMAIL PROTECTED] wrote: The patch titled watchdog-new-sbc8360-driver-tidy has been added to the -mm tree. Its filename is watchdog-new-sbc8360-driver-tidy.patch Andrew, Please find below a revised version of the SBC8360 watchdog driver patch which incorporates a few cleanups (no code changes): - integrates your above 'tidy' patch - fixes typos in the documentation related to the ioports used - removes some end-of-line trailing spaces - run through scripts/Lindent You may replace the above two patches with the one below. It patches cleanly on 2.6.13. Regards, Ian Morgan -- --- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- diff -urN linux/drivers/char/watchdog/Kconfig~ linux/drivers/char/watchdog/Kconfig --- linux/drivers/char/watchdog/Kconfig~2005-02-15 18:19:22.0 -0500 +++ linux/drivers/char/watchdog/Kconfig 2005-02-15 18:19:22.0 -0500 @@ -224,6 +224,19 @@ Most people will say N. +config SBC8360_WDT + tristate "SBC8360 Watchdog Timer" + depends on WATCHDOG && X86 + ---help--- + + This is the driver for the hardware watchdog on the SBC8360 Single + Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). + + To compile this driver as a module, choose M here: the + module will be called sbc8360.ko. + + Most people will say N. + config WAFER_WDT tristate "ICP Wafer 5823 Single Board Computer Watchdog" depends on WATCHDOG && X86 diff -urN linux/drivers/char/watchdog/Makefile~ linux/drivers/char/watchdog/Makefile --- linux/drivers/char/watchdog/Makefile~ 2005-02-15 18:20:03.0 -0500 +++ linux/drivers/char/watchdog/Makefile2005-02-15 18:20:03.0 -0500 @@ -6,6 +6,7 @@ obj-$(CONFIG_ACQUIRE_WDT) += acquirewdt.o obj-$(CONFIG_ADVANTECH_WDT) += advantechwdt.o obj-$(CONFIG_IB700_WDT) += ib700wdt.o +obj-$(CONFIG_SBC8360_WDT) += sbc8360.o obj-$(CONFIG_MIXCOMWD) += mixcomwd.o obj-$(CONFIG_SCx200_WDT) += scx200_wdt.o obj-$(CONFIG_60XX_WDT) += sbc60xxwdt.o diff -urN /dev/null linux/drivers/char/watchdog/sbc8360.c --- /dev/null 2004-02-23 16:02:56.0 -0500 +++ linux/drivers/char/watchdog/sbc8360.c 2005-08-30 17:08:35.0 -0400 @@ -0,0 +1,419 @@ +/* + * SBC8360 Watchdog driver + * + * (c) Copyright 2005 Webcon, Inc. + * + * Based on ib700wdt.c, which is based on advantechwdt.c which is based + * on acquirewdt.c which is based on wdt.c. + * + * (c) Copyright 2001 Charles Howes <[EMAIL PROTECTED]> + * + * Based on advantechwdt.c which is based on acquirewdt.c which + * is based on wdt.c. + * + * (c) Copyright 2000-2001 Marek Michalkiewicz <[EMAIL PROTECTED]> + * + * Based on acquirewdt.c which is based on wdt.c. + * Original copyright messages: + * + * (c) Copyright 1996 Alan Cox <[EMAIL PROTECTED]>, All Rights Reserved. + * http://www.redhat.com + * + * 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; either version + * 2 of the License, or (at your option) any later version. + * + * Neither Alan Cox nor CymruNet Ltd. admit liability nor provide + * warranty for any of this software. This material is provided + * "AS-IS" and at no charge. + * + * (c) Copyright 1995Alan Cox <[EMAIL PROTECTED]> + * + * 14-Dec-2001 Matt Domsch <[EMAIL PROTECTED]> + * Added nowayout module option to override CONFIG_WATCHDOG_NOWAYOUT + * Added timeout module option to override default + * + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +static unsigned long sbc8360_is_open; +static spinlock_t sbc8360_lock; +static char expect_close; + +#define PFX "sbc8360: " + +/* + * + * Watchdog Timer Configuration + * + * The function of the watchdog timer is to reset the system automatically + * and is defined at I/O port 0120H and 0121H. To enable the watchdog timer + * and allow the system to reset, write appropriate values from the table + * below to I/O port 0120H and 0121H. To disable the timer, write a zero + * value to I/O port 0121H for the
[PATCH] New SBC8360 watchdog driver (revised)
On Mon, 29 Aug 2005, [EMAIL PROTECTED] wrote: The patch titled watchdog: new SBC8360 driver has been added to the -mm tree. Its filename is watchdog-new-sbc8360-driver.patch On Mon, 29 Aug 2005, [EMAIL PROTECTED] wrote: The patch titled watchdog-new-sbc8360-driver-tidy has been added to the -mm tree. Its filename is watchdog-new-sbc8360-driver-tidy.patch Andrew, Please find below a revised version of the SBC8360 watchdog driver patch which incorporates a few cleanups (no code changes): - integrates your above 'tidy' patch - fixes typos in the documentation related to the ioports used - removes some end-of-line trailing spaces - run through scripts/Lindent You may replace the above two patches with the one below. It patches cleanly on 2.6.13. Regards, Ian Morgan -- --- Ian E. Morgan Vice President C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- diff -urN linux/drivers/char/watchdog/Kconfig~ linux/drivers/char/watchdog/Kconfig --- linux/drivers/char/watchdog/Kconfig~2005-02-15 18:19:22.0 -0500 +++ linux/drivers/char/watchdog/Kconfig 2005-02-15 18:19:22.0 -0500 @@ -224,6 +224,19 @@ Most people will say N. +config SBC8360_WDT + tristate SBC8360 Watchdog Timer + depends on WATCHDOG X86 + ---help--- + + This is the driver for the hardware watchdog on the SBC8360 Single + Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). + + To compile this driver as a module, choose M here: the + module will be called sbc8360.ko. + + Most people will say N. + config WAFER_WDT tristate ICP Wafer 5823 Single Board Computer Watchdog depends on WATCHDOG X86 diff -urN linux/drivers/char/watchdog/Makefile~ linux/drivers/char/watchdog/Makefile --- linux/drivers/char/watchdog/Makefile~ 2005-02-15 18:20:03.0 -0500 +++ linux/drivers/char/watchdog/Makefile2005-02-15 18:20:03.0 -0500 @@ -6,6 +6,7 @@ obj-$(CONFIG_ACQUIRE_WDT) += acquirewdt.o obj-$(CONFIG_ADVANTECH_WDT) += advantechwdt.o obj-$(CONFIG_IB700_WDT) += ib700wdt.o +obj-$(CONFIG_SBC8360_WDT) += sbc8360.o obj-$(CONFIG_MIXCOMWD) += mixcomwd.o obj-$(CONFIG_SCx200_WDT) += scx200_wdt.o obj-$(CONFIG_60XX_WDT) += sbc60xxwdt.o diff -urN /dev/null linux/drivers/char/watchdog/sbc8360.c --- /dev/null 2004-02-23 16:02:56.0 -0500 +++ linux/drivers/char/watchdog/sbc8360.c 2005-08-30 17:08:35.0 -0400 @@ -0,0 +1,419 @@ +/* + * SBC8360 Watchdog driver + * + * (c) Copyright 2005 Webcon, Inc. + * + * Based on ib700wdt.c, which is based on advantechwdt.c which is based + * on acquirewdt.c which is based on wdt.c. + * + * (c) Copyright 2001 Charles Howes [EMAIL PROTECTED] + * + * Based on advantechwdt.c which is based on acquirewdt.c which + * is based on wdt.c. + * + * (c) Copyright 2000-2001 Marek Michalkiewicz [EMAIL PROTECTED] + * + * Based on acquirewdt.c which is based on wdt.c. + * Original copyright messages: + * + * (c) Copyright 1996 Alan Cox [EMAIL PROTECTED], All Rights Reserved. + * http://www.redhat.com + * + * 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; either version + * 2 of the License, or (at your option) any later version. + * + * Neither Alan Cox nor CymruNet Ltd. admit liability nor provide + * warranty for any of this software. This material is provided + * AS-IS and at no charge. + * + * (c) Copyright 1995Alan Cox [EMAIL PROTECTED] + * + * 14-Dec-2001 Matt Domsch [EMAIL PROTECTED] + * Added nowayout module option to override CONFIG_WATCHDOG_NOWAYOUT + * Added timeout module option to override default + * + */ + +#include linux/config.h +#include linux/module.h +#include linux/types.h +#include linux/miscdevice.h +#include linux/watchdog.h +#include linux/ioport.h +#include linux/delay.h +#include linux/notifier.h +#include linux/fs.h +#include linux/reboot.h +#include linux/init.h +#include linux/spinlock.h +#include linux/moduleparam.h + +#include asm/io.h +#include asm/uaccess.h +#include asm/system.h + +static unsigned long sbc8360_is_open; +static spinlock_t sbc8360_lock; +static char expect_close; + +#define PFX sbc8360: + +/* + * + * Watchdog Timer Configuration + * + * The function of the watchdog timer is to reset the system automatically + * and is defined at I/O port 0120H and 0121H. To enable the watchdog timer + * and allow the system to reset, write appropriate values from the table + * below to I
[PATCH] New SBC8360 watchdog driver
Andrew, Attached patch provides a driver for the hardware watchdog on-board the SBC8360 single board computer. This board is used in many industrial and embedded systems, including many touch-panel computers from Axiomtek, Inc. Please consider for inclusion into the mainline Linux kernel. Signed-off-by: Ian E. Morgan <[EMAIL PROTECTED]> drivers/char/watchdog/Kconfig | 13 + drivers/char/watchdog/Makefile |1 drivers/char/watchdog/sbc8360.c | 421 3 files changed, 435 insertions(+) Regards, Ian Morgan -- ------- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- diff -urN linux/drivers/char/watchdog/Kconfig~ linux/drivers/char/watchdog/Kconfig --- linux/drivers/char/watchdog/Kconfig~2005-02-15 18:19:22.0 -0500 +++ linux/drivers/char/watchdog/Kconfig 2005-02-15 18:19:22.0 -0500 @@ -224,6 +224,19 @@ Most people will say N. +config SBC8360_WDT + tristate "SBC8360 Watchdog Timer" + depends on WATCHDOG && X86 + ---help--- + + This is the driver for the hardware watchdog on the SBC8360 Single + Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). + + To compile this driver as a module, choose M here: the + module will be called sbc8360.ko. + + Most people will say N. + config WAFER_WDT tristate "ICP Wafer 5823 Single Board Computer Watchdog" depends on WATCHDOG && X86 diff -urN linux/drivers/char/watchdog/Makefile~ linux/drivers/char/watchdog/Makefile --- linux/drivers/char/watchdog/Makefile~ 2005-02-15 18:20:03.0 -0500 +++ linux/drivers/char/watchdog/Makefile2005-02-15 18:20:03.0 -0500 @@ -6,6 +6,7 @@ obj-$(CONFIG_ACQUIRE_WDT) += acquirewdt.o obj-$(CONFIG_ADVANTECH_WDT) += advantechwdt.o obj-$(CONFIG_IB700_WDT) += ib700wdt.o +obj-$(CONFIG_SBC8360_WDT) += sbc8360.o obj-$(CONFIG_MIXCOMWD) += mixcomwd.o obj-$(CONFIG_SCx200_WDT) += scx200_wdt.o obj-$(CONFIG_60XX_WDT) += sbc60xxwdt.o diff -urN /dev/null linux/drivers/char/watchdog/sbc8360.c --- /dev/null 2004-02-23 16:02:56.0 -0500 +++ linux/drivers/char/watchdog/sbc8360.c 2005-08-26 16:41:12.0 -0400 @@ -0,0 +1,421 @@ +/* + * SBC8360 Watchdog driver + * + * (c) Copyright 2005 Webcon, Inc. + * + * Based on ib700wdt.c, which is based on advantechwdt.c which is based + * on acquirewdt.c which is based on wdt.c. + * + * (c) Copyright 2001 Charles Howes <[EMAIL PROTECTED]> + * + * Based on advantechwdt.c which is based on acquirewdt.c which + * is based on wdt.c. + * + * (c) Copyright 2000-2001 Marek Michalkiewicz <[EMAIL PROTECTED]> + * + * Based on acquirewdt.c which is based on wdt.c. + * Original copyright messages: + * + * (c) Copyright 1996 Alan Cox <[EMAIL PROTECTED]>, All Rights Reserved. + * http://www.redhat.com + * + * 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; either version + * 2 of the License, or (at your option) any later version. + * + * Neither Alan Cox nor CymruNet Ltd. admit liability nor provide + * warranty for any of this software. This material is provided + * "AS-IS" and at no charge. + * + * (c) Copyright 1995Alan Cox <[EMAIL PROTECTED]> + * + * 14-Dec-2001 Matt Domsch <[EMAIL PROTECTED]> + * Added nowayout module option to override CONFIG_WATCHDOG_NOWAYOUT + * Added timeout module option to override default + * + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +static unsigned long sbc8360_is_open; +static spinlock_t sbc8360_lock; +static char expect_close; + +#define PFX "sbc8360: " + +/* + * + * Watchdog Timer Configuration + * + * The function of the watchdog timer is to reset the system automatically + * and is defined at I/O port 0120H and 0121H. To enable the watchdog timer + * and allow the system to reset, write appropriate values from the table + * below to I/O port 0220H and 0221H. To disable the timer, write a zero + * value to I/O port 0221H for the system to stop the watchdog function. + * + * The following describes how the timer should be programmed (according to + * the vendor documentation) + * + * Enabling Watchdog: + * MOV AX,000AH (enable, phase I) + * MOV DX,0120H + * OUT DX,AX + * MOV AX,000BH (enable, phase I
[PATCH] New SBC8360 watchdog driver
Andrew, Attached patch provides a driver for the hardware watchdog on-board the SBC8360 single board computer. This board is used in many industrial and embedded systems, including many touch-panel computers from Axiomtek, Inc. Please consider for inclusion into the mainline Linux kernel. Signed-off-by: Ian E. Morgan [EMAIL PROTECTED] drivers/char/watchdog/Kconfig | 13 + drivers/char/watchdog/Makefile |1 drivers/char/watchdog/sbc8360.c | 421 3 files changed, 435 insertions(+) Regards, Ian Morgan -- --- Ian E. Morgan Vice President C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- diff -urN linux/drivers/char/watchdog/Kconfig~ linux/drivers/char/watchdog/Kconfig --- linux/drivers/char/watchdog/Kconfig~2005-02-15 18:19:22.0 -0500 +++ linux/drivers/char/watchdog/Kconfig 2005-02-15 18:19:22.0 -0500 @@ -224,6 +224,19 @@ Most people will say N. +config SBC8360_WDT + tristate SBC8360 Watchdog Timer + depends on WATCHDOG X86 + ---help--- + + This is the driver for the hardware watchdog on the SBC8360 Single + Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). + + To compile this driver as a module, choose M here: the + module will be called sbc8360.ko. + + Most people will say N. + config WAFER_WDT tristate ICP Wafer 5823 Single Board Computer Watchdog depends on WATCHDOG X86 diff -urN linux/drivers/char/watchdog/Makefile~ linux/drivers/char/watchdog/Makefile --- linux/drivers/char/watchdog/Makefile~ 2005-02-15 18:20:03.0 -0500 +++ linux/drivers/char/watchdog/Makefile2005-02-15 18:20:03.0 -0500 @@ -6,6 +6,7 @@ obj-$(CONFIG_ACQUIRE_WDT) += acquirewdt.o obj-$(CONFIG_ADVANTECH_WDT) += advantechwdt.o obj-$(CONFIG_IB700_WDT) += ib700wdt.o +obj-$(CONFIG_SBC8360_WDT) += sbc8360.o obj-$(CONFIG_MIXCOMWD) += mixcomwd.o obj-$(CONFIG_SCx200_WDT) += scx200_wdt.o obj-$(CONFIG_60XX_WDT) += sbc60xxwdt.o diff -urN /dev/null linux/drivers/char/watchdog/sbc8360.c --- /dev/null 2004-02-23 16:02:56.0 -0500 +++ linux/drivers/char/watchdog/sbc8360.c 2005-08-26 16:41:12.0 -0400 @@ -0,0 +1,421 @@ +/* + * SBC8360 Watchdog driver + * + * (c) Copyright 2005 Webcon, Inc. + * + * Based on ib700wdt.c, which is based on advantechwdt.c which is based + * on acquirewdt.c which is based on wdt.c. + * + * (c) Copyright 2001 Charles Howes [EMAIL PROTECTED] + * + * Based on advantechwdt.c which is based on acquirewdt.c which + * is based on wdt.c. + * + * (c) Copyright 2000-2001 Marek Michalkiewicz [EMAIL PROTECTED] + * + * Based on acquirewdt.c which is based on wdt.c. + * Original copyright messages: + * + * (c) Copyright 1996 Alan Cox [EMAIL PROTECTED], All Rights Reserved. + * http://www.redhat.com + * + * 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; either version + * 2 of the License, or (at your option) any later version. + * + * Neither Alan Cox nor CymruNet Ltd. admit liability nor provide + * warranty for any of this software. This material is provided + * AS-IS and at no charge. + * + * (c) Copyright 1995Alan Cox [EMAIL PROTECTED] + * + * 14-Dec-2001 Matt Domsch [EMAIL PROTECTED] + * Added nowayout module option to override CONFIG_WATCHDOG_NOWAYOUT + * Added timeout module option to override default + * + */ + +#include linux/config.h +#include linux/module.h +#include linux/types.h +#include linux/miscdevice.h +#include linux/watchdog.h +#include linux/ioport.h +#include linux/delay.h +#include linux/notifier.h +#include linux/fs.h +#include linux/reboot.h +#include linux/init.h +#include linux/spinlock.h +#include linux/moduleparam.h + +#include asm/io.h +#include asm/uaccess.h +#include asm/system.h + +static unsigned long sbc8360_is_open; +static spinlock_t sbc8360_lock; +static char expect_close; + +#define PFX sbc8360: + +/* + * + * Watchdog Timer Configuration + * + * The function of the watchdog timer is to reset the system automatically + * and is defined at I/O port 0120H and 0121H. To enable the watchdog timer + * and allow the system to reset, write appropriate values from the table + * below to I/O port 0220H and 0221H. To disable the timer, write a zero + * value to I/O port 0221H for the system to stop the watchdog function. + * + * The following describes how the timer should be programmed (according to + * the vendor documentation) + * + * Enabling Watchdog
Re: ALPS tapping disabled. WHY?
On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan -- --- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan -- --- Ian E. Morgan Vice President C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ALPS tapping disabled. WHY?
Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
reading several threads related to the topic, noe seemed to resolve my
issue.
The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
2.6.10.
This change fixes the problem by NOT disabling hardware tapping:
--- linux-2.6.11-rc5/drivers/input/mouse/alps.c~2005-02-24
18:16:03.0 -0500
+++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24 18:16:03.0
-0500
@@ -334,8 +334,8 @@
if (alps_get_status(psmouse, param))
return -1;
- if (param[0] & 0x04)
- alps_tap_mode(psmouse, 0);
+// if (param[0] & 0x04)
+// alps_tap_mode(psmouse, 0);
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
@@ -372,11 +372,11 @@
return -1;
}
- if (param[0] & 0x04) {
- printk(KERN_INFO " Disabling hardware tapping\n");
- if (alps_tap_mode(psmouse, 0))
- printk(KERN_WARNING "alps.c: Failed to disable hardware
tapping\n");
- }
+// if (param[0] & 0x04) {
+// printk(KERN_INFO " Disabling hardware tapping\n");
+// if (alps_tap_mode(psmouse, 0))
+// printk(KERN_WARNING "alps.c: Failed to disable hardware
tapping\n");
+// }
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
So now, can anyone explain what bit 3 of param[0] does, and why you would
want to disable hardware tapping support when it's set? My pad (ALPS
56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
plain PS/2 mouse, no special ALPS support req'd.
Can this disabling of hardware tapping support be made optional (boot time
param or other)? I don't want to have to patch every kernel from here on
out.
Regards,
Ian Morgan
--
---
Ian E. Morgan Vice President & C.O.O. Webcon, Inc.
imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca
* Customized Linux Network Solutions for your Business *
---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ALPS tapping disabled. WHY?
Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
reading several threads related to the topic, noe seemed to resolve my
issue.
The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
2.6.10.
This change fixes the problem by NOT disabling hardware tapping:
--- linux-2.6.11-rc5/drivers/input/mouse/alps.c~2005-02-24
18:16:03.0 -0500
+++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24 18:16:03.0
-0500
@@ -334,8 +334,8 @@
if (alps_get_status(psmouse, param))
return -1;
- if (param[0] 0x04)
- alps_tap_mode(psmouse, 0);
+// if (param[0] 0x04)
+// alps_tap_mode(psmouse, 0);
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
@@ -372,11 +372,11 @@
return -1;
}
- if (param[0] 0x04) {
- printk(KERN_INFO Disabling hardware tapping\n);
- if (alps_tap_mode(psmouse, 0))
- printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
- }
+// if (param[0] 0x04) {
+// printk(KERN_INFO Disabling hardware tapping\n);
+// if (alps_tap_mode(psmouse, 0))
+// printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
+// }
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
So now, can anyone explain what bit 3 of param[0] does, and why you would
want to disable hardware tapping support when it's set? My pad (ALPS
56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
plain PS/2 mouse, no special ALPS support req'd.
Can this disabling of hardware tapping support be made optional (boot time
param or other)? I don't want to have to patch every kernel from here on
out.
Regards,
Ian Morgan
--
---
Ian E. Morgan Vice President C.O.O. Webcon, Inc.
imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca
* Customized Linux Network Solutions for your Business *
---
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
