From owner-freebsd-mobile Mon Sep 16 20:27:34 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03705 for mobile-outgoing; Mon, 16 Sep 1996 20:27:34 -0700 (PDT) Received: from cssun.mathcs.emory.edu (cssun.mathcs.emory.edu [199.76.28.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03678; Mon, 16 Sep 1996 20:27:24 -0700 (PDT) Received: (from gshapiro@localhost) by cssun.mathcs.emory.edu (8.7.5/8.6.9-940818.01cssun) id XAA14628; Mon, 16 Sep 1996 23:27:17 -0400 (EDT) From: Gregg Shapiro Message-Id: <199609170327.XAA14628@cssun.mathcs.emory.edu> Subject: automatically initiating apm and CPU idling questions To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Date: Mon, 16 Sep 1996 23:27:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi: I am running 2.1 on a Micron P166 mini-tower PC and am just about to upgrade to 2.1.5. My questions are: 1 - If I am running X, is there a way to initiate the APM functionality automatically after say my X server places my monitor into suspend mode ? Is this also possible if X is not running ? I can manually run zzz to put the CPU into sleep mode, but it would be great to do it automatically, (kinda like the way Windows 95 does it - sorry if I offended anybody by mentioning a lesser OS) 2 - Is there anyway to enable CPU Idling ? I know my CPU and video hardware support it because it works under Windows 95. But when I boot FreeBSD, it says that it is disabling CPU idling. 3 - Is there a way to automatically power off my PC after shutting down ? I have a "soft ?" power button on my motherboard that, under WIN 95 will turn off the power after exiting. Thanks a lot, Gregg -- Gregg Shapiro Emory University, Atlanta, GA email: gshapiro@mathcs.emory.edu From owner-freebsd-mobile Tue Sep 17 14:43:54 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16182 for mobile-outgoing; Tue, 17 Sep 1996 14:43:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16176 for ; Tue, 17 Sep 1996 14:43:48 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03719; Tue, 17 Sep 1996 15:40:16 -0600 (MDT) Date: Tue, 17 Sep 1996 15:40:16 -0600 (MDT) Message-Id: <199609172140.PAA03719@rocky.mt.sri.com> From: Nate Williams To: BRETT_GLASS@ccgate.infoworld.com Cc: mobile@freebsd.org Subject: Re: PCMCIA, APM, 3C562 In-Reply-To: <9608168429.AA842902427@ccgate.infoworld.com> References: <9608168429.AA842902427@ccgate.infoworld.com> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Moved to -mobile ] > Have given up on OS/2 for my laptop.... It seems to be crashing and failing > big-time under the Merlin gamma, and my bug reports have been utterly > ignored. So, I'd like to try FreeBSD on it. But first, some questions: > > How good is the PCMCIA support in FreeBSD? Will I be able to swap cards? Pretty good, but not great. For a Unix, it's as good as almost every other one out on the market. (Better than SCO, better than Unixware, almost as good as Linux, and a bit worse than Solaris x86 which has pretty good support. > Is APM supported? Most newer laptops work pretty well. Some still have problems though, but I'm working on those. APM has been my baby (and thorn in the flesh), and I'm hoping to make it better in the very near future using some code from John Kohl I just got. > Will the system (including PCMCIA) be able to survive a > suspend/resume cycle without "freaking out" or getting too busy to use due > to missed items in /etc/crontab? Not a problem. On my laptops (I use various ThinkPad and NEC Versa for development and testing) suspend/resume works 'most of the time'. I haven't taken the time to look more into things this summer due to other committments, but I hope to ramp back up again pretty quick on things. As far as cron goes, it'll do all the old cron jobs when it comes up (or at least it's supposed to.) If you're worried about old cron jobs getting queued up, either disable cron or don't leave your laptop suspended for more than 48 hours. :) > (Come to think of it, how DOES it handle > missed items in /etc/crontab?) See above. > Is there a sync on suspend? If the battery > dies during a suspend (common on many laptops that suspend when the > battery gets low), is the filesystem left "clean" and ready for a reboot? The above could be done, but aren't right now. Because 'suspend' means "I'll be back", you don't want it to go into single user mode. I'm not sure if we do a 'sync', but we certainly should. I can't check right now as we just moved offices and all our FreeBSD boxes except the router are off the network until we get it wired 'for real'. > Finally, there doesn't appear to be a driver for my 3C562 Modem/Ethernet > combo card. As I understand it, this card is really just a 3Com Ethernet > adapter and a modem (with standard UART) sharing an IRQ. Is there a driver > available? No, and I don't think you'll find one very soon. The support for 'sharing' interrupts doesn't work very well (at all?) right now, and given the task of making the existing code work better I don't see it happening anytime soon. However, the Nomad's may be working on getting a driver for it, but if/when that'll happen only they know. [ The Nomad's are a group of Japanese SW developers who have been doing most of the new PCCARD development for the past 9 months. ] Nate From owner-freebsd-mobile Tue Sep 17 21:13:20 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA29542 for mobile-outgoing; Tue, 17 Sep 1996 21:13:20 -0700 (PDT) Received: from lserver.infoworld.com (root@lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29530 for ; Tue, 17 Sep 1996 21:13:17 -0700 (PDT) Received: from ccgate.infoworld.com (ccgate.infoworld.com [192.216.49.101]) by lserver.infoworld.com (8.7.5/8.7.3) with SMTP id VAA02975; Tue, 17 Sep 1996 21:13:06 -0700 (PDT) From: BRETT_GLASS@infoworld.com Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA843019805; Tue, 17 Sep 96 23:08:20 PST Date: Tue, 17 Sep 96 23:08:20 PST Message-Id: <9608178430.AA843019805@ccgate.infoworld.com> To: Nate Williams Cc: nate@mt.sri.com, mobile@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: PCMCIA, APM, 3C562 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The PCIC support code currently doesn't shared interrupts. But, > *anything* is possible given enough time and effort, and if you choose > not to use the PCIC support code (/sys/pccard), then you might be able > to pull it off. I think you misunderstand. What I would do is write ONE DRIVER that handled interrupts from the card by passing them through to existing serial and Ethernet code. As far as the PCMCIA code was concerned, the interrupt wouldn't look as if it was shared, since the interrupts would all be dispatched by that driver. --Brett From owner-freebsd-mobile Tue Sep 17 21:17:12 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01586 for mobile-outgoing; Tue, 17 Sep 1996 21:17:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01540 for ; Tue, 17 Sep 1996 21:17:05 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA05200; Tue, 17 Sep 1996 22:16:43 -0600 (MDT) Date: Tue, 17 Sep 1996 22:16:43 -0600 (MDT) Message-Id: <199609180416.WAA05200@rocky.mt.sri.com> From: Nate Williams To: BRETT_GLASS@infoworld.com Cc: Nate Williams , mobile@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: PCMCIA, APM, 3C562 In-Reply-To: <9608178430.AA843019805@ccgate.infoworld.com> References: <9608178430.AA843019805@ccgate.infoworld.com> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The PCIC support code currently doesn't shared interrupts. But, > > *anything* is possible given enough time and effort, and if you choose > > not to use the PCIC support code (/sys/pccard), then you might be able > > to pull it off. > > I think you misunderstand. What I would do is write ONE DRIVER that handled > interrupts from the card by passing them through to existing serial and > Ethernet code. As far as the PCMCIA code was concerned, the interrupt > wouldn't look as if it was shared, since the interrupts would all be > dispatched by that driver. Again, like I said anything is possible given enought time and effort. Hooking into the existing drivers from a driver isn't a trivial task since they have 'bottom-end' drivers which expect to run quickly as interrupt handlers and thus must act quickly. I expect the upper drivers might 'MUX' well, it's the lower-end stuff that's a bit more work. But, I'm more than willing to be blown away with ingenuity of software developers. :) :) Nate From owner-freebsd-mobile Wed Sep 18 00:02:27 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA18448 for mobile-outgoing; Wed, 18 Sep 1996 00:02:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA18396 for ; Wed, 18 Sep 1996 00:02:21 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA04623; Wed, 18 Sep 1996 16:31:29 +0930 From: Michael Smith Message-Id: <199609180701.QAA04623@genesis.atrad.adelaide.edu.au> Subject: Re: PCMCIA, APM, 3C562 To: BRETT_GLASS@infoworld.com Date: Wed, 18 Sep 1996 16:31:28 +0930 (CST) Cc: nate@mt.sri.com, mobile@freebsd.org, msmith@atrad.adelaide.edu.au In-Reply-To: <9608178430.AA843015988@ccgate.infoworld.com> from "BRETT_GLASS@infoworld.com" at Sep 17, 96 05:38:53 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk BRETT_GLASS@infoworld.com stands accused of saying: > > >> Will the system (including PCMCIA) be able to survive a > >> suspend/resume cycle without "freaking out" or getting too busy to use > >> due > to missed items in /etc/crontab? > > > Not a problem. On my laptops (I use various ThinkPad and NEC Versa for > > development and testing) suspend/resume works 'most of the time'. I > > haven't taken the time to look more into things this summer due to other > > committments, but I hope to ramp back up again pretty quick on things. > > As far as cron goes, it'll do all the old cron jobs when it comes up (or > > at least it's supposed to.) If you're worried about old cron jobs > > getting queued up, either disable cron or don't leave your laptop > > suspended for more than 48 hours. :) > > But Michael says: > > > The system syncs on suspend, and snaps the clock when it resumes, so that > > missed cron jobs are just lost. Filesystems aren't marked clean, as that > > requires an unmount. Some PCC's require reinitialisation coming out of > > a suspend (and removing a card while suspended can cause grief), and > > support for that is in place but not implemented. > > Which is correct? I should have said "I think missed cron jobs are lost". I've never pulled mine out of suspend and had it go nuts cron-wise; but I reserve the right to be totally wrong. > You also said that the system might NOT do a sync on suspend, which > concerns me. I don't have my system here, so I can't verify this, but again I'm _fairly_ sure that it does. YMMV; I would suggest trying it 8) > Also, in response to my question about the existence of a 3C562 driver, you > said: > > > No, and I don't think you'll find one very soon. The support for > > 'sharing' interrupts doesn't work very well (at all?) right now, and > > given the task of making the existing code work better I don't see it > > happening anytime soon. > > But Michael affirmed that it might be possible to write a combination > driver that links parts of the SIO and 3Com PCMCIA Ethernet code. (Because > it would be one driver, it could dispatch the interrupts to routines from > the existing drivers.) What do you think? I guess this is a difference of interpretation. Nate can't see it happening soon because it's low on his list; I can see you doing it if you persevere with FreeBSD just because it's necessary 8) > --Brett -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-mobile Wed Sep 18 17:02:34 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA15573 for mobile-outgoing; Wed, 18 Sep 1996 17:02:34 -0700 (PDT) Received: from lachesis.c2.net (niobe.c2.net [140.174.185.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA15549 for ; Wed, 18 Sep 1996 17:02:31 -0700 (PDT) Received: (from sameer@localhost) by lachesis.c2.net (8.7.5/CSUA) id RAA24835 for freebsd-mobile@freebsd.org; Wed, 18 Sep 1996 17:02:13 -0700 (PDT) Message-Id: <199609190002.RAA24835@lachesis.c2.net> Subject: 3com pcmcia etherlink question To: freebsd-mobile@freebsd.org Date: Wed, 18 Sep 1996 17:02:12 -0700 (PDT) From: sameer X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This isn't freebsd-related, but please bear with me. So I've just now broken for the second time the thing that plugs my etherlink iii into my 10baseT cable. The first time I broke it I just bought a new card, but that's really not a good long term solution. Is there some way I can just buy the things? thanks, -- Sameer Parekh Voice: 510-986-8770 C2Net FAX: 510-986-8777 The Internet Privacy Provider http://www.c2.net/ sameer@c2.net From owner-freebsd-mobile Wed Sep 18 21:22:46 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25004 for mobile-outgoing; Wed, 18 Sep 1996 21:22:46 -0700 (PDT) Received: from lachesis.c2.net (niobe.c2.net [140.174.185.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24972 for ; Wed, 18 Sep 1996 21:22:42 -0700 (PDT) Received: (from sameer@localhost) by lachesis.c2.net (8.7.5/CSUA) id VAA03333; Wed, 18 Sep 1996 21:22:17 -0700 (PDT) Message-Id: <199609190422.VAA03333@lachesis.c2.net> Subject: Re: 3com pcmcia etherlink question To: nate@mt.sri.com (Nate Williams) Date: Wed, 18 Sep 1996 21:22:16 -0700 (PDT) Cc: sameer@c2.net, freebsd-mobile@freebsd.org In-Reply-To: <199609190415.WAA15806@rocky.mt.sri.com> from "Nate Williams" at Sep 18, 96 10:15:43 pm From: sameer X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have the C. It doesn't seem all that robust to me, having broken two of them already. Know of any other options for this sort of thing? > > > So I've just now broken for the second time the thing that > > plugs my etherlink iii into my 10baseT cable. The first time I broke > > it I just bought a new card, but that's really not a good long term > > solution. > > Is there some way I can just buy the things? > > Nope. Are you using the 3C589B or 3C589C card? The newer model (C) has > a much better connector than the older models. I have both, and I > prefer the newer style as it 'seems' more robust. > > > Nate > -- Sameer Parekh Voice: 510-986-8770 C2Net FAX: 510-986-8777 The Internet Privacy Provider http://www.c2.net/ sameer@c2.net From owner-freebsd-mobile Wed Sep 18 21:23:25 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25326 for mobile-outgoing; Wed, 18 Sep 1996 21:23:25 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA25299 for ; Wed, 18 Sep 1996 21:23:21 -0700 (PDT) Received: from rocky.mt.sri.com by mail.crl.com with SMTP id AA11822 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 21:23:55 -0700 Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA15806; Wed, 18 Sep 1996 22:15:43 -0600 (MDT) Date: Wed, 18 Sep 1996 22:15:43 -0600 (MDT) Message-Id: <199609190415.WAA15806@rocky.mt.sri.com> From: Nate Williams To: sameer Cc: freebsd-mobile@freebsd.org Subject: Re: 3com pcmcia etherlink question In-Reply-To: <199609190002.RAA24835@lachesis.c2.net> References: <199609190002.RAA24835@lachesis.c2.net> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > So I've just now broken for the second time the thing that > plugs my etherlink iii into my 10baseT cable. The first time I broke > it I just bought a new card, but that's really not a good long term > solution. > Is there some way I can just buy the things? Nope. Are you using the 3C589B or 3C589C card? The newer model (C) has a much better connector than the older models. I have both, and I prefer the newer style as it 'seems' more robust. Nate From owner-freebsd-mobile Wed Sep 18 21:33:18 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA29834 for mobile-outgoing; Wed, 18 Sep 1996 21:33:18 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA29802 for ; Wed, 18 Sep 1996 21:33:14 -0700 (PDT) Received: from rocky.mt.sri.com by mail.crl.com with SMTP id AA13391 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 21:33:18 -0700 Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA15849; Wed, 18 Sep 1996 22:25:52 -0600 (MDT) Date: Wed, 18 Sep 1996 22:25:52 -0600 (MDT) Message-Id: <199609190425.WAA15849@rocky.mt.sri.com> From: Nate Williams To: sameer Cc: nate@mt.sri.com (Nate Williams), freebsd-mobile@freebsd.org Subject: Re: 3com pcmcia etherlink question In-Reply-To: <199609190422.VAA03333@lachesis.c2.net> References: <199609190415.WAA15806@rocky.mt.sri.com> <199609190422.VAA03333@lachesis.c2.net> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Breaking the network connectors on the 3Com PCMCIA ethernet cards ] > I have the C. It doesn't seem all that robust to me, having > broken two of them already. Know of any other options for this sort of > thing? Be gentler on the connector. Patient: "Doctor, doctor, it hurts when I do this." Doctor: "Don't do that." Seriously, I've had both my 3Com cards and have never had any problems with them, and the older of the two is a year and a half old. If you be careful with them, they'll last a long time. Almost *all* PCCARD with external connectors have the same problem. It's a simple problem with size. When things get that small and cheap, they are easily broken. Nate From owner-freebsd-mobile Thu Sep 19 08:06:48 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15380 for mobile-outgoing; Thu, 19 Sep 1996 08:06:48 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA15261; Thu, 19 Sep 1996 08:06:27 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA18010; Thu, 19 Sep 1996 09:06:25 -0600 (MDT) Date: Thu, 19 Sep 1996 09:06:25 -0600 (MDT) Message-Id: <199609191506.JAA18010@rocky.mt.sri.com> From: Nate Williams To: Poul-Henning Kamp Cc: CVS-committers@freefall.freebsd.org, mobile@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 swtch.s src/sys/i386/conf LINT In-Reply-To: <199609190828.BAA14440@freefall.freebsd.org> References: <199609190828.BAA14440@freefall.freebsd.org> Sender: owner-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Modified: sys/i386/conf LINT > sys/i386/i386 swtch.s > Log: > Add APM_IDLE_CPU option, that is off by default. > I maintain that it saves more power to simply "hlt" the CPU than to > spend tons of time trying to tell the APM bios to do the same. > In particular if you do it 100 times a second... FWIW, I sort of agree with Poul here. He asked me to do some timing tests on my laptops (which I actually did), and it appears that doing the idle/busy stuff on one of my laptops made very little difference. I got an extra 9 minutes with the APM code enabled 3 hours, 10 minutes vs 3 hours and 1 minutes with it disabled. However, this was one run on a fairly modern latop. I want to try testing on the other three models I have lying around, but other committments have been brutal. If other folks could test out disabling the idle stuff it would be great. Power cycle your battery a couple times to make sure you aren't affected by that, and then power it up full. Boot a kernel with the busy/idle loop enabled (the default), enable apm (apmconf -e), unplug it and wait until it suspends. Mark the time down and do the same thing with a kernel with the above option enabled and see what you get. Poul and I have talked about this already, and we think that a hueristic which determines 'a period' of idleness would be a better solution. That way we could kick it into 'apm_idle' if the machine has been idle for X cycles rather than kicking it in and out *all* the time. Nate From owner-freebsd-mobile Thu Sep 19 08:28:56 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA24194 for mobile-outgoing; Thu, 19 Sep 1996 08:28:56 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA24154; Thu, 19 Sep 1996 08:28:48 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id RAA00221; Thu, 19 Sep 1996 17:28:15 +0200 (MET DST) To: Nate Williams cc: Poul-Henning Kamp , CVS-committers@freefall.freebsd.org, mobile@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 swtch.s src/sys/i386/conf LINT In-reply-to: Your message of "Thu, 19 Sep 1996 09:06:25 MDT." <199609191506.JAA18010@rocky.mt.sri.com> Date: Thu, 19 Sep 1996 17:28:15 +0200 Message-ID: <219.843146895@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199609191506.JAA18010@rocky.mt.sri.com>, Nate Williams writes: >Poul and I have talked about this already, and we think that a hueristic >which determines 'a period' of idleness would be a better solution. >That way we could kick it into 'apm_idle' if the machine has been idle >for X cycles rather than kicking it in and out *all* the time. And we could even use the various "slowdown" modes available in some cases too... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-mobile Thu Sep 19 10:48:01 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15599 for mobile-outgoing; Thu, 19 Sep 1996 10:48:01 -0700 (PDT) Received: from lachesis.c2.net (niobe.c2.net [140.174.185.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA15568 for ; Thu, 19 Sep 1996 10:47:58 -0700 (PDT) Received: (from sameer@localhost) by lachesis.c2.net (8.7.5/CSUA) id KAA26443; Thu, 19 Sep 1996 10:46:40 -0700 (PDT) Message-Id: <199609191746.KAA26443@lachesis.c2.net> Subject: Re: 3com pcmcia etherlink question To: nate@mt.sri.com (Nate Williams) Date: Thu, 19 Sep 1996 10:46:40 -0700 (PDT) Cc: sameer@c2.net, nate@mt.sri.com, freebsd-mobile@freebsd.org In-Reply-To: <199609190425.WAA15849@rocky.mt.sri.com> from "Nate Williams" at Sep 18, 96 10:25:52 pm From: sameer X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Be gentler on the connector. I suppose that's what I'll have to do. Thanks. > external connectors have the same problem. It's a simple problem with > size. When things get that small and cheap, they are easily broken. -- Sameer Parekh Voice: 510-986-8770 C2Net FAX: 510-986-8777 The Internet Privacy Provider http://www.c2.net/ sameer@c2.net