From owner-freebsd-mobile Mon Apr 14 06:19:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA10995 for mobile-outgoing; Mon, 14 Apr 1997 06:19:24 -0700 (PDT) Received: from postman.osf.org (postman.osf.org [130.105.1.152]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10990 for ; Mon, 14 Apr 1997 06:19:21 -0700 (PDT) Received: from conan.osf.org (conan.osf.org [130.105.2.35]) by postman.osf.org (8.7.6/8.7.3) with SMTP id JAA14216 for ; Mon, 14 Apr 1997 09:18:50 -0400 (EDT) Message-Id: <199704141318.JAA14216@postman.osf.org> X-Authentication-Warning: postman.osf.org: Host conan.osf.org [130.105.2.35] didn't use HELO protocol X-Mailer: exmh version 2.0gamma 1/27/97 To: mobile@freebsd.org Subject: 3c562 X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://www.osf.org/~loverso/ Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_269710104180" Date: Mon, 14 Apr 1997 09:18:48 -0400 From: John Robert LoVerso Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --==_Exmh_269710104180 Content-Type: text/plain I have a laptop (using PAO-960831 with 2.1.5; it'll be upgraded later this week) with which I've been successfully using a 3c589c. However, I also have two different 3c562s, one with a 28.8 and one with a 33.3 modem. The later, newer one claims to be a "3c562c". I understand that there is no support yet for duplicating IRQs for multifunction cards. I just want to get FreeBSD to use *either* the modem *or* the Ethernet controller on the 562. Perferrably the Ethernet, as it would allow me to give up the 589 (to someone else here who needs it). Can anyone help me? Enclosed are the "pccardc dumpcis" output from all three cards. Thanks, John --==_Exmh_269710104180 Content-Type: text/plain ; name="dumpcis.562.new" Content-Description: dumpcis.562.new Content-Disposition: attachment; filename="dumpcis.562.new" Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 66 000: 04 01 33 43 6f 6d 20 43 6f 72 70 6f 72 61 74 69 010: 6f 6e 00 33 43 35 36 32 43 2f 33 43 35 36 33 43 020: 00 45 74 68 65 72 4c 69 6e 6b 20 49 49 49 00 4c 030: 41 4e 2b 4d 6f 64 65 6d 20 50 43 20 43 61 72 64 040: 00 ff Version = 4.1, Manuf = [3Com Corporation],card vers = [3C562C/3C563C] Addit. info = [EtherLink III],[LAN+Modem PC Card] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 01 01 62 05 PCMCIA ID = 0x101, OEM ID = 0x562 Tuple #4, code = 0x12 (Long link to common memory), length = 4 000: 00 00 00 00 Long link to common memory, address 0x0 Tuple #5, code = 0x1a (Configuration map), length = 6 000: 05 09 80 10 ff 03 Reg len = 2, config register addr = 0x1080, last config = 0x9 Registers: XXXXXXXX XX------ Tuple #6, code = 0x1b (Configuration entry), length = 15 000: c9 01 1d 71 55 35 55 54 e0 72 5d 64 30 ff ff Config index = 0x9(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 3 x 10mA Max current average over 10 ms: 5 x 10mA Power down supply current: 5 x 1mA Wait scale Speed = 7.0 x 100 ns RDY/BSY scale Speed = 5.0 x 100 us Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #7, code = 0x1b (Configuration entry), length = 7 000: 09 01 71 55 26 26 54 Config index = 0x9 Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2 x 100mA Max current average over 10 ms: 2 x 100mA Power down supply current: 5 x 1mA Tuple #8, code = 0x17 (Attribute memory descriptor), length = 3 000: 43 02 ff Attribute memory device information: Device number 1, type EEPROM, WPS = OFF Speed = 150nS, Memory block size = 8Kb, 1 units Tuple #9, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #10, code = 0x10 (Checksum), length = 5 000: 81 ff 89 00 00 Checksum from offset -127, length 137, value is 0x0 Tuple #11, code = 0xff (Terminator), length = 112 000: 00 13 03 43 49 53 21 02 06 00 1a 06 05 07 80 10 010: ff 03 1b 0f c7 01 1d 71 55 35 55 54 e0 72 5d 64 020: 30 ff ff 1b 07 07 01 71 55 26 26 54 ff 13 03 43 030: 49 53 21 02 02 01 22 04 00 02 0f 5c 22 09 01 1f 040: 3f 00 04 00 00 04 00 22 0c 02 06 00 2f 1f 03 03 050: 17 02 00 00 ff 22 08 13 06 00 1f 00 00 00 ff 22 060: 08 23 06 00 1f 00 01 00 ff 1a 06 05 27 00 10 ff --==_Exmh_269710104180 Content-Type: text/plain ; name="dumpcis.562.old" Content-Description: dumpcis.562.old Content-Disposition: attachment; filename="dumpcis.562.old" Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 58 000: 04 01 33 43 6f 6d 20 43 6f 72 70 6f 72 61 74 69 010: 6f 6e 00 33 43 35 36 32 00 45 74 68 65 72 4c 69 020: 6e 6b 20 49 49 49 00 4c 41 4e 2b 4d 6f 64 65 6d 030: 20 50 43 20 43 61 72 64 00 ff Version = 4.1, Manuf = [3Com Corporation],card vers = [3C562] Addit. info = [EtherLink III],[LAN+Modem PC Card] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 01 01 62 05 PCMCIA ID = 0x101, OEM ID = 0x562 Tuple #4, code = 0x12 (Long link to common memory), length = 4 000: 00 00 00 00 Long link to common memory, address 0x0 Tuple #5, code = 0x1a (Configuration map), length = 6 000: 05 09 80 10 ff 03 Reg len = 2, config register addr = 0x1080, last config = 0x9 Registers: XXXXXXXX XX------ Tuple #6, code = 0x1b (Configuration entry), length = 15 000: c9 01 1d 71 55 35 55 54 e0 72 5d 64 30 ff ff Config index = 0x9(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 3 x 10mA Max current average over 10 ms: 5 x 10mA Power down supply current: 5 x 1mA Wait scale Speed = 7.0 x 100 ns RDY/BSY scale Speed = 5.0 x 100 us Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #7, code = 0x1b (Configuration entry), length = 7 000: 09 01 71 55 26 26 54 Config index = 0x9 Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2 x 100mA Max current average over 10 ms: 2 x 100mA Power down supply current: 5 x 1mA Tuple #8, code = 0x17 (Attribute memory descriptor), length = 3 000: 43 02 ff Attribute memory device information: Device number 1, type EEPROM, WPS = OFF Speed = 150nS, Memory block size = 8Kb, 1 units Tuple #9, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #10, code = 0x10 (Checksum), length = 5 000: 89 ff 80 00 00 Checksum from offset -119, length 128, value is 0x0 Tuple #11, code = 0xff (Terminator), length = 66 000: 13 03 43 49 53 21 02 06 00 1a 06 05 09 80 10 ff 010: 03 1b 0f c9 01 1d 71 55 35 55 54 e0 72 5d 64 30 020: ff ff 1b 07 09 01 71 55 26 26 54 ff 13 03 43 49 030: 53 21 02 02 01 22 04 00 02 0f 5c 22 09 01 1f 3f 040: 00 04 --==_Exmh_269710104180 Content-Type: text/plain ; name="dumpcis.589c" Content-Description: dumpcis.589c Content-Disposition: attachment; filename="dumpcis.589c" Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 43 02 ff Attribute memory device information: Device number 1, type EEPROM, WPS = OFF Speed = 150nS, Memory block size = 8Kb, 1 units Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 01 01 89 05 PCMCIA ID = 0x101, OEM ID = 0x589 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 57 000: 04 01 33 43 6f 6d 20 43 6f 72 70 6f 72 61 74 69 010: 6f 6e 00 33 43 35 38 39 00 54 50 2f 42 4e 43 20 020: 4c 41 4e 20 43 61 72 64 20 56 65 72 2e 20 32 61 030: 00 30 30 30 30 30 32 00 ff Version = 4.1, Manuf = [3Com Corporation],card vers = [3C589] Addit. info = [TP/BNC LAN Card Ver. 2a],[000002] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 02 03 00 00 01 03 Reg len = 3, config register addr = 0x10000, last config = 0x3 Registers: XX------ Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 01 1d 71 55 35 55 54 e0 72 5d 64 30 ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 3 x 10mA Max current average over 10 ms: 5 x 10mA Power down supply current: 5 x 1mA Wait scale Speed = 7.0 x 100 ns RDY/BSY scale Speed = 5.0 x 100 us Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #8, code = 0x1b (Configuration entry), length = 7 000: 03 01 71 55 26 26 54 Config index = 0x3 Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2 x 100mA Max current average over 10 ms: 2 x 100mA Power down supply current: 5 x 1mA Tuple #9, code = 0x19 (JEDEC descr for attribute memory), length = 3 000: 00 00 ff Tuple #10, code = 0x14 (No link), length = 0 Tuple #11, code = 0x10 (Checksum), length = 5 000: 89 ff 80 00 00 Checksum from offset -119, length 128, value is 0x0 Tuple #12, code = 0xff (Terminator), length = 218 000: 00 03 00 00 00 00 00 00 43 32 20 54 45 41 4d 2d 010: 45 61 72 6c 20 41 6c 64 72 69 64 67 65 2c 20 52 020: 65 78 20 41 6c 6c 65 72 73 2c 20 52 75 73 73 65 030: 6c 6c 20 43 68 61 6e 67 2c 20 44 61 76 69 64 20 040: 43 68 69 68 2c 20 48 65 72 6d 61 6e 20 4c 61 6f 050: 2c 20 47 65 6e 65 20 4c 69 6e 2c 20 4c 69 61 6e 060: 67 20 4c 69 6e 2c 20 48 69 65 6e 20 4e 67 75 79 070: 65 6e 2c 20 4b 61 70 20 53 6f 68 2c 20 47 61 72 080: 79 20 57 61 6e 67 00 ff ff ff ff ff ff ff ff ff 090: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0d0: ff ff ff ff ff ff ff ff ff ff --==_Exmh_269710104180-- From owner-freebsd-mobile Mon Apr 14 08:13:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA19803 for mobile-outgoing; Mon, 14 Apr 1997 08:13:53 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19787 for ; Mon, 14 Apr 1997 08:13:44 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA23185; Mon, 14 Apr 1997 09:13:17 -0600 (MDT) Date: Mon, 14 Apr 1997 09:13:17 -0600 (MDT) Message-Id: <199704141513.JAA23185@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Robert LoVerso Cc: mobile@freebsd.org Subject: Re: 3c562 In-Reply-To: <199704141318.JAA14216@postman.osf.org> References: <199704141318.JAA14216@postman.osf.org> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just want to get FreeBSD to use *either* the > modem *or* the Ethernet controller on the 562. Perferrably the Ethernet, > as it would allow me to give up the 589 (to someone else here who needs it). Does it work with the normal 589 entry? Looking at the output of dumpcis, it might. I haven't messed with multiple device cards enough to read the results of dumpcis. Maybe Tatsumi-san can help here? Nate From owner-freebsd-mobile Mon Apr 14 09:23:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA24565 for mobile-outgoing; Mon, 14 Apr 1997 09:23:01 -0700 (PDT) Received: from postman.osf.org (postman.osf.org [130.105.1.152]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24538 for ; Mon, 14 Apr 1997 09:22:49 -0700 (PDT) Received: from conan.osf.org (conan.osf.org [130.105.2.35]) by postman.osf.org (8.7.6/8.7.3) with SMTP id MAA18654; Mon, 14 Apr 1997 12:21:43 -0400 (EDT) Message-Id: <199704141621.MAA18654@postman.osf.org> X-Authentication-Warning: postman.osf.org: Host conan.osf.org [130.105.2.35] didn't use HELO protocol To: Nate Williams Cc: mobile@freebsd.org Subject: Re: 3c562 In-reply-to: Message from Nate Williams <199704141513.JAA23185@rocky.mt.sri.com> . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://www.osf.org/~loverso/ Date: Mon, 14 Apr 1997 12:21:41 -0400 From: John Robert LoVerso Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, if it worked with the 589 entry, would I be sending this mail? 8-} All I get is this pccardd[30]: Resource allocation failure for 3Com Corporation pccardd[30]: Reason: CIS not found I tried to create pccard.conf entries for the two cards (562 and 562c). They are identical, 'cept that I was trying to use the Enet on the 562c and the sio on the 562. # 3Com Etherlink III 3C562 card "3Com Corporation" "3C562" # config default "ep0" any # config 0x23 "sio2" any config 0x22 "sio2" any insert echo 562 In remove echo 562 Out # 3Com Etherlink III 3C562C card "3Com Corporation" "3C562C/3C563C" config default "ep0" any # config 0x23 "sio2" any # config 0x22 "sio2" any insert echo 562 In remove echo 562 Out John From owner-freebsd-mobile Mon Apr 14 09:28:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA24987 for mobile-outgoing; Mon, 14 Apr 1997 09:28:17 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24981 for ; Mon, 14 Apr 1997 09:28:14 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA23626; Mon, 14 Apr 1997 10:28:08 -0600 (MDT) Date: Mon, 14 Apr 1997 10:28:08 -0600 (MDT) Message-Id: <199704141628.KAA23626@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Robert LoVerso Cc: Nate Williams , mobile@freebsd.org Subject: Re: 3c562 In-Reply-To: <199704141621.MAA18654@postman.osf.org> References: <199704141513.JAA23185@rocky.mt.sri.com> <199704141621.MAA18654@postman.osf.org> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, if it worked with the 589 entry, would I be sending this mail? 8-} You never know. :) > All I get is this > > pccardd[30]: Resource allocation failure for 3Com Corporation > pccardd[30]: Reason: CIS not found Try 'pccard -d' and see what the output is. Nate From owner-freebsd-mobile Thu Apr 17 13:10:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01475 for mobile-outgoing; Thu, 17 Apr 1997 13:10:48 -0700 (PDT) Received: from sol.harbor.ab.ca (sol100.harbor.ab.ca [198.161.82.169]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA01468; Thu, 17 Apr 1997 13:10:44 -0700 (PDT) Received: from olympus (olympus.harbor.ab.ca [198.161.82.144]) by sol.harbor.ab.ca (8.6.10/8.6.9) with SMTP id UAA07169; Thu, 17 Apr 1997 20:08:05 GMT Date: Thu, 17 Apr 1997 14:07:25 -0600 (MDT) From: Stephen Mathezer X-Sender: mathezer@olympus To: questions@freebsd.org, mobile@freebsd.org Subject: Routing DHCP requests Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is FreeBSD capable of routing DHCP requests (RFC 1542) ? If not, is there any way of using a crowbar to accomplish this. I know I could use the FreeBSD machine as a DHCP server but that is something we wish to avoid if possible. We are running 2.2.1 if it matters. -Steve From owner-freebsd-mobile Thu Apr 17 14:26:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07142 for mobile-outgoing; Thu, 17 Apr 1997 14:26:20 -0700 (PDT) Received: from scds.ziplink.net (scds.ziplink.net [206.15.128.34]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07123; Thu, 17 Apr 1997 14:26:12 -0700 (PDT) Received: (from jseger@localhost) by scds.ziplink.net (8.8.5/8.8.4) id QAA06560; Thu, 17 Apr 1997 16:31:55 GMT Date: Thu, 17 Apr 1997 16:31:55 GMT From: "Justin M. Seger" Message-Id: <199704171631.QAA06560@scds.ziplink.net> To: mathezer@harbor.ab.ca, mobile@FreeBSD.org, questions@FreeBSD.org Subject: Re: Routing DHCP requests Sender: owner-mobile@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sure, look at the isc-dhcp-b5.14 package/port. -Justin Seger- From owner-freebsd-mobile Thu Apr 17 15:50:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA12124 for mobile-outgoing; Thu, 17 Apr 1997 15:50:15 -0700 (PDT) Received: from sol.harbor.ab.ca (sol100.harbor.ab.ca [198.161.82.169]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA12116; Thu, 17 Apr 1997 15:50:11 -0700 (PDT) Received: from olympus (olympus.harbor.ab.ca [198.161.82.144]) by sol.harbor.ab.ca (8.6.10/8.6.9) with SMTP id WAA10109; Thu, 17 Apr 1997 22:47:24 GMT Date: Thu, 17 Apr 1997 16:46:46 -0600 (MDT) From: Stephen Mathezer X-Sender: mathezer@olympus Reply-To: Stephen Mathezer To: "Justin M. Seger" cc: questions@freebsd.org, mobile@freebsd.org Subject: Re: Routing DHCP requests In-Reply-To: <199704171631.QAA06560@scds.ziplink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Perhaps you should cut the CC list down to whichever mailing list you saw this on... I wasn't sure which one was more appropriate. OK, I grabbed the port and have read through all the doc but I can't tell if what I want to do can be done. We have 3 token rings and 4 ethernets (I'll try not to go into too many details about why we've done certain things... it's a long story). Anyways, the 3 TRs and 2 of the ethernets are hung off of 2 Ciscos. On one of those ethernets, is a FreeBSD router which routes to the other 2 ethernets. The main DHCP server is an NT server on one of the token rings. We need DHCP to work for the 2 ethernets hung off of the FreeBSD machine. We don't want to have to manage DHCP servers both on NT AND on FreeBSD. This means that the FreeBSD machine just needs to act as a 'dhcp relay'. DHCP broadcasts on one ethernet need to be passed on to the others. Is this possible? -Steve On Thu, 17 Apr 1997, Justin M. Seger wrote: > Sure, look at the isc-dhcp-b5.14 package/port. > > -Justin Seger- > From owner-freebsd-mobile Thu Apr 17 19:01:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA24084 for mobile-outgoing; Thu, 17 Apr 1997 19:01:18 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA24066; Thu, 17 Apr 1997 19:01:07 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost.lan.awfulhak.org [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id CAA04740; Fri, 18 Apr 1997 02:34:42 +0100 (BST) Message-Id: <199704180134.CAA04740@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Justin M. Seger" cc: mathezer@harbor.ab.ca, mobile@freebsd.org, questions@freebsd.org Subject: Re: Routing DHCP requests In-reply-to: Your message of "Thu, 17 Apr 1997 16:31:55 GMT." <199704171631.QAA06560@scds.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Apr 1997 02:34:42 +0100 From: Brian Somers Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Sure, look at the isc-dhcp-b5.14 package/port. > > -Justin Seger- wide-dhcp (the other port) can do the job too. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-mobile Sat Apr 19 20:26:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA00669 for mobile-outgoing; Sat, 19 Apr 1997 20:26:43 -0700 (PDT) Received: from life.eecs.umich.edu (pmchen@life.eecs.umich.edu [141.213.8.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA00664 for ; Sat, 19 Apr 1997 20:26:38 -0700 (PDT) Received: (from pmchen@localhost) by life.eecs.umich.edu (8.8.5/8.8.0) id XAA11769 for freebsd-mobile@freebsd.org; Sat, 19 Apr 1997 23:25:40 -0400 (EDT) Date: Sat, 19 Apr 1997 23:25:40 -0400 (EDT) From: "Peter M. Chen" Message-Id: <199704200325.XAA11769@life.eecs.umich.edu> To: freebsd-mobile@freebsd.org Subject: disk spindown Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does FreeBSD (or PAO) support spinning down the disk (it appears from the apm man page that it does not)? Is anyone working on this (and if so, how close is it to working)? Any idea how much work it would be to support this? Pete From owner-freebsd-mobile Sat Apr 19 22:59:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA06477 for mobile-outgoing; Sat, 19 Apr 1997 22:59:19 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06472 for ; Sat, 19 Apr 1997 22:59:16 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA02249; Sat, 19 Apr 1997 23:59:11 -0600 (MDT) Date: Sat, 19 Apr 1997 23:59:11 -0600 (MDT) Message-Id: <199704200559.XAA02249@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Peter M. Chen" Cc: freebsd-mobile@freebsd.org Subject: Re: disk spindown In-Reply-To: <199704200325.XAA11769@life.eecs.umich.edu> References: <199704200325.XAA11769@life.eecs.umich.edu> X-Mailer: VM 6.27 under 19.15 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does FreeBSD (or PAO) support spinning down the disk (it appears from the > apm man page that it does not)? I think PHK just committed code to the wd driver to do this recently. Nate From owner-freebsd-mobile Sat Apr 19 23:07:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA06925 for mobile-outgoing; Sat, 19 Apr 1997 23:07:53 -0700 (PDT) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.129.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA06918; Sat, 19 Apr 1997 23:07:47 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id IAA03968; Sun, 20 Apr 1997 08:06:55 +0200 (CEST) To: "Peter M. Chen" cc: freebsd-mobile@freebsd.org From: Poul-Henning Kamp Subject: Re: disk spindown In-reply-to: Your message of "Sat, 19 Apr 1997 23:25:40 EDT." <199704200325.XAA11769@life.eecs.umich.edu> Date: Sun, 20 Apr 1997 08:06:55 +0200 Message-ID: <3966.861516415@critter> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199704200325.XAA11769@life.eecs.umich.edu>, "Peter M. Chen" writes: >Does FreeBSD (or PAO) support spinning down the disk (it appears from the >apm man page that it does not)? > >Is anyone working on this (and if so, how close is it to working)? Any idea >how much work it would be to support this? Not much work, in the works but not high priority. Can't your bios do it ? Poul-Henning -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.