- 20 Aug, 2003 7 commits
-
-
bk://kernel.bkbits.net//home/mochel/linux-2.5-powerPatrick Mochel authored
into osdl.org:/home/mochel/src/kernel/linux-2.5-power
-
Patrick Mochel authored
It should depend on X86, since we can boot more generic kernels on a P4.
-
Patrick Mochel authored
Instead of having each driver set them in their own drivers.
-
Patrick Mochel authored
Instead of setting them manually in each driver, as they are registered.
-
Patrick Mochel authored
into osdl.org:/home/mochel/src/kernel/linux-2.5-power
-
Alan Cox authored
- Roadrunner address is defunct - 3c501/Z85230 are no longer maintained - Update other stuff because I will be away for a year
-
bk://linux.bkbits.net/linux-2.5Patrick Mochel authored
into kernel.bkbits.net:/home/mochel/linux-2.5-power
-
- 19 Aug, 2003 33 commits
-
-
bk://kernel.bkbits.net//home/mochel/linux-2.5-powerPatrick Mochel authored
into osdl.org:/home/mochel/src/kernel/linux-2.5-power
-
Patrick Mochel authored
Instead of putting them in struct device_driver (which few, if any drivers use directly), put them in the controlling bus_type of the device (which are currently responsible for claiming the methods and forwarding the calls to the bus-specific driver anyway). This will save 8 bytes per driver instance, which isn't that much, but it's something. It also makes it more obvious to the reader what is going on. And, it makes for easier bus-level defaults in the case the device has no driver attached. The old calls remain until all instances have been fixed up.
-
Patrick Mochel authored
- From conversations with Ben Herrenschmidt. Most devices should be able to handle powering down with interrupts enabled, which I already assume. But since suspending will stop I/O transactions before the call to power it off (making the device unusable anyway), there is no need to separate the calls - we may as well make it simpler for driver authors and require that driver authors do everything at the same time. There will always be devices that need to either power down or power up the device with interrupts disabled. They will get called with interrupts enabled, but may return -EAGAIN to be called again with interrupts disabled to do what they need to do. System devices are now always called only with interrupts disabled. Come on - they're system devices. Of course we need interrupts disabled.
-
bk://kernel.bkbits.net/davem/net-2.5Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Patrick Mochel authored
- Remove drivers_resume() and call from do_magic_resume2(). Handled by core. - When bringing devices back to life, call device_pm_resume() - Make sure we report the error from write_suspend_image() - Remove suspend_power_down() and call to it. Handled by PM core. - Move swap file resetting and freeing of pagedir to swsusp_free() - Remove extraneous in_atomic() checks. - Mark all resume functions __init. - Move resume_suspend_image() inside swsusp_read() and cleanup. - Make do_magic() report error.
-
Patrick Mochel authored
- Split suspend/resume code into the four functions called from the PM core. - Remove now-duplicated code. - Make sure PM core frees memory and sync's disks before we shut down devices. - Remove software_suspend(), in favor of pm_suspend(). - Remove unused definitions from suspend.h
-
Patrick Mochel authored
- Wrap unused function in same #ifdef as caller. - Boggle as to WTF CONFIG_MOUNT_ROOT_FAILED_MSG is supposed to do.
-
Patrick Mochel authored
A recent slew of ACPI "fixes" completely broke the build when one built without SMP, IO APICs, or Local APICs. Bad Intel, no cookie.
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.5
-
David S. Miller authored
-
Stephen Hemminger authored
-
François Romieu authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
Remove duplicate string definition. Same table already defined and exported in irlan_event.c
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
Ircomm in 2.6.0-test3 can just set the owner field in the tty structure like other drivers, and not mess with MOD_INC/MOD_DEC.
-
Robert Olsson authored
-
Chas Williams authored
-
Stephen Hemminger authored
- set owner field on tty ldisc - allocate network device objects with alloc_netdev - use list_head macros and put locking around list of devices - convert to seq_file for /proc - use change_mtu hook rather than guessing at mtu changes
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
When doing the audit for this change, it was obvious that several drivers allocate but never free the net_device. This fixes these drivers. This patch is riskier than the earlier ones, because it isn't just a simple substitution and maybe there is a reason they never free.
-
Stephen Hemminger authored
Drivers that use kfree in destructor are easily converted to use free_netdev.
-
Stephen Hemminger authored
Replace kfree with free_netdev in cleanup routines of protocols and network pseudo drivers.
-
Stephen Hemminger authored
s/kfree/free_netdev/ in cleanup routines of a bunch of different network drivers.
-
Stephen Hemminger authored
Replace kfree with free_netdev
-
Stephen Hemminger authored
s/kfree/free_netdev/ as appropriate for tokenring drivers.
-
Stephen Hemminger authored
Simple one line substitution of kfree with free_netdev for the bulk of the network drivers.
-