* [PATCH] eeepc-laptop: enable camera by default @ 2009-06-05 8:59 Pekka J Enberg 2009-06-05 11:46 ` Corentin Chary 2009-06-05 20:08 ` Andrew Morton 0 siblings, 2 replies; 32+ messages in thread From: Pekka J Enberg @ 2009-06-05 8:59 UTC (permalink / raw) To: corentincj; +Cc: acpi4asus-user, len.brown, linux-kernel From: Pekka Enberg <penberg@cs.helsinki.fi> If we leave the camera disabled by default, userspace programs (e.g. Skype, Cheese) leave the user out in the cold saying that the machine "has no camera." Therefore, it's better to enable camera by default and let people who really don't want it just disable the thing. Cc: <acpi4asus-user@lists.sourceforge.net> Cc: Len Brown <len.brown@intel.com> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> --- drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c index 353a898..c0f8eb1 100644 --- a/drivers/platform/x86/eeepc-laptop.c +++ b/drivers/platform/x86/eeepc-laptop.c @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, enum rfkill_state *state) } /* + * Camera helpers + */ + +static void eeepc_enable_camera(void) +{ + int err; + + err = set_acpi(CM_ASL_CAMERA, 1); + if (err) + printk(EEEPC_WARNING "Unable to enable camera %d\n", err); +} + +/* * Sys helpers */ static int parse_arg(const char *buf, unsigned long count, int *val) @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) result = eeepc_hwmon_init(dev); if (result) goto fail_hwmon; + + eeepc_enable_camera(); + /* Register platform stuff */ result = platform_driver_register(&platform_driver); if (result) -- 1.5.6.3 ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 8:59 [PATCH] eeepc-laptop: enable camera by default Pekka J Enberg @ 2009-06-05 11:46 ` Corentin Chary 2009-06-05 12:44 ` Pekka Enberg 2009-06-05 21:01 ` Woody Suwalski 2009-06-05 20:08 ` Andrew Morton 1 sibling, 2 replies; 32+ messages in thread From: Corentin Chary @ 2009-06-05 11:46 UTC (permalink / raw) To: Pekka J Enberg; +Cc: acpi4asus-user, len.brown, linux-kernel On Fri, Jun 5, 2009 at 10:59 AM, Pekka J Enberg<penberg@cs.helsinki.fi> wrote: > From: Pekka Enberg <penberg@cs.helsinki.fi> > > If we leave the camera disabled by default, userspace programs (e.g. > Skype, Cheese) leave the user out in the cold saying that the machine "has > no camera." Therefore, it's better to enable camera by default and let > people who really don't want it just disable the thing. > > Cc: <acpi4asus-user@lists.sourceforge.net> > Cc: Len Brown <len.brown@intel.com> > Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> > --- > drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ > 1 files changed, 16 insertions(+), 0 deletions(-) > > diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c > index 353a898..c0f8eb1 100644 > --- a/drivers/platform/x86/eeepc-laptop.c > +++ b/drivers/platform/x86/eeepc-laptop.c > @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, enum rfkill_state *state) > } > > /* > + * Camera helpers > + */ > + > +static void eeepc_enable_camera(void) > +{ > + int err; > + > + err = set_acpi(CM_ASL_CAMERA, 1); > + if (err) > + printk(EEEPC_WARNING "Unable to enable camera %d\n", err); > +} > + > +/* > * Sys helpers > */ > static int parse_arg(const char *buf, unsigned long count, int *val) > @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) > result = eeepc_hwmon_init(dev); > if (result) > goto fail_hwmon; > + > + eeepc_enable_camera(); > + > /* Register platform stuff */ > result = platform_driver_register(&platform_driver); > if (result) > -- > 1.5.6.3 > > Hi, First, I think a one line set_acpi(CM_ASL_CAMERA, 1); with a small comment is better. (If it fails, it's because there no camera, so we don't mind). Anyway, I'm not sure it's a good idea to enable the camera by default. It depends how many power the camera is using (when idle). Coud you check that (with power top maybe ?). Thanks -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 11:46 ` Corentin Chary @ 2009-06-05 12:44 ` Pekka Enberg 2009-06-05 13:02 ` Corentin Chary 2009-06-05 21:01 ` Woody Suwalski 1 sibling, 1 reply; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 12:44 UTC (permalink / raw) To: Corentin Chary; +Cc: acpi4asus-user, len.brown, linux-kernel Hi Corentin, On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: > First, I think a one line > set_acpi(CM_ASL_CAMERA, 1); > with a small comment is better. (If it fails, it's because there no > camera, so we don't mind). OK, I've included an updated version of the patch. On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: > Anyway, I'm not sure it's a good idea to enable the camera by default. > It depends how many power the camera is using (when idle). Coud you > check that (with power top maybe ?). People who prefer power savings over functional camera can always disable it. If you look at the amount of "my camera doesn't" work bug reports, I think it's pretty evident that we should enable it by default or provide a config option that does it. That said, I am more than happy to measure this but I need a little bit more information to get started as I have never used powertop. So what is it exactly you want me to do? Pekka >From 8a0abd12147c18e8cbc939134af5ae40b44300f0 Mon Sep 17 00:00:00 2001 From: Pekka Enberg <penberg@cs.helsinki.fi> Date: Fri, 5 Jun 2009 11:30:07 +0300 Subject: [PATCH] eeepc-laptop: enable camera by default If we leave the camera disabled by default, userspace programs (e.g. Skype, Cheese) leave the user out in the cold saying that the machine "has no camera." Therefore, it's better to enable camera by default and let people who really don't want it just disable the thing. Cc: <acpi4asus-user@lists.sourceforge.net> Cc: Len Brown <len.brown@intel.com> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> --- drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c index 353a898..6a8426f 100644 --- a/drivers/platform/x86/eeepc-laptop.c +++ b/drivers/platform/x86/eeepc-laptop.c @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, enum rfkill_state *state) } /* + * Camera helpers + */ + +static void eeepc_enable_camera(void) +{ + /* + * If the following call to set_acpi() fails, it's because there's no + * camera so we can ignore the error. + */ + set_acpi(CM_ASL_CAMERA, 1); +} + +/* * Sys helpers */ static int parse_arg(const char *buf, unsigned long count, int *val) @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) result = eeepc_hwmon_init(dev); if (result) goto fail_hwmon; + + eeepc_enable_camera(); + /* Register platform stuff */ result = platform_driver_register(&platform_driver); if (result) -- 1.5.6.3 ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 12:44 ` Pekka Enberg @ 2009-06-05 13:02 ` Corentin Chary 2009-06-05 13:39 ` Alan Jenkins 2009-06-05 13:51 ` Pekka Enberg 0 siblings, 2 replies; 32+ messages in thread From: Corentin Chary @ 2009-06-05 13:02 UTC (permalink / raw) To: Pekka Enberg; +Cc: acpi4asus-user, len.brown, linux-kernel On Fri, Jun 5, 2009 at 2:44 PM, Pekka Enberg<penberg@cs.helsinki.fi> wrote: > Hi Corentin, > > On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: >> First, I think a one line >> set_acpi(CM_ASL_CAMERA, 1); >> with a small comment is better. (If it fails, it's because there no >> camera, so we don't mind). > > OK, I've included an updated version of the patch. > > On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: >> Anyway, I'm not sure it's a good idea to enable the camera by default. >> It depends how many power the camera is using (when idle). Coud you >> check that (with power top maybe ?). > > People who prefer power savings over functional camera can always > disable it. If you look at the amount of "my camera doesn't" work bug > reports, I think it's pretty evident that we should enable it by default > or provide a config option that does it. Ok, your right, I'll apply that one > That said, I am more than happy to measure this but I need a little bit > more information to get started as I have never used powertop. So what > is it exactly you want me to do? PowerTop (with a corretly configured kernel) will give you a power usage estimate. CONFIG_NO_HZ=y CONFIG_TIMER_STATS=y CONFIG_DEBUG_KERNEL=y For propers results, shutdown all services and just keep a shell (without X or network). You can also test that with and without the camera driver. -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 13:02 ` Corentin Chary @ 2009-06-05 13:39 ` Alan Jenkins 2009-06-05 13:51 ` Pekka Enberg 1 sibling, 0 replies; 32+ messages in thread From: Alan Jenkins @ 2009-06-05 13:39 UTC (permalink / raw) To: Corentin Chary; +Cc: Pekka Enberg, acpi4asus-user, len.brown, linux-kernel On 6/5/09, Corentin Chary <corentin.chary@gmail.com> wrote: > On Fri, Jun 5, 2009 at 2:44 PM, Pekka Enberg<penberg@cs.helsinki.fi> wrote: >> Hi Corentin, >> >> On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: >>> First, I think a one line >>> set_acpi(CM_ASL_CAMERA, 1); >>> with a small comment is better. (If it fails, it's because there no >>> camera, so we don't mind). >> >> OK, I've included an updated version of the patch. >> >> On Fri, 2009-06-05 at 13:46 +0200, Corentin Chary wrote: >>> Anyway, I'm not sure it's a good idea to enable the camera by default. >>> It depends how many power the camera is using (when idle). Coud you >>> check that (with power top maybe ?). >> >> People who prefer power savings over functional camera can always >> disable it. If you look at the amount of "my camera doesn't" work bug >> reports, I think it's pretty evident that we should enable it by default >> or provide a config option that does it. > > Ok, your right, I'll apply that one > >> That said, I am more than happy to measure this but I need a little bit >> more information to get started as I have never used powertop. So what >> is it exactly you want me to do? > > PowerTop (with a corretly configured kernel) will give you a power > usage estimate. > > CONFIG_NO_HZ=y > CONFIG_TIMER_STATS=y > CONFIG_DEBUG_KERNEL=y > > For propers results, shutdown all services and just keep a shell > (without X or network). > You can also test that with and without the camera driver. Hmm, this relies on good acpi battery information, I hope your EeePC is better than mine in that regard. The ideal solution is if USB auto-suspend could be used to save the same amount. Google says there was a patch for uvcvideo last year [1]. I'll see what the current status is on my model and report back :-). [1] <http://lists.berlios.de/pipermail/linux-uvc-devel/2008-January/002707.html> Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 13:02 ` Corentin Chary 2009-06-05 13:39 ` Alan Jenkins @ 2009-06-05 13:51 ` Pekka Enberg 2009-06-05 13:54 ` Pekka Enberg ` (2 more replies) 1 sibling, 3 replies; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 13:51 UTC (permalink / raw) To: Corentin Chary; +Cc: acpi4asus-user, len.brown, linux-kernel, Alan Jenkins Hi Corentin, On Fri, 2009-06-05 at 15:02 +0200, Corentin Chary wrote: > > That said, I am more than happy to measure this but I need a little bit > > more information to get started as I have never used powertop. So what > > is it exactly you want me to do? > > PowerTop (with a corretly configured kernel) will give you a power > usage estimate. > > CONFIG_NO_HZ=y > CONFIG_TIMER_STATS=y > CONFIG_DEBUG_KERNEL=y > > For propers results, shutdown all services and just keep a shell > (without X or network). > You can also test that with and without the camera driver. I did not see a power usage estimate. I am running PowerTOP 1.11 that comes with Ubuntu 9.04. So I am not sure if what I did is what you wanted me to do but I ran "powertop -t 60 -d" with camera enabled and disabled and here are the results. Also, when I run plain powertop, it keeps complaining that some USB device causes wakeups (probably the camera?) and suggests suspending. But doing that doesn't seem to help things. Pekka Camera Disabled --------------- $ powertop -t 60 -d PowerTOP 1.11 (C) 2007, 2008 Intel Corporation Collecting data for 60 seconds Cn Avg residency C0 (cpu running) ( 0.0%) polling 0.0ms ( 0.0%) C1 0.0ms ( 0.0%) C2 0.9ms ( 0.0%) C3 966.9ms (100.1%) P-states (frequencies) Wakeups-from-idle per second : 1.2 interval: 60.0s no ACPI power usage estimate available Top causes for wakeups: 37.1% ( 0.6) <kernel core> : hrtimer_start (tick_sched_timer) 16.5% ( 0.3) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer) 12.4% ( 0.2) <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 8.2% ( 0.1) <interrupt> : acpi 6.2% ( 0.1) <kernel core> : sta_info_start (sta_info_cleanup) 4.1% ( 0.1) <interrupt> : ata_piix 4.1% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn) 4.1% ( 0.1) events/0 : queue_delayed_work (delayed_work_timer_fn) 1.0% ( 0.0) <interrupt> : PS/2 keyboard/mouse/touchpad 1.0% ( 0.0) <kernel core> : inet_initpeers (peer_check_expire) 1.0% ( 0.0) <kernel core> : queue_delayed_work (delayed_work_timer_fn) 1.0% ( 0.0) cifsoplockd : schedule_timeout (process_timeout) 1.0% ( 0.0) async/2 : scsi_request_fn (blk_rq_timed_out_timer) 1.0% ( 0.0) khungtaskd : schedule_timeout (process_timeout) 1.0% ( 0.0) <kernel core> : addrconf_verify (addrconf_verify) A USB device is active 100.0% of the time: USB device 1-5 : UB6225 (ENE) Recent USB suspend statistics Active Device name 100.0% USB device 1-5 : UB6225 (ENE) 0.0% USB device usb5 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb4 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb3 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb2 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 100.0% USB device usb1 : EHCI Host Controller (Linux 2.6.30-rc8-eee ehci_hcd) Camera Enabled -------------- $ powertop -t 60 -d PowerTOP 1.11 (C) 2007, 2008 Intel Corporation Collecting data for 60 seconds Cn Avg residency C0 (cpu running) ( 0.0%) polling 0.0ms ( 0.0%) C1 0.0ms ( 0.0%) C2 1.0ms ( 0.0%) C3 91.9ms (100.0%) P-states (frequencies) Wakeups-from-idle per second : 11.1 interval: 60.0s no ACPI power usage estimate available Top causes for wakeups: 48.4% ( 10.6) <kernel core> : hrtimer_start (tick_sched_timer) 45.7% ( 10.0) <kernel core> : ehci_work (ehci_watchdog) 1.7% ( 0.4) <interrupt> : acpi 1.2% ( 0.3) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer) 0.8% ( 0.2) <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 0.6% ( 0.1) <interrupt> : ata_piix 0.5% ( 0.1) <kernel core> : sta_info_start (sta_info_cleanup) 0.3% ( 0.1) events/0 : queue_delayed_work (delayed_work_timer_fn) 0.3% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn) 0.1% ( 0.0) <interrupt> : PS/2 keyboard/mouse/touchpad 0.1% ( 0.0) khungtaskd : schedule_timeout (process_timeout) 0.1% ( 0.0) <kernel core> : hangcheck_init (hangcheck_fire) 0.1% ( 0.0) <kernel core> : addrconf_verify (addrconf_verify) 0.1% ( 0.0) pdflush : __make_request (blk_unplug_timeout) 0.1% ( 0.0) async/2 : scsi_request_fn (blk_rq_timed_out_timer) 0.1% ( 0.0) cifsoplockd : schedule_timeout (process_timeout) 0.1% ( 0.0) <kernel core> : queue_delayed_work (delayed_work_timer_fn) A USB device is active 100.0% of the time: USB device 1-5 : UB6225 (ENE) Suggestion: Enable USB autosuspend by pressing the U key or adding usbcore.autosuspend=1 to the kernel command line in the grub config Recent USB suspend statistics Active Device name 100.0% /sys/bus/usb/devices/1-8 100.0% USB device 1-5 : UB6225 (ENE) 0.0% USB device usb5 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb4 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb3 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 0.0% USB device usb2 : UHCI Host Controller (Linux 2.6.30-rc8-eee uhci_hcd) 100.0% USB device usb1 : EHCI Host Controller (Linux 2.6.30-rc8-eee ehci_hcd) Pekka ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 13:51 ` Pekka Enberg @ 2009-06-05 13:54 ` Pekka Enberg 2009-06-05 13:58 ` Corentin Chary 2009-06-05 14:38 ` Alan Jenkins 2 siblings, 0 replies; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 13:54 UTC (permalink / raw) To: Corentin Chary; +Cc: acpi4asus-user, len.brown, linux-kernel, Alan Jenkins On Fri, 2009-06-05 at 16:51 +0300, Pekka Enberg wrote: > I did not see a power usage estimate. I am running PowerTOP 1.11 that > comes with Ubuntu 9.04. So I am not sure if what I did is what you > wanted me to do but I ran "powertop -t 60 -d" with camera enabled and > disabled and here are the results. > > Also, when I run plain powertop, it keeps complaining that some USB > device causes wakeups (probably the camera?) and suggests suspending. > But doing that doesn't seem to help things. Here's my config just in case you need it. Pekka # # Automatically generated make config: don't edit # Linux kernel version: 2.6.30-rc8 # Fri Jun 5 16:03:57 2009 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_32_LAZY_GS=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="-eee" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y # CONFIG_KERNEL_GZIP is not set # CONFIG_KERNEL_BZIP2 is not set CONFIG_KERNEL_LZMA=y # CONFIG_SWAP is not set CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set # CONFIG_SYSFS_DEPRECATED_V2 is not set # CONFIG_RELAY is not set # CONFIG_NAMESPACES is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y # CONFIG_RD_BZIP2 is not set # CONFIG_RD_LZMA is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_EMBEDDED=y # CONFIG_UID16 is not set # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_STRIP_ASM_SYMS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y # CONFIG_AIO is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y # CONFIG_SLUB_DEBUG is not set # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set # CONFIG_MARKERS is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_API_DEBUG=y # CONFIG_SLOW_WORK is not set CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_BSG is not set # CONFIG_BLK_DEV_INTEGRITY is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set CONFIG_DEFAULT_NOOP=y CONFIG_DEFAULT_IOSCHED="noop" CONFIG_FREEZER=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # CONFIG_SMP is not set # CONFIG_SPARSE_IRQ is not set CONFIG_X86_MPPARSE=y # CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_SCHED_OMIT_FRAME_POINTER=y # CONFIG_PARAVIRT_GUEST is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set CONFIG_MPENTIUMM=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_X86_DEBUGCTLMSR=y CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_INTEL=y # CONFIG_CPU_SUP_CYRIX_32 is not set # CONFIG_CPU_SUP_AMD is not set # CONFIG_CPU_SUP_CENTAUR is not set # CONFIG_CPU_SUP_TRANSMETA_32 is not set # CONFIG_CPU_SUP_UMC_32 is not set # CONFIG_X86_DS is not set CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y # CONFIG_IOMMU_HELPER is not set # CONFIG_IOMMU_API is not set CONFIG_NR_CPUS=1 # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # CONFIG_X86_CPU_DEBUG is not set # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_2G_OPT is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_HIGHMEM=y # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_PHYS_ADDR_T_64BIT is not set CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_UNEVICTABLE_LRU=y CONFIG_HAVE_MLOCK=y CONFIG_HAVE_MLOCKED_PAGE_BIT=y # CONFIG_HIGHPTE is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set # CONFIG_X86_PAT is not set # CONFIG_EFI is not set # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x100000 # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x100000 # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management and ACPI options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=2001 CONFIG_ACPI_DEBUG=y # CONFIG_ACPI_DEBUG_FUNC_TRACE is not set # CONFIG_ACPI_PCI_SLOT is not set CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # CONFIG_ACPI_SBS is not set # CONFIG_APM is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y # CONFIG_CPU_FREQ_STAT_DETAILS is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # CPUFreq processor drivers # # CONFIG_X86_ACPI_CPUFREQ is not set # CONFIG_X86_POWERNOW_K6 is not set # CONFIG_X86_POWERNOW_K7 is not set # CONFIG_X86_POWERNOW_K8 is not set # CONFIG_X86_GX_SUSPMOD is not set # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_SPEEDSTEP_ICH is not set # CONFIG_X86_SPEEDSTEP_SMI is not set # CONFIG_X86_P4_CLOCKMOD is not set # CONFIG_X86_CPUFREQ_NFORCE2 is not set # CONFIG_X86_LONGRUN is not set # CONFIG_X86_LONGHAUL is not set # CONFIG_X86_E_POWERSAVER is not set # # shared options # # CONFIG_X86_SPEEDSTEP_LIB is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Bus options (PCI etc.) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set # CONFIG_PCI_GOOLPC is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_DOMAINS=y # CONFIG_DMAR is not set CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y # CONFIG_PCIEASPM is not set CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y # CONFIG_PCI_LEGACY is not set # CONFIG_PCI_DEBUG is not set # CONFIG_PCI_STUB is not set # CONFIG_HT_IRQ is not set # CONFIG_PCI_IOV is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # CONFIG_OLPC is not set # CONFIG_PCCARD is not set CONFIG_HOTPLUG_PCI=y CONFIG_HOTPLUG_PCI_FAKE=y # CONFIG_HOTPLUG_PCI_IBM is not set CONFIG_HOTPLUG_PCI_ACPI=y # CONFIG_HOTPLUG_PCI_ACPI_IBM is not set # CONFIG_HOTPLUG_PCI_CPCI is not set # CONFIG_HOTPLUG_PCI_SHPC is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y CONFIG_HAVE_AOUT=y # CONFIG_BINFMT_AOUT is not set # CONFIG_BINFMT_MISC is not set CONFIG_HAVE_ATOMIC_IOMAP=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y CONFIG_XFRM=y # CONFIG_XFRM_USER is not set # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set CONFIG_INET_TUNNEL=y CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y CONFIG_INET_XFRM_MODE_BEET=y CONFIG_INET_LRO=y CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set CONFIG_IPV6=y # CONFIG_IPV6_PRIVACY is not set # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set # CONFIG_INET6_AH is not set # CONFIG_INET6_ESP is not set # CONFIG_INET6_IPCOMP is not set # CONFIG_IPV6_MIP6 is not set # CONFIG_INET6_XFRM_TUNNEL is not set # CONFIG_INET6_TUNNEL is not set CONFIG_INET6_XFRM_MODE_TRANSPORT=y CONFIG_INET6_XFRM_MODE_TUNNEL=y CONFIG_INET6_XFRM_MODE_BEET=y # CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=y CONFIG_IPV6_NDISC_NODETYPE=y # CONFIG_IPV6_TUNNEL is not set # CONFIG_IPV6_MULTIPLE_TABLES is not set # CONFIG_IPV6_MROUTE is not set # CONFIG_NETWORK_SECMARK is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=y # CONFIG_NETFILTER_NETLINK_QUEUE is not set CONFIG_NETFILTER_NETLINK_LOG=y CONFIG_NF_CONNTRACK=y CONFIG_NF_CT_ACCT=y CONFIG_NF_CONNTRACK_MARK=y # CONFIG_NF_CONNTRACK_EVENTS is not set # CONFIG_NF_CT_PROTO_DCCP is not set # CONFIG_NF_CT_PROTO_SCTP is not set # CONFIG_NF_CT_PROTO_UDPLITE is not set # CONFIG_NF_CONNTRACK_AMANDA is not set CONFIG_NF_CONNTRACK_FTP=y # CONFIG_NF_CONNTRACK_H323 is not set CONFIG_NF_CONNTRACK_IRC=y # CONFIG_NF_CONNTRACK_NETBIOS_NS is not set # CONFIG_NF_CONNTRACK_PPTP is not set # CONFIG_NF_CONNTRACK_SANE is not set CONFIG_NF_CONNTRACK_SIP=y # CONFIG_NF_CONNTRACK_TFTP is not set CONFIG_NF_CT_NETLINK=y # CONFIG_NETFILTER_TPROXY is not set CONFIG_NETFILTER_XTABLES=y CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y CONFIG_NETFILTER_XT_TARGET_CONNMARK=y CONFIG_NETFILTER_XT_TARGET_DSCP=y # CONFIG_NETFILTER_XT_TARGET_HL is not set # CONFIG_NETFILTER_XT_TARGET_LED is not set CONFIG_NETFILTER_XT_TARGET_MARK=y CONFIG_NETFILTER_XT_TARGET_NFLOG=y CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y # CONFIG_NETFILTER_XT_TARGET_RATEEST is not set CONFIG_NETFILTER_XT_TARGET_TCPMSS=y # CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set # CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set # CONFIG_NETFILTER_XT_MATCH_COMMENT is not set CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=y CONFIG_NETFILTER_XT_MATCH_CONNMARK=y CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y # CONFIG_NETFILTER_XT_MATCH_DCCP is not set CONFIG_NETFILTER_XT_MATCH_DSCP=y # CONFIG_NETFILTER_XT_MATCH_ESP is not set # CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set # CONFIG_NETFILTER_XT_MATCH_HELPER is not set # CONFIG_NETFILTER_XT_MATCH_HL is not set # CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set # CONFIG_NETFILTER_XT_MATCH_LENGTH is not set CONFIG_NETFILTER_XT_MATCH_LIMIT=y CONFIG_NETFILTER_XT_MATCH_MAC=y CONFIG_NETFILTER_XT_MATCH_MARK=y # CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set # CONFIG_NETFILTER_XT_MATCH_OWNER is not set CONFIG_NETFILTER_XT_MATCH_POLICY=y # CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set # CONFIG_NETFILTER_XT_MATCH_QUOTA is not set # CONFIG_NETFILTER_XT_MATCH_RATEEST is not set # CONFIG_NETFILTER_XT_MATCH_REALM is not set # CONFIG_NETFILTER_XT_MATCH_RECENT is not set # CONFIG_NETFILTER_XT_MATCH_SCTP is not set CONFIG_NETFILTER_XT_MATCH_STATE=y # CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set # CONFIG_NETFILTER_XT_MATCH_STRING is not set CONFIG_NETFILTER_XT_MATCH_TCPMSS=y # CONFIG_NETFILTER_XT_MATCH_TIME is not set # CONFIG_NETFILTER_XT_MATCH_U32 is not set # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=y CONFIG_NF_CONNTRACK_IPV4=y CONFIG_NF_CONNTRACK_PROC_COMPAT=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=y # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_AH is not set # CONFIG_IP_NF_MATCH_ECN is not set # CONFIG_IP_NF_MATCH_TTL is not set CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_LOG=y CONFIG_IP_NF_TARGET_ULOG=y # CONFIG_NF_NAT is not set CONFIG_IP_NF_MANGLE=y # CONFIG_IP_NF_TARGET_CLUSTERIP is not set # CONFIG_IP_NF_TARGET_ECN is not set # CONFIG_IP_NF_TARGET_TTL is not set # CONFIG_IP_NF_RAW is not set # CONFIG_IP_NF_ARPTABLES is not set # # IPv6: Netfilter Configuration # # CONFIG_NF_CONNTRACK_IPV6 is not set # CONFIG_IP6_NF_QUEUE is not set # CONFIG_IP6_NF_IPTABLES is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_NET_DSA 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_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_PHONET is not set CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=y CONFIG_NET_SCH_HTB=y CONFIG_NET_SCH_HFSC=y CONFIG_NET_SCH_PRIO=y # CONFIG_NET_SCH_MULTIQ is not set # CONFIG_NET_SCH_RED is not set # CONFIG_NET_SCH_SFQ is not set # CONFIG_NET_SCH_TEQL is not set # CONFIG_NET_SCH_TBF is not set # CONFIG_NET_SCH_GRED is not set # CONFIG_NET_SCH_DSMARK is not set # CONFIG_NET_SCH_NETEM is not set # CONFIG_NET_SCH_DRR is not set # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=y CONFIG_NET_CLS_TCINDEX=y CONFIG_NET_CLS_ROUTE4=y CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=y CONFIG_NET_CLS_U32=y # CONFIG_CLS_U32_PERF is not set CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=y CONFIG_NET_CLS_RSVP6=y CONFIG_NET_CLS_FLOW=y # CONFIG_NET_EMATCH is not set # CONFIG_NET_CLS_ACT is not set # CONFIG_NET_CLS_IND is not set CONFIG_NET_SCH_FIFO=y # CONFIG_DCB is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set CONFIG_BT=y CONFIG_BT_L2CAP=y CONFIG_BT_SCO=y CONFIG_BT_RFCOMM=y CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=y CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_HIDP=y # # Bluetooth device drivers # CONFIG_BT_HCIBTUSB=y # CONFIG_BT_HCIUART is not set CONFIG_BT_HCIBCM203X=y CONFIG_BT_HCIBPA10X=y CONFIG_BT_HCIBFUSB=y CONFIG_BT_HCIVHCI=y # CONFIG_AF_RXRPC is not set CONFIG_WIRELESS=y CONFIG_CFG80211=y # CONFIG_CFG80211_REG_DEBUG is not set # CONFIG_WIRELESS_OLD_REGULATORY is not set CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y # CONFIG_LIB80211 is not set CONFIG_MAC80211=y # # Rate control algorithm selection # CONFIG_MAC80211_RC_PID=y CONFIG_MAC80211_RC_MINSTREL=y # CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel" # CONFIG_MAC80211_MESH is not set CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUG_MENU is not set # CONFIG_WIMAX is not set CONFIG_RFKILL=y CONFIG_RFKILL_INPUT=y CONFIG_RFKILL_LEDS=y # CONFIG_NET_9P is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_PNP=y CONFIG_PNP_DEBUG_MESSAGES=y # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_FD 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_COW_COMMON 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_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 # CONFIG_BLK_DEV_XIP is not set CONFIG_CDROM_PKTCDVD=y CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set # CONFIG_ATA_OVER_ETH is not set # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_ICS932S401 is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_HP_ILO is not set # CONFIG_ISL29003 is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_AT24 is not set # CONFIG_EEPROM_LEGACY is not set # CONFIG_EEPROM_93CX6 is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set # CONFIG_SCSI_LOWLEVEL is not set # CONFIG_SCSI_DH is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ACPI is not set # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5535 is not set # CONFIG_PATA_CS5536 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_PLATFORM is not set # CONFIG_PATA_SCH is not set CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_DM_DELAY is not set # CONFIG_DM_UEVENT is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # Enable only one of the two stacks, unless you know what you are doing # # CONFIG_FIREWIRE is not set # CONFIG_IEEE1394 is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_COMPAT_NET_DEV_OPS=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set CONFIG_TUN=y # CONFIG_VETH is not set # CONFIG_NET_SB1000 is not set # CONFIG_ARCNET is not set # CONFIG_PHYLIB is not set CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_CASSINI is not set # CONFIG_NET_VENDOR_3COM is not set # CONFIG_ETHOC is not set # CONFIG_DNET is not set # CONFIG_NET_TULIP is not set # CONFIG_HP100 is not set # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set # CONFIG_NET_PCI is not set # CONFIG_B44 is not set CONFIG_ATL2=y # CONFIG_NETDEV_1000 is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set CONFIG_WLAN_80211=y # CONFIG_LIBERTAS is not set # CONFIG_LIBERTAS_THINFIRM is not set # CONFIG_AIRO is not set # CONFIG_ATMEL is not set # CONFIG_AT76C50X_USB is not set # CONFIG_PRISM54 is not set # CONFIG_USB_ZD1201 is not set # CONFIG_USB_NET_RNDIS_WLAN is not set # CONFIG_RTL8180 is not set # CONFIG_RTL8187 is not set # CONFIG_ADM8211 is not set # CONFIG_MAC80211_HWSIM is not set # CONFIG_MWL8K is not set # CONFIG_P54_COMMON is not set CONFIG_ATH5K=y CONFIG_ATH5K_DEBUG=y # CONFIG_ATH9K is not set # CONFIG_AR9170_USB is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IWLWIFI is not set # CONFIG_HOSTAP is not set # CONFIG_B43 is not set # CONFIG_B43LEGACY is not set # CONFIG_ZD1211RW is not set # CONFIG_RT2X00 is not set # CONFIG_HERMES is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # # USB Network Adapters # # 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 # CONFIG_USB_HSO is not set # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set CONFIG_PPP=y # CONFIG_PPP_MULTILINK is not set CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=y CONFIG_PPP_SYNC_TTY=y CONFIG_PPP_DEFLATE=y CONFIG_PPP_BSDCOMP=y CONFIG_PPP_MPPE=y CONFIG_PPPOE=y # CONFIG_PPPOL2TP is not set # CONFIG_SLIP is not set CONFIG_SLHC=y # CONFIG_NET_FC is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # CONFIG_INPUT_POLLDEV is not set # # 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_EVDEV=y # CONFIG_INPUT_EVBUG 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_KEYBOARD_STOWAWAY is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set CONFIG_GAMEPORT=y # CONFIG_GAMEPORT_NS558 is not set # CONFIG_GAMEPORT_L4 is not set # CONFIG_GAMEPORT_EMU10K1 is not set # CONFIG_GAMEPORT_FM801 is not set # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set CONFIG_DEVKMEM=y # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set # CONFIG_LEGACY_PTYS is not set # CONFIG_IPMI_HANDLER is not set # CONFIG_HW_RANDOM is not set CONFIG_NVRAM=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_RAW_DRIVER is not set CONFIG_HPET=y CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=y # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y # CONFIG_I2C_CHARDEV is not set CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_ALGOBIT=y # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # 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_I801=y # CONFIG_I2C_ISCH is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_NFORCE2 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 # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_OCORES is not set # CONFIG_I2C_SIMTEC is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Graphics adapter I2C/DDC channel drivers # # CONFIG_I2C_VOODOO3 is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_STUB is not set # CONFIG_SCx200_ACB is not set # # Miscellaneous I2C Chip support # # CONFIG_DS1682 is not set # CONFIG_SENSORS_PCF8574 is not set # CONFIG_PCF8575 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 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 # CONFIG_SPI is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_BATTERY_DS2760 is not set # CONFIG_BATTERY_BQ27x00 is not set CONFIG_HWMON=y # CONFIG_HWMON_VID is not set # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_K8TEMP is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATK0110 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_G760A is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 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_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4215 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_LM95241 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL=y # CONFIG_THERMAL_HWMON is not set # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_MFD_TMIO is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_REGULATOR is not set # # Multimedia devices # # # Multimedia core support # CONFIG_VIDEO_DEV=y CONFIG_VIDEO_V4L2_COMMON=y # CONFIG_VIDEO_ALLOW_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=y CONFIG_VIDEO_MEDIA=y # # Multimedia drivers # # CONFIG_MEDIA_ATTACH is not set CONFIG_MEDIA_TUNER=y # CONFIG_MEDIA_TUNER_CUSTOMISE is not set CONFIG_MEDIA_TUNER_SIMPLE=y CONFIG_MEDIA_TUNER_TDA8290=y CONFIG_MEDIA_TUNER_TDA9887=y CONFIG_MEDIA_TUNER_TEA5761=y CONFIG_MEDIA_TUNER_TEA5767=y CONFIG_MEDIA_TUNER_MT20XX=y CONFIG_MEDIA_TUNER_XC2028=y CONFIG_MEDIA_TUNER_XC5000=y CONFIG_MEDIA_TUNER_MC44S803=y CONFIG_VIDEO_V4L2=y CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y # CONFIG_VIDEO_VIVI is not set # CONFIG_VIDEO_BT848 is not set # CONFIG_VIDEO_SAA5246A is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_VIDEO_ZORAN is not set # CONFIG_VIDEO_SAA7134 is not set # CONFIG_VIDEO_HEXIUM_ORION is not set # CONFIG_VIDEO_HEXIUM_GEMINI is not set # CONFIG_VIDEO_CX88 is not set # CONFIG_VIDEO_CX23885 is not set # CONFIG_VIDEO_AU0828 is not set # CONFIG_VIDEO_IVTV is not set # CONFIG_VIDEO_CX18 is not set # CONFIG_VIDEO_CAFE_CCIC is not set # CONFIG_SOC_CAMERA is not set CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=y CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y # CONFIG_USB_GSPCA is not set # CONFIG_VIDEO_PVRUSB2 is not set # CONFIG_VIDEO_HDPVR is not set # CONFIG_VIDEO_EM28XX is not set # CONFIG_VIDEO_CX231XX is not set # CONFIG_VIDEO_USBVISION is not set # CONFIG_USB_ET61X251 is not set # CONFIG_USB_SN9C102 is not set # CONFIG_USB_ZC0301 is not set CONFIG_USB_PWC_INPUT_EVDEV=y # CONFIG_USB_ZR364XX is not set # CONFIG_USB_STKWEBCAM is not set # CONFIG_USB_S2255 is not set # CONFIG_RADIO_ADAPTERS is not set # CONFIG_DVB_DYNAMIC_MINORS is not set CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # # CONFIG_TTPCI_EEPROM is not set # CONFIG_DVB_AV7110 is not set # CONFIG_DVB_BUDGET_CORE is not set # # Supported USB Adapters # # CONFIG_DVB_USB is not set # CONFIG_DVB_TTUSB_BUDGET is not set # CONFIG_DVB_TTUSB_DEC is not set # CONFIG_DVB_SIANO_SMS1XXX is not set # # Supported FlexCopII (B2C2) Adapters # # CONFIG_DVB_B2C2_FLEXCOP is not set # # Supported BT878 Adapters # # # Supported Pluto2 Adapters # # CONFIG_DVB_PLUTO2 is not set # # Supported SDMC DM1105 Adapters # # CONFIG_DVB_DM1105 is not set # # Supported DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set # CONFIG_DAB is not set # # Graphics support # CONFIG_AGP=y # CONFIG_AGP_ALI is not set # CONFIG_AGP_ATI is not set # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=y # CONFIG_AGP_NVIDIA is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set # CONFIG_AGP_VIA is not set # CONFIG_AGP_EFFICEON is not set CONFIG_DRM=y # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set # CONFIG_DRM_I830 is not set CONFIG_DRM_I915=y # CONFIG_DRM_I915_KMS is not set # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=y CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_UVESA is not set CONFIG_FB_VESA=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA 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_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_ILI9320 is not set CONFIG_LCD_PLATFORM=y CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_GENERIC is not set # CONFIG_BACKLIGHT_PROGEAR is not set # CONFIG_BACKLIGHT_MBP_NVIDIA is not set # CONFIG_BACKLIGHT_SAHARA is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=128 CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_LOGO is not set CONFIG_SOUND=y CONFIG_SOUND_OSS_CORE=y CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_HWDEP=y CONFIG_SND_RAWMIDI=y CONFIG_SND_JACK=y CONFIG_SND_SEQUENCER=y # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_HRTIMER=y CONFIG_SND_SEQ_HRTIMER_DEFAULT=y # CONFIG_SND_DYNAMIC_MINORS is not set # CONFIG_SND_SUPPORT_OLD_API is not set # CONFIG_SND_VERBOSE_PROCFS is not set # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y # CONFIG_SND_DRIVERS is not set CONFIG_SND_PCI=y # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AW2 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_OXYGEN is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 is not set # CONFIG_SND_CS5535AUDIO is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_INDIGOIOX is not set # CONFIG_SND_INDIGODJX is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X 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_FM801 is not set CONFIG_SND_HDA_INTEL=y CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_CODEC_REALTEK=y # CONFIG_SND_HDA_CODEC_ANALOG is not set # CONFIG_SND_HDA_CODEC_SIGMATEL is not set # CONFIG_SND_HDA_CODEC_VIA is not set # CONFIG_SND_HDA_CODEC_ATIHDMI is not set # CONFIG_SND_HDA_CODEC_NVHDMI is not set # CONFIG_SND_HDA_CODEC_INTELHDMI is not set # CONFIG_SND_HDA_CODEC_CONEXANT is not set # CONFIG_SND_HDA_CODEC_CMEDIA is not set # CONFIG_SND_HDA_CODEC_SI3054 is not set # CONFIG_SND_HDA_GENERIC is not set CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=5 # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_HIFIER 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_KORG1212 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_SIS7019 is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VIRTUOSO is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=y # CONFIG_SND_USB_USX2Y is not set # CONFIG_SND_USB_CAIAQ is not set # CONFIG_SND_USB_US122L is not set # CONFIG_SND_SOC is not set # CONFIG_SOUND_PRIME is not set CONFIG_HID_SUPPORT=y CONFIG_HID=y # CONFIG_HID_DEBUG is not set CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=y # CONFIG_HID_PID is not set CONFIG_USB_HIDDEV=y # # Special HID drivers # # CONFIG_HID_A4TECH is not set # CONFIG_HID_APPLE is not set # CONFIG_HID_BELKIN is not set # CONFIG_HID_CHERRY is not set # CONFIG_HID_CHICONY is not set # CONFIG_HID_CYPRESS is not set # CONFIG_DRAGONRISE_FF is not set # CONFIG_HID_EZKEY is not set # CONFIG_HID_KYE is not set # CONFIG_HID_GYRATION is not set # CONFIG_HID_KENSINGTON is not set CONFIG_HID_LOGITECH=y # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_HID_MICROSOFT=y # CONFIG_HID_MONTEREY is not set # CONFIG_HID_NTRIG is not set # CONFIG_HID_PANTHERLORD is not set # CONFIG_HID_PETALYNX is not set # CONFIG_HID_SAMSUNG is not set # CONFIG_HID_SONY is not set # CONFIG_HID_SUNPLUS is not set # CONFIG_GREENASIA_FF is not set # CONFIG_HID_TOPSEED is not set # CONFIG_THRUSTMASTER_FF is not set # CONFIG_ZEROPLUS_FF is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set # CONFIG_USB_OTG_WHITELIST is not set # CONFIG_USB_OTG_BLACKLIST_HUB is not set # CONFIG_USB_MON is not set # CONFIG_USB_WUSB is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_OHCI_HCD is not set CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_WHCI_HCD is not set # CONFIG_USB_HWA_HCD is not set # # USB Device Class drivers # CONFIG_USB_ACM=y CONFIG_USB_PRINTER=y # CONFIG_USB_WDM is not set # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB port drivers # CONFIG_USB_SERIAL=y # CONFIG_USB_SERIAL_CONSOLE is not set # CONFIG_USB_EZUSB is not set CONFIG_USB_SERIAL_GENERIC=y # CONFIG_USB_SERIAL_AIRCABLE is not set # CONFIG_USB_SERIAL_ARK3116 is not set # CONFIG_USB_SERIAL_BELKIN is not set # CONFIG_USB_SERIAL_CH341 is not set # CONFIG_USB_SERIAL_WHITEHEAT is not set # CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set # CONFIG_USB_SERIAL_CP210X is not set # CONFIG_USB_SERIAL_CYPRESS_M8 is not set # CONFIG_USB_SERIAL_EMPEG is not set # CONFIG_USB_SERIAL_FTDI_SIO is not set # CONFIG_USB_SERIAL_FUNSOFT is not set # CONFIG_USB_SERIAL_VISOR is not set # 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_GARMIN is not set # CONFIG_USB_SERIAL_IPW is not set # CONFIG_USB_SERIAL_IUU is not set # CONFIG_USB_SERIAL_KEYSPAN_PDA is not set # CONFIG_USB_SERIAL_KEYSPAN 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_MOS7720 is not set # CONFIG_USB_SERIAL_MOS7840 is not set # CONFIG_USB_SERIAL_MOTOROLA is not set # CONFIG_USB_SERIAL_NAVMAN is not set # CONFIG_USB_SERIAL_PL2303 is not set # CONFIG_USB_SERIAL_OTI6858 is not set # CONFIG_USB_SERIAL_QUALCOMM is not set # CONFIG_USB_SERIAL_SPCP8X5 is not set # CONFIG_USB_SERIAL_HP4X is not set # CONFIG_USB_SERIAL_SAFE is not set # CONFIG_USB_SERIAL_SIEMENS_MPI is not set # CONFIG_USB_SERIAL_SIERRAWIRELESS is not set # CONFIG_USB_SERIAL_SYMBOL is not set # CONFIG_USB_SERIAL_TI is not set # CONFIG_USB_SERIAL_CYBERJACK is not set # CONFIG_USB_SERIAL_XIRCOM is not set CONFIG_USB_SERIAL_OPTION=y # CONFIG_USB_SERIAL_OMNINET is not set # CONFIG_USB_SERIAL_OPTICON is not set # CONFIG_USB_SERIAL_DEBUG is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set CONFIG_USB_BERRY_CHARGE=y CONFIG_USB_LED=y # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_VST is not set # CONFIG_USB_GADGET is not set # # OTG and related infrastructure # # CONFIG_NOP_USB_XCEIV is not set # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # # CONFIG_LEDS_ALIX2 is not set # CONFIG_LEDS_PCA9532 is not set # CONFIG_LEDS_LP5521 is not set # CONFIG_LEDS_CLEVO_MAIL is not set # CONFIG_LEDS_PCA955X is not set # CONFIG_LEDS_BD2802 is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y # CONFIG_LEDS_TRIGGER_TIMER is not set # CONFIG_LEDS_TRIGGER_HEARTBEAT is not set # CONFIG_LEDS_TRIGGER_BACKLIGHT is not set # CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set # # iptables trigger is under Netfilter config (LED target) # # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_DS1307 is not set # CONFIG_RTC_DRV_DS1374 is not set # CONFIG_RTC_DRV_DS1672 is not set # CONFIG_RTC_DRV_MAX6900 is not set # CONFIG_RTC_DRV_RS5C372 is not set # CONFIG_RTC_DRV_ISL1208 is not set # CONFIG_RTC_DRV_X1205 is not set # CONFIG_RTC_DRV_PCF8563 is not set # CONFIG_RTC_DRV_PCF8583 is not set # CONFIG_RTC_DRV_M41T80 is not set # CONFIG_RTC_DRV_S35390A is not set # CONFIG_RTC_DRV_FM3130 is not set # CONFIG_RTC_DRV_RX8581 is not set # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y # CONFIG_RTC_DRV_DS1286 is not set # CONFIG_RTC_DRV_DS1511 is not set # CONFIG_RTC_DRV_DS1553 is not set # CONFIG_RTC_DRV_DS1742 is not set # CONFIG_RTC_DRV_STK17TA8 is not set # CONFIG_RTC_DRV_M48T86 is not set # CONFIG_RTC_DRV_M48T35 is not set # CONFIG_RTC_DRV_M48T59 is not set # CONFIG_RTC_DRV_BQ4802 is not set # CONFIG_RTC_DRV_V3020 is not set # # on-CPU RTC drivers # # CONFIG_DMADEVICES is not set # CONFIG_AUXDISPLAY is not set # CONFIG_UIO is not set # CONFIG_STAGING is not set CONFIG_X86_PLATFORM_DEVICES=y # CONFIG_ACER_WMI is not set CONFIG_ASUS_LAPTOP=y # CONFIG_FUJITSU_LAPTOP is not set # CONFIG_TC1100_WMI is not set # CONFIG_MSI_LAPTOP is not set # CONFIG_PANASONIC_LAPTOP is not set # CONFIG_COMPAL_LAPTOP is not set # CONFIG_SONY_LAPTOP is not set # CONFIG_THINKPAD_ACPI is not set # CONFIG_INTEL_MENLOW is not set CONFIG_EEEPC_LAPTOP=y # CONFIG_ACPI_WMI is not set # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_FIRMWARE_MEMMAP is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # CONFIG_DMIID is not set # CONFIG_ISCSI_IBFT_FIND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y # CONFIG_EXT2_FS_SECURITY is not set # CONFIG_EXT2_FS_XIP is not set # CONFIG_EXT3_FS is not set # CONFIG_EXT4_FS is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_FILE_LOCKING=y # CONFIG_XFS_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y CONFIG_GENERIC_ACL=y # # Caches # # CONFIG_FSCACHE is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set CONFIG_UDF_FS=y CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y 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_PROC_SYSCTL=y # CONFIG_PROC_PAGE_MONITOR is not set CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set # CONFIG_CONFIGFS_FS is not set CONFIG_MISC_FILESYSTEMS=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_ECRYPT_FS is not set # CONFIG_HFS_FS is not set CONFIG_HFSPLUS_FS=y # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set CONFIG_SQUASHFS=y # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 # CONFIG_VXFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_OMFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set CONFIG_NILFS2_FS=y CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_RPCSEC_GSS_SPKM3 is not set CONFIG_SMB_FS=y # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=y # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_WEAK_PW_HASH is not set # CONFIG_CIFS_UPCALL is not set CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set # CONFIG_CIFS_DFS_UPCALL is not set # CONFIG_CIFS_EXPERIMENTAL 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_KARMA_PARTITION is not set # CONFIG_EFI_PARTITION is not set # CONFIG_SYSV68_PARTITION is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # 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=y # 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=y CONFIG_NLS_ISO8859_1=y # 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=y # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set CONFIG_NLS_UTF8=y # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_WARN_DEPRECATED is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y # CONFIG_SCHEDSTATS is not set CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set CONFIG_DEBUG_PREEMPT=y # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set # CONFIG_DEBUG_BUGVERBOSE is not set # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set # CONFIG_DEBUG_MEMORY_INIT is not set # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y # CONFIG_FRAME_POINTER is not set # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_LATENCYTOP is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_FTRACE_SYSCALLS=y CONFIG_TRACING_SUPPORT=y # # Tracers # # CONFIG_FUNCTION_TRACER is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_PREEMPT_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_CONTEXT_SWITCH_TRACER is not set # CONFIG_EVENT_TRACER is not set # CONFIG_FTRACE_SYSCALLS is not set # CONFIG_BOOT_TRACER is not set # CONFIG_TRACE_BRANCH_PROFILING is not set # CONFIG_POWER_TRACER is not set # CONFIG_STACK_TRACER is not set # CONFIG_KMEMTRACE is not set # CONFIG_WORKQUEUE_TRACER is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_MMIOTRACE is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set CONFIG_STRICT_DEVMEM=y # CONFIG_X86_VERBOSE_BOOTUP is not set # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_4KSTACKS is not set CONFIG_DOUBLEFAULT=y CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # # Security options # CONFIG_KEYS=y # CONFIG_KEYS_DEBUG_PROC_KEYS is not set # CONFIG_SECURITY is not set # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set # CONFIG_IMA is not set CONFIG_CRYPTO=y # # Crypto core or helper # # CONFIG_CRYPTO_FIPS is not set CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=y # CONFIG_CRYPTO_NULL is not set CONFIG_CRYPTO_WORKQUEUE=y # CONFIG_CRYPTO_CRYPTD is not set # CONFIG_CRYPTO_AUTHENC is not set # CONFIG_CRYPTO_TEST is not set # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=y CONFIG_CRYPTO_GCM=y CONFIG_CRYPTO_SEQIV=y # # Block modes # CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=y # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_LRW=y # CONFIG_CRYPTO_PCBC is not set # CONFIG_CRYPTO_XTS is not set # # Hash modes # # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_XCBC is not set # # Digest # CONFIG_CRYPTO_CRC32C=y # CONFIG_CRYPTO_CRC32C_INTEL is not set # CONFIG_CRYPTO_MD4 is not set # CONFIG_CRYPTO_MD5 is not set CONFIG_CRYPTO_MICHAEL_MIC=y # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_SHA512=y # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # # Ciphers # CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_586=y # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_586 is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # # Compression # # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_ZLIB is not set CONFIG_CRYPTO_LZO=y # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set # CONFIG_CRYPTO_HW is not set CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y # CONFIG_VIRTUALIZATION is not set # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=y CONFIG_CRC16=y # CONFIG_CRC_T10DIF is not set CONFIG_CRC_ITU_T=y CONFIG_CRC32=y # CONFIG_CRC7 is not set CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_DECOMPRESS_GZIP=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_NLATTR=y ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 13:51 ` Pekka Enberg 2009-06-05 13:54 ` Pekka Enberg @ 2009-06-05 13:58 ` Corentin Chary 2009-06-05 14:38 ` Alan Jenkins 2 siblings, 0 replies; 32+ messages in thread From: Corentin Chary @ 2009-06-05 13:58 UTC (permalink / raw) To: Pekka Enberg; +Cc: acpi4asus-user, len.brown, linux-kernel, Alan Jenkins On Fri, Jun 5, 2009 at 3:51 PM, Pekka Enberg<penberg@cs.helsinki.fi> wrote: > Hi Corentin, > > On Fri, 2009-06-05 at 15:02 +0200, Corentin Chary wrote: >> > That said, I am more than happy to measure this but I need a little bit >> > more information to get started as I have never used powertop. So what >> > is it exactly you want me to do? >> >> PowerTop (with a corretly configured kernel) will give you a power >> usage estimate. >> >> CONFIG_NO_HZ=y >> CONFIG_TIMER_STATS=y >> CONFIG_DEBUG_KERNEL=y >> >> For propers results, shutdown all services and just keep a shell >> (without X or network). >> You can also test that with and without the camera driver. > > I did not see a power usage estimate. I am running PowerTOP 1.11 that > comes with Ubuntu 9.04. So I am not sure if what I did is what you > wanted me to do but I ran "powertop -t 60 -d" with camera enabled and > disabled and here are the results. Thanks for the results, next week I'll do some test on a minimal setup. -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 13:51 ` Pekka Enberg 2009-06-05 13:54 ` Pekka Enberg 2009-06-05 13:58 ` Corentin Chary @ 2009-06-05 14:38 ` Alan Jenkins 2009-06-05 14:50 ` Pekka Enberg 2 siblings, 1 reply; 32+ messages in thread From: Alan Jenkins @ 2009-06-05 14:38 UTC (permalink / raw) To: Pekka Enberg; +Cc: Corentin Chary, acpi4asus-user, len.brown, linux-kernel On 6/5/09, Pekka Enberg <penberg@cs.helsinki.fi> wrote: > Hi Corentin, > > On Fri, 2009-06-05 at 15:02 +0200, Corentin Chary wrote: >> > That said, I am more than happy to measure this but I need a little bit >> > more information to get started as I have never used powertop. So what >> > is it exactly you want me to do? >> >> For propers results, shutdown all services and just keep a shell >> (without X or network). >> You can also test that with and without the camera driver. > > I did not see a power usage estimate. I am running PowerTOP 1.11 that > comes with Ubuntu 9.04. So I am not sure if what I did is what you > wanted me to do but I ran "powertop -t 60 -d" with camera enabled and > disabled and here are the results. Yeah, "no ACPI power usage estimate available", just like my eeepc. > Also, when I run plain powertop, it keeps complaining that some USB > device causes wakeups (probably the camera?) and suggests suspending. > But doing that doesn't seem to help things. /me hijacks thread Unfortunately powertop is out of date now. The default behaviour is not to suspend and it must be enabled on a per-device basis, because there's lots of buggy hardware. > Camera Disabled > --------------- > Wakeups-from-idle per second : 1.2 interval: 60.0s > Camera Enabled > -------------- > Wakeups-from-idle per second : 11.1 interval: 60.0s Ok. I didn't bother shutting down my system, but I get a similar difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally, disabling the camera does help battery life, and presumably Asus had good reason to implement it! (The shipped OS "fixes" the usability problem by patching the camera apps). BUT I found that autosuspend didn't seem to break anything, and enabling it also got me down to 16 wakeups/s. I think this is ideal because autosuspend is automatic so I can save power without manual toggling. Here's some magic to enable autosuspend: # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level Ideally this wants to be enabled automatically using a udev rule. Anyway, my point is we should be happy to enable the camera by default, because it will encourage the development of userspace autosuspend whitelists :-). Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 14:38 ` Alan Jenkins @ 2009-06-05 14:50 ` Pekka Enberg 2009-06-05 14:55 ` Alan Jenkins 0 siblings, 1 reply; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 14:50 UTC (permalink / raw) To: alan-jenkins; +Cc: Corentin Chary, acpi4asus-user, len.brown, linux-kernel Hi Alan, On Fri, 2009-06-05 at 15:38 +0100, Alan Jenkins wrote: > Ok. I didn't bother shutting down my system, but I get a similar > difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally, > disabling the camera does help battery life, and presumably Asus had > good reason to implement it! (The shipped OS "fixes" the usability > problem by patching the camera apps). > > BUT I found that autosuspend didn't seem to break anything, and > enabling it also got me down to 16 wakeups/s. I think this is ideal > because autosuspend is automatic so I can save power without manual > toggling. > > Here's some magic to enable autosuspend: > > # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level > > Ideally this wants to be enabled automatically using a udev rule. Can the kernel do this by default for this specific driver on eeepc? Pekka ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 14:50 ` Pekka Enberg @ 2009-06-05 14:55 ` Alan Jenkins 2009-06-05 15:08 ` Alan Jenkins 2009-06-05 15:13 ` Alan Stern 0 siblings, 2 replies; 32+ messages in thread From: Alan Jenkins @ 2009-06-05 14:55 UTC (permalink / raw) To: Pekka Enberg Cc: Corentin Chary, acpi4asus-user, len.brown, linux-kernel, USB list Pekka Enberg wrote: > Hi Alan, > > On Fri, 2009-06-05 at 15:38 +0100, Alan Jenkins wrote: > >> Ok. I didn't bother shutting down my system, but I get a similar >> difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally, >> disabling the camera does help battery life, and presumably Asus had >> good reason to implement it! (The shipped OS "fixes" the usability >> problem by patching the camera apps). >> >> BUT I found that autosuspend didn't seem to break anything, and >> enabling it also got me down to 16 wakeups/s. I think this is ideal >> because autosuspend is automatic so I can save power without manual >> toggling. >> >> Here's some magic to enable autosuspend: >> >> # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level >> >> Ideally this wants to be enabled automatically using a udev rule. >> > > Can the kernel do this by default for this specific driver on eeepc? > > Pekka > > Auto-suspend white-listing would be done on the basis of USB ids (vendor, product). At the moment it's expected that userspace should take ownership of it. There's no infrastructure for in-kernel whitelisting. I think. Large lists in udev rules can work, there are already lists of USB devices to set permissions for libusb access, e.g. for libmtp. [CC usb list - in the hope someone will point out if I got this wrong :-)] Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 14:55 ` Alan Jenkins @ 2009-06-05 15:08 ` Alan Jenkins 2009-06-05 15:14 ` Pekka Enberg 2009-06-07 14:54 ` Darren Salt 2009-06-05 15:13 ` Alan Stern 1 sibling, 2 replies; 32+ messages in thread From: Alan Jenkins @ 2009-06-05 15:08 UTC (permalink / raw) To: Pekka Enberg Cc: Corentin Chary, acpi4asus-user, len.brown, linux-kernel, USB list Alan Jenkins wrote: > Pekka Enberg wrote: >> Hi Alan, >> >> On Fri, 2009-06-05 at 15:38 +0100, Alan Jenkins wrote: >> >>> Ok. I didn't bother shutting down my system, but I get a similar >>> difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally, >>> disabling the camera does help battery life, and presumably Asus had >>> good reason to implement it! (The shipped OS "fixes" the usability >>> problem by patching the camera apps). >>> >>> BUT I found that autosuspend didn't seem to break anything, and >>> enabling it also got me down to 16 wakeups/s. I think this is ideal >>> because autosuspend is automatic so I can save power without manual >>> toggling. >>> >>> Here's some magic to enable autosuspend: >>> >>> # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level >>> >>> Ideally this wants to be enabled automatically using a udev rule. >>> >> >> Can the kernel do this by default for this specific driver on eeepc? >> >> Pekka >> >> > > Auto-suspend white-listing would be done on the basis of USB ids > (vendor, product). At the moment it's expected that userspace should > take ownership of it. There's no infrastructure for in-kernel > whitelisting. I think. > > Large lists in udev rules can work, there are already lists of USB > devices to set permissions for libusb access, e.g. for libmtp. > > [CC usb list - in the hope someone will point out if I got this wrong > :-)] > > Alan Btw I've now tested the udev rule, you can just dump this in a new .rules file under /etc/udev/rules.d: SUBSYSTEM=="usb", ATTR{idVendor}=="eb1a", ATTR{idProduct}=="2761", ATTR{power/level}="auto" Not sure who I should submit it to though :-). debian-eeepc would take it, but perhaps it should go in udev's default rules. Regards Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 15:08 ` Alan Jenkins @ 2009-06-05 15:14 ` Pekka Enberg 2009-06-07 14:54 ` Darren Salt 1 sibling, 0 replies; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 15:14 UTC (permalink / raw) To: Alan Jenkins Cc: Corentin Chary, acpi4asus-user, len.brown, linux-kernel, USB list, kay.sievers Hi Alan, On Fri, 2009-06-05 at 16:08 +0100, Alan Jenkins wrote: > Alan Jenkins wrote: > > Pekka Enberg wrote: > >> Hi Alan, > >> > >> On Fri, 2009-06-05 at 15:38 +0100, Alan Jenkins wrote: > >> > >>> Ok. I didn't bother shutting down my system, but I get a similar > >>> difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally, > >>> disabling the camera does help battery life, and presumably Asus had > >>> good reason to implement it! (The shipped OS "fixes" the usability > >>> problem by patching the camera apps). > >>> > >>> BUT I found that autosuspend didn't seem to break anything, and > >>> enabling it also got me down to 16 wakeups/s. I think this is ideal > >>> because autosuspend is automatic so I can save power without manual > >>> toggling. > >>> > >>> Here's some magic to enable autosuspend: > >>> > >>> # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level > >>> > >>> Ideally this wants to be enabled automatically using a udev rule. > >>> > >> > >> Can the kernel do this by default for this specific driver on eeepc? > >> > >> Pekka > >> > >> > > > > Auto-suspend white-listing would be done on the basis of USB ids > > (vendor, product). At the moment it's expected that userspace should > > take ownership of it. There's no infrastructure for in-kernel > > whitelisting. I think. > > > > Large lists in udev rules can work, there are already lists of USB > > devices to set permissions for libusb access, e.g. for libmtp. > > > > [CC usb list - in the hope someone will point out if I got this wrong > > :-)] > > > > Alan > > Btw I've now tested the udev rule, you can just dump this in a new > .rules file under /etc/udev/rules.d: > > SUBSYSTEM=="usb", ATTR{idVendor}=="eb1a", ATTR{idProduct}=="2761", ATTR{power/level}="auto" > > > Not sure who I should submit it to though :-). debian-eeepc would take > it, but perhaps it should go in udev's default rules. AFAIK, Kay Sievers maintains the udev rules so lets cc him. And yeah, I totally agree that it should go to the generic ones, not to debian-eeepc. Pekka ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 15:08 ` Alan Jenkins 2009-06-05 15:14 ` Pekka Enberg @ 2009-06-07 14:54 ` Darren Salt 2009-06-07 15:41 ` Alan Jenkins 1 sibling, 1 reply; 32+ messages in thread From: Darren Salt @ 2009-06-07 14:54 UTC (permalink / raw) To: Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb I demand that Alan Jenkins may or may not have written... > Btw I've now tested the udev rule, you can just dump this in a new .rules > file under /etc/udev/rules.d: > SUBSYSTEM=="usb", ATTR{idVendor}=="eb1a", ATTR{idProduct}=="2761", ATTR{power/level}="auto" And a similar line for 05e3:0505, which seems to be working fine here. [snip] -- | Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon | Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army | + Buy less and make it last longer. INDUSTRY CAUSES GLOBAL WARMING. Nobody expects the Spanish Inquisition! ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-07 14:54 ` Darren Salt @ 2009-06-07 15:41 ` Alan Jenkins 2009-06-07 23:28 ` Matthew Garrett 0 siblings, 1 reply; 32+ messages in thread From: Alan Jenkins @ 2009-06-07 15:41 UTC (permalink / raw) To: Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On 6/7/09, Darren Salt <linux@youmustbejoking.demon.co.uk> wrote: > I demand that Alan Jenkins may or may not have written... > >> Btw I've now tested the udev rule, you can just dump this in a new .rules >> file under /etc/udev/rules.d: > >> SUBSYSTEM=="usb", ATTR{idVendor}=="eb1a", ATTR{idProduct}=="2761", >> ATTR{power/level}="auto" > > And a similar line for 05e3:0505, which seems to be working fine here. Ok. Hmm, some cameras have input devices (i.e. buttons). In fact, uvcvideo registers an input device on my EEE even though it has no buttons. I think that needs investigating :-(. It's quite likely that the buttons can stop working when suspended. And there might be other devices with the same IDs, which have a button wired up. Regards Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-07 15:41 ` Alan Jenkins @ 2009-06-07 23:28 ` Matthew Garrett 2009-06-08 3:03 ` Alan Stern 0 siblings, 1 reply; 32+ messages in thread From: Matthew Garrett @ 2009-06-07 23:28 UTC (permalink / raw) To: alan-jenkins Cc: Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Sun, Jun 07, 2009 at 04:41:30PM +0100, Alan Jenkins wrote: > Hmm, some cameras have input devices (i.e. buttons). In fact, uvcvideo > registers an input device on my EEE even though it has no buttons. I > think that needs investigating :-(. > > It's quite likely that the buttons can stop working when suspended. > And there might be other devices with the same IDs, which have a > button wired up. A change has recently been committed that results in the button only working if the v4l device is open. Otherwise you've got several wakeups a second due to the polling of the button endpoint. I'm assuming that opening the device disables autosuspend, so I wouldn't worry about that. It'd be interesting to try enabling autosuspend on all UVC devices. Can a driver indicate that its hardware supports it? -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-07 23:28 ` Matthew Garrett @ 2009-06-08 3:03 ` Alan Stern 2009-06-08 3:07 ` Matthew Garrett 0 siblings, 1 reply; 32+ messages in thread From: Alan Stern @ 2009-06-08 3:03 UTC (permalink / raw) To: Matthew Garrett Cc: alan-jenkins, Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Mon, 8 Jun 2009, Matthew Garrett wrote: > On Sun, Jun 07, 2009 at 04:41:30PM +0100, Alan Jenkins wrote: > > > Hmm, some cameras have input devices (i.e. buttons). In fact, uvcvideo > > registers an input device on my EEE even though it has no buttons. I > > think that needs investigating :-(. > > > > It's quite likely that the buttons can stop working when suspended. > > And there might be other devices with the same IDs, which have a > > button wired up. > > A change has recently been committed that results in the button only > working if the v4l device is open. Otherwise you've got several wakeups > a second due to the polling of the button endpoint. I'm assuming that > opening the device disables autosuspend, so I wouldn't worry about that. > > It'd be interesting to try enabling autosuspend on all UVC devices. Can > a driver indicate that its hardware supports it? There's no mechanism for this. It many environments it couldn't work, because the decision about whether to enable autosuspend is made when the device is first created (i.e., when the creation uevent is received), whereas driver binding doesn't occur until later. Alan Stern ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-08 3:03 ` Alan Stern @ 2009-06-08 3:07 ` Matthew Garrett 2009-06-08 3:10 ` Alan Stern 0 siblings, 1 reply; 32+ messages in thread From: Matthew Garrett @ 2009-06-08 3:07 UTC (permalink / raw) To: Alan Stern Cc: alan-jenkins, Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote: > There's no mechanism for this. It many environments it couldn't work, > because the decision about whether to enable autosuspend is made when > the device is first created (i.e., when the creation uevent is > received), whereas driver binding doesn't occur until later. There's a lot of power management situations where you don't end up with the optimal power configuration until a driver's bound. It's certainly possible to do this in userspace, but if we know that the hardware supported by a given driver will always work then it seems reasonable to have it whitelist autosuspend on that device. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-08 3:07 ` Matthew Garrett @ 2009-06-08 3:10 ` Alan Stern 2009-06-08 15:00 ` Matthew Garrett 0 siblings, 1 reply; 32+ messages in thread From: Alan Stern @ 2009-06-08 3:10 UTC (permalink / raw) To: Matthew Garrett Cc: alan-jenkins, Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Mon, 8 Jun 2009, Matthew Garrett wrote: > On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote: > > > There's no mechanism for this. It many environments it couldn't work, > > because the decision about whether to enable autosuspend is made when > > the device is first created (i.e., when the creation uevent is > > received), whereas driver binding doesn't occur until later. > > There's a lot of power management situations where you don't end up with > the optimal power configuration until a driver's bound. It's certainly > possible to do this in userspace, but if we know that the hardware > supported by a given driver will always work then it seems reasonable to > have it whitelist autosuspend on that device. Sure. Such a thing could be added easily enough. It just doesn't exist now, that's all. Alan Stern ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-08 3:10 ` Alan Stern @ 2009-06-08 15:00 ` Matthew Garrett 2009-06-08 20:44 ` Alan Stern 0 siblings, 1 reply; 32+ messages in thread From: Matthew Garrett @ 2009-06-08 15:00 UTC (permalink / raw) To: Alan Stern Cc: alan-jenkins, Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Sun, Jun 07, 2009 at 11:10:52PM -0400, Alan Stern wrote: > On Mon, 8 Jun 2009, Matthew Garrett wrote: > > > On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote: > > > > > There's no mechanism for this. It many environments it couldn't work, > > > because the decision about whether to enable autosuspend is made when > > > the device is first created (i.e., when the creation uevent is > > > received), whereas driver binding doesn't occur until later. > > > > There's a lot of power management situations where you don't end up with > > the optimal power configuration until a driver's bound. It's certainly > > possible to do this in userspace, but if we know that the hardware > > supported by a given driver will always work then it seems reasonable to > > have it whitelist autosuspend on that device. > > Sure. Such a thing could be added easily enough. It just doesn't > exist now, that's all. Something roughly like this? We'd probably also want a function call so drivers can do it based on the ID of the device they're handling, but in some cases we can probably assume that all devices supported by the driver will work. diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c index d0a21a5..36f63a7 100644 --- a/drivers/usb/core/driver.c +++ b/drivers/usb/core/driver.c @@ -355,6 +355,8 @@ int usb_driver_claim_interface(struct usb_driver *driver, iface->condition = USB_INTERFACE_BOUND; mark_active(iface); iface->pm_usage_cnt = !(driver->supports_autosuspend); + if (driver->supports_autosuspend && driver->enable_autosuspend) + udev->autosuspend_disabled=0; usb_pm_unlock(udev); /* if interface was already added, bind now; else let diff --git a/include/linux/usb.h b/include/linux/usb.h index 3aa2cd1..b4696f2 100644 --- a/include/linux/usb.h +++ b/include/linux/usb.h @@ -819,6 +819,8 @@ struct usbdrv_wrap { * added to this driver by preventing the sysfs file from being created. * @supports_autosuspend: if set to 0, the USB core will not allow autosuspend * for interfaces bound to this driver. + * @enable_autosuspend: if set to 1, the USB core will automatically enable + * autosuspend for interfaces bound to this driver. * @soft_unbind: if set to 1, the USB core will not kill URBs and disable * endpoints before calling the driver's disconnect method. * @@ -861,6 +863,7 @@ struct usb_driver { struct usbdrv_wrap drvwrap; unsigned int no_dynamic_id:1; unsigned int supports_autosuspend:1; + unsigned int enable_autosuspend:1; unsigned int soft_unbind:1; }; #define to_usb_driver(d) container_of(d, struct usb_driver, drvwrap.driver) -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-08 15:00 ` Matthew Garrett @ 2009-06-08 20:44 ` Alan Stern 0 siblings, 0 replies; 32+ messages in thread From: Alan Stern @ 2009-06-08 20:44 UTC (permalink / raw) To: Matthew Garrett Cc: alan-jenkins, Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, linux-usb, Darren Salt On Mon, 8 Jun 2009, Matthew Garrett wrote: > On Sun, Jun 07, 2009 at 11:10:52PM -0400, Alan Stern wrote: > > On Mon, 8 Jun 2009, Matthew Garrett wrote: > > > > > On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote: > > > > > > > There's no mechanism for this. It many environments it couldn't work, > > > > because the decision about whether to enable autosuspend is made when > > > > the device is first created (i.e., when the creation uevent is > > > > received), whereas driver binding doesn't occur until later. > > > > > > There's a lot of power management situations where you don't end up with > > > the optimal power configuration until a driver's bound. It's certainly > > > possible to do this in userspace, but if we know that the hardware > > > supported by a given driver will always work then it seems reasonable to > > > have it whitelist autosuspend on that device. > > > > Sure. Such a thing could be added easily enough. It just doesn't > > exist now, that's all. > > Something roughly like this? We'd probably also want a function call so > drivers can do it based on the ID of the device they're handling, but in > some cases we can probably assume that all devices supported by the > driver will work. My preference would be to use a function call always, rather than relying on static driver information. It provides more flexibility. > diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c > index d0a21a5..36f63a7 100644 > --- a/drivers/usb/core/driver.c > +++ b/drivers/usb/core/driver.c > @@ -355,6 +355,8 @@ int usb_driver_claim_interface(struct usb_driver *driver, > iface->condition = USB_INTERFACE_BOUND; > mark_active(iface); > iface->pm_usage_cnt = !(driver->supports_autosuspend); > + if (driver->supports_autosuspend && driver->enable_autosuspend) > + udev->autosuspend_disabled=0; Style violation: You should have blanks around the '=' sign. :-) > usb_pm_unlock(udev); That's right. If implemented as a function, turning off udev->autosuspend_disabled is all the function would need to do (provided we add the restriction that it should never be called from anywhere except inside a driver's probe routine). Alan Stern ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 14:55 ` Alan Jenkins 2009-06-05 15:08 ` Alan Jenkins @ 2009-06-05 15:13 ` Alan Stern 2009-06-05 15:22 ` Pekka Enberg 1 sibling, 1 reply; 32+ messages in thread From: Alan Stern @ 2009-06-05 15:13 UTC (permalink / raw) To: Alan Jenkins Cc: Pekka Enberg, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, USB list On Fri, 5 Jun 2009, Alan Jenkins wrote: > Auto-suspend white-listing would be done on the basis of USB ids > (vendor, product). At the moment it's expected that userspace should > take ownership of it. There's no infrastructure for in-kernel > whitelisting. I think. That's right. We found it was hopeless to try doing this in the kernel so we dumped the whole mess into userspace. Alan Stern ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 15:13 ` Alan Stern @ 2009-06-05 15:22 ` Pekka Enberg 0 siblings, 0 replies; 32+ messages in thread From: Pekka Enberg @ 2009-06-05 15:22 UTC (permalink / raw) To: Alan Stern Cc: Alan Jenkins, Corentin Chary, acpi4asus-user, len.brown, linux-kernel, USB list Hi Alan, On Fri, 5 Jun 2009, Alan Jenkins wrote: >> Auto-suspend white-listing would be done on the basis of USB ids >> (vendor, product). At the moment it's expected that userspace should >> take ownership of it. There's no infrastructure for in-kernel >> whitelisting. I think. On Fri, Jun 5, 2009 at 6:13 PM, Alan Stern<stern@rowland.harvard.edu> wrote: > That's right. We found it was hopeless to try doing this in the kernel > so we dumped the whole mess into userspace. :-) I prefer that the kernel takes care of this things because, quite frankly, I usually end up fighting with user-space more than I ever do with the kernel. But don't mind me, I really have no say in USB development. I am just happy to have a working camera and can hand over the laptop back to my better half :-). Pekka ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 11:46 ` Corentin Chary 2009-06-05 12:44 ` Pekka Enberg @ 2009-06-05 21:01 ` Woody Suwalski 2009-06-06 7:12 ` Corentin Chary 1 sibling, 1 reply; 32+ messages in thread From: Woody Suwalski @ 2009-06-05 21:01 UTC (permalink / raw) To: Corentin Chary; +Cc: Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel Corentin Chary wrote: > On Fri, Jun 5, 2009 at 10:59 AM, Pekka J Enberg<penberg@cs.helsinki.fi> wrote: > >> From: Pekka Enberg <penberg@cs.helsinki.fi> >> >> If we leave the camera disabled by default, userspace programs (e.g. >> Skype, Cheese) leave the user out in the cold saying that the machine "has >> no camera." Therefore, it's better to enable camera by default and let >> people who really don't want it just disable the thing. >> >> Cc: <acpi4asus-user@lists.sourceforge.net> >> Cc: Len Brown <len.brown@intel.com> >> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> >> --- >> drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ >> 1 files changed, 16 insertions(+), 0 deletions(-) >> >> diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c >> index 353a898..c0f8eb1 100644 >> --- a/drivers/platform/x86/eeepc-laptop.c >> +++ b/drivers/platform/x86/eeepc-laptop.c >> @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, enum rfkill_state *state) >> } >> >> /* >> + * Camera helpers >> + */ >> + >> +static void eeepc_enable_camera(void) >> +{ >> + int err; >> + >> + err = set_acpi(CM_ASL_CAMERA, 1); >> + if (err) >> + printk(EEEPC_WARNING "Unable to enable camera %d\n", err); >> +} >> + >> +/* >> * Sys helpers >> */ >> static int parse_arg(const char *buf, unsigned long count, int *val) >> @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) >> result = eeepc_hwmon_init(dev); >> if (result) >> goto fail_hwmon; >> + >> + eeepc_enable_camera(); >> + >> /* Register platform stuff */ >> result = platform_driver_register(&platform_driver); >> if (result) >> -- >> 1.5.6.3 >> >> >> > > Hi, > First, I think a one line > set_acpi(CM_ASL_CAMERA, 1); > with a small comment is better. (If it fails, it's because there no > camera, so we don't mind). > > Anyway, I'm not sure it's a good idea to enable the camera by default. > It depends how many > power the camera is using (when idle). Coud you check that (with power > top maybe ?). > > Thanks > From our old measurements: idle camera is ~20mA out of ~650mA total power... (measured on 901 model). Woody -- Woody Suwalski, Xandros, Ottawa, Canada, 1-613-842-3498 x414 ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 21:01 ` Woody Suwalski @ 2009-06-06 7:12 ` Corentin Chary 2009-06-06 8:04 ` Alan Jenkins 0 siblings, 1 reply; 32+ messages in thread From: Corentin Chary @ 2009-06-06 7:12 UTC (permalink / raw) To: Woody Suwalski; +Cc: Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel On Fri, Jun 5, 2009 at 11:01 PM, Woody Suwalski<woodys@xandros.com> wrote: > Corentin Chary wrote: >> >> On Fri, Jun 5, 2009 at 10:59 AM, Pekka J Enberg<penberg@cs.helsinki.fi> >> wrote: >> >>> >>> From: Pekka Enberg <penberg@cs.helsinki.fi> >>> >>> If we leave the camera disabled by default, userspace programs (e.g. >>> Skype, Cheese) leave the user out in the cold saying that the machine >>> "has >>> no camera." Therefore, it's better to enable camera by default and let >>> people who really don't want it just disable the thing. >>> >>> Cc: <acpi4asus-user@lists.sourceforge.net> >>> Cc: Len Brown <len.brown@intel.com> >>> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> >>> --- >>> drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ >>> 1 files changed, 16 insertions(+), 0 deletions(-) >>> >>> diff --git a/drivers/platform/x86/eeepc-laptop.c >>> b/drivers/platform/x86/eeepc-laptop.c >>> index 353a898..c0f8eb1 100644 >>> --- a/drivers/platform/x86/eeepc-laptop.c >>> +++ b/drivers/platform/x86/eeepc-laptop.c >>> @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, >>> enum rfkill_state *state) >>> } >>> >>> /* >>> + * Camera helpers >>> + */ >>> + >>> +static void eeepc_enable_camera(void) >>> +{ >>> + int err; >>> + >>> + err = set_acpi(CM_ASL_CAMERA, 1); >>> + if (err) >>> + printk(EEEPC_WARNING "Unable to enable camera %d\n", >>> err); >>> +} >>> + >>> +/* >>> * Sys helpers >>> */ >>> static int parse_arg(const char *buf, unsigned long count, int *val) >>> @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) >>> result = eeepc_hwmon_init(dev); >>> if (result) >>> goto fail_hwmon; >>> + >>> + eeepc_enable_camera(); >>> + >>> /* Register platform stuff */ >>> result = platform_driver_register(&platform_driver); >>> if (result) >>> -- >>> 1.5.6.3 >>> >>> >>> >> >> Hi, >> First, I think a one line >> set_acpi(CM_ASL_CAMERA, 1); >> with a small comment is better. (If it fails, it's because there no >> camera, so we don't mind). >> >> Anyway, I'm not sure it's a good idea to enable the camera by default. >> It depends how many >> power the camera is using (when idle). Coud you check that (with power >> top maybe ?). >> >> Thanks >> > > From our old measurements: > > idle camera is ~20mA out of ~650mA total power... (measured on 901 model). > > Woody > > -- > Woody Suwalski, Xandros, Ottawa, Canada, 1-613-842-3498 x414 > > Do also have some results with echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level ? Thanks -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-06 7:12 ` Corentin Chary @ 2009-06-06 8:04 ` Alan Jenkins 0 siblings, 0 replies; 32+ messages in thread From: Alan Jenkins @ 2009-06-06 8:04 UTC (permalink / raw) To: Corentin Chary Cc: Woody Suwalski, Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel On 6/6/09, Corentin Chary <corentin.chary@gmail.com> wrote: > On Fri, Jun 5, 2009 at 11:01 PM, Woody Suwalski<woodys@xandros.com> wrote: >> Corentin Chary wrote: >>> >>> On Fri, Jun 5, 2009 at 10:59 AM, Pekka J Enberg<penberg@cs.helsinki.fi> >>> wrote: >>> >>>> >>>> From: Pekka Enberg <penberg@cs.helsinki.fi> >>>> >>>> If we leave the camera disabled by default, userspace programs (e.g. >>>> Skype, Cheese) leave the user out in the cold saying that the machine >>>> "has >>>> no camera." Therefore, it's better to enable camera by default and let >>>> people who really don't want it just disable the thing. >>>> >>>> Cc: <acpi4asus-user@lists.sourceforge.net> >>>> Cc: Len Brown <len.brown@intel.com> >>>> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi> >>>> --- >>>> drivers/platform/x86/eeepc-laptop.c | 16 ++++++++++++++++ >>>> 1 files changed, 16 insertions(+), 0 deletions(-) >>>> >>>> diff --git a/drivers/platform/x86/eeepc-laptop.c >>>> b/drivers/platform/x86/eeepc-laptop.c >>>> index 353a898..c0f8eb1 100644 >>>> --- a/drivers/platform/x86/eeepc-laptop.c >>>> +++ b/drivers/platform/x86/eeepc-laptop.c >>>> @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data, >>>> enum rfkill_state *state) >>>> } >>>> >>>> /* >>>> + * Camera helpers >>>> + */ >>>> + >>>> +static void eeepc_enable_camera(void) >>>> +{ >>>> + int err; >>>> + >>>> + err = set_acpi(CM_ASL_CAMERA, 1); >>>> + if (err) >>>> + printk(EEEPC_WARNING "Unable to enable camera %d\n", >>>> err); >>>> +} >>>> + >>>> +/* >>>> * Sys helpers >>>> */ >>>> static int parse_arg(const char *buf, unsigned long count, int *val) >>>> @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) >>>> result = eeepc_hwmon_init(dev); >>>> if (result) >>>> goto fail_hwmon; >>>> + >>>> + eeepc_enable_camera(); >>>> + >>>> /* Register platform stuff */ >>>> result = platform_driver_register(&platform_driver); >>>> if (result) >>>> -- >>>> 1.5.6.3 >>>> >>>> >>>> >>> >>> Hi, >>> First, I think a one line >>> set_acpi(CM_ASL_CAMERA, 1); >>> with a small comment is better. (If it fails, it's because there no >>> camera, so we don't mind). >>> >>> Anyway, I'm not sure it's a good idea to enable the camera by default. >>> It depends how many >>> power the camera is using (when idle). Coud you check that (with power >>> top maybe ?). >>> >>> Thanks >>> >> >> From our old measurements: >> >> idle camera is ~20mA out of ~650mA total power... (measured on 901 model). >> >> Woody >> >> -- >> Woody Suwalski, Xandros, Ottawa, Canada, 1-613-842-3498 x414 >> >> > > Do also have some results with > echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level > > ? Can I also ask if you tested with CONFIG_NO_HZ=y ? IIRC, the kernel shipped on my old Eee didn't have NOHZ. Without NOHZ, it won't save much _cpu_ power; cutting 10 wakeups/s off >100 won't make much difference. Ta Alan ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 8:59 [PATCH] eeepc-laptop: enable camera by default Pekka J Enberg 2009-06-05 11:46 ` Corentin Chary @ 2009-06-05 20:08 ` Andrew Morton 2009-06-06 7:25 ` Corentin Chary 1 sibling, 1 reply; 32+ messages in thread From: Andrew Morton @ 2009-06-05 20:08 UTC (permalink / raw) To: Pekka J Enberg; +Cc: corentincj, acpi4asus-user, len.brown, linux-kernel On Fri, 5 Jun 2009 11:59:41 +0300 (EEST) Pekka J Enberg <penberg@cs.helsinki.fi> wrote: > /* > + * Camera helpers > + */ > + > +static void eeepc_enable_camera(void) > +{ > + int err; > + > + err = set_acpi(CM_ASL_CAMERA, 1); > + if (err) > + printk(EEEPC_WARNING "Unable to enable camera %d\n", err); > +} > + > +/* > * Sys helpers > */ > static int parse_arg(const char *buf, unsigned long count, int *val) > @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) We can do this: --- a/drivers/platform/x86/eeepc-laptop.c~eeepc-laptop-enable-camera-by-default-fix +++ a/drivers/platform/x86/eeepc-laptop.c @@ -334,7 +334,7 @@ static const struct rfkill_ops eeepc_rfk * Camera helpers */ -static void eeepc_enable_camera(void) +static void __init eeepc_enable_camera(void) { int err; _ if we're so inclined? ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-05 20:08 ` Andrew Morton @ 2009-06-06 7:25 ` Corentin Chary 2009-06-06 7:31 ` Andrew Morton 0 siblings, 1 reply; 32+ messages in thread From: Corentin Chary @ 2009-06-06 7:25 UTC (permalink / raw) To: Andrew Morton; +Cc: Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel On Fri, Jun 5, 2009 at 10:08 PM, Andrew Morton<akpm@linux-foundation.org> wrote: > On Fri, 5 Jun 2009 11:59:41 +0300 (EEST) > Pekka J Enberg <penberg@cs.helsinki.fi> wrote: > >> /* >> + * Camera helpers >> + */ >> + >> +static void eeepc_enable_camera(void) >> +{ >> + int err; >> + >> + err = set_acpi(CM_ASL_CAMERA, 1); >> + if (err) >> + printk(EEEPC_WARNING "Unable to enable camera %d\n", err); >> +} >> + >> +/* >> * Sys helpers >> */ >> static int parse_arg(const char *buf, unsigned long count, int *val) >> @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void) > > We can do this: > > --- a/drivers/platform/x86/eeepc-laptop.c~eeepc-laptop-enable-camera-by-default-fix > +++ a/drivers/platform/x86/eeepc-laptop.c > @@ -334,7 +334,7 @@ static const struct rfkill_ops eeepc_rfk > * Camera helpers > */ > > -static void eeepc_enable_camera(void) > +static void __init eeepc_enable_camera(void) > { > int err; > > _ > > if we're so inclined? > Right, thanks, fixed patch pushed into acpi4asus. -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-06 7:25 ` Corentin Chary @ 2009-06-06 7:31 ` Andrew Morton 2009-06-06 7:52 ` Corentin Chary 0 siblings, 1 reply; 32+ messages in thread From: Andrew Morton @ 2009-06-06 7:31 UTC (permalink / raw) To: Corentin Chary; +Cc: Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary <corentin.chary@gmail.com> wrote: > fixed patch pushed into acpi4asus. What's that? Should it be added to linux-next? ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-06 7:31 ` Andrew Morton @ 2009-06-06 7:52 ` Corentin Chary 2009-06-06 9:17 ` Pekka Enberg 0 siblings, 1 reply; 32+ messages in thread From: Corentin Chary @ 2009-06-06 7:52 UTC (permalink / raw) To: Andrew Morton; +Cc: Pekka J Enberg, acpi4asus-user, len.brown, linux-kernel On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<akpm@linux-foundation.org> wrote: > On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary <corentin.chary@gmail.com> wrote: > >> fixed patch pushed into acpi4asus. > > What's that? > > Should it be added to linux-next? > http://acpi4asus.sourceforge.net/ - http://git.iksaif.net/?p=acpi4asus.git;a=summary The tree is based on git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 It's where I regroup eeepc/asus patchs before sending them to Len. I don't think it should be added to linux-next, because the patchs will first go into the acpi tree, wich is in linux-next. -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-06 7:52 ` Corentin Chary @ 2009-06-06 9:17 ` Pekka Enberg 2009-06-06 10:17 ` Corentin Chary 0 siblings, 1 reply; 32+ messages in thread From: Pekka Enberg @ 2009-06-06 9:17 UTC (permalink / raw) To: Corentin Chary; +Cc: Andrew Morton, acpi4asus-user, len.brown, linux-kernel Hi Corentin, On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary <corentin.chary@gmail.com> wrote: >>> fixed patch pushed into acpi4asus. On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<akpm@linux-foundation.org> wrote: >> What's that? >> >> Should it be added to linux-next? On Sat, Jun 6, 2009 at 10:52 AM, Corentin Chary <corentin.chary@gmail.com> wrote: > http://acpi4asus.sourceforge.net/ - > http://git.iksaif.net/?p=acpi4asus.git;a=summary > The tree is based on > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 > > It's where I regroup eeepc/asus patchs before sending them to Len. > > I don't think it should be added to linux-next, because the patchs > will first go into the acpi tree, wich is in linux-next. I guess the main question is how often does Len pull from your tree? If the delay is longer than few days, it might make sense to put your tree directly into linux-next for early integration. And as long as you don't rebase the "for-next" branch and keep it append-only, there isn't going to be any conflicts either when Len pulls your tree and publishes the result in linux-next. Pekka ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH] eeepc-laptop: enable camera by default 2009-06-06 9:17 ` Pekka Enberg @ 2009-06-06 10:17 ` Corentin Chary 0 siblings, 0 replies; 32+ messages in thread From: Corentin Chary @ 2009-06-06 10:17 UTC (permalink / raw) To: Pekka Enberg; +Cc: Andrew Morton, acpi4asus-user, len.brown, linux-kernel On Sat, Jun 6, 2009 at 11:17 AM, Pekka Enberg<penberg@cs.helsinki.fi> wrote: > Hi Corentin, > > On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary > <corentin.chary@gmail.com> wrote: >>>> fixed patch pushed into acpi4asus. > > On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<akpm@linux-foundation.org> wrote: >>> What's that? >>> >>> Should it be added to linux-next? > > On Sat, Jun 6, 2009 at 10:52 AM, Corentin Chary > <corentin.chary@gmail.com> wrote: >> http://acpi4asus.sourceforge.net/ - >> http://git.iksaif.net/?p=acpi4asus.git;a=summary >> The tree is based on >> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 >> >> It's where I regroup eeepc/asus patchs before sending them to Len. >> >> I don't think it should be added to linux-next, because the patchs >> will first go into the acpi tree, wich is in linux-next. > > I guess the main question is how often does Len pull from your tree? > If the delay is longer than few days, it might make sense to put your > tree directly into linux-next for early integration. And as long as > you don't rebase the "for-next" branch and keep it append-only, there > isn't going to be any conflicts either when Len pulls your tree and > publishes the result in linux-next. > > Pekka > Len does not pull my tree, I send series to him and cc linux-acpi. But if it could help early integration, maybe linux-next is the right way to go. I'm not very familiar with it, the only thing I have to do is create a "for-next" branch (no rebase, only finalized patchs) and them ask Andrew (or someone else ?) to add it to linux-next ? -- Corentin Chary http://xf.iksaif.net - http://uffs.org ^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~2009-06-08 20:44 UTC | newest] Thread overview: 32+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-06-05 8:59 [PATCH] eeepc-laptop: enable camera by default Pekka J Enberg 2009-06-05 11:46 ` Corentin Chary 2009-06-05 12:44 ` Pekka Enberg 2009-06-05 13:02 ` Corentin Chary 2009-06-05 13:39 ` Alan Jenkins 2009-06-05 13:51 ` Pekka Enberg 2009-06-05 13:54 ` Pekka Enberg 2009-06-05 13:58 ` Corentin Chary 2009-06-05 14:38 ` Alan Jenkins 2009-06-05 14:50 ` Pekka Enberg 2009-06-05 14:55 ` Alan Jenkins 2009-06-05 15:08 ` Alan Jenkins 2009-06-05 15:14 ` Pekka Enberg 2009-06-07 14:54 ` Darren Salt 2009-06-07 15:41 ` Alan Jenkins 2009-06-07 23:28 ` Matthew Garrett 2009-06-08 3:03 ` Alan Stern 2009-06-08 3:07 ` Matthew Garrett 2009-06-08 3:10 ` Alan Stern 2009-06-08 15:00 ` Matthew Garrett 2009-06-08 20:44 ` Alan Stern 2009-06-05 15:13 ` Alan Stern 2009-06-05 15:22 ` Pekka Enberg 2009-06-05 21:01 ` Woody Suwalski 2009-06-06 7:12 ` Corentin Chary 2009-06-06 8:04 ` Alan Jenkins 2009-06-05 20:08 ` Andrew Morton 2009-06-06 7:25 ` Corentin Chary 2009-06-06 7:31 ` Andrew Morton 2009-06-06 7:52 ` Corentin Chary 2009-06-06 9:17 ` Pekka Enberg 2009-06-06 10:17 ` Corentin Chary
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox