pbbuttons-users Mailing List for PBButtons (Page 12)
Brought to you by:
matthiasgrimm
Menu
▾
▴
pbbuttons-users — Everything regarding pbbuttons' usage and develpment
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(3) |
Jul
(13) |
Aug
(9) |
Sep
(9) |
Oct
|
Nov
(8) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(13) |
Feb
(10) |
Mar
(4) |
Apr
(17) |
May
(20) |
Jun
(4) |
Jul
(15) |
Aug
(9) |
Sep
(15) |
Oct
(23) |
Nov
(9) |
Dec
(14) |
| 2006 |
Jan
(13) |
Feb
(5) |
Mar
(9) |
Apr
(6) |
May
(16) |
Jun
|
Jul
(11) |
Aug
|
Sep
(9) |
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2008 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Matthias G. <mat...@us...> - 2004-12-02 17:02:05
|
On Wed, 1 Dec 2004 23:15:18 -0500
David <di...@gm...> wrote:
> Hi. I have pbbuttonsd (and gtkpbbuttons) installed on an iBook G3 800
> (running Ubuntu Linux 5.04). Everything is working great except one
> minor glitch: the dim buttons don't work after the machine is put to
> sleep then woke back up. The dim buttons work fine prior to sleep, and
> after resume I can still do dimming via pbbcmb like so: "pbbcmd config
> TAG_LCDBRIGHTNESS 4" (and the gtkpbbutton window pops up too).
There was a bug in version 0.6.5 that caused excactly that behaviour you
described. Please update to 0.6.6 and it will work again.
Best Regards
Matthias
|
|
From: David <di...@gm...> - 2004-12-02 04:15:23
|
Hi. I have pbbuttonsd (and gtkpbbuttons) installed on an iBook G3 800 (running Ubuntu Linux 5.04). Everything is working great except one minor glitch: the dim buttons don't work after the machine is put to sleep then woke back up. The dim buttons work fine prior to sleep, and after resume I can still do dimming via pbbcmb like so: "pbbcmd config TAG_LCDBRIGHTNESS 4" (and the gtkpbbutton window pops up too). I have no idea what the fix might be; I'm hoping someone can give me a clue or point me in the right direction. Thank you, David -- |
|
From: Matthias G. <mat...@us...> - 2004-11-29 20:50:26
|
On Tue, 23 Nov 2004 05:26:36 +1030
John Steele Scott <to...@to...> wrote:
> Did you run "autoreconf --force" in the top level directory? I did test my patch
Yes, I did.
> on a clean copy of the sources, but I'm not an expert with the autotools. I
> thought AM_PATH_ALSA added the alsa libs to LDFLAGS automatically.
No, it doesn't. AM_PATH_ALSA exported some new symbols ALSA_LIBS
and another one but they won't be used by Makefile.in. First I thought
the problem occour due to my ancient version of automake and autoconf
but after an update nothing changed.
But this is not a real problem. I added ALSA_LIBS to LDFLAGS in my
Makefile.am and everything works.
> > 2. Your module doesn't change volume on my machine (G3 Pismo).
> > The problem: Your module change the master volume channel only (viewed with
> > the alsamixer), but this channel does nothing on my machine. I have to
> > change the PC Speaker volume channel to get a result, but I don't know how
> > to specify that channel in dev_Mixer. What is the right keyword for the PC
> > Speaker channel?
> > Running pbbuttonsd with OSS emulation of ALSA modify both channels due to
> > the MixerChannels configuration option. Maybe you could use the
> > MixerChannels configuration option to control this too.
>
> Ah, I just assumed that all mixers would have a working "Master". I will try and
> get this fixed (by adding the MixerChannels option) this week some time.
Great. After you have solved this little problem and after some more testing
pbbuttonsd 0.6.7 will be released. If you like to test a little bit by now please have
a look into the CVS repository.
Best Regards
Matthias
|
|
From: John S. S. <to...@to...> - 2004-11-22 18:57:20
|
Matthias Grimm <mat...@us...> writes: > Hi John, > I just integrated your module in my distribution and i got some problems you > might know a solution for: > > 1. Your patch don't compile on my machine out of the box. > The problem: The linker doesn't got the alsa libraries after running > configure. Have you modified files not included in the patch? I had to > modify src/Makefile.am to add the ALSA_LIBS. > I updated my autoconf and libasound2 but there was no trick. Did you run "autoreconf --force" in the top level directory? I did test my patch on a clean copy of the sources, but I'm not an expert with the autotools. I thought AM_PATH_ALSA added the alsa libs to LDFLAGS automatically. > 2. Your module doesn't change volume on my machine (G3 Pismo). > The problem: Your module change the master volume channel only (viewed with > the alsamixer), but this channel does nothing on my machine. I have to > change the PC Speaker volume channel to get a result, but I don't know how > to specify that channel in dev_Mixer. What is the right keyword for the PC > Speaker channel? > Running pbbuttonsd with OSS emulation of ALSA modify both channels due to > the MixerChannels configuration option. Maybe you could use the > MixerChannels configuration option to control this too. Ah, I just assumed that all mixers would have a working "Master". I will try and get this fixed (by adding the MixerChannels option) this week some time. cheers, John |
|
From: Matthias G. <mat...@us...> - 2004-11-21 16:55:42
|
Am Freitag, 19. November 2004 03:14 schrieb John Steele Scott:
> I have updated the patch. It ended up being a bit more difficult than that,
> because ALSA does not place any restrictions on how drivers specify the
> volume. For instance, on my iBook G4, the volume range is from 0 to 176. I
> have included code to map this range to 0-100, but the rounding makes
> things appear weird sometimes.
Hi John,
I just integrated your module in my distribution and i got some problems you
might know a solution for:
1. Your patch don't compile on my machine out of the box.
The problem: The linker doesn't got the alsa libraries after running
configure. Have you modified files not included in the patch? I had to
modify src/Makefile.am to add the ALSA_LIBS.
I updated my autoconf and libasound2 but there was no trick.
2. Your module doesn't change volume on my machine (G3 Pismo).
The problem: Your module change the master volume channel only (viewed with
the alsamixer), but this channel does nothing on my machine. I have to
change the PC Speaker volume channel to get a result, but I don't know how
to specify that channel in dev_Mixer. What is the right keyword for the PC
Speaker channel?
Running pbbuttonsd with OSS emulation of ALSA modify both channels due to
the MixerChannels configuration option. Maybe you could use the
MixerChannels configuration option to control this too.
After solving this little problems the alsamixer will become part of my
distribution. You will be able to compile your favourite version with ALSA or
OSS or decide at runtime with a new configuration option. I will send you the
package for test after the above problems have been solved.
Best regards
Matthias
|
|
From: John S. S. <to...@to...> - 2004-11-19 02:18:07
|
> Yes I can. You need to send the volume information to gtkpbbuttons. This > could be done with the function call: > > singletag_to_clients (CHANGEVALUE, base->mute ? TAG_MUTE : TAG_VOLUME, > vol); Thanks Matthias, I have updated the patch. It ended up being a bit more difficult than that, because ALSA does not place any restrictions on how drivers specify the volume. For instance, on my iBook G4, the volume range is from 0 to 176. I have included code to map this range to 0-100, but the rounding makes things appear weird sometimes. cheers, John |
|
From: Matthias G. <mat...@us...> - 2004-11-18 18:28:59
|
Am Donnerstag, 18. November 2004 06:03 schrieb John Steele Scott: > Hi all, > > This patch allows pbbuttonsd to use ALSA without requiring the OSS > emulation modules be loaded. More comments are included in the patch file. nice work :-) > It allows for muting and increase/decrease of the volume. One thing I've > noticed is that gtkpbbuttonsd does not recognise when it changes the > volume. Can anyone give me a hint why that might be? Yes I can. You need to send the volume information to gtkpbbuttons. This could be done with the function call: singletag_to_clients (CHANGEVALUE, base->mute ? TAG_MUTE : TAG_VOLUME, vol); Add this line somewhere in your function alsamixer_set_and_send() and gtkpbbuttons will display your volume again. The only thing left to do is to decide which channel's volume should be sent. Best Regards Matthias |
|
From: John S. S. <to...@to...> - 2004-11-18 05:05:55
|
Hi all, This patch allows pbbuttonsd to use ALSA without requiring the OSS emulation modules be loaded. More comments are included in the patch file. It allows for muting and increase/decrease of the volume. One thing I've noticed is that gtkpbbuttonsd does not recognise when it changes the volume. Can anyone give me a hint why that might be? cheers, John |
|
From: Marc B. <mar...@kp...> - 2004-11-14 12:56:52
|
Hi, I'm trying to turn off automatically my Ibook G4 backlight off when there's no activity or when lid is closed... But It doesn't work. I use pbbuttonsd 0.6.5 with a 2.6.8.1 kernel. I can use the special key "eject", so pbbuttons seems to work properly. But the screen never goes off... Is someone has a G4 with this feature ? Thanks.. Here's my pbbuttons.conf : # [SYSTEM] #userallowed = "paranoid"; user who is allowed to use IPC autorescan = no ; automatic rescan of event devices CmdTimeout = 4 replace_pmud = yes # [MODULE POWERSAVE] onAC_policy = performance ; nochange, performance, custom or powersave onAC_sleep = yes onAC_coversleep = yes onAC_Tsleep = yes onAC_Tdim = yes onBattery_policy = powersave onBattery_sleep = yes onBattery_coversleep = yes onBattery_Tsleep = 3000 ; time in 1/10s onBattery_Tdim = 600 ; time in 1/10s SleepKey = 116 SleepKeyDelay = 0 ; values > 0 may be dangerous, if the power key is used to trigger sleep SleepKeySleep = no ; yes=sleep, no=blank BWL_first = 22 ; first battery warnlevel, time in minutes BWL_second = 10 ; second battery warnlevel, time in minutes BWL_last = 3 ; last battery warnlevel, time in minutes Script_PMCS = "/etc/power/pmcs-pbbuttonsd %s %s" EmergencyAction = sleep ; action, if battery is critically low HeartbeatBeep = no ; beep, if nothing else showed that the computer lives CPULoad_sleeplock = yes CPULoad_min = 20 ; value in percent CPULoad_period = 20 ; time in seconds NETLoad_sleeplock = yes NETLoad_min = 4096 ; trafic in Bytes/s NETLoad_period = 20 ; time in seconds NETLoad_device = "eth0" # [MODULE DISPLAY] #LCD_Brightness = 8 ; initial LCD brightness level LCD_FadingSpeed = 5 ; 0 = no smooth fading LCD_AutoAdjust = yes ; only on Aluminum PowerBooks LCD_IllumUpKey = 225 LCD_IllumDownKey = 224 LCD_Threshold = 94 LCD_AutoAdjMin_Bat = 2 ; autoadjust parameter LCD_AutoAdjMax_Bat = 7 LCD_AutoAdjMin_AC = 1 LCD_AutoAdjMax_AC = 15 #KBD_Brightness = 0 ; initial keyboard illumination level KBD_FadingSpeed = 5 ; 0 = no smooth fading KBD_AutoAdjust = yes ; only on Aluminum PowerBooks KBD_IllumUpKey = 0 KBD_IllumDownKey = 0 KBD_IllumOnKey = 0 KBD_Threshold = 28 ; only on Aluminum PowerBooks dev_FrameBuffer = "/dev/fb0" UseFBBlank = yes DimFullyDark = yes # [MODULE OSSMIXER] #Volume = 50 ; initial volume level Speakers_muted = no ; mute after startup? VolumeUpKey = 115 VolumeDownKey = 114 MuteKey = 113 dev_Mixer = "/dev/mixer" MixerInitDelay = no MixerChannels = "volume, speaker" # [MODULE CDROM] dev_CDROM = "/dev/cdrom" EjectCDKey = 161 EjectCDKeyDelay = 0 # [MODULE PMAC] dev_PMU = "/dev/pmu" dev_ADB = "/dev/adb" TPModeUpKey = 225 + alt TPModeDownKey = 224 + alt TPMode = drag KBDMode = fkeysfirst Here's my .config... # # Automatically generated make config: don't edit # CONFIG_MMU=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_HAVE_DEC_LOCK=y CONFIG_PPC=y CONFIG_PPC32=y CONFIG_GENERIC_NVRAM=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor # CONFIG_6xx=y # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_POWER3 is not set # CONFIG_POWER4 is not set # CONFIG_8xx is not set # CONFIG_E500 is not set CONFIG_ALTIVEC=y CONFIG_TAU=y # CONFIG_TAU_INT is not set # CONFIG_TAU_AVERAGE is not set CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_PROC_INTF=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y # CONFIG_CPU_FREQ_24_API is not set CONFIG_CPU_FREQ_PMAC=y CONFIG_CPU_FREQ_TABLE=y CONFIG_PPC601_SYNC_FIX=y CONFIG_PM=y CONFIG_PPC_STD_MMU=y # # Platform options # CONFIG_PPC_MULTIPLATFORM=y # CONFIG_APUS is not set # CONFIG_WILLOW is not set # CONFIG_PCORE is not set # CONFIG_POWERPMC250 is not set # CONFIG_EV64260 is not set # CONFIG_SPRUCE is not set # CONFIG_LOPEC is not set # CONFIG_MCPN765 is not set # CONFIG_MVME5100 is not set # CONFIG_PPLUS is not set # CONFIG_PRPMC750 is not set # CONFIG_PRPMC800 is not set # CONFIG_SANDPOINT is not set # CONFIG_ADIR is not set # CONFIG_K2 is not set # CONFIG_PAL4 is not set # CONFIG_GEMINI is not set # CONFIG_EST8260 is not set # CONFIG_SBC82xx is not set # CONFIG_SBS8260 is not set # CONFIG_RPX8260 is not set # CONFIG_TQM8260 is not set # CONFIG_ADS8272 is not set # CONFIG_LITE5200 is not set CONFIG_PPC_CHRP=y CONFIG_PPC_PMAC=y CONFIG_PPC_PREP=y CONFIG_PPC_OF=y CONFIG_PPCBUG_NVRAM=y # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_HIGHMEM is not set CONFIG_KERNEL_ELF=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PROC_DEVICETREE=y CONFIG_PREP_RESIDUAL=y CONFIG_PROC_PREPRESIDUAL=y CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE="console=ttyS0,9600 console=tty0 root=/dev/sda2" # # Bus options # CONFIG_ISA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_PCI=y CONFIG_PCI_DOMAINS=y CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_PCMCIA_PROBE=y # # Advanced setup # CONFIG_ADVANCED_OPTIONS=y CONFIG_HIGHMEM_START=0xfe000000 # CONFIG_LOWMEM_SIZE_BOOL is not set CONFIG_LOWMEM_SIZE=0x30000000 # CONFIG_KERNEL_START_BOOL is not set CONFIG_KERNEL_START=0xc0000000 # CONFIG_TASK_SIZE_BOOL is not set CONFIG_TASK_SIZE=0x80000000 CONFIG_BOOT_LOAD=0x00800000 # # Device Drivers # # # Generic Driver Options # # CONFIG_STANDALONE is not set CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_MAC_FLOPPY is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_LBD=y # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set CONFIG_BLK_DEV_IDEFLOPPY=y CONFIG_BLK_DEV_IDESCSI=y # CONFIG_IDE_TASK_IOCTL is not set # CONFIG_IDE_TASKFILE_IO is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set CONFIG_BLK_DEV_SL82C105=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set CONFIG_BLK_DEV_ADMA=y # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set # CONFIG_BLK_DEV_PIIX is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set CONFIG_BLK_DEV_IDE_PMAC=y CONFIG_BLK_DEV_IDE_PMAC_ATA100FIRST=y CONFIG_BLK_DEV_IDEDMA_PMAC=y # CONFIG_BLK_DEV_IDE_PMAC_BLINK is not set CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SCSI_FC_ATTRS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AACRAID is not set CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=253 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 # CONFIG_AIC7XXX_BUILD_FIRMWARE is not set CONFIG_AIC7XXX_DEBUG_ENABLE=y CONFIG_AIC7XXX_DEBUG_MASK=0 CONFIG_AIC7XXX_REG_PRETTY_PRINT=y CONFIG_SCSI_AIC7XXX_OLD=m # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_SATA is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set CONFIG_SCSI_SYM53C8XX_2=y CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 # CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_QLOGIC_ISP is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA2XXX=y # CONFIG_SCSI_QLA21XX is not set # CONFIG_SCSI_QLA22XX is not set # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set # CONFIG_SCSI_QLA6322 is not set # CONFIG_SCSI_SYM53C416 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set CONFIG_SCSI_MESH=y CONFIG_SCSI_MESH_SYNC_RATE=5 CONFIG_SCSI_MESH_RESET_DELAY_MS=4000 CONFIG_SCSI_MAC53C94=y # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Macintosh device drivers # CONFIG_ADB=y CONFIG_ADB_CUDA=y CONFIG_ADB_PMU=y CONFIG_PMAC_PBOOK=y CONFIG_PMAC_APM_EMU=y CONFIG_PMAC_BACKLIGHT=y CONFIG_ADB_MACIO=y CONFIG_INPUT_ADBHID=y CONFIG_MAC_EMUMOUSEBTN=y CONFIG_THERM_WINDTUNNEL=m CONFIG_THERM_ADT746X=m # CONFIG_ANSLCD is not set # # Networking support # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set # CONFIG_NETLINK_DEV is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # # IP: Virtual Server Configuration # # CONFIG_IP_VS is not set # CONFIG_IPV6 is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=m CONFIG_IP_NF_FTP=m CONFIG_IP_NF_IRC=m CONFIG_IP_NF_TFTP=m CONFIG_IP_NF_AMANDA=m # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_LIMIT=m CONFIG_IP_NF_MATCH_IPRANGE=m CONFIG_IP_NF_MATCH_MAC=m CONFIG_IP_NF_MATCH_PKTTYPE=m CONFIG_IP_NF_MATCH_MARK=m CONFIG_IP_NF_MATCH_MULTIPORT=m CONFIG_IP_NF_MATCH_TOS=m CONFIG_IP_NF_MATCH_RECENT=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_DSCP=m CONFIG_IP_NF_MATCH_AH_ESP=m CONFIG_IP_NF_MATCH_LENGTH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_TCPMSS=m CONFIG_IP_NF_MATCH_HELPER=m CONFIG_IP_NF_MATCH_STATE=m CONFIG_IP_NF_MATCH_CONNTRACK=m CONFIG_IP_NF_MATCH_OWNER=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_SAME=m # CONFIG_IP_NF_NAT_LOCAL is not set CONFIG_IP_NF_NAT_SNMP_BASIC=m CONFIG_IP_NF_NAT_IRC=m CONFIG_IP_NF_NAT_FTP=m CONFIG_IP_NF_NAT_TFTP=m CONFIG_IP_NF_NAT_AMANDA=m # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_TARGET_LOG is not set # CONFIG_IP_NF_TARGET_ULOG is not set CONFIG_IP_NF_TARGET_TCPMSS=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m CONFIG_IP_NF_COMPAT_IPCHAINS=m # CONFIG_IP_NF_COMPAT_IPFWADM is not set CONFIG_IP_NF_TARGET_NOTRACK=m CONFIG_IP_NF_RAW=m # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_REALM is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_MACE is not set CONFIG_BMAC=y # CONFIG_HAPPYMEAL is not set CONFIG_SUNGEM=y # CONFIG_NET_VENDOR_3COM is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # # CONFIG_NET_TULIP is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set # CONFIG_NET_PCI is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SK98LIN is not set # CONFIG_TIGON3 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # # Obsolete Wireless cards support (pre-802.11) # # CONFIG_STRIP is not set # CONFIG_ARLAN is not set # CONFIG_WAVELAN is not set # # Wireless 802.11b ISA/PCI cards support # # CONFIG_AIRO is not set CONFIG_HERMES=m CONFIG_APPLE_AIRPORT=m # CONFIG_PLX_HERMES is not set # CONFIG_TMD_HERMES is not set # CONFIG_PCI_HERMES is not set # CONFIG_ATMEL is not set # # Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support # # CONFIG_PRISM54 is not set CONFIG_NET_WIRELESS=y # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y CONFIG_INPUT_EVBUG=y # # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_PMACZILOG is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # CONFIG_QIC02_TAPE is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set CONFIG_NVRAM=y CONFIG_GEN_RTC=y # CONFIG_GEN_RTC_X is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_RAW_DRIVER is not set # # I2C support # CONFIG_I2C=y CONFIG_I2C_CHARDEV=y # # I2C Algorithms # CONFIG_I2C_ALGOBIT=y # CONFIG_I2C_ALGOPCF is not set # # I2C Hardware Bus support # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_ELEKTOR is not set # CONFIG_I2C_HYDRA is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_I810 is not set # CONFIG_I2C_ISA is not set CONFIG_I2C_KEYWEST=y # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_PROSAVAGE is not set # CONFIG_I2C_SAVAGE4 is not set # CONFIG_SCx200_ACB is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # CONFIG_I2C_VOODOO3 is not set # # Hardware Sensors Chip support # # CONFIG_I2C_SENSOR is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83627HF is not set # # Other I2C Chip support # # CONFIG_SENSORS_EEPROM is not set # CONFIG_SENSORS_PCF8574 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_RTC8564 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Misc devices # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set CONFIG_FB_OF=y CONFIG_FB_CONTROL=y CONFIG_FB_PLATINUM=y CONFIG_FB_VALKYRIE=y CONFIG_FB_CT65550=y CONFIG_FB_ASILIANT=y CONFIG_FB_IMSTT=y # CONFIG_FB_VGA16 is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set CONFIG_FB_RADEON=y CONFIG_FB_RADEON_I2C=y # CONFIG_FB_RADEON_DEBUG is not set CONFIG_FB_ATY128=y CONFIG_FB_ATY=y CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GX=y # CONFIG_FB_ATY_XL_INIT is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y # CONFIG_FONT_8x8 is not set # CONFIG_FONT_8x16 is not set CONFIG_FONT_6x11=y # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set # CONFIG_FONT_MINI_4x6 is not set # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # # Sound # CONFIG_SOUND=m CONFIG_DMASOUND_PMAC=m CONFIG_DMASOUND=m # # Advanced Linux Sound Architecture # CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_SEQUENCER_OSS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # ISA devices # # CONFIG_SND_AD1848 is not set # CONFIG_SND_CS4231 is not set CONFIG_SND_CS4232=m # CONFIG_SND_CS4236 is not set # CONFIG_SND_ES1688 is not set # CONFIG_SND_ES18XX is not set # CONFIG_SND_GUSCLASSIC is not set # CONFIG_SND_GUSEXTREME is not set # CONFIG_SND_GUSMAX is not set # CONFIG_SND_INTERWAVE is not set # CONFIG_SND_INTERWAVE_STB is not set # CONFIG_SND_OPTI92X_AD1848 is not set # CONFIG_SND_OPTI92X_CS4231 is not set # CONFIG_SND_OPTI93X is not set # CONFIG_SND_SB8 is not set # CONFIG_SND_SB16 is not set # CONFIG_SND_SBAWE is not set # CONFIG_SND_WAVEFRONT is not set # CONFIG_SND_CMI8330 is not set # CONFIG_SND_OPL3SA2 is not set # CONFIG_SND_SGALAXY is not set # CONFIG_SND_SSCAPE is not set # # PCI devices # # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set # CONFIG_SND_INTEL8X0 is not set # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VX222 is not set # # ALSA PowerMac devices # CONFIG_SND_POWERMAC=m # # ALSA USB devices # CONFIG_SND_USB_AUDIO=m # # Open Sound System # # CONFIG_SOUND_PRIME is not set # # USB support # CONFIG_USB=y # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_DYNAMIC_MINORS is not set # # USB Host Controller Drivers # # CONFIG_USB_EHCI_HCD is not set CONFIG_USB_OHCI_HCD=y # CONFIG_USB_UHCI_HCD is not set # # USB Device Class drivers # # CONFIG_USB_AUDIO is not set # CONFIG_USB_BLUETOOTH_TTY is not set # CONFIG_USB_MIDI is not set CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_RW_DETECT is not set # CONFIG_USB_STORAGE_DATAFAB is not set CONFIG_USB_STORAGE_FREECOM=y # CONFIG_USB_STORAGE_ISD200 is not set CONFIG_USB_STORAGE_DPCM=y # CONFIG_USB_STORAGE_HP8200e is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # # USB Human Interface Devices (HID) # CONFIG_USB_HID=y CONFIG_USB_HIDINPUT=y # CONFIG_HID_FF is not set # CONFIG_USB_HIDDEV is not set # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_MTOUCH is not set # CONFIG_USB_EGALAX is not set # CONFIG_USB_XPAD is not set # CONFIG_USB_ATI_REMOTE is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_HPUSBSCSI is not set # # USB Multimedia devices # # CONFIG_USB_DABUSB is not set # # Video4Linux support is needed for USB Multimedia device support # # # USB Network adaptors # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set # # USB port drivers # # # USB Serial Converter support # CONFIG_USB_SERIAL=m # CONFIG_USB_SERIAL_GENERIC is not set # CONFIG_USB_SERIAL_BELKIN is not set # CONFIG_USB_SERIAL_WHITEHEAT is not set # CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set # CONFIG_USB_SERIAL_EMPEG is not set # CONFIG_USB_SERIAL_FTDI_SIO is not set CONFIG_USB_SERIAL_VISOR=m # CONFIG_USB_SERIAL_IPAQ is not set # CONFIG_USB_SERIAL_IR is not set # CONFIG_USB_SERIAL_EDGEPORT is not set # CONFIG_USB_SERIAL_EDGEPORT_TI is not set # CONFIG_USB_SERIAL_KEYSPAN_PDA is not set CONFIG_USB_SERIAL_KEYSPAN=m # CONFIG_USB_SERIAL_KEYSPAN_MPR is not set CONFIG_USB_SERIAL_KEYSPAN_USA28=y CONFIG_USB_SERIAL_KEYSPAN_USA28X=y # CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set CONFIG_USB_SERIAL_KEYSPAN_USA19=y CONFIG_USB_SERIAL_KEYSPAN_USA18X=y CONFIG_USB_SERIAL_KEYSPAN_USA19W=y # CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set CONFIG_USB_SERIAL_KEYSPAN_USA49W=y # CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set # CONFIG_USB_SERIAL_KLSI is not set # CONFIG_USB_SERIAL_KOBIL_SCT is not set # CONFIG_USB_SERIAL_MCT_U232 is not set # CONFIG_USB_SERIAL_PL2303 is not set # CONFIG_USB_SERIAL_SAFE is not set # CONFIG_USB_SERIAL_CYBERJACK is not set # CONFIG_USB_SERIAL_XIRCOM is not set # CONFIG_USB_SERIAL_OMNINET is not set CONFIG_USB_EZUSB=y # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_TIGL is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGETSERVO is not set # CONFIG_USB_TEST is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y # CONFIG_JOLIET is not set # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_DEVFS_MOUNT=y # CONFIG_DEVFS_DEBUG is not set # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V4 is not set # CONFIG_NFS_DIRECTIO is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V4 is not set CONFIG_NFSD_TCP=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=m # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_DEBUG_KERNEL is not set CONFIG_BOOTX_TEXT=y # # Security options # # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set |
|
From: Matthias G. <mat...@ht...> - 2004-11-05 16:32:18
|
Hi. A new PBButtons release was born. This release fixes some annoying bugs. The cover status will now be detected correctly after sleep. Furthermore the LMU detection routine has slightly be modified to cope better with recent PowerBooks. Last but not least the availableness of the power source signal has been increased on PowerBooks with PMU version 12 and later. see: http://pbbuttons.sourceforge.net Best Regards Matthias |
|
From: Matthias G. <mat...@us...> - 2004-09-27 15:15:56
|
Am Mittwoch, 15. September 2004 13:25 schrieb Pierre Habouzit:
> on my brand new 15" powerbook 1.5 GHz the pbbutons fail to detect the
> right device for getting the env light ...
>
> it llops on devices from 0 to 255 to find one that match. the thing is
> it seems to choose the i2c-0 whereas on my pbook it's the i2c-4 ...
>
> I've patched pbbuttonsd sources in otder to make the function
> find_lmu_dev or whatever its name is to loop from 4 instead of 0 and it
> works ...
I prepared some patches so solve the problem: One patch is for the version
0.6.3a (currently debian unstable) and the other one for version 0.6.5
(currently debian experimental).
The patch for version 0.6.5 also fixes the backlight bug after cover
close/open.
Especially regarding the keyboard backlight problem I need feedback from you
if it works correctly now. Please mention your machine type and the used i2c
device in your feedback. Thanks.
I will release a bugfix release after receiving your positive feedback.
Best Regards
Matthias
|
|
From: Matthias G. <mat...@us...> - 2004-09-17 11:49:43
|
Am Donnerstag, 16. September 2004 20:01 schrieben Sie:
> sure, I'll do what I can.
> the thing is I'm sure it thinks /dev/i2c-0 is the one he wants, whereas
> it's in fact the i2c-4
Thanks, this might help to make detection safe.
> btw, why don't you use sysfs to know wich device you want ? because (my
> pb is off atm, I'll see later which name it was) the name of the device
> for lmu is really caracteristic...
That's quit easy: Pbbuttonsd has also to run under kernel 2.4 and sysfs is a
kernel 2.6 thing.
Best Regards
Matthias
|
|
From: Pierre H. <pie...@m4...> - 2004-09-16 19:54:20
|
> sure, I'll do what I can.
> the thing is I'm sure it thinks /dev/i2c-0 is the one he wants,
> whereas it's in fact the i2c-4
>
> btw, why don't you use sysfs to know wich device you want ? because
> (my pb is off atm, I'll see later which name it was) the name of the
> device for lmu is really caracteristic...
here are some things you asked for.
I've not had the time for the debug wrt i2c you asked for.
but One thing I find useful is the info given by the udevruler tool (and
the 'right' device for me seems to be i2c-4) :
i2c-0 : SYSFS{dev}="89:0"
SYSFS{name}="monid"
BUS="pci"
ID="0000:00:10.0"
SYSFS{class}="0x030000"
SYSFS{detach_state}="0"
SYSFS{device}="0x4e50"
SYSFS{devspec}="/pci@f0000000/ATY,JasperParent@10"
SYSFS{irq}="48"
SYSFS{subsystem_device}="0x4e50"
SYSFS{subsystem_vendor}="0x1002"
SYSFS{vendor}="0x1002"
i2c-1: SYSFS{dev}="89:1"
SYSFS{name}="dvi"
BUS="pci"
<same as previous>
i2c-2: SYSFS{dev}="89:2"
SYSFS{name}="vga"
BUS="pci"
<same as previous>
i2c-3: SYSFS{dev}="89:3"
SYSFS{name}="crt2"
BUS="pci"
<same as previous>
i2c-4: SYSFS{dev}="89:4"
SYSFS{name}="uni-n 0"
BUS="of_platform"
ID="uni-n-i2c"
SYSFS{detach_state}="0"
SYSFS{devspec}="/uni-n@f8000000/i2c@f8001000"
i2c-5: SYSFS{dev}="89:5"
SYSFS{name}="uni-n 1"
BUS="of_platform"
ID="uni-n-i2c"
SYSFS{detach_state}="0"
SYSFS{devspec}="/uni-n@f8000000/i2c@f8001000"
i2c-6: SYSFS{dev}="89:6"
SYSFS{name}="mac-io 0"
BUS="macio"
ID="0.00018000:i2c"
SYSFS{detach_state}="0"
SYSFS{devspec}="/pci@f2000000/mac-io@17/i2c@18000"
BUS="macio"
ID="0.80000000:mac-io"
SYSFS{detach_state}="0"
SYSFS{devspec}="/pci@f2000000/mac-io@17"
BUS="pci"
ID="0001:01:17.0"
SYSFS{class}="0xff0000"
SYSFS{detach_state}="0"
SYSFS{device}="0x003e"
SYSFS{devspec}="/pci@f2000000/mac-io@17"
SYSFS{irq}="0"
SYSFS{subsystem_device}="0x0000"
SYSFS{subsystem_vendor}="0x0000"
SYSFS{vendor}="0x106b"
--
Pierre Habouzit http://www.madism.org/
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
gpg : 1024D/A1EE761C 6045 409E 5CB5 2CEA 3E70 F17E C41E 995C C98C 90BE
spam: mad...@ma...
|
|
From: Pierre H. <pie...@m4...> - 2004-09-16 18:01:21
|
Le Jeu 16 Septembre 2004 17:43, Matthias Grimm a =E9crit : > Am Mittwoch, 15. September 2004 13:25 schrieb Pierre Habouzit: > > on my brand new 15" powerbook 1.5 GHz the pbbutons fail to detect > > the right device for getting the env light ... > > > > it llops on devices from 0 to 255 to find one that match. the thing > > is it seems to choose the i2c-0 whereas on my pbook it's the i2c-4 > > ... > > > > I've patched pbbuttonsd sources in otder to make the function > > find_lmu_dev or whatever its name is to loop from 4 instead of 0 > > and it works ... > > Could you please provide some additional information about i2c > devices installed in your system? Contents of /proc/???/i2c, > /sys/bus/i2c, log-files, /proc/cpu, etc. > > Pbbuttonsd reads 4 bytes from the i2c-dev and checks if it get 4. It > would be interesting what has been read. Maybe you could add some > debug code in your copy, print the contents of the 4 bytes to console > and send it to me. > > All this could help to improve LMU detection. > > Best Regards > Matthias sure, I'll do what I can. the thing is I'm sure it thinks /dev/i2c-0 is the one he wants, whereas=20 it's in fact the i2c-4 btw, why don't you use sysfs to know wich device you want ? because (my=20 pb is off atm, I'll see later which name it was) the name of the device=20 for lmu is really caracteristic... =2D-=20 Pierre Habouzit http://www.madism.org/ =2D=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--= =3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D- gpg : 1024D/A1EE761C 6045 409E 5CB5 2CEA 3E70 F17E C41E 995C C98C 90BE=20 spam: mad...@ma... |
|
From: Matthias G. <mat...@us...> - 2004-09-16 15:45:01
|
Am Mittwoch, 15. September 2004 13:25 schrieb Pierre Habouzit:
> on my brand new 15" powerbook 1.5 GHz the pbbutons fail to detect the
> right device for getting the env light ...
>
> it llops on devices from 0 to 255 to find one that match. the thing is
> it seems to choose the i2c-0 whereas on my pbook it's the i2c-4 ...
>
> I've patched pbbuttonsd sources in otder to make the function
> find_lmu_dev or whatever its name is to loop from 4 instead of 0 and it
> works ...
Could you please provide some additional information about i2c devices
installed in your system? Contents of /proc/???/i2c, /sys/bus/i2c,
log-files, /proc/cpu, etc.
Pbbuttonsd reads 4 bytes from the i2c-dev and checks if it get 4. It would be
interesting what has been read. Maybe you could add some debug code in your
copy, print the contents of the 4 bytes to console and send it to me.
All this could help to improve LMU detection.
Best Regards
Matthias
|
|
From: Pierre H. <pie...@m4...> - 2004-09-15 11:25:13
|
on my brand new 15" powerbook 1.5 GHz the pbbutons fail to detect the=20 right device for getting the env light ... it llops on devices from 0 to 255 to find one that match. the thing is=20 it seems to choose the i2c-0 whereas on my pbook it's the i2c-4 ... I've patched pbbuttonsd sources in otder to make the function=20 find_lmu_dev or whatever its name is to loop from 4 instead of 0 and it=20 works ... cheers, PS: Cc me as I'm not on the list =2D-=20 Pierre Habouzit http://www.madism.org/ =2D=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--= =3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D- gpg : 1024D/A1EE761C 6045 409E 5CB5 2CEA 3E70 F17E C41E 995C C98C 90BE=20 spam: mad...@ma... |
|
From: Matthias G. <mat...@us...> - 2004-09-10 08:52:44
|
Hi. A new PBButtons release was born. This release has got a restructuredpower management configuration to support more powersave modes and to allow better fine tuning. The PMCS interface changes slightly but in a compatible way. Suspend-to-disk now is supported and the sleepkey could trigger different actions depending on power source. Old configuration files could still be used but they will be updated next time the configuration file is written. Furtheron the CDROM module will close the tray again if it is already open and the drive supports this. see: http://pbbuttons.sourceforge.net Best Regards Matthias |
|
From: Matthias G. <mat...@us...> - 2004-09-10 08:52:44
|
Hi A new GTKPbbuttons release was born. The main new part of GTKPBButtons is the new 'Crystal' theme from Johannes Kanefendt, many thanks to him. Furthermore it shows a special message if the CDROM closes and a bug in the brightness popup was fixed. see: http://pbbuttons.sourceforge.net Best Regards Matthias |
|
From: Matthias G. <mat...@us...> - 2004-09-10 08:52:43
|
Hi Powerprefs now suports the new restructured power management configuration and all other new options of the server. All power management modes could be adjusted with a comfortable GUI as usual. see: http://pbbuttons.sourceforge.net Best Regards Matthias |
|
From: Matthias G. <mat...@us...> - 2004-08-29 11:47:51
|
Hi,
I have joined the development branch and the stable tree. The result could be
downloaded from CVS for beta testing.
This version contain a new power management configuration scheme that is much
more flexible and supports suspend-to-disk. The old configuration still works
but is marked as depreciated.
Please test this version and report problems and bugs.
Thanks and best regards
Matthias
|
|
From: Matthias G. <mat...@us...> - 2004-08-26 13:53:22
|
Hi, PBButtons has a new home in WWW: http://pbbuttons.sourceforge.net My old web host has given up business and switched off all his servers during the last days. Since then PBButtons have not been available in the web anymore but this changes now. I hope Sourceforge will do for a while. ;-) I used this break to slightly update the website's design. It is more straight forward now. Feel free to have a look. Best Regards Matthias |
|
From: Matthias G. <mat...@us...> - 2004-08-10 20:07:24
|
Am Montag, 9. August 2004 18:05 schrieb Wolfram Quester:
Hi,
> Thanks for considering my suggestions. Unfortunately I had no time to
> try the new feature since my last question. But I tried to find
> Documentation about the pmu on the net for a while but couldn't find
> one. Do you have a link to specifications or such? The reason why I ask
> is because I noticed on a toshiba notebook I get a time in /proc/apm if
> AC is plugged in which give me the time how long battery charging will
> take. I thought about changing apm-emu.c so that we have this on
> PowerBooks also, but the time in /proc/pmu/battery_0 seems quite wrong.
Sorry, but all I know about the PMU is from various programs using the PMU
like pmud, the kernel sources, the darwin sources and some try and error.
The Apple developer network is not very usefull regarding hardware issues.
Mostly they describe the MacOSX API, which we can't use.
I never did exact measurements but I hadn't the feeling that the charge time
in /proc/pmu is very inaccurate. The time comes from the battery and drifts
over lifetime. The battery needs recalibration from time to time to reflect
battery degrading.
I'm sorry that I can't tell you more
Best Regards
Matthias
|
|
From: Wolfram Q. <wo...@mi...> - 2004-08-09 16:06:02
|
Hi Matthias! On Sun, Aug 01, 2004 at 01:27:14PM +0200, Matthias Grimm wrote: > Am Donnerstag, 29. Juli 2004 09:04 schrieb Matthias Grimm: >=20 > Hi, > It is now a branch called 'devel' in CVS which will contain the latest wo= rk in=20 > progress. Be carefull using this version in production environments. The = code=20 > is not finished yet and may contain errors. Also the documentation may no= t=20 > cover the new features. >=20 > I will ensure that the source will compile and doesn't crash immediately = after=20 > startup ;-) Keep in mind: This is work in progress. Thanks for considering my suggestions. Unfortunately I had no time to try the new feature since my last question. But I tried to find Documentation about the pmu on the net for a while but couldn't find one. Do you have a link to specifications or such? The reason why I ask is because I noticed on a toshiba notebook I get a time in /proc/apm if AC is plugged in which give me the time how long battery charging will take. I thought about changing apm-emu.c so that we have this on PowerBooks also, but the time in /proc/pmu/battery_0 seems quite wrong. With best wishes, Wolfi >=20 > Best Regards > Matthias >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > pbbuttons-users mailing list > pbb...@li... > https://lists.sourceforge.net/lists/listinfo/pbbuttons-users |
|
From: Matthias G. <mat...@us...> - 2004-08-03 13:43:42
|
Am Montag, 2. August 2004 21:26 schrieb Brian Sammon:
> Are there any battery monitor apps that work with pbbuttons?
> I'd like an application that displays the power level in percent. Ideally,
> something that looks like xapm (or as a second choice, batmon).
>
> Also, I'm thinking about modifying xapm to use pbbuttons. They only way I
> could think of to do it was to have it read from /proc/pmu/ . Any better
> ideas? Any suggestions?
There are some old battery monitors out that uses pmuds socket interface
directly. In that days this was necessary because only pmud provides
information about battery status.
Today there are better inerfaces available that are more robust against
hardware changes. A battery monitor could and should use one of this:
1. /proc/pmu/battery_?.
Avaliable only on PowerPC. All releated battery data is availabe in an easy to
parse text file. A battery monitor (the one I know of, there might be more)
that uses this interface is gkrellm-pmu.
2. /proc/apm
This interface in usually known from i386 hardware. Pmud is able to emulate
this interface but nowadays this job has been taken over by the kernel. If
the apm emulation has been compiled in or the module has been loaded the
kernel provides battery data in /proc/apm and due to this most of the battery
monitors originally written for i386 laptops based on APM also work on Apple
Powerbooks without changes.
If your favourite battery monitor rely on pmud and doesn't support one of the
newer interfaces you have two choices:
1. You continue to use pmud and your unmodified battery monitor or
2. you patch the battery monitor to use one of the new interfaces. The code
for getting battery information from /proc/pmu/ could be lent from
gkrellm-pmu. Version 1.4 also contains code to use /proc/apm.
Pbbuttonsd also uses /proc/pmu/ for battery information and I think a battery
monitor should work independently of the used power management daemon. There
is no need for any dependency due to the very good and easy accessible kernel
support
Best Regards
Matthias
|
|
From: <dj...@de...> - 2004-08-02 20:14:00
|
[ Argh, SF didn't liked my From address, resending as fwd ] On Mon, Aug 02, 2004 at 03:26:33PM -0400, Brian Sammon wrote: > Are there any battery monitor apps that work with pbbuttons? > I'd like an application that displays the power level in percent. Ideally, something that looks like xapm (or as a second choice, batmon). I use xpmumon > Also, I'm thinking about modifying xapm to use pbbuttons. They only way I could think of to do it was to have it read from /proc/pmu/ . > Any better ideas? Any suggestions? > > I'm running debian. The debian pbbuttons maintainer believes that pbbuttons > is enough of a replacement for pmud that he has put "Conflicts: pmud" in the > configuration of the pbbuttons package. I've recently taken over the maintainance of the pbbuttonsd package. I haven't had the time yet to investigate if one could drop this conflict. Please note that the whole discussion in #249501 was between a user and the upstream maintainer, not the Debian one. Gruesse, -- Frank Lichtenheld <fr...@li...> www: http://www.djpig.de/ |
