From owner-freebsd-mobile Sun Mar 28 1: 5:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 939C514F35 for ; Sun, 28 Mar 1999 01:05:54 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA12319; Sun, 28 Mar 1999 01:05:39 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA28573; Sun, 28 Mar 1999 01:05:02 -0800 (PST) Date: Sun, 28 Mar 1999 01:05:02 -0800 (PST) Message-Id: <199903280905.BAA28573@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: kenney@netacc.net Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: (message from Jeffrey Kenney on Sat, 27 Mar 1999 22:57:32 +0000 (GMT)) Subject: Re: Pao in 3.1 Stable. From: asami@FreeBSD.ORG (Satoshi "the Wraith" Asami) References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Jeffrey Kenney * Is there a version of PAO for 3.1, my computer works beutifully with 2.2.8 * (it is a toshiba 3015ct) but that is with PAO. I've heard that the PAO team is currently working on it. I think it's in beta test stage now. So hang on a few more weeks (days?). :) -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 1:26:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id D9ADE14D46 for ; Sun, 28 Mar 1999 01:26:48 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp396.kt.rim.or.jp [202.247.140.96]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id SAA15152 for ; Sun, 28 Mar 1999 18:26:28 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id SAA13546 for ; Sun, 28 Mar 1999 18:26:26 +0900 (JST) Message-ID: <36FDF5A7.417600CC@sky.rim.or.jp> Date: Sun, 28 Mar 1999 18:25:59 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) References: <199903251636.RAA04214@greatoak.home> <199903270255.CAA28337@chandra.eatell.msr.prug.or.jp> <199903272106.OAA05479@mt.sri.com> <199903280328.MAA01166@rei.snipe.rim.or.jp> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thread like this is repeated many times... We should clearify what is problem about this. I don't like flames like this. Nate Williams wrote: > No no no. You got it all wrong. PAO support is buggy, FreeBSD APM is > good, and PCCARD support is limited. :) :) :) Nate, I think what you want to say about "PAO support is buggy" is an approach for bus-architectural things and handling of kernel options. I think you didn't say "everything in PAO is not useful", right? Motoyuki Konno wrote: > Why do you think "PAO support is buggy"? Do you read the recent > PAO patch? If you found bugs in PAO, please list up them. IMHO, PAO has much of "work around" approach to solve problem. And PAO has much of "#ifdef"s for experimental and product specific codes. I don't know who maintains these codes and whether currently used or not. PAO has Japanese version of man page for pccardc. Should we translate it into English? We should re-hack PAO code to separate by functionallity. And let's post -mobile and -current for reviewing. -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 2: 3:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.173.221]) by hub.freebsd.org (Postfix) with ESMTP id 491D114C0C for ; Sun, 28 Mar 1999 02:03:40 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id SAA26481; Sun, 28 Mar 1999 18:04:02 +0800 (CST) (envelope-from robinson) Date: Sun, 28 Mar 1999 18:04:02 +0800 (CST) From: Michael Robinson Message-Id: <199903281004.SAA26481@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG, kuriyama@sky.rim.or.jp Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: <36FDF5A7.417600CC@sky.rim.or.jp> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jun Kuriyama writes: >We should re-hack PAO code to separate by functionallity. And let's >post -mobile and -current for reviewing. I think that would be an excellent idea. Break up PAO into self-contained diffs against the 3.1 tree, based on single units of functionality. This would have three positive effects: 1. It would be easier for FreeBSD core team members to evaluate the quality of the changes, and apply the acceptable ones to the tree. This method would result in the greatest amount of PAO being integrated in the shortest amount of time. 2. It would be easier for volunteers to find small, easy-to-handle projects to work on to bring the PAO code up to higher quality. This would result in more people working on more features. 3. People who only needed specific features from PAO could install only the parts they needed, which would make it easier to handle parallel tracking of PAO and -STABLE. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8: 7:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS28.kng.mesh.ad.jp [133.205.214.28]) by hub.freebsd.org (Postfix) with ESMTP id 486391536D for ; Sun, 28 Mar 1999 08:07:04 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA00919; Sun, 28 Mar 1999 14:22:30 +0900 (JST) Message-Id: <199903280522.OAA00919@chandra.eatell.msr.prug.or.jp> To: Juriy Goloveshkin Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Re[2]: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Sat, 27 Mar 1999 23:05:57 +0300." <10962.990327@avias.com> Date: Sun, 28 Mar 1999 14:22:30 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > and if PAO is better, why it isn`t in "plain FreeBSD"? Because Nate disagree PAO integrate. He didn't understand PAO correctly. He belive "PAO is buggy", but it is not true. Many PAO code is very useful and correctly working. Main part of PAO, it should be integrated to "plain FreeBSD" (some experiments codes are not). -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8: 8: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS28.kng.mesh.ad.jp [133.205.214.28]) by hub.freebsd.org (Postfix) with ESMTP id C1FD715328 for ; Sun, 28 Mar 1999 08:07:59 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA00928; Sun, 28 Mar 1999 14:24:54 +0900 (JST) Message-Id: <199903280524.OAA00928@chandra.eatell.msr.prug.or.jp> To: Nate Williams Cc: Philippe CASIDY , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Sat, 27 Mar 1999 14:06:21 MST." <199903272106.OAA05479@mt.sri.com> Date: Sun, 28 Mar 1999 14:24:53 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > No no no. You got it all wrong. PAO support is buggy, FreeBSD APM is > good, and PCCARD support is limited. :) :) :) You are not recognized current status. For example, 3.1R APM with flags 0x31, it can't work power-off. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8: 8:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS28.kng.mesh.ad.jp [133.205.214.28]) by hub.freebsd.org (Postfix) with ESMTP id DF4661565C for ; Sun, 28 Mar 1999 08:08:16 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA00907; Sun, 28 Mar 1999 14:15:38 +0900 (JST) Message-Id: <199903280515.OAA00907@chandra.eatell.msr.prug.or.jp> To: Jeff Kletsky Cc: Philippe CASIDY , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Sat, 27 Mar 1999 09:38:35 PST." Date: Sun, 28 Mar 1999 14:15:36 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmmm... 3.1R was requested -- no PAO. And part of me seems to > believe that if PAO were all that much more stable *and* functional than > pccard, it would have been accepted onto the main branch. PAO for 3.1R is already working, not yet released. But, it will be released in near days. If you want to get PAO snap shot, you can get by CVSup. See PAO page. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8: 8:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS28.kng.mesh.ad.jp [133.205.214.28]) by hub.freebsd.org (Postfix) with ESMTP id 67D6415692; Sun, 28 Mar 1999 08:08:16 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id BAA00642; Mon, 29 Mar 1999 01:03:38 +0900 (JST) Message-Id: <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> To: Nate Williams Cc: Motoyuki Konno , Philippe CASIDY , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Sat, 27 Mar 1999 21:30:09 MST." <199903280430.VAA06189@mt.sri.com> Date: Mon, 29 Mar 1999 01:03:36 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Working together to solve a problem means 'working together', and I have > seen no attempts at any of the PAO folks (except for kuriyama) who have > any desire to work 'with' the FreeBSD people to solve the problem. Even 1. Many PAO people are Japanese, so we have language and communication problem. # Nate's this mail is very long, I need long time for reading the #mail. We are not native of English. It is hard. Japanese is very #different to western-europe languages. 2. Nate, you are nagative to PAO, so we become passive for PAO integrate. 3. Many PAO people go to newconfig project. (me too) > 3) The ability to 'kill -HUP' pccardd and have it re-read the device > table. It is include some bug. (not free memory when got -HUP.) # I wrote that code. It is corner-cutting. :-) > 1) Most of the ATA support hu-m. ATA support is temporary. Because, original wdc depend isa_biotab_wdc[] of ioconf.c and re-write is hard. So, we will rewrite on newconfig project. > 1) pcic is now an ISA device, even though it should not be. I disagree. PCIC is true ISA device. Now, CardBus controller is used by Legacy-mode, so it should be probe as ISA device (and additionaly PCI setup). (It likes wdc driver.) In the future, it is used by native CardBus mode, it should be handle true PCI device. (It likes new ata driver.) And, it should be separate PCIC common core code and bus code, so no wrong affects to native CardBus support. Additionaly, UserConfig is good solution at now, it is strong point, other BSDs not have. So, PCIC should be use it. > Most of this is configuration. In old ISA PCIC, it is true, but other is not. > There already exists Win95 as well, so should we all start using it? It is sophism. > Integrating PAO into FreeBSD is not an option if 'integrating PAO' means > applying all of the PAO patches to FreeBSD, regardless of how it > negatively affects desktop systems and future work for supporting > hardware. I think, first merge new feature, second brush up and stabilize, it is FreeBSD-style. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8:21:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 9C25C156A7 for ; Sun, 28 Mar 1999 08:21:51 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp097.dialup.st.keio.ac.jp [131.113.27.97]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id BAA03771; Mon, 29 Mar 1999 01:21:29 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.2/3.7W) id BAA12826; Mon, 29 Mar 1999 01:21:27 +0900 (JST) Date: Mon, 29 Mar 1999 01:21:27 +0900 (JST) Message-Id: <199903281621.BAA12826@lavender.yy.cs.keio.ac.jp> To: y-nakaga@nwsl.mesh.ad.jp Cc: root@wagsky.com, pcasidy@worldnet.fr, freebsd-mobile@FreeBSD.ORG, sanpei@sanpei.org Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: Your message of "Sun, 28 Mar 1999 14:15:36 JST". <199903280515.OAA00907@chandra.eatell.msr.prug.or.jp> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > Hmmm... 3.1R was requested -- no PAO. And part of me seems to >> > believe that if PAO were all that much more stable *and* functional than >> > pccard, it would have been accepted onto the main branch. >> >> PAO for 3.1R is already working, not yet released. But, it will be >> released in near days. If you want to get PAO snap shot, you can >> get by CVSup. >> >> See PAO page. I'm one of PAO page maintainer. Sorry, we don't update PAO page, there is no information about PAO3 (currently for 3.1-RELEASE.) You can get latest PAO3 code by below file. *default host=cvsup.jp.FreeBSD.org *default base=/somewhere/you/want/to/put *default prefix=/somewhere/you/want/to/put *default release=cvs tag=. jp-pao3 MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8:22:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id BC78E156BD for ; Sun, 28 Mar 1999 08:22:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA07722; Mon, 29 Mar 1999 01:22:06 +0900 (JST) Message-ID: <36FE5562.5F563E6C@newsguy.com> Date: Mon, 29 Mar 1999 01:14:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: Nate Williams , Philippe CASIDY , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) References: <199903280524.OAA00928@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > > > No no no. You got it all wrong. PAO support is buggy, FreeBSD APM is > > good, and PCCARD support is limited. :) :) :) > > You are not recognized current status. For example, 3.1R APM with > flags 0x31, it can't work power-off. This is the safe setting. Change the flags to 0, if you don't have buggy hardware, and you everything is fine. Is that a problem? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What kind of psychologist laughs at her patients?" "I don't laugh at all of them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8:42:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 9213F14C87; Sun, 28 Mar 1999 08:42:54 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA19533; Sun, 28 Mar 1999 09:42:34 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA07849; Sun, 28 Mar 1999 09:42:34 -0700 Date: Sun, 28 Mar 1999 09:42:34 -0700 Message-Id: <199903281642.JAA07849@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: NAKAGAWA Yoshihisa Cc: Nate Williams , Motoyuki Konno , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> References: <199903280430.VAA06189@mt.sri.com> <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Working together to solve a problem means 'working together', and I have > > seen no attempts at any of the PAO folks (except for kuriyama) who have > > any desire to work 'with' the FreeBSD people to solve the problem. Even > > 1. Many PAO people are Japanese, so we have language and > communication problem. I'll grant you that. However, in my experience from living in Japan and from articles I've had from many Japanese people, most Japanese technical people (engineers) have *ver* good written English skills (your English skills is much better than my Japanese skills. *grin*) However, if we grant that you can't communicate well, then how do you expect the FreeBSD developers to 'hand over' the maintenance of a large portion of FreeBSD code-base to people who are unable to communicate with most of their userbase. (I'm not saying that the the largest portion of FreeBSD's support base are American, but that English is the most common language to communicate with the userbase.) > # Nate's this mail is very long, I need long time for reading the > #mail. We are not native of English. It is hard. Japanese is very > #different to western-europe languages. You don't have to convince me of that. :) > 2. Nate, you are nagative to PAO, so we become passive for PAO > integrate. I was not always negative towards PAO, and neither was the person who was before me (PHK). But, after attempting to work with the PAO folks, it became very frustrating to see that they had no intention of working 'with' the FreeBSD folks to provide a 'joint' project. > 3. Many PAO people go to newconfig project. (me too) I know very little about newconfig, but as I understand it the FreeBSD core team is not interested in using newconfig, so any work you do using it is wasted effort. Note, I was not part of that decision (I'm no core member), but I do respect their technical ability. [ Features I liked in PAO mostly delted ] > > 3) The ability to 'kill -HUP' pccardd and have it re-read the device > > table. > > It is include some bug. (not free memory when got -HUP.) > > # I wrote that code. It is corner-cutting. :-) I didn't say I liked the implementation, but I do like the feature. (Most of the features I like need to re-vamped for FreeBSD, but in many cases *most* of the code and ideas are valid in PAO.) In this case, I've not reviewed how it's implemented, but you've convinced me that it's not done correctly. :) > > 1) Most of the ATA support > > hu-m. ATA support is temporary. Because, original wdc depend > isa_biotab_wdc[] of ioconf.c and re-write is hard. So, we will > rewrite on newconfig project. Warner Losh is already re-writing it, and I suspect (I'll let him correct me if I'm wrong) he's using the ideas and possibly some of the code from the PAO patches. > > 1) pcic is now an ISA device, even though it should not be. > > I disagree. PCIC is true ISA device. Now, CardBus controller is > used by Legacy-mode, so it should be probe as ISA device (and > additionaly PCI setup). (It likes wdc driver.) I disagree. PCIC is not an ISA device, but a completely new (and separate) device. It should be able to deal with other devices w/out knowing the details of the controller. > In the future, it is used by native CardBus mode, it should be > handle true PCI device. (It likes new ata driver.) > > And, it should be separate PCIC common core code and bus code, so > no wrong affects to native CardBus support. Agreed, but making it into an ISA device is not the right direction. > > Integrating PAO into FreeBSD is not an option if 'integrating PAO' means > > applying all of the PAO patches to FreeBSD, regardless of how it > > negatively affects desktop systems and future work for supporting > > hardware. > > I think, first merge new feature, second brush up and stabilize, > it is FreeBSD-style. No, that's the Linux style. The FreeBSD style is to try and only integrate stable features that have been tested well, *then* debug them when they are found to be unstable in a larger audience. Adding in 'buggy/poorly implemented code' is never the right way to do software engineering. That is the 'Microsoft Way', and we can see what it has us. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 8:48:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7FD551554F for ; Sun, 28 Mar 1999 08:48:49 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA26260; Sun, 28 Mar 1999 18:48:29 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA17233; Sun, 28 Mar 1999 18:48:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: NAKAGAWA Yoshihisa Cc: Juriy Goloveshkin , freebsd-mobile@FreeBSD.ORG Subject: Re: Re[2]: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Sun, 28 Mar 1999 14:22:30 +0900." <199903280522.OAA00919@chandra.eatell.msr.prug.or.jp> Date: Sun, 28 Mar 1999 18:48:24 +0200 Message-ID: <17231.922639704@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199903280522.OAA00919@chandra.eatell.msr.prug.or.jp>, NAKAGAWA Yosh ihisa writes: >> and if PAO is better, why it isn`t in "plain FreeBSD"? > >Because Nate disagree PAO integrate. He didn't understand PAO >correctly. He belive "PAO is buggy", but it is not true. Many PAO >code is very useful and correctly working. Main part of PAO, it >should be integrated to "plain FreeBSD" (some experiments codes >are not). I'm sorry, but clearly Nate and I have a quite different oppinion than you do here. Please notice that code can be "very useful and correctly working" and still be a royal mess. Several major projects I've worked on would be classified in that category. For all practical purposes the Danish Tax law fits that description too. The main objection from my side is that the PAO code is prototype quality. The secondary objection from my side is that we need a general (as in: pccard & cardbus & docking station & mini-pci & hot-plug-pci &c &c) framework for dealing with devices with dynamic precense. The PAO code doesn't provide anything even close to that, but does provide some experience with some of the low-level pccard cases. As I said in my previous email on the topic: everybody should grab hold of, and read "The Mythical Man-Month" by Frederick P. Brooks. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 9:27:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rainey.blueneptune.com (rainey.blueneptune.com [209.133.45.253]) by hub.freebsd.org (Postfix) with ESMTP id 1C73F14CAA for ; Sun, 28 Mar 1999 09:27:48 -0800 (PST) (envelope-from aland@SoftOrchestra.com) Received: from SoftOrchestra.com (ppp118.blueneptune.com [209.133.45.118]) by rainey.blueneptune.com (8.8.8/8.8.7) with ESMTP id JAA15895; Sun, 28 Mar 1999 09:27:23 -0800 (PST) (envelope-from aland@SoftOrchestra.com) Message-ID: <36FE6686.D3B89ECB@SoftOrchestra.com> Date: Sun, 28 Mar 1999 09:27:34 -0800 From: Alan DuBoff Organization: Software Orchestration, Inc. X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: FreeBSD Mobile List Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) References: <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > 1. Many PAO people are Japanese, so we have language and > communication problem. > > # Nate's this mail is very long, I need long time for reading the > #mail. We are not native of English. It is hard. Japanese is very > #different to western-europe languages. Nakagawa, I've been watching everyone blast bad comments back and forth and I've personally become sick with it. I commend you guys for being able to do this in English, I know it's not easy for you. In fact, I was telling my wife how you guys do use your english to communicate, and I think it is a very noble thing for you to do. OTOH, few would understand if you were to use Japanese. > 2. Nate, you are nagative to PAO, so we become passive for PAO > integrate. I have noticed this also, and I've not been able to determine what the exact problem is. Maybe it is that many of the people have a difficult time communicating with the Japan, where PAO is done, that I don't know, but I notice the lack of willingness to work with the PAO authors, and I've been staying out of it as I don't know all the politics. It has turned me off from trying to help out with this effort recentely though, I don't need to be in the middle of a war, and quite honestly I don't have time to fight with people on issues like pccard or pao or both, or this or that... One thing I must admit is that you PAO guys seem to know what you are talking about, and you have given examples of where the PCCaard code is broken and/or could never work. Wether Nate or anyone else likes it, it appears that you guys have done your homework. And I respect you for that, as well as being able to debate the issues with english which is not your native tongue, omedetou gozaimasu! For me, my Japanese is poor in the sense that I don't have good grammar, and for the Japanese it's similar, their english doesn't have good grammar a lot of times, but you guys should be commmended for your efforts in trying to communicate with some of the other people, I know it's difficult. -- Alan DuBoff - Conductor Software Orchestration, Inc. aland@SoftOrchestra.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 10:20:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id D4C8A14D80 for ; Sun, 28 Mar 1999 10:20:55 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id TAA23563; Sun, 28 Mar 1999 19:20:35 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 28 Mar 1999 19:06:29 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <36FDF5A7.417600CC@sky.rim.or.jp> References: <199903251636.RAA04214@greatoak.home> <199903270255.CAA28337@chandra.eatell.msr.prug.or.jp> <199903272106.OAA05479@mt.sri.com> <199903280328.MAA01166@rei.snipe.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Mar 1999 19:06:27 +0000 To: Jun Kuriyama From: Bob Bishop Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) Cc: freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, >PAO has Japanese version of man page for pccardc. Should we translate >it into English? Please do. If you want to send me a draft I'll happily tidy it up. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 11: 0:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 8AECD1566F for ; Sun, 28 Mar 1999 11:00:19 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA20454; Sun, 28 Mar 1999 12:00:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA08284; Sun, 28 Mar 1999 11:59:58 -0700 Date: Sun, 28 Mar 1999 11:59:58 -0700 Message-Id: <199903281859.LAA08284@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jun Kuriyama Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: <36FDF5A7.417600CC@sky.rim.or.jp> References: <199903251636.RAA04214@greatoak.home> <199903270255.CAA28337@chandra.eatell.msr.prug.or.jp> <199903272106.OAA05479@mt.sri.com> <199903280328.MAA01166@rei.snipe.rim.or.jp> <36FDF5A7.417600CC@sky.rim.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thread like this is repeated many times... We should clearify what is > problem about this. I don't like flames like this. This wasn't supposed to be a flame. It was a poor attempt at humour, which is why I added the smiley's. :) > Nate Williams wrote: > > No no no. You got it all wrong. PAO support is buggy, FreeBSD APM is > > good, and PCCARD support is limited. :) :) :) > > Nate, I think what you want to say about "PAO support is buggy" is an > approach for bus-architectural things and handling of kernel options. > > I think you didn't say "everything in PAO is not useful", right? I never said anything about PAO not being useful. Heck, I've recommended it to people who have hardware not support in FreeBSD. > We should re-hack PAO code to separate by functionallity. And let's > post -mobile and -current for reviewing. Agreed. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 11: 2:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 92FBE1573C for ; Sun, 28 Mar 1999 11:02:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA20486; Sun, 28 Mar 1999 12:02:15 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA08303; Sun, 28 Mar 1999 12:02:14 -0700 Date: Sun, 28 Mar 1999 12:02:14 -0700 Message-Id: <199903281902.MAA08303@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Robinson Cc: freebsd-mobile@FreeBSD.ORG, kuriyama@sky.rim.or.jp Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: <199903281004.SAA26481@netrinsics.com> References: <36FDF5A7.417600CC@sky.rim.or.jp> <199903281004.SAA26481@netrinsics.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Jun Kuriyama writes: > >We should re-hack PAO code to separate by functionallity. And let's > >post -mobile and -current for reviewing. > > I think that would be an excellent idea. Break up PAO into self-contained > diffs against the 3.1 tree, based on single units of functionality. This is what I did for almost 18 months, but unfortunately what happened was that any changes I made to make it fit into the FreeBSD model better were rejected by PAO, even good changes. :( This is just one of the many reasons I don't do laptop support on FreeBSD anymore (but only one of them). And, based on recent feedback I've had with PAO members, it seems that the same sort of behavior would happen again due to the difficulties in communicating and design methodologies. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 14:32:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8D935153AE; Sun, 28 Mar 1999 14:32:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA37290; Sun, 28 Mar 1999 14:32:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: NAKAGAWA Yoshihisa Cc: Nate Williams , Motoyuki Konno , Philippe CASIDY , freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Mon, 29 Mar 1999 01:03:36 +0900." <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> Date: Sun, 28 Mar 1999 14:32:02 -0800 Message-ID: <37288.922660322@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If I might step in here for a moment... It sounds to me like we're looking at the tail end of a long-standing communications problem, and we probably need to work on resolving it as the first order of business before even necessarily discussing code and what needs to be done with it. It's not even a particularly easy problem to solve, and I'm open to suggestions on it. When I went to Japan last year to discuss these and other issues with the PAO team, for example, I returned with an agreement that Tatsumi Hosokawa should be given commit priviledges immediately in order to begin a "closer relationship" as far as the PAO stuff is concerned. I returned, I got Tatsumi commit priviledges and, as far as I've been able to see, absolutely nothing happened after that. Whoops. Do I blame Tatsumi for this? No. Who I blame is myself for not setting up a decent framework for future communications, and I can almost see from here exactly what happened: Tatsumi got his commit priviledges and a mountain of other work to do somewhat simultaneously, our best-laid plans then falling apart due to over-committment among the various people involved (including myself). Once that happened, the total lack of communication only further lent the impression that everyone had lost interest again since clearly nothing was happening. We didn't go into "problem solving" mode with it and try and figure out how best to make it happen without Tatsumi-san, we just let the communications barrier drop back into place and went on to other things. I think we need to convene a periodic "working group meeting" if we want to make real progress here, and I'm willing to fly to Japan a couple of times a year if that's what it takes to foster closer cooperation between the teams. Once we get enough interest generated on this side of the Pacific, I'm even willing to do the opposite and fly some of the Japanese folks over here to meet with their U.S. counterparts (and, if we've get some significant PAO stuff going in Europe/Australia, we'll bring them over too). That meeting in Japan seemed very promising, but we didn't follow it up with another one to make sure that everything we'd discussed was actually happening and on track. We need to do better at following up. We've also got the USENIX Annual Technical conference event coming up which should bring a lot of these people together, including the newconfig folks given that they're presenting a paper on it in the FREENIX track. I think the various core folk who are interested in this simply need to attend that talk and discuss what newconfig has become and what its overall goals are with the presenters afterwards, seeing for themselves if it's truly everything people here seem to think it is (and is not). I don't think it's accurate to say that there's "no interest" here in what the Japanese folks have done, simply a lot of ignorance as to what specifically it *is* that they have done. :-) Each and every one of you who's going to be at USENIX should therefore make a point of contacting me once you arrive in Monterey, CA. I'll be at the Doubletree hotel (where the conference is actually taking place, so that should be easy to remember) and you should definitely check in with me anyway if you're presenting a paper since I'll need to check you off my list of people not to send a search party after if you don't show up (ah, the joys of chairing the FREENIX track). Somewhat on a similar but not directly related topic, I think it's time to hold another FreeBSD PR event in Japan. Wasn't Satoshi going to speak at the next one, even? I seem to remember that he agreed to, anyway, and I'd be happy to go along and say a few words as well. I'd also welcome suggestions on where to hold it; please contact me off the list if you've some ideas and we'll discuss projected costs, staffing requirements, etc. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 16:14:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from relay02.netaddress.usa.net (relay02.netaddress.usa.net [204.68.24.182]) by hub.freebsd.org (Postfix) with SMTP id 5BF6E1547D for ; Sun, 28 Mar 1999 16:14:16 -0800 (PST) (envelope-from monroyj@usa.net) Received: (qmail 6820 invoked from network); 29 Mar 1999 00:13:37 -0000 Received: from www0a.netaddress.usa.net (204.68.24.30) by outbound.netaddress.usa.net with SMTP; 29 Mar 1999 00:13:37 -0000 Received: (qmail 19631 invoked by uid 60001); 29 Mar 1999 00:13:36 -0000 Message-ID: <19990329001336.19630.qmail@www0a.netaddress.usa.net> Received: from 204.68.24.30 by www0a via web-mailer(M3.0.0.30) on Mon Mar 29 00:13:36 GMT 1999 Date: 28 Mar 99 16:13:36 PST From: JESSE MONROY To: freebsd-mobile@FreeBSD.ORG, Nate Williams Subject: Re: [Re: Which LAN PCCARD for FreeBSD (no PAO!)] X-Mailer: USANET web-mailer (M3.0.0.30) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > Jun Kuriyama writes: > > ......[SNIP]........ > = > This is what I did for almost 18 months, but unfortunately what happene= d > was that any changes I made to make it fit into the FreeBSD model bette= r > were rejected by PAO, even good changes. :( > = > This is just one of the many reasons I don't do laptop support on > FreeBSD anymore (but only one of them). > = > And, based on recent feedback I've had with PAO members, it seems that > the same sort of behavior would happen again due to the difficulties in= > communicating and design methodologies. > = Please excuse me for breaking in. I have been monitoring this group for about a year or two. Lately, I've noted that subject threads seem to break into bursts. This seems to be an indicator. Without getting to convoluted, I seems that things need to change in this mailing-list. I not sure what, because I don't read the mail, just the subject headers. I'm not meaning to be insultive or rash; this is just an observation. ____________________________________________________________________ Get free e-mail and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 17:22:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 6808D152CE; Sun, 28 Mar 1999 17:22:12 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id KAA06196; Mon, 29 Mar 1999 10:21:42 +0900 (JST) Date: Mon, 29 Mar 1999 10:21:42 +0900 (JST) Message-Id: <199903290121.KAA06196@afs.ntc.mita.keio.ac.jp> To: nate@mt.sri.com Cc: y-nakaga@nwsl.mesh.ad.jp, motoyuki@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: Your message of "Mon, 29 Mar 1999 01:42:34 JST". <199903281642.JAA07849@mt.sri.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199903281642.JAA07849@mt.sri.com> nate@mt.sri.com writes: >> I was not always negative towards PAO, and neither was the person who >> was before me (PHK). But, after attempting to work with the PAO folks, >> it became very frustrating to see that they had no intention of working >> 'with' the FreeBSD folks to provide a 'joint' project. I admit that part of this problem was due to me because I was terribly busy one or two years ago (I changed my job, etc.), and unfortunately, PAO was developped in centralized style these days (this means that the bottleneck was me). Today I have more spare time and PAO has moved to distributed developping style. We can work together now. I haven't thought that we won't work together, and I haven't thought and don't think that PAO is the best code and should be merged without many bug fix, as I wrote in README of PAO. In fact, I prepared the powerful CardBus desktop machine dedicated to -current and I want to start working about -current's PC-card/CardBus support. >> > 3. Many PAO people go to newconfig project. (me too) >> >> I know very little about newconfig, but as I understand it the FreeBSD >> core team is not interested in using newconfig, so any work you do using >> it is wasted effort. Note, I was not part of that decision (I'm no core >> member), but I do respect their technical ability. At least, *I* haven't moved to newconfig and neutral about it. I agree that new bus architecture is disired. But I have little knowledge about the technical differences between newconfig and new-bus. Somebody can explain it briefly? >> [ Features I liked in PAO mostly delted ] >> >> > > 1) Most of the ATA support >> > >> > hu-m. ATA support is temporary. Because, original wdc depend >> > isa_biotab_wdc[] of ioconf.c and re-write is hard. So, we will >> > rewrite on newconfig project. >> >> Warner Losh is already re-writing it, and I suspect (I'll let him >> correct me if I'm wrong) he's using the ideas and possibly some of the >> code from the PAO patches. I welcome it. I'd like to see the code. The PAO implementation of multiple I/O window is ugly, and I have wanted to re-write it for long. >> > > 1) pcic is now an ISA device, even though it should not be. >> > >> > I disagree. PCIC is true ISA device. Now, CardBus controller is >> > used by Legacy-mode, so it should be probe as ISA device (and >> > additionaly PCI setup). (It likes wdc driver.) >> >> I disagree. PCIC is not an ISA device, but a completely new (and >> separate) device. It should be able to deal with other devices w/out >> knowing the details of the controller. Practically, *I* think that I'll be satisfied if PCIC I/O address can be configured without compiling kernel. I'll test it on my new -current CardBus machine. By the way, perhaps this helps to port the new drivers to -current. http://wing-yee.ntc.keio.ac.jp/PAO/PAO3-19990329-beta.tar.gz Again, I *don't* want to merge it in -current without fixes (this is the port of PAO to 3.1-RELEASE and many problems of PAO still remains). But it'll be the better basis in merging new drivers into -current. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 18:36:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id B473D15479 for ; Sun, 28 Mar 1999 18:36:45 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA23355; Sun, 28 Mar 1999 19:36:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA09290; Sun, 28 Mar 1999 19:36:20 -0700 Date: Sun, 28 Mar 1999 19:36:20 -0700 Message-Id: <199903290236.TAA09290@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alan DuBoff Cc: NAKAGAWA Yoshihisa , FreeBSD Mobile List Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: <36FE6686.D3B89ECB@SoftOrchestra.com> References: <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> <36FE6686.D3B89ECB@SoftOrchestra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > One thing I must admit is that you PAO guys seem to know what you are talking > about, and you have given examples of where the PCCaard code is broken and/or > could never work. Huh? I was the one who stated what was wrong with the current PCCARD code, as well as with PAO. I also spent about 18 months doing the laptop support for FreeBSD, as well as rewrote most of the APM code. I also was the first person to support working suspend/removal in FreeBSD, with or without PAO. I take offense that you seem to be seeing things one-sided, but maybe I'm taking it too personally. In any case, my opinions are not without technical merit. To anyone who thinks the PAO good is the greatest things since sliced bread, I challenge you to actually look at the patches and tell me again why you consider the current implementation in PAO a good thing? If you aren't a programmer or technical person, then you have very little to say. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 22:12: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 3C03515471 for ; Sun, 28 Mar 1999 22:11:54 -0800 (PST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id OAA18029; Mon, 29 Mar 1999 14:33:54 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-mobile@FreeBSD.ORG, dcs@newsguy.com Cc: y-nakaga@nwsl.mesh.ad.jp Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) From: Tomoaki NISHIYAMA In-Reply-To: <36FE5562.5F563E6C@newsguy.com> References: <199903280524.OAA00928@chandra.eatell.msr.prug.or.jp> <36FE5562.5F563E6C@newsguy.com> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990329143353Q.tomoaki@moss.nibb.ac.jp> Date: Mon, 29 Mar 1999 14:33:53 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 33 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Daniel C. Sobral" Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) Date: Mon, 29 Mar 1999 01:14:26 +0900 Message-ID: <36FE5562.5F563E6C@newsguy.com> dcs> NAKAGAWA Yoshihisa wrote: dcs> > dcs> > > No no no. You got it all wrong. PAO support is buggy, FreeBSD APM is dcs> > > good, and PCCARD support is limited. :) :) :) dcs> > dcs> > You are not recognized current status. For example, 3.1R APM with dcs> > flags 0x31, it can't work power-off. dcs> dcs> This is the safe setting. Change the flags to 0, if you don't have dcs> buggy hardware, and you everything is fine. dcs> dcs> Is that a problem? There *is* a problem with the code, which is discussed recently in FreeBSD-users-jp mailing list (in Japanese). The flags 0x31 should mean "Statclock is broken, and Limit APM protocol to 1.1 or 1.0". Thus even with flags 0x31 one should be able to power off using APM protocol 1.1. What really happens is that apm_driver_version is never called in apmattach (pointed out by Hideaki Okada in [FreeBSD-users-jp 40205] <199903260948.SAA21263@jaz.jp.freebsd.org>). Perhaps, this is a small bug, but can't be regarded as a safe setting. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 28 22:46:25 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rainey.blueneptune.com (rainey.blueneptune.com [209.133.45.253]) by hub.freebsd.org (Postfix) with ESMTP id B4AEF14ECF for ; Sun, 28 Mar 1999 22:46:24 -0800 (PST) (envelope-from aland@SoftOrchestra.com) Received: from jester (ppp168.blueneptune.com [209.133.45.168]) by rainey.blueneptune.com (8.8.8/8.8.7) with SMTP id WAA12665; Sun, 28 Mar 1999 22:45:55 -0800 (PST) (envelope-from aland@SoftOrchestra.com) Message-Id: <3.0.32.19990328224506.01f79cd0@blueneptune.com> X-Sender: aland@blueneptune.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 28 Mar 1999 22:45:09 -0800 To: Nate Williams From: Alan DuBoff Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) Cc: NAKAGAWA Yoshihisa , FreeBSD Mobile List Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 07:36 PM 3/28/99 -0700, Nate Williams wrote: >I take offense that you seem to be seeing things one-sided, but maybe >I'm taking it too personally. I'm seeing both sides of it Nate, but I have a feeling you are only seeing your side. >In any case, my opinions are not without >technical merit. And nobody said they were, I was merely stating that the PAO guys seems to have *SOME* information which counters some of your "technical merit". >To anyone who thinks the PAO good is the greatest >things since sliced bread, I challenge you to actually look at the >patches and tell me again why you consider the current implementation in >PAO a good thing? Nobody has said that PAO is the greatest thing since sliced bread. You seem to be putting words in other's mouths. >If you aren't a programmer or technical person, then you have very >little to say. Well, maybe I can set up an interview with you so I can get certified to label myself as a programmer or technical person, however my schedule seems fairly booked up at the moment. You won't have to worry about me rufflin' your feathers Nate, I'm taking myself off this list. At least the Japanese folks were giving an effort to try and communicate with you, and I still commend them for that. They tried to offer how they see things from their eyes, and they admit their code is not perfect. Yes, their english is not perfect, they even apologize to you for that. But I consider that a noble effort on their part, since you probably couldn't read a handful of kanjis to save your life. Anato wa bacatari desu yo? Alan DuBoff - Conductor Software Orchestration, Inc. aland@SoftOrchestra.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 1:28:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 6D22614E30; Mon, 29 Mar 1999 01:28:44 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA13887; Mon, 29 Mar 1999 01:28:10 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA31650; Mon, 29 Mar 1999 01:27:29 -0800 (PST) Date: Mon, 29 Mar 1999 01:27:29 -0800 (PST) Message-Id: <199903290927.BAA31650@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: jkh@zippy.cdrom.com Cc: y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, motoyuki@FreeBSD.ORG, pcasidy@worldnet.fr, freebsd-mobile@FreeBSD.ORG In-reply-to: <37288.922660322@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) From: asami@FreeBSD.ORG (Satoshi "the Wraith" Asami) References: <37288.922660322@zippy.cdrom.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Honestly, I was getting more than a little tired of all the "you suck" "no, it's you that sucks" messages (paraphrased, of course). I'm glad at least Hosokawa-san and Jordan is injecting some reality check here. * From: "Jordan K. Hubbard" * It sounds to me like we're looking at the tail end of a long-standing * communications problem, and we probably need to work on resolving it * as the first order of business before even necessarily discussing code * and what needs to be done with it. I agree. It seems to me that what happened was what started as some disagreements just snowballed with misunderstandings and language barriers caused things to deteriorate into a pretty sad state. Now both sides are saying the other "rejected" their offer, which in international politics usually means they don't want to talk to each other. :) * I think we need to convene a periodic "working group meeting" if we * want to make real progress here, and I'm willing to fly to Japan a * couple of times a year if that's what it takes to foster closer * cooperation between the teams. Once we get enough interest generated Do we really need to go that far? From Hosokawa-san's last post, it seems the PAO folks have gotten things a little less centralized now so maybe we can re-try our regular communications method, i.e., e-mails. Another thing we have to do is to select a contact point on this side of the Pacific. Nate (as he said himself) isn't working on PCCARD stuff anymore, so who's the point man now? (Was it Warner?) Also, we need firm committments from all parties involved to make this work. What we need are people who want to see some of the PAO improvements merged into the mainlike code, not people who just want to complain about broken stuff and attitude problems and stuff. By the way, if it's going to be any help, I'm willing to sit in that exchange and help resolve the language barrier issues. * Each and every one of you who's going to be at USENIX should therefore * make a point of contacting me once you arrive in Monterey, CA. I'll * be at the Doubletree hotel (where the conference is actually taking * place, so that should be easy to remember) and you should definitely The conference is in Doubletree? I thought it was in the Conference Center. :) (BTW, I'm staying in Marriott.) * Somewhat on a similar but not directly related topic, I think it's * time to hold another FreeBSD PR event in Japan. Wasn't Satoshi going * to speak at the next one, even? I seem to remember that he agreed to, * anyway, and I'd be happy to go along and say a few words as well. I'd * also welcome suggestions on where to hold it; please contact me off * the list if you've some ideas and we'll discuss projected costs, * staffing requirements, etc. Great, tack a little message to me at the end of a long and unrelated post which I happened to read just because I was interested in the topic. Now that's communication, Jordan! :> Kidding aside, yes, I agreed to speak in the next one. You guys were supposed to come up with some timetable/schedule/whatever so we can start planning. (You can even save the entire lodging budget for me if you hold the event in Tokyo. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 1:30:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 0BDA3157FC; Mon, 29 Mar 1999 01:30:31 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA13894; Mon, 29 Mar 1999 01:30:15 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA31655; Mon, 29 Mar 1999 01:29:36 -0800 (PST) Date: Mon, 29 Mar 1999 01:29:36 -0800 (PST) Message-Id: <199903290929.BAA31655@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: nate@mt.sri.com Cc: y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, motoyuki@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: <199903281642.JAA07849@mt.sri.com> (message from Nate Williams on Sun, 28 Mar 1999 09:42:34 -0700) Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) From: asami@FreeBSD.ORG (Satoshi "the Wraith" Asami) References: <199903280430.VAA06189@mt.sri.com> <199903281603.BAA00642@chandra.eatell.msr.prug.or.jp> <199903281642.JAA07849@mt.sri.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just one more point, I'm not sure if people noticed Jordan's mention to it in his other post.... * From: Nate Williams * I know very little about newconfig, but as I understand it the FreeBSD * core team is not interested in using newconfig, so any work you do using * it is wasted effort. Note, I was not part of that decision (I'm no core * member), but I do respect their technical ability. The core team has not made any decision on new-bus or newconfig. In fact, there hasn't even been any discussion about that issue on the core list. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 2:19:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id 5284615814; Mon, 29 Mar 1999 02:19:46 -0800 (PST) (envelope-from wosch@cs.tu-berlin.de) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id MAA20842; Mon, 29 Mar 1999 12:12:31 +0200 (MET DST) Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.9.1/8.9.0) id MAA27761; Mon, 29 Mar 1999 12:12:29 +0200 (MET DST) Message-ID: <19990329121227.B26082@cs.tu-berlin.de> Date: Mon, 29 Mar 1999 12:12:27 +0200 From: Wolfram Schneider To: Brian Somers Cc: freebsd-mobile@freebsd.org, wosch@freebsd.org Subject: Re: Sony VAIO PCG-745/LT References: <19990319150713.A27218@cs.tu-berlin.de> <199903191820.SAA01924@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903191820.SAA01924@keep.lan.Awfulhak.org>; from Brian Somers on Fri, Mar 19, 1999 at 06:20:25PM +0000 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-03-19 18:20:25 +0000, Brian Somers wrote: > > Does FreeBSD (with XFree86) runs on a Sony VAIO PCG-745/LT? > > > > VAIO PCG-745/LT, > > Pentium 266 MHz MMX, 3,2 GB HDD, > > 32 MB SDRAM (max. 128 MB), PCI- BUS, > > 12,1" DSTN SVGA (800x600), 2MB Video-RAM, > > FDD, 24xCD-ROM > > Li Ion-Akku, ohne Modem, > > Sound, 2x PCMCIA Type II (CardBus, ZV-Port), Touchpad, 2,5 kg > > I run -current on a Sony VAIO PCG-747. Mine's A4 size and has a 4Gb > disk (I think the one you mention is physically smaller), but apart > from that they seem the same (I didn't want the modem, so I don't > know if it's soft). Yes, the 745 has a smaller disk (3,2 instead 4GB) and a smaller resolution (800x600 instead 1024x768). But the price is also *alot* smaller, 1250 Euro instead 2000 Euro ;-) See http://www.vaio.sony-europe.com/facts/700_series/technical_specifications/747_745.htm > X runs 800x600x16bpp (the neo driver in XF86_SVGA with 3.3.3*). I just updated from 2.2.6 to 4.0-current and XFree runs now fine. -- Wolfram Schneider http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 5: 7:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.180.107]) by hub.freebsd.org (Postfix) with ESMTP id 862B3157D0 for ; Mon, 29 Mar 1999 05:07:49 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id VAA04415 for freebsd-mobile@FreeBSD.ORG; Mon, 29 Mar 1999 21:08:19 +0800 (CST) (envelope-from robinson) Date: Mon, 29 Mar 1999 21:08:19 +0800 (CST) From: Michael Robinson Message-Id: <199903291308.VAA04415@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG Subject: Re: newbus and newconfig Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org asami@FreeBSD.ORG (Satoshi "the Wraith" Asami) writes: >The core team has not made any decision on new-bus or newconfig. In >fact, there hasn't even been any discussion about that issue on the >core list. It sort of seems like this can happen one of two ways: 1. These issues are discussed and decided before all the code gets written. 2. These issues are discussed and decided after all the code gets written. -Michael Robinson (Of course, this observation is based on the assumption that all the code does, in fact, get written.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 5:26:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BDBF15808 for ; Mon, 29 Mar 1999 05:26:49 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from ext105.sra.co.jp (ext105 [133.137.20.200]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with SMTP id WAA26912 for ; Mon, 29 Mar 1999 22:26:28 +0900 (JST) Received: by ext105.sra.co.jp; id AA23126; Mon, 29 Mar 1999 22:26:27 +0900 To: hosokawa@ntc.keio.ac.jp Cc: freebsd-mobile@freebsd.org Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: Your message of "Mon, 29 Mar 1999 10:21:42 +0900 (JST)" <199903290121.KAA06196@afs.ntc.mita.keio.ac.jp> References: <199903290121.KAA06196@afs.ntc.mita.keio.ac.jp> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990329222627V.furuta@sra.co.jp> Date: Mon, 29 Mar 1999 22:26:27 +0900 From: Atsushi Furuta X-Dispatcher: imput version 980905(IM100) Lines: 44 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> In article <199903290121.KAA06196@afs.ntc.mita.keio.ac.jp>, hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) writes: > At least, *I* haven't moved to newconfig and neutral about it. I > agree that new bus architecture is disired. But I have little > knowledge about the technical differences between newconfig and > new-bus. Somebody can explain it briefly? I am one of developers of newconfig, so I can not fairly evaluate difference between newconfig and new-bus. Instead of it, please let me explain why we are developing newconfig. Newconfig was derived from an opinion that there were not enough framework of device configuration in FreeBSD (at least in those days). We decided that we don't do temporary workarounds, and should reform basis of the devices. There were some people (including me) who ports drivers from NetBSD to FreeBSD for PAO. They were aware of elegant device framework of NetBSD, so we tried to port it to FreeBSD. After we began the project, we were notified another framework "new-bus". Then we discussed which we should change to new-bus or not. We decided not to adopt new-bus. (If you can read Japanese, you can read the discussion archive http://www.jp.freebsd.org/mail-list/newconfig-jp/199806-month.html ) The reasons (which I understand) are: * We already have a framework "subr_autoconf.c". It is not needed to invent new wheel. * new-bus does not provide to "priority probe" feature. * new-bus remains old config(8) and old bus such as ISA. What we need is the reformation of them, so we can not adopt it. * There is no framework to separate bus-dependent part of a driver from bus-independent part in new-bus, but newconfig has. Many PC-card driver shares core code from another buses, so we reuqire such a framework. * new-bus scatters device tree structure informations into each driver codes. Aproach to center the informations is better than scatter it. (Please imagine "LINT" file informations are scattered to each driver.) -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 5:42:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 551CE15813 for ; Mon, 29 Mar 1999 05:42:25 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 29 Mar 1999 14:40:18 +0100 Message-ID: From: paul@originative.co.uk To: furuta@sra.co.jp, hosokawa@ntc.keio.ac.jp Cc: freebsd-mobile@freebsd.org Subject: RE: Which LAN PCCARD for FreeBSD (no PAO!) Date: Mon, 29 Mar 1999 14:40:14 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Atsushi Furuta [mailto:furuta@sra.co.jp] > Sent: 29 March 1999 14:26 > To: hosokawa@ntc.keio.ac.jp > Cc: freebsd-mobile@freebsd.org > Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) > > > >> In article <199903290121.KAA06196@afs.ntc.mita.keio.ac.jp>, > hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) writes: > > > At least, *I* haven't moved to newconfig and neutral about it. I > > agree that new bus architecture is disired. But I have little > > knowledge about the technical differences between newconfig and > > new-bus. Somebody can explain it briefly? > > I am one of developers of newconfig, so I can not fairly evaluate > difference between newconfig and new-bus. Instead of it, please let me > explain why we are developing newconfig. > > Newconfig was derived from an opinion that there were not enough > framework of device configuration in FreeBSD (at least in those days). > We decided that we don't do temporary workarounds, and should reform > basis of the devices. There were some people (including me) who ports > drivers from NetBSD to FreeBSD for PAO. They were aware of elegant > device framework of NetBSD, so we tried to port it to FreeBSD. > > After we began the project, we were notified another framework > "new-bus". Then we discussed which we should change to new-bus or not. > We decided not to adopt new-bus. (If you can read Japanese, you can > read the discussion archive > http://www.jp.freebsd.org/mail-list/newconfig-jp/199806-month.html ) > > The reasons (which I understand) are: These are actually very inaccurate points regarding new-bus. > > * We already have a framework "subr_autoconf.c". > It is not needed to invent new wheel. I think actually the whole point was that a "new wheel" was needed to support dynamic handling of devices. > * new-bus does not provide to "priority probe" feature. No, but we have talked about supporting this on the new-bus list. > * new-bus remains old config(8) and old bus such as ISA. > What we need is the reformation of them, so we can not > adopt it. I'm not quite sure what you mean here. It does currently use the existig config(8) but that is not central to the issue of new-bus. As the work gets completed the aim is to make the handling of devices totally dynamic. What role the current static oriented config(8) will play isn't completely determined. > * There is no framework to separate bus-dependent part > of a driver from bus-independent part in new-bus, > but newconfig has. Many PC-card driver shares core code from > another buses, so we reuqire such a framework. That's not true, this is an area where new-bus already has everything well established. > * new-bus scatters device tree structure informations into > each driver codes. Aproach to center the informations > is better > than scatter it. (Please imagine "LINT" file informations are > scattered to each driver.) I don't really understand what you mean by this either. What device tree structure information are you referring to? In any case, you're approach of using a central information source (e.g. LINT) fails to take into account the dynamic nature of new-bus and it's ability to support third-party supplied drivers. These drivers would need to be self-contained since they are not developed by the project but by some third party and would need to be able to install itself without changes to the installed system. I think there is clear misunderstanding as to what new-bus is and why the project is so keen to pursue that direction. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 5:43:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4B54315008 for ; Mon, 29 Mar 1999 05:43:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA02786; Mon, 29 Mar 1999 15:43:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA20065; Mon, 29 Mar 1999 15:43:30 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Atsushi Furuta Cc: hosokawa@ntc.keio.ac.jp, freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Mon, 29 Mar 1999 22:26:27 +0900." <19990329222627V.furuta@sra.co.jp> Date: Mon, 29 Mar 1999 15:43:29 +0200 Message-ID: <20063.922715009@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Let me try to clear some of the smoke around here... Static configurations is something which belongs in the past where you didn't need to tweak your kernel config unless you had written a cheque to your DEC sales rep. Today most new technologies are dynamic by nature, CardBUS and PCCARD are just the most prominent cases, but many more are on the way. FreeBSD is moving away from static configurations, it should be particular obvious in this group why, and new-config doesn't buy us much if anything to that goal (as far as I know), so new-config must provide something else of significant value to stand a chance of integration. Any argument about "better handling of ISA" will not do, the ISA bus is finally showing signs of terminal age, and improving on the current level of config support for ISA will not be a major priority. I think the general modus operandi in regards to this can be summed up as "Rather than mess with^H^H^H^H^H^H^H^Himprove config/newconfig, lets get rid of the bloddy thing alltogether" It is my understanding that new-bus has dynamic devices as a design principle, not something bolted on afterwards, that makes new-bus a very likely future key component of FreeBSD. The important thing here is that recognizing the speed at which we can code, we should look at the hardware as it will be in 2002 when we design/architect today, >that< is our target! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 9:19:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.175.159]) by hub.freebsd.org (Postfix) with ESMTP id 7C21615906 for ; Mon, 29 Mar 1999 09:19:33 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id BAA00898 for freebsd-mobile@FreeBSD.ORG; Tue, 30 Mar 1999 01:20:02 +0800 (CST) (envelope-from robinson) Date: Tue, 30 Mar 1999 01:20:02 +0800 (CST) From: Michael Robinson Message-Id: <199903291720.BAA00898@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG Subject: Re: new-bus Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org paul@originative.co.uk writes: >fails to take into account >the dynamic nature of new-bus and it's ability to support third-party >supplied drivers. These drivers would need to be self-contained since they >are not developed by the project but by some third party and would need to >be able to install itself without changes to the installed system. Unless new-bus implements a device-driver API used by operating systems other than FreeBSD, I don't see the rationale, here. Otherwise, any new-bus device driver will necessarily be written with specific reference to the "developed by the project" part of the system. Whether the programmer doing this is a volunteer or some unspecified "third party", they should be able to employ as much of the existing code as modularity and architectural hygiene will permit. This will get more device drivers written faster for FreeBSD, and will ensure fewer bugs in the shared code. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 15:28:30 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id EACBE14C4C for ; Mon, 29 Mar 1999 15:28:27 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA14797; Mon, 29 Mar 1999 15:28:14 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id PAA33893; Mon, 29 Mar 1999 15:27:35 -0800 (PST) Date: Mon, 29 Mar 1999 15:27:35 -0800 (PST) Message-Id: <199903292327.PAA33893@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: robinson@netrinsics.com Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: <199903291308.VAA04415@netrinsics.com> (message from Michael Robinson on Mon, 29 Mar 1999 21:08:19 +0800 (CST)) Subject: Re: newbus and newconfig From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <199903291308.VAA04415@netrinsics.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Michael Robinson * It sort of seems like this can happen one of two ways: * * 1. These issues are discussed and decided before all the code gets written. * 2. These issues are discussed and decided after all the code gets written. That is a good point. It appears to me that, so far, both parties have preferred to go for option 2 and talk only in closed mailing lists among their friends. I invite developers from both parties to convene in a public mailing list (either this one or -hackers) to discuss the architectural issues for awhile. * (Of course, this observation is based on the assumption that all the code * does, in fact, get written.) I hope that this observation is, in fact, correct. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 15:59:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 94B31159A5; Mon, 29 Mar 1999 15:59:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA42257; Mon, 29 Mar 1999 15:58:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: asami@FreeBSD.ORG (Satoshi "the Wraith" Asami) Cc: y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, motoyuki@FreeBSD.ORG, pcasidy@worldnet.fr, freebsd-mobile@FreeBSD.ORG Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) In-reply-to: Your message of "Mon, 29 Mar 1999 01:27:29 PST." <199903290927.BAA31650@silvia.hip.berkeley.edu> Date: Mon, 29 Mar 1999 15:58:41 -0800 Message-ID: <42255.922751921@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Do we really need to go that far? From Hosokawa-san's last post, it > seems the PAO folks have gotten things a little less centralized now > so maybe we can re-try our regular communications method, i.e., > e-mails. I think it couldn't possibly hurt, and besides, I want an official excuse to go to Japan twice a year (stop messing with my thinly-veiled justications here, Satoshi - *whack!* :-) More importantly, I think it would keep everybody moving if we sort of had milestones to hit twice a year or so - people tend to be a bit more motivated if they know they have a big meeting coming up where they'll be expected to discuss their latest progress and will look a little silly if there's no progress to discuss. > Also, we need firm committments from all parties involved to make this > work. What we need are people who want to see some of the PAO > improvements merged into the mainlike code, not people who just want > to complain about broken stuff and attitude problems and stuff. Amen. That should practically be in the FAQ. Or would that be the FC? (Frequent Complaints). > By the way, if it's going to be any help, I'm willing to sit in that > exchange and help resolve the language barrier issues. It will, and thanks. > The conference is in Doubletree? I thought it was in the Conference > Center. :) (BTW, I'm staying in Marriott.) The conference center is *in* the Doubletree hotel. ;) It's no big deal either way since the Marriott is just across the street and they even have a connecting walkway. Monterey is a great town, I think we're going to have some fun there. It certainly beats NEW ORLEANS IN THE SUMMER, that's for sure! :-) > Great, tack a little message to me at the end of a long and unrelated > post which I happened to read just because I was interested in the > topic. Now that's communication, Jordan! :> No, that's stealth. I wanted to commit you quietly to this without you necessarily noticing. ;) > Kidding aside, yes, I agreed to speak in the next one. You guys were > supposed to come up with some timetable/schedule/whatever so we can > start planning. (You can even save the entire lodging budget for me > if you hold the event in Tokyo. :) We'll work on all of that over the next 60 days, I promise. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 19:54: 0 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 8EBE414F17; Mon, 29 Mar 1999 19:53:57 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from bubble.didi.com ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA15102; Mon, 29 Mar 1999 19:53:36 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.9.2/8.8.8) id TAA05798; Mon, 29 Mar 1999 19:52:56 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Date: Mon, 29 Mar 1999 19:52:56 -0800 (PST) Message-Id: <199903300352.TAA05798@bubble.didi.com> X-Authentication-Warning: bubble.didi.com: asami set sender to asami@cs.berkeley.edu using -f To: jkh@zippy.cdrom.com Cc: y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, motoyuki@FreeBSD.ORG, pcasidy@worldnet.fr, freebsd-mobile@FreeBSD.ORG In-reply-to: <42255.922751921@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <42255.922751921@zippy.cdrom.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: "Jordan K. Hubbard" * I think it couldn't possibly hurt, and besides, I want an official * excuse to go to Japan twice a year (stop messing with my thinly-veiled * justications here, Satoshi - *whack!* :-) I won't complain if you promise to tag me along once in a while.... :> * More importantly, I think it would keep everybody moving if we sort of * had milestones to hit twice a year or so - people tend to be a bit * more motivated if they know they have a big meeting coming up where * they'll be expected to discuss their latest progress and will look a * little silly if there's no progress to discuss. Good point. * Amen. That should practically be in the FAQ. Or would that be the FC? * (Frequent Complaints). Speaking of which, I asked the PAO people to come up with a list of features missing from the mainline code and notebooks affected by it. It should help the merge discussion as well as serve as a guide for users looking for something to install on their machines. * The conference center is *in* the Doubletree hotel. ;) It's no big Oops, didn't know that. * deal either way since the Marriott is just across the street and they * even have a connecting walkway. Monterey is a great town, I think * we're going to have some fun there. It certainly beats NEW ORLEANS IN * THE SUMMER, that's for sure! :-) Well, you can try Tokyo in the summer and see if you still want to complain about New Orleans. :> * No, that's stealth. I wanted to commit you quietly to this without * you necessarily noticing. ;) Oh, great. * We'll work on all of that over the next 60 days, I promise. ^^^^^^^^^^^^^^^^^^^^^ You talk like one of those venture capitalists now.... -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 20:20:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by hub.freebsd.org (Postfix) with ESMTP id 0702A15792 for ; Mon, 29 Mar 1999 20:20:30 -0800 (PST) (envelope-from raj@cisco.com) Received: from kitab.cisco.com (kitab.cisco.com [171.69.187.233]) by hubbub.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id UAA27145 for ; Mon, 29 Mar 1999 20:20:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by kitab.cisco.com (8.9.2/8.9.2) with ESMTP id UAA00485 for ; Mon, 29 Mar 1999 20:20:09 -0800 (PST) (envelope-from raj@cisco.com) Message-Id: <199903300420.UAA00485@kitab.cisco.com> To: freebsd-mobile@freebsd.org Subject: Powering down PCMCIA modem card X-Mailer: MH, Xemacs, X11R6, and FreeBSD from my laptop. Unbeatable! X-Quote: "Truth is not absolute. We define it every minute of every day." Date: Mon, 29 Mar 1999 20:20:09 -0800 From: Richard Johnson Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to write some code to power down my PCMCIA modem card when it's not in use. I've been successful in suspending the disk drive, in this method so I know the code it working correctly and that I'm understanding the standards correctly. According to the APM V1.2 specs (this is the version of APM I have) device codes starting with 0x600 are for PCMCIA cards. I have tried powering down all devices between 0x600 and 0x6ff, and the only one which doesn't fail is 0x6ff (all PCMCIA devices), however this doesn't power off the modem or ethernet cards which are plugged in at the time. Has anyone had any success with powering down PCMCIA devices? /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 20:38:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 00A091580D for ; Mon, 29 Mar 1999 20:38:26 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id NAA20589; Tue, 30 Mar 1999 13:37:59 +0900 (JST) Date: Tue, 30 Mar 1999 13:37:59 +0900 (JST) Message-Id: <199903300437.NAA20589@afs.ntc.mita.keio.ac.jp> To: raj@cisco.com Cc: freebsd-mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: Powering down PCMCIA modem card In-Reply-To: Your message of "Tue, 30 Mar 1999 13:20:09 JST". <199903300420.UAA00485@kitab.cisco.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199903300420.UAA00485@kitab.cisco.com> raj@cisco.com writes: >> I'm trying to write some code to power down my PCMCIA modem card when >> it's not in use. I've been successful in suspending the disk drive, >> in this method so I know the code it working correctly and that I'm >> understanding the standards correctly. According to the APM V1.2 >> specs (this is the version of APM I have) device codes starting with >> 0x600 are for PCMCIA cards. I have tried powering down all devices >> between 0x600 and 0x6ff, and the only one which doesn't fail is 0x6ff >> (all PCMCIA devices), however this doesn't power off the modem or >> ethernet cards which are plugged in at the time. >> >> Has anyone had any success with powering down PCMCIA devices? "pccardc power ? 0" option of pccardc in PAO can power down the PCMCIA cards without removal, but it also disables the corresponding device drivers (it only emulates removal of PCMCIA cards), and it won't back to the active status without using "pccardc power ? 1" manually again. Better implementation is desired but I have no idea. And I'm using this feature because it's useful in outdoor use. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 29 21:39:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id EB0CB15137 for ; Mon, 29 Mar 1999 21:39:31 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from ext105.sra.co.jp (ext105 [133.137.20.200]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with SMTP id OAA05971 for ; Tue, 30 Mar 1999 14:39:07 +0900 (JST) Received: by ext105.sra.co.jp; id AA24812; Tue, 30 Mar 1999 14:39:06 +0900 To: paul@originative.co.uk Cc: freebsd-mobile@freebsd.org Subject: RE: Which LAN PCCARD for FreeBSD (no PAO!) In-Reply-To: Your message of "Mon, 29 Mar 1999 14:40:14 +0100" References: X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990330143905B.furuta@sra.co.jp> Date: Tue, 30 Mar 1999 14:39:05 +0900 From: Atsushi Furuta X-Dispatcher: imput version 980905(IM100) Lines: 108 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> In article , paul@originative.co.uk writes: >> * We already have a framework "subr_autoconf.c". >> It is not needed to invent new wheel. > I think actually the whole point was that a "new wheel" was needed to > support dynamic handling of devices. No, I don't think so. I admit that the code implemented in subr_autoconf.c does not handle dynamic aggregation and its handling of dynamic configuration is limited. But, since it is possible to add these features to the framework of subr_autoconf.c, subr_bus.c is a new wheel. Thus we are adding the feature of dynamic device handling to subr_autoconf.c >> * new-bus does not provide to "priority probe" feature. > No, but we have talked about supporting this on the new-bus list. Ok, you admit that priority probe feature is required and is lacking in current new-bus. We recognized the importance of priority probe from the start and coped with that problem. Since many drivers of FreeBSD assumes that attach() comes just after probe(), it will be a large work to remove this assumption from all the code. >> * new-bus remains old config(8) and old bus such as ISA. >> What we need is the reformation of them, so we can not >> adopt it. > I'm not quite sure what you mean here. It does currently use the existig > config(8) but that is not central to the issue of new-bus. As the work gets > completed the aim is to make the handling of devices totally dynamic. What > role the current static oriented config(8) will play isn't completely > determined. I understand that config(8) is not playing a central roll, but I do think that current new-bus can not handle well the ISA devices. The database generated by config(8) is required to use ISA devices after all. We want such dirty tool removed as early as possible, as we had many troubles with isa_devtab of config(8). Perhaps new-bus trusts the data from the bus for self-parametric device (or device on PnP bus), but a way to specify the parameters by the user should be left because there are always devices that do not conform to the standard. From this point we require a syntax to specify flexibly the parameters. This is the reason why we think config.new(8) is good. Yes, another tool to process such syntax would be required for dynamic configuration, but it should be easily achieved changing config.new(8). >> * There is no framework to separate bus-dependent part >> of a driver from bus-independent part in new-bus, >> but newconfig has. Many PC-card driver shares core code from >> another buses, so we reuqire such a framework. > That's not true, this is an area where new-bus already has everything well > established. Well, I apologize for my mistake. But new-bus does not give a "framework" to separate the device driver frontend (bus dependent part such as ed_isa.c) and device driver backend (bus independent part such as ed.c) as newconfig has. Am I wrong? >> * new-bus scatters device tree structure informations into >> each driver codes. Aproach to center the informations >> is better >> than scatter it. (Please imagine "LINT" file informations are >> scattered to each driver.) > I don't really understand what you mean by this either. What device tree > structure information are you referring to? In any case, you're approach of > using a central information source (e.g. LINT) fails to take into account > the dynamic nature of new-bus and it's ability to support third-party > supplied drivers. These drivers would need to be self-contained since they > are not developed by the project but by some third party and would need to > be able to install itself without changes to the installed system. My explanation was not good. What I wanted to say is, "device tree" information is required, which is well organized and can be referred from many tools. Device tree information keeps the information of which device is connected to which bus, as well as explanatory information of each device. We think the driver provided by the third party need not be "self-contained" but it is sufficient if such information is provided with the driver. The feature to pass dynamically such information to the kernel will be necessary. In newconfig, "files" file will play this role. Anyway, it is important that formal device tree information can be accessed by other tools. In new-bus, such informations are hard coded in the driver, isn't it? -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. P.S. Almost all message of this is originally written in Japanese by me, and Tomoaki NISHIYAMA-san translate to English. I thank him for the translation very much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 30 10:43:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by hub.freebsd.org (Postfix) with ESMTP id A448F14C8F for ; Tue, 30 Mar 1999 10:43:30 -0800 (PST) (envelope-from raj@cisco.com) Received: from kitab.cisco.com (kitab.cisco.com [171.69.187.233]) by hubbub.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id KAA15108; Tue, 30 Mar 1999 10:43:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by kitab.cisco.com (8.9.2/8.9.2) with ESMTP id KAA02121; Tue, 30 Mar 1999 10:43:08 -0800 (PST) (envelope-from raj@cisco.com) Message-Id: <199903301843.KAA02121@kitab.cisco.com> To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: freebsd-mobile@freebsd.org Subject: Re: Powering down PCMCIA modem card In-reply-to: Your message of "Tue, 30 Mar 1999 13:37:59 +0900." <199903300437.NAA20589@afs.ntc.mita.keio.ac.jp> X-Quote: If you consult enough experts, you can confirm any opinion. Date: Tue, 30 Mar 1999 10:43:08 -0800 From: Richard Johnson Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The version of pccardc distributed with 3.1 doesn't have the "power" command. I'll have to investigate this further. Perhaps I can just grab the PAO version and use that. /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 30 14:27:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id AF1BA15C1E for ; Tue, 30 Mar 1999 14:27:14 -0800 (PST) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id AAA01478 for ; Wed, 31 Mar 1999 00:26:51 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma001476; Wed, 31 Mar 99 00:26:49 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id AAA10756 for freebsd-mobile@freebsd.org; Wed, 31 Mar 1999 00:26:49 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199903302226.AAA10756@helena.otelo-call.de> Subject: pcmcia ethernet installation trouble To: freebsd-mobile@freebsd.org Date: Wed, 31 Mar 1999 00:26:49 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm trying to install 2.2.7 on a Toshiba T1910 via a Fiberline FL-4680 Ethernet card. (I have no more documentation on this one, but found some Linux Data claiming it to be a Tulip Card). I got the 2.2.7 boot-pao.flp. This one recogniszes the card and says it assigns it ed0. But ed0 doesn't appear in the list of available devices when choosing installation media. What am I missing ? Regards, and thanks in advance, Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 30 23:31:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (Postfix) with ESMTP id 66C4014DBF for ; Tue, 30 Mar 1999 23:31:34 -0800 (PST) (envelope-from rsmith@trltech.co.uk) Received: from trltech.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id IAA28454 for ; Wed, 31 Mar 1999 08:31:09 +0100 (BST) (envelope-from rsmith@trltech.co.uk) Message-ID: <3701CF8B.6A4D91F5@trltech.co.uk> Date: Wed, 31 Mar 1999 08:32:27 +0100 From: Richard Smith Reply-To: richard@jezebel.demon.co.uk Organization: http://www.trltech.co.uk/ X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.org Subject: PCMCIA confusion Content-Type: multipart/mixed; boundary="------------9D85A18EBC9EA02BE0E99EF1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------9D85A18EBC9EA02BE0E99EF1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tried -questions yesterday, sorry for the urgency, but I get this going by friday or give up for now :( I am trying to use the PCMCIA slots on a Viglen P120 notebook running 3.1R - I have attached the dmesg.boot for your information. After boot, further relevant messages are as follows: kernel pcic module loaded. pccardc: /dev/card0: Device not configured I have built a custom kernel with ze and zp removed and the three pccard lines uncommented: controller card0, and two pcic devices. I have enabled APM and PCCARD in rc.conf. I have copied pccard.conf.sample to pccard.conf, and even tried it with fewer IRQs. I get the same state irrespective of whether there are cards in the slot or not. Is pccardd supposed to run all the time, it simply exits with no error messages (with or without the -d option). Confused. Any help would be gratefully appreciated. Thanks, Richard. --------------9D85A18EBC9EA02BE0E99EF1 Content-Type: text/plain; charset=us-ascii; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Mon Mar 29 21:01:50 BST 1999 richard@notebook.wan:/usr/src/sys/compile/NOTEBOOK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (120.27-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 37548032 (36668K bytes) Preloaded elf kernel "kernel" at 0xf0340000. Probing for devices on PCI bus 0: chip0: rev 0xb0 on pci0.0.0 vga0: rev 0x00 on pci0.17.0 chip1: rev 0xb2 on pci0.18.0 ide_pci0: rev 0x10 on pci0.18.1 pcic0: rev 0xfe int a irq 255 on pci0.23.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 777MB (1591632 sectors), 1579 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordis acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ppc0 at 0x378 irq 7 on isa ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Initializing PC-card drivers: ed Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a --------------9D85A18EBC9EA02BE0E99EF1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 30 23:55:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39]) by hub.freebsd.org (Postfix) with SMTP id 37065154D6 for ; Tue, 30 Mar 1999 23:55:25 -0800 (PST) (envelope-from olivier.charles@cnet.francetelecom.fr) Received: from cnet.francetelecom.fr (p-brokenpipe.issy.cnet.fr [139.100.16.186]) by p-voyageur.issy.cnet.fr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id GGMHTNTG; Wed, 31 Mar 1999 09:55:05 +0200 Message-ID: <3701D485.69A3ACE0@cnet.francetelecom.fr> Date: Wed, 31 Mar 1999 09:53:41 +0200 From: Olivier Charles X-Mailer: Mozilla 4.06 [fr] (WinNT; I) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: How to use a GSM pccard? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have installed FreeBSD+PAO on a compaq armada3500 and I would like to use an OPTION FirstFone GSM pccard. The Card is correctly managed by PAO. However I have no idea on how to communicate with it (chat, kermit?). I've tried to do it as if it was a usual modem card but I failed. For example I wonder how and when should I enter the PIN code (Win95 asks it in a diologue box). The doc gives also AT commands that do not seem to by recongnized by the card. Does anybody have any experience in such product (FirstFone or any other Cellular Card)? Thank you Olivier Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 4: 5:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id E5AD914D96 for ; Wed, 31 Mar 1999 04:05:23 -0800 (PST) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.2/8.9.2) with ESMTP id NAA10642; Wed, 31 Mar 1999 13:00:36 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3701CF8B.6A4D91F5@trltech.co.uk> Date: Wed, 31 Mar 1999 13:00:36 +0100 (IST) From: "Steve O'Hara-Smith" To: richard@jezebel.demon.co.uk Subject: RE: PCMCIA confusion Cc: freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31-Mar-99 Richard Smith wrote: > Tried -questions yesterday, sorry for the urgency, but I get this > going > by friday or give up for now : Try disabling the kldload in /etc/rc.pccardd, and then ring the changes around pccard linked/kld'd/both and see how far you get. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 31-Mar-99 Time: 12:58:33 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 5: 1:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (Postfix) with ESMTP id 6D1F114BDA for ; Wed, 31 Mar 1999 05:01:21 -0800 (PST) (envelope-from rsmith@trltech.co.uk) Received: from trltech.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id OAA29441; Wed, 31 Mar 1999 14:00:50 +0100 (BST) (envelope-from rsmith@trltech.co.uk) Message-ID: <37021CCE.3538BE41@trltech.co.uk> Date: Wed, 31 Mar 1999 14:02:06 +0100 From: Richard Smith Reply-To: richard@jezebel.demon.co.uk Organization: http://www.trltech.co.uk/ X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "Steve O'Hara-Smith" Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCMCIA confusion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Steve O'Hara-Smith wrote: > > Try disabling the kldload in /etc/rc.pccardd, and then ring the > changes around pccard linked/kld'd/both and see how far you get. If I understand things correctly, I am linking pcic into my custom kernal and then kld the same module again. I have just booted GENERIC (which has pcic etc. commented out), logged in as root and invoked: kldload pcic I get the following error messages: link_elf: symbol pccard_remove_controller undefined Does this help? Does it indicate why the linked version doesn't work either? Is there any other tests I should do? Thanks, Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 6:55:44 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hermes.vmunix.dhs.org (unknown [195.192.213.120]) by hub.freebsd.org (Postfix) with ESMTP id 201ED14F96 for ; Wed, 31 Mar 1999 06:55:42 -0800 (PST) (envelope-from stjerneby@hermes.vmunix.dhs.org) Received: (from stjerneby@localhost) by hermes.vmunix.dhs.org (8.9.2/8.9.2) id QAA75611 for freebsd-mobile@freebsd.org; Wed, 31 Mar 1999 16:55:12 +0200 (CEST) (envelope-from stjerneby) Date: Wed, 31 Mar 1999 16:55:12 +0200 (CEST) From: Sune Stjerneby Message-Id: <199903311455.QAA75611@hermes.vmunix.dhs.org> To: freebsd-mobile@freebsd.org Subject: IBM Thinkpad/WD XF86Config Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, Would anyone happen to have a working Thinkpad XF86Config - I've got an older 486DX2/66 model with a greyscale display and a WD90C24 chipset, but I can only get the VGA16 and Mono servers up (in 640x480) - the SVGA server (in 8bit) gives me display faults (duplicated cursor/screen) - configs or hints are welcomed 8). -Suine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 7: 2:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (Postfix) with ESMTP id DDF1014F96 for ; Wed, 31 Mar 1999 07:02:09 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.2/8.9.2) with ESMTP id KAA05229; Wed, 31 Mar 1999 10:26:00 -0500 (EST) (envelope-from oleg@ogurok.com) Date: Wed, 31 Mar 1999 10:26:00 -0500 (EST) From: Oleg Ogurok To: Sune Stjerneby Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: IBM Thinkpad/WD XF86Config In-Reply-To: <199903311455.QAA75611@hermes.vmunix.dhs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Try http://www.cs.utexas.edu/users/kharker/linux-laptop/ It's for Linux, but may help. Oleg Ogurok oleg@ogurok.com http://www.ogurok.com On Wed, 31 Mar 1999, Sune Stjerneby wrote: > Hi there, > > Would anyone happen to have a working Thinkpad XF86Config - I've got an older 486DX2/66 model with a greyscale display and a WD90C24 chipset, but I can only get the VGA16 and Mono servers up (in 640x480) - the SVGA server (in 8bit) gives me display faults (duplicated cursor/screen) - configs or hints are welcomed 8). > > -Suine > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 7:32: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id D9F4F15C64 for ; Wed, 31 Mar 1999 07:31:52 -0800 (PST) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.2/8.9.2) with ESMTP id QAA10886; Wed, 31 Mar 1999 16:27:11 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <37021CCE.3538BE41@trltech.co.uk> Date: Wed, 31 Mar 1999 16:27:10 +0100 (IST) From: "Steve O'Hara-Smith" To: richard@jezebel.demon.co.uk Subject: Re: PCMCIA confusion Cc: freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31-Mar-99 Richard Smith wrote: > If I understand things correctly, I am linking pcic into my custom > kernal and then kld the same module again. Your understanding is correct. > I have just booted GENERIC (which has pcic etc. commented out), OK given that that failed, try your custom kernel and remove the kldload from /etc/rc.pccard (this is the arrangement that works for me). ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 31-Mar-99 Time: 15:59:57 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 8:20:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hotpoint.dcs.qmw.ac.uk (hotpoint.dcs.qmw.ac.uk [138.37.88.162]) by hub.freebsd.org (Postfix) with ESMTP id A577A1545B for ; Wed, 31 Mar 1999 08:20:52 -0800 (PST) (envelope-from scott@dcs.qmw.ac.uk) Received: from brian.dcs.qmw.ac.uk [138.37.88.7]; by hotpoint.dcs.qmw.ac.uk (8.8.7/8.8.5/S-4.0) with ESMTP; id RAA11588; Wed, 31 Mar 1999 17:20:19 +0100 (BST) Received: (from scott@localhost) by brian.dcs.qmw.ac.uk (8.9.1b+Sun/8.9.1) id RAA02148; Wed, 31 Mar 1999 17:20:21 +0100 (BST) Message-ID: <19990331172021.C1985@dcs.qmw.ac.uk> Date: Wed, 31 Mar 1999 17:20:21 +0100 From: Scott Mitchell To: "Steve O'Hara-Smith" , richard@jezebel.demon.co.uk Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCMCIA confusion References: <37021CCE.3538BE41@trltech.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steve O'Hara-Smith on Wed, Mar 31, 1999 at 04:27:10PM +0100 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 31, 1999 at 04:27:10PM +0100, Steve O'Hara-Smith wrote: > > On 31-Mar-99 Richard Smith wrote: > > > If I understand things correctly, I am linking pcic into my custom > > kernal and then kld the same module again. > > Your understanding is correct. > > > I have just booted GENERIC (which has pcic etc. commented out), > > OK given that that failed, try your custom kernel and remove > the kldload from /etc/rc.pccard (this is the arrangement that works for > me). I think you need to leave the 'controller card0' line in the kernel config, and have *either* the 'device pcicN at card?' stuff statically compiled in *or* dynamically loaded at boot time. I've gone the dynamic route and it seems to be working fine, modulo all the other problems with the PCCARD code. I submitted a PR to get this into the ERRATA file, since it seems to be biting just about everyone...committers? Scott -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just | 0x54B171B9 | like a dried up piece of roast goat" QMW College, London, UK | 0xAA775B8B | -- J. S. Bach. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 9:38:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id D1FA2155E8 for ; Wed, 31 Mar 1999 09:38:12 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA02485; Wed, 31 Mar 1999 12:33:45 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 31 Mar 1999 12:33:44 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Robert Withrow Cc: freebsd-mobile@freebsd.org Subject: Re: Closing laptop lid confuses X In-Reply-To: <199903252329.SAA25764@tuva.engeast.baynetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Mar 1999, Robert Withrow wrote: > On my Gateway Solo 9100 (with a trident chipset), running PAO 2.2.8, > when I close the lid and re-open it, the X11 display (XF86 3.3.3) > has disappeared. I've tried: > > - Switching VTs > - Building the kernel with the SYSCONS_VTY_RESUME option > - Killing and re-starting XDM > > Only the last option fixes the screen. > > If I am at the X11 vty, switching to standby mode doesn't cause > screen problems but suspending does. If I'm at a normal vty, > I can do either and X11 is fine when I switch back to the X11 vty. > > Anyone know of a fix? If not, should I go to the XFree people? Is > there an XFree-mobile list? I have a similar problem using XiG on an IBM 560E with the Trident chipset. Whenever the notebook suspends, if X is the active VT, then the display does not wake up again (although everything else is fine). If I switch to a VT after waking up and resuspend, it remembers to power up the display. I'm not sure if this is a bug in APM, or in the X server. This is actually much worse when the notebook isn't plugged in--if it's running off battery, and suspended while X was active, then I have to hard boot the machine. VTs work fine in either case. Since XFree86 provides extremely poor support for the Trident chipset (no 800x600xdecentnumberofcolors), I haven't tried XFree86 much. I'd really prefer to, as AccelX has a number of bugs in its X protocols support resulting in the X server crashing a bit too often for my liking (especially when I run KDE or xfig). XiG has also disclaimed any support for recent versions of FreeBSD, at least last time I contacted their technical support. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 12:51:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 97A6C1511B for ; Wed, 31 Mar 1999 12:51:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01152; Wed, 31 Mar 1999 12:45:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903312045.MAA01152@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: richard@jezebel.demon.co.uk Cc: "Steve O'Hara-Smith" , freebsd-mobile@FreeBSD.ORG Subject: Re: PCMCIA confusion In-reply-to: Your message of "Wed, 31 Mar 1999 14:02:06 +0100." <37021CCE.3538BE41@trltech.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Mar 1999 12:45:09 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do not attempt to load the pcic module. You need everything static. > Steve O'Hara-Smith wrote: > > > > Try disabling the kldload in /etc/rc.pccardd, and then ring the > > changes around pccard linked/kld'd/both and see how far you get. > > If I understand things correctly, I am linking pcic into my custom > kernal and then kld the same module again. > > I have just booted GENERIC (which has pcic etc. commented out), logged > in as root and invoked: > > kldload pcic > > I get the following error messages: > > link_elf: symbol pccard_remove_controller undefined > > Does this help? Does it indicate why the linked version doesn't work > either? Is there any other tests I should do? > > Thanks, > Richard. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 12:54:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Bespin.worldnet.net (bespin.worldnet.net [195.3.3.4]) by hub.freebsd.org (Postfix) with ESMTP id 9801714BFF for ; Wed, 31 Mar 1999 12:54:27 -0800 (PST) (envelope-from pcasidy@worldnet.fr) Received: from greatoak.home (p15-201.province.worldnet.fr [195.3.15.201]) by Bespin.worldnet.net (8.8.8/8.8.8) with ESMTP id WAA11880 for ; Wed, 31 Mar 1999 22:51:57 +0200 (CEST) Received: (from pcasidy@localhost) by greatoak.home (8.8.8/8.8.8) id WAA04224 for freebsd-mobile@freebsd.org; Wed, 31 Mar 1999 22:36:16 +0200 (CEST) (envelope-from pcasidy) Message-Id: <199903312036.WAA04224@greatoak.home> Date: Wed, 31 Mar 1999 22:36:16 +0200 (CEST) From: Philippe CASIDY Subject: Re: Which LAN PCCARD for FreeBSD (no PAO!) To: freebsd-mobile@freebsd.org In-Reply-To: <199903251636.RAA04214@greatoak.home> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25 Mar, Philippe CASIDY wrote: > Hello! > > I need urgently a working ethernet PCCARD while waiting for someone or > I make the 3COM 3CCFEM556BI works! > > I would like to know which card works under FreeBSD 3.1R and FreeBSD > 2.2.8R WITHOUT PAO! > > Thanks! > Thanks for people who gave me an answer! I did not want to start a war with this mail. I mentioned that I did not want a 'PAO' answer for two reasons : - I did not want an answer being : "check PAO web page blabla" - I did not want to have to fall back from 3.1R to 2.2.8R when I upgrade to it. As far as I am concern, 2.2.8R works pretty well with laptop : - APM suspend to disk works very well (except that I cannot set the timeout to suspend mode) - the PCCARD I use works well with it. So, this is not a technical issue but an 'availabality' (is it spelled correctly?) issue. At the beginning, I was quite worried about the emails going from one side to the other trying to show who made the biggest bugs! But now things seems to become clearer, I have just one thing to say : HEY GUYS! WHAT YOU ARE DOING IS GREAT! Keep up the good work and do it right! Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 22:28:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 87336151AF for ; Wed, 31 Mar 1999 22:28:16 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id PAA16114; Wed, 31 Mar 1999 15:24:58 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98122515) with ESMTP id PAA00950; Wed, 31 Mar 1999 15:24:57 +0900 (JST) Message-Id: <199903310624.PAA00950@hotaka.csl.sony.co.jp> To: freebsd-mobile@FreeBSD.ORG Cc: Poul-Henning Kamp Subject: timer problem (calcru: negative time) after resume Date: Wed, 31 Mar 1999 15:24:57 +0900 From: Kenjiro Cho Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some laptop machines running 3.x/4.x exhibit the "calcru: negative time" problem after resume. At least, the following machines appear to have this problem. - ThinkPad 235 (Chandra II) - MITSUBISHI Pedion M3041 - Sharp Mebius MN-5400D Iwasaki-san and I were working on this back in February. (We should've reported this earlier...) It turns out that the countdown register of i8254 timer is destroyed after resume. The counter value becomes more than "timer0_max_count", which spoils the hardclock interval and timecounter badly. It seems that, though bios should restore the i8254 registers, it is safer to restore the register value on resume since the "calcru" problem is hard to track down. The patch below has been tested for a while among the PAO users. --Kenjiro --- i386/apm/apm.c Fri Feb 19 04:20:13 1999 +++ /sys/i386/apm/apm.c Sun Feb 28 03:43:40 1999 @@ -471,6 +471,7 @@ else { /* modified for adjkerntz */ pl = splsoftclock(); + i8254_restore(); /* restore timer_freq and hz */ inittodr(0); /* adjust time to RTC */ microtime(&resume_time); getmicrotime(&tmp_time); diff -ru i386/include/clock.h /sys/i386/include/clock.h --- i386/include/clock.h Fri Nov 6 15:33:23 1998 +++ /sys/i386/include/clock.h Sat Feb 27 16:03:28 1999 @@ -44,6 +44,7 @@ #endif int sysbeep __P((int pitch, int period)); int sysbeep_cancel __P((void)); +void i8254_restore __P((void)); #endif /* KERNEL */ diff -ru i386/isa/clock.c /sys/i386/isa/clock.c --- i386/isa/clock.c Fri Feb 19 04:21:19 1999 +++ /sys/i386/isa/clock.c Sat Feb 27 16:23:19 1999 @@ -744,6 +744,28 @@ #endif /* ncv port */ /* + * i8254_restore is called from apm_default_resume() to reload + * the countdown register. + * this should not be necessary but there are broken laptops that + * do not restore the countdown register on resume. + * when it happnes, it messes up the hardclock interval and system clock, + * which leads to the infamous "calcru: negative time" problem. + */ +void +i8254_restore(void) +{ + u_long ef; + + ef = read_eflags(); + disable_intr(); + outb(TIMER_MODE, TIMER_SEL0 | TIMER_RATEGEN | TIMER_16BIT); + outb(TIMER_CNTR0, timer0_max_count & 0xff); + outb(TIMER_CNTR0, timer0_max_count >> 8); + CLOCK_UNLOCK(); + write_eflags(ef); +} + +/* * Initialize 8254 timer 0 early so that it can be used in DELAY(). * XXX initialization of other timers is unintentionally left blank. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 22:49:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id BD69A15C98 for ; Wed, 31 Mar 1999 22:49:18 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id IAA00410; Wed, 31 Mar 1999 08:37:59 +0900 (JST) Date: Wed, 31 Mar 1999 08:37:59 +0900 (JST) Message-Id: <199903302337.IAA00410@afs.ntc.mita.keio.ac.jp> To: raj@cisco.com Cc: freebsd-mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: Powering down PCMCIA modem card In-Reply-To: Your message of "Wed, 31 Mar 1999 03:43:08 JST". <199903301843.KAA02121@kitab.cisco.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199903301843.KAA02121@kitab.cisco.com> raj@cisco.com writes: >> The version of pccardc distributed with 3.1 doesn't have the "power" >> command. I'll have to investigate this further. Perhaps I can just >> grab the PAO version and use that. pccardc power option requires the correspoinding ioctl in sys/pccard/pccard.c. Please see the code of beta version in http://wing-yee.ntc.keio.ac.jp/PAO/ -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 31 23:11:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39]) by hub.freebsd.org (Postfix) with SMTP id E70401516C for ; Wed, 31 Mar 1999 23:11:15 -0800 (PST) (envelope-from olivier.charles@cnet.francetelecom.fr) Received: from cnet.francetelecom.fr (p-brokenpipe.issy.cnet.fr [139.100.16.186]) by p-voyageur.issy.cnet.fr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id GGMHTW9Q; Thu, 1 Apr 1999 09:10:54 +0200 Message-ID: <37031BAA.26C17DBF@cnet.francetelecom.fr> Date: Thu, 01 Apr 1999 09:09:30 +0200 From: Olivier Charles X-Mailer: Mozilla 4.06 [fr] (WinNT; I) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org unsubscribe freebsd-mobile To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 1 1: 3:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hotpoint.dcs.qmw.ac.uk (hotpoint.dcs.qmw.ac.uk [138.37.88.162]) by hub.freebsd.org (Postfix) with ESMTP id EA9BF14E7C for ; Thu, 1 Apr 1999 01:03:37 -0800 (PST) (envelope-from scott@dcs.qmw.ac.uk) Received: from brian.dcs.qmw.ac.uk [138.37.88.7]; by hotpoint.dcs.qmw.ac.uk (8.8.7/8.8.5/S-4.0) with ESMTP; id KAA27715; Thu, 1 Apr 1999 10:03:13 +0100 (BST) Received: (from scott@localhost) by brian.dcs.qmw.ac.uk (8.9.1b+Sun/8.9.1) id KAA02528; Thu, 1 Apr 1999 10:03:17 +0100 (BST) Message-ID: <19990401100317.K1985@dcs.qmw.ac.uk> Date: Thu, 1 Apr 1999 10:03:17 +0100 From: Scott Mitchell To: Mike Smith Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCMCIA confusion References: <37021CCE.3538BE41@trltech.co.uk> <199903312045.MAA01152@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903312045.MAA01152@dingo.cdrom.com>; from Mike Smith on Wed, Mar 31, 1999 at 12:45:09PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 31, 1999 at 12:45:09PM -0800, Mike Smith wrote: > > Do not attempt to load the pcic module. You need everything static. Why is that Mike? Things seem to more-or-less work with a static card0 controller and the pcic module, for me anyway. Scott > > Steve O'Hara-Smith wrote: > > > > > > Try disabling the kldload in /etc/rc.pccardd, and then ring the > > > changes around pccard linked/kld'd/both and see how far you get. > > > > If I understand things correctly, I am linking pcic into my custom > > kernal and then kld the same module again. > > > > I have just booted GENERIC (which has pcic etc. commented out), logged > > in as root and invoked: > > > > kldload pcic > > > > I get the following error messages: > > > > link_elf: symbol pccard_remove_controller undefined > > > > Does this help? Does it indicate why the linked version doesn't work > > either? Is there any other tests I should do? > > > > Thanks, > > Richard. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-mobile" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just | 0x54B171B9 | like a dried up piece of roast goat" QMW College, London, UK | 0xAA775B8B | -- J. S. Bach. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 1 9:13:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4AC7D1524B for ; Thu, 1 Apr 1999 09:13:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA03698; Thu, 1 Apr 1999 19:13:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA32945; Thu, 1 Apr 1999 19:12:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kenjiro Cho Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: timer problem (calcru: negative time) after resume In-reply-to: Your message of "Wed, 31 Mar 1999 15:24:57 +0900." <199903310624.PAA00950@hotaka.csl.sony.co.jp> Date: Thu, 01 Apr 1999 19:12:48 +0200 Message-ID: <32943.922986768@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, yeah I see the problem. Calling inittodr(0) is not without problems either. Gak! I need to think about this one... Poul-Henning In message <199903310624.PAA00950@hotaka.csl.sony.co.jp>, Kenjiro Cho writes: > >Some laptop machines running 3.x/4.x exhibit the "calcru: negative time" >problem after resume. >At least, the following machines appear to have this problem. > - ThinkPad 235 (Chandra II) > - MITSUBISHI Pedion M3041 > - Sharp Mebius MN-5400D > >Iwasaki-san and I were working on this back >in February. (We should've reported this earlier...) > >It turns out that the countdown register of i8254 timer is destroyed >after resume. The counter value becomes more than >"timer0_max_count", which spoils the hardclock interval and >timecounter badly. > >It seems that, though bios should restore the i8254 registers, it is >safer to restore the register value on resume since the "calcru" >problem is hard to track down. >The patch below has been tested for a while among the PAO users. > >--Kenjiro > >--- i386/apm/apm.c Fri Feb 19 04:20:13 1999 >+++ /sys/i386/apm/apm.c Sun Feb 28 03:43:40 1999 >@@ -471,6 +471,7 @@ > else { > /* modified for adjkerntz */ > pl = splsoftclock(); >+ i8254_restore(); /* restore timer_freq and hz */ > inittodr(0); /* adjust time to RTC */ > microtime(&resume_time); > getmicrotime(&tmp_time); >diff -ru i386/include/clock.h /sys/i386/include/clock.h >--- i386/include/clock.h Fri Nov 6 15:33:23 1998 >+++ /sys/i386/include/clock.h Sat Feb 27 16:03:28 1999 >@@ -44,6 +44,7 @@ > #endif > int sysbeep __P((int pitch, int period)); > int sysbeep_cancel __P((void)); >+void i8254_restore __P((void)); > > #endif /* KERNEL */ > >diff -ru i386/isa/clock.c /sys/i386/isa/clock.c >--- i386/isa/clock.c Fri Feb 19 04:21:19 1999 >+++ /sys/i386/isa/clock.c Sat Feb 27 16:23:19 1999 >@@ -744,6 +744,28 @@ > #endif /* ncv port */ > > /* >+ * i8254_restore is called from apm_default_resume() to reload >+ * the countdown register. >+ * this should not be necessary but there are broken laptops that >+ * do not restore the countdown register on resume. >+ * when it happnes, it messes up the hardclock interval and system clock, >+ * which leads to the infamous "calcru: negative time" problem. >+ */ >+void >+i8254_restore(void) >+{ >+ u_long ef; >+ >+ ef = read_eflags(); >+ disable_intr(); >+ outb(TIMER_MODE, TIMER_SEL0 | TIMER_RATEGEN | TIMER_16BIT); >+ outb(TIMER_CNTR0, timer0_max_count & 0xff); >+ outb(TIMER_CNTR0, timer0_max_count >> 8); >+ CLOCK_UNLOCK(); >+ write_eflags(ef); >+} >+ >+/* > * Initialize 8254 timer 0 early so that it can be used in DELAY(). > * XXX initialization of other timers is unintentionally left blank. > */ > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-mobile" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 0:41:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from turtle.ee.ncku.edu.tw (turtle.ee.ncku.edu.tw [140.116.72.72]) by hub.freebsd.org (Postfix) with ESMTP id 5D9A015334 for ; Fri, 2 Apr 1999 00:38:44 -0800 (PST) (envelope-from tung@turtle.ee.ncku.edu.tw) Received: (from tung@localhost) by turtle.ee.ncku.edu.tw (8.9.2/8.9.2) id QAA81251 for freebsd-mobile@FreeBSD.ORG; Fri, 2 Apr 1999 16:38:25 +0800 (CST) (envelope-from tung) Date: Fri, 2 Apr 1999 16:38:25 +0800 From: Chung-Kie Tung To: freebsd-mobile@FreeBSD.ORG Subject: Any success with CirrusLogic 6729/6730??? Message-ID: <19990402163825.A81222@turtle.ee.ncku.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello.... I have exactly the same problem as Richard(rsmith@trltech.co.uk) does. Cause both our notebook use Cirrus Logic 6729/6730 pcic, I am wondering that if any one with Cirrus Logic PD6729/6730 pcic has been successfully running FreeBSD 3.1 Release with pcmcia activie? tung@garfield.ee.ncku.edu.tw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 1:29:43 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 08F5914E65 for ; Fri, 2 Apr 1999 01:29:41 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id SAA03448; Fri, 2 Apr 1999 18:27:48 +0900 (JST) Message-Id: <199904020927.SAA03448@chandra.eatell.msr.prug.or.jp> To: Chung-Kie Tung Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 02 Apr 1999 16:38:25 +0800." <19990402163825.A81222@turtle.ee.ncku.edu.tw> Date: Fri, 02 Apr 1999 18:27:47 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am wondering that if any one with Cirrus Logic PD6729/6730 pcic > has been successfully running FreeBSD 3.1 Release with pcmcia activie? These are supported by PAO. If BIOS setuped ioport for generally port (0x3e0), probably it works with plain FreeBSD. But, If BIOS not set it, you need initialized code, it included PAO. If BIOS setuped non-generally port, you must change ioport. plain FreeBSD can't change it by UserConfig, PAO can change it. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 9: 5:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 0776A14CB4 for ; Fri, 2 Apr 1999 09:05:17 -0800 (PST) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id JAA07233 for ; Fri, 2 Apr 1999 09:05:03 -0800 (PST) (envelope-from gfish@uniqsite.com) Date: Fri, 2 Apr 1999 09:05:03 -0800 (PST) From: Gold Fish To: mobile@freebsd.org Subject: 3Com 3C575 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What needs to go to pccard.conf in order to make this card under R 3.1? The manual gave some settings as follows: CIS memory address: 0090H-00FFH IO Base Address: 3000H (?? strange, isn't it?) IRQ: 5, 7, 9, 10, 11, 12. How come the IO address goes above 0x0FFF? When I specified it in pccard.conf, it says the address is invalid and pccardd refuse to load. Help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 9:12:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 7AEAD14CB1 for ; Fri, 2 Apr 1999 09:12:19 -0800 (PST) (envelope-from nsayer@medusa.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [170.1.70.5]) by quack.kfu.com (8.9.2/8.8.5) with ESMTP id JAA50828 for ; Fri, 2 Apr 1999 09:12:00 -0800 (PST) Received: (from nsayer@localhost) by medusa.kfu.com (8.9.2/8.8.8) id JAA12272 for freebsd-mobile@freebsd.org; Fri, 2 Apr 1999 09:12:00 -0800 (PST) (envelope-from nsayer) From: Nick Sayer Message-Id: <199904021712.JAA12272@medusa.kfu.com> Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904020927.SAA03448@chandra.eatell.msr.prug.or.jp> from NAKAGAWA Yoshihisa at "Apr 2, 1999 6:27:47 pm" To: freebsd-mobile@freebsd.org Date: Fri, 2 Apr 1999 09:12:00 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I am wondering that if any one with Cirrus Logic PD6729/6730 pcic > > has been successfully running FreeBSD 3.1 Release with pcmcia activie? > > These are supported by PAO. If BIOS setuped ioport for generally > port (0x3e0), probably it works with plain FreeBSD. But, If BIOS > not set it, you need initialized code, it included PAO. > > If BIOS setuped non-generally port, you must change ioport. plain > FreeBSD can't change it by UserConfig, PAO can change it. This was the prime reason my last laptop needed PAO. It had a 6729, but didn't live in the usual 0x3e0 spot. I would like to very carefully merge some of the pcic_p.c initialization routines from PAO to -current. Or at least try. I would not, however, like to be beaten to a bloody pulp for doing so. :-) -- echo afnlre@dhnpx.xsh.pbz |\ : Anita Hill then, Paula Jones now. tr 'a-z' 'n-za-m' : or remove nospam in From: line : What goes around, comes around. http://www.kfu.com/~nsayer/ : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 9:31:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 555FD14BDB for ; Fri, 2 Apr 1999 09:31:23 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id LAA09091; Fri, 2 Apr 1999 11:30:53 -0600 (CST) Date: Fri, 2 Apr 1999 11:30:53 -0600 (CST) From: Steve Price To: Gold Fish Cc: mobile@FreeBSD.ORG Subject: Re: 3Com 3C575 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This card won't work at present. It is a CardBus (32-bit PCMCIA) card and FreeBSD doesn't (yet) have a driver for it. -steve On Fri, 2 Apr 1999, Gold Fish wrote: # # What needs to go to pccard.conf in order to make this card under R 3.1? # # The manual gave some settings as follows: # # CIS memory address: 0090H-00FFH # IO Base Address: 3000H (?? strange, isn't it?) # IRQ: 5, 7, 9, 10, 11, 12. # # How come the IO address goes above 0x0FFF? When I specified it in # pccard.conf, it says the address is invalid and pccardd refuse to load. # # Help. # # # # # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-mobile" in the body of the message # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 9:55:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 9AD9714DBB for ; Fri, 2 Apr 1999 09:55:31 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA13237; Fri, 2 Apr 1999 10:55:12 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA01627; Fri, 2 Apr 1999 10:55:11 -0700 Date: Fri, 2 Apr 1999 10:55:11 -0700 Message-Id: <199904021755.KAA01627@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nick Sayer Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904021712.JAA12272@medusa.kfu.com> References: <199904020927.SAA03448@chandra.eatell.msr.prug.or.jp> <199904021712.JAA12272@medusa.kfu.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I would like to very carefully merge some of the pcic_p.c initialization > routines from PAO to -current. Or at least try. Send them to the mailing list at least for review. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 11: 8:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 6EB5514E0F for ; Fri, 2 Apr 1999 11:08:14 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA18797; Fri, 2 Apr 1999 11:07:43 -0800 (PST) Message-Id: <199904021907.LAA18797@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 02 Apr 1999 10:55:11 MST." <199904021755.KAA01627@mt.sri.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Apr 1999 11:07:42 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: >> I would like to very carefully merge some of the pcic_p.c initialization >> routines from PAO to -current. Or at least try. > >Send them to the mailing list at least for review. OK. :-) Hi Nate! Someone with a 6729 try applying this patch to pcic_p.[ch] (i.e., cd to /sys/pci and do patch < file ) and tell me if it recognizes your card. If it doesn't, send me the dmesg from a verbose boot, and we'll see what we can do. ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc *** pcic_p.c.orig Sun Dec 13 22:32:57 1998 --- pcic_p.c Fri Apr 2 10:56:36 1999 *************** *** 48,53 **** --- 48,54 ---- static void pcic_pci_attach(pcici_t, int); static void pd6832_legacy_init(pcici_t tag, int unit); + static void pd6729_init(pcici_t tag, int unit); static struct pci_device pcic_pci_driver = { "pcic", *************** *** 97,102 **** --- 98,106 ---- case PCI_DEVICE_ID_PCIC_CLPD6832: pd6832_legacy_init(config_id, unit); break; + case PCI_DEVICE_ID_PCIC_CLPD6729: + pd6729_init(config_id, unit); + break; } if (bootverbose) { *************** *** 188,193 **** --- 192,233 ---- /* After initializing 2 sockets, the chip is fully configured */ if (unit == 1) num6832++; + + if (bootverbose) + printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", + io_port); + } + /* + * Set up the CL-PD6729 This routine is called once per PCMCIA socket. + */ + static void + pd6729_init(pcici_t tag, int unit) + { + u_short io_port; /* the io_port to map this slot on */ + static int num6729 = 0; /* The number of 6832s initialized */ + + /* + * Some BIOS leave the legacy address uninitialized. This + * insures that the PD6829 puts itself where the driver will + * look. We assume that multiple 6829's should be laid out + * sequentially. We only initialize the first socket's legacy port, + * the other is a dummy. + */ + io_port = PCIC_INDEX_0 + num6729 * CLPD6729_NUM_REGS; + + /* + * Configure the I/O window to contain CLPD6832_NUM_REGS + * words. + */ + pci_conf_write(tag, CLPD6729_BASE0, io_port | 1); + + /* + * Set default operating mode (I/O port space) + */ + pci_conf_write(tag, PCI_COMMAND_STATUS_REG, CLPD6729_COMMAND_DEFAULTS ); + /* After initializing 2 sockets, the chip is fully configured */ + if (unit == 1) + num6729++; if (bootverbose) printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", *** pcic_p.h.orig Tue Jan 20 13:11:03 1998 --- pcic_p.h Fri Apr 2 10:56:24 1999 *************** *** 52,54 **** --- 52,62 ---- #define CLPD6832_NUM_REGS 2 /* End of CL-PD6832 defines */ + /* CL-PD6729 defines */ + #define CLPD6729_BASE0 0x0010 + + /* Configuration constants */ + #define CLPD6729_COMMAND_DEFAULTS 0x00000041 + #define CLPD6729_NUM_REGS 2 + + /* End of CL-PD6832 defines */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 2 11:45:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 8B7E214CB3 for ; Fri, 2 Apr 1999 11:45:38 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10T9sT-0003Cy-00 for freebsd-mobile@freebsd.org; Fri, 2 Apr 1999 14:45:17 -0500 To: freebsd-mobile@freebsd.org From: "Gary Palmer" Subject: 3com 575 Date: Fri, 02 Apr 1999 14:45:17 -0500 Message-ID: <12335.923082317@noop.colo.erols.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've downloaded and patched up a kernel with the patches posted by `UCHIYAMA Yasushi ' two weeks ago or so. I have a 3Com 3CCFE575BT-D (according to the back) (rebadged as a Dell card). However, the vendor/product ID's don't match any 3Com card (infact I suspect the vendor is Intel). dmesg shows: Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 128118784 (125116K bytes) Preloaded elf kernel "kernel.3.1" at 0xf025e000. mainbus0 (root) BIOS32 rev. 0 found at 0xffe90 PCI BIOS rev. 2.1 config mechanism: [1][x] special cycle: [x][x] last bus#:00 pcibios_get_intr_routing: interrupt routing map is broken. mainbus_attach: PCI BIOS fix up failed. pci0 at mainbus0 Probing for devices on PCI bus 0: pchb0 at pci0 dev 0 func 0: Intel 82443BX host to PCI bridge (AGP disabled) vga1 at pci0 dev 2 func 0: NeoMagic NM2160 laptop SVGA controller cbb0 at pci0 dev 3 func 0 (TI1131), flags 3 cbb0: CardBus resister address 0x0 -> 0x68000000 intrpin A, intrtag 11 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=11 trigger=level ipl=bio cbb0: interrupting at irq 11 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68000000 02000000 10000000 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340010b 0x40: 00741028 00000001 00000000 00000000 0x80: 00241024 00000000 00000000 00000000 0x90: 0070aa00 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000006 00000000 00000000 ExCA regs: 84 00 00 10 00 00 00 00 cardbus0 at cbb0 bus 0 device 0 pccbbattach: found cardbus pcmcia0 at cbb0 slot 0 cbb1 at pci0 dev 3 func 1 (TI1131), flags 3 cbb1: CardBus resister address 0x0 -> 0x68010000 intrpin B, intrtag 11 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=11 trigger=level ipl=bio cbb1: interrupting at irq 11 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68010000 02000000 10000000 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340020b 0x40: 00741028 00000001 00000000 00000000 0x80: 00243024 00000000 00000000 00000000 0x90: 0070aa00 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000820 00000000 00000000 ExCA regs: 84 0c 00 10 00 00 00 00 cardbus1 at cbb1 bus 0 device 1 cardbusattach: CardBus card found [0x2] cardbus_attach_card: cb1 start pccbb_power: CARDBUS_VCC_3V and CARDBUS_VPP_UC [1] cardbus_attach_card: Vendor 0x8086, Product 0x7192, CIS 0x0 WRONG TUPLE xl0 at cardbus1 dev 0 function 0pccbb_io_open: 0x8300[0x2c] - 0x8380[0x30] pccbb_cardenable: command reg 0x2000007 xl0: failed to enable I/O ports! pccbbattach: found cardbus pcmcia1 at cbb1 slot 1 pcib0 at pci0 dev 7 func 0: Intel 82371AB PCI to ISA bridge vendor 0x8086 id 0x7111 at pci0 dev 7 func 1: not configured uhci0 at pci0 dev 7 func 2: Intel 82371AB/EB USB Host Controller intr_establish:irq=11 trigger=level ipl=bio usb0 at uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chipset0 at pci0 dev 7 func 3: Intel 82371AB Power management controller isa0 at pcib0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support sc0 at isa0 sc0: VGA color <16 virtual consoles, flags=0x0> vga0 at isa0 npx0 at isa0 irq 13: INT 16 interface apm0 at isa0: found APM BIOS version 1.2 atkbdc0 at isa0 atkbd0 at isa0 irq 1 psm0 at isa0 irq 12 intr_establish:irq=12 trigger=level ipl=bio : model Generic PS/2 mouse, device ID 0 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 intr_establish:irq=6 trigger=edge ipl=bio : FIFO enabled, 8 bytes threshold wdc0 at isa0 irq 14 wd0 at wdc0 unit 0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S isapnp0: no ISA Plug 'n Play devices found changing root device to wd0s2a As you can see, I hacked the cardbus stuff a bit to try and get the xl0 driver to attach to the card, but no luck. Is this indeed a card based on an intel chip? Anyone know? What is a good card to get which is available today and supported? Thanks, Gary P.S. This is a Dell Lattitude CPi, if anyone is curious. -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 7:37: 6 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS34.kng.mesh.ad.jp [133.205.214.34]) by hub.freebsd.org (Postfix) with ESMTP id 4602214C8B for ; Sat, 3 Apr 1999 07:36:55 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id LAA06995; Sat, 3 Apr 1999 11:43:27 +0900 (JST) Message-Id: <199904030243.LAA06995@chandra.eatell.msr.prug.or.jp> To: Ted Faber Cc: Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 02 Apr 1999 11:07:42 PST." <199904021907.LAA18797@boreas.isi.edu> Date: Sat, 03 Apr 1999 11:43:25 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Someone with a 6729 try applying this patch to pcic_p.[ch] (i.e., cd Probably same initialize code is working with O2 micro OZ6729/6730. > + io_port = PCIC_INDEX_0 + num6729 * CLPD6729_NUM_REGS; Cirrus chip has 4byte boundary. First chip is 0x3e0, second chip is 0x3e4, ... Using hard code PCIC_INDEX_0 is dirty. This code is always re-setup ioports, if BIOS setup it, it should be use. Because, BIOS is resource management for the machine. > + if (unit == 1) > + num6729++; What's ? CL-PD6729 is not multi-function. > printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", CL-PD6729 is not CardBus controller. :-) -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 8: 1:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 2D21C152B7 for ; Sat, 3 Apr 1999 08:00:47 -0800 (PST) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id RAA16251 for ; Sat, 3 Apr 1999 17:58:47 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma016249; Sat, 3 Apr 99 17:58:47 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id RAA23491 for freebsd-mobile@freebsd.org; Sat, 3 Apr 1999 17:58:47 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904031558.RAA23491@helena.otelo-call.de> Subject: Re: pcmcia ethernet installation trouble In-Reply-To: From listmail at "Mar 31, 99 00:26:49 am" To: freebsd-mobile@freebsd.org Date: Sat, 3 Apr 1999 17:58:46 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, recently 1 wrote here: > I'm trying to install 2.2.7 on a Toshiba T1910 > via a Fiberline FL-4680 Ethernet card. (I have no more documentation > on this one, but found some Linux Data claiming it to be a Tulip > Card). > > I got the 2.2.7 boot-pao.flp. This one recogniszes the card > and says it assigns it ed0. > > But ed0 doesn't appear in the list of available devices when choosing > installation media. I have now tried with the 2.2.8 based boot_pao.flp as well, without success. It shows the same effect. - Any hints, advice, etc? I think I have read all available documentation on pao (which is not that much, BTW) but maybe I'm missing something crucial ? - I have not got a single response or comment to my first posting. Is there some Information missing, could I add further Information to shed light on this issue ? - From what I've read this card could well work with pao, having a supported chip set. I this perception correct, or doesn't it work anyway since it's not expressedly listed as a supported card ? Regards, and thanks in advance for any answer, Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 9:31:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from f77.nop.or.jp (f77.nop.or.jp [210.145.217.241]) by hub.freebsd.org (Postfix) with ESMTP id D6A5A14C90; Sat, 3 Apr 1999 09:31:04 -0800 (PST) (envelope-from uch@nop.or.jp) Received: from localhost (localhost [127.0.0.1]) by f77.nop.or.jp (8.9.1a/3.7W) with ESMTP id CAA12413; Sun, 4 Apr 1999 02:29:00 +0900 (JST) To: gpalmer@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: 3com 575 X-Mailer: Mew version 1.92 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990404022859A.uch@nop.or.jp> Date: Sun, 04 Apr 1999 02:28:59 +0900 From: UCHIYAMA Yasushi X-Dispatcher: imput version 971024 Lines: 227 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org | I've downloaded and patched up a kernel with the patches posted by | `UCHIYAMA Yasushi ' two weeks ago or so. I have a 3Com | 3CCFE575BT-D (according to the back) (rebadged as a Dell | card). However, the vendor/product ID's don't match any 3Com card | (infact I suspect the vendor is Intel). Thank you for testing my patch. | BIOS32 rev. 0 found at 0xffe90 | PCI BIOS rev. 2.1 config mechanism: [1][x] special cycle: [x][x] last bus#:00 | pcibios_get_intr_routing: interrupt routing map is broken. | mainbus_attach: PCI BIOS fix up failed. Your machines' default PCI configuration register setting is not correct.(but almost PCI-CardBus bridge are so.) Because PCI bus enumeration is bogus, configuration cycle didn't come down to PCI bus #1,2(cbb0,cbb1) so didn't find 3c575. (but found Intel chip on bus #0). cardbus0 at cbb0 bus 0 device 0 cardbus1 at cbb1 bus 0 device 1 should be cardbus0 at cbb0 bus 1 device 0 cardbus1 at cbb1 bus 2 device 1 Please change sys/i386/pci/pcibios.c to ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/pcibios.c Then, Let me see its dmesg. And 3C575BTX support is not completed(This card needs CardBus specific change in if_xl.c). 3C575TX is more stable. --- UCHIYAMA Yasushi uch@nop.or.jp My 3CXFE575BT + TI PCI-1131 dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #1: Sun Apr 4 01:57:49 JST 1999 uch@r3000.rfe.nop.or.jp:/usr/src/sys/compile/ALEXANDLITE Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (200.46-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x561 Stepping=1 Features=0x8001bf real memory = 62914560 (61440K bytes) avail memory = 58781696 (57404K bytes) Preloaded elf kernel "kernel" at 0xf025a000. mainbus0 (root) BIOS32 rev. 0 found at 0xf04a0 PCI BIOS at 0xf0000-0xf0b52 entry point: 0xf04d0 rev. 2.1 config mechanism: [1][x] special cycle: [1][x] last bus#:00 PCI only IRQ bitmap:................ bus: 0 device: 12 slot: 1 INTA# link=1...||||.|.|||... INTB# link=2...||||.|.|||... INTC# link=3...||||.|.|||... INTD# link=4...||||.|.|||... bus: 0 device: 11 slot: 2 INTA# link=2...||||.|.|||... INTB# link=3...||||.|.|||... INTC# link=4...||||.|.|||... INTD# link=1...||||.|.|||... bus: 0 device: 10 slot: 3 INTA# link=3...||||.|.|||... INTB# link=4...||||.|.|||... INTC# link=1...||||.|.|||... INTD# link=2...||||.|.|||... bus: 0 device: 9 slot: 4 INTA# link=4...||||.|.|||... INTB# link=1...||||.|.|||... INTC# link=2...||||.|.|||... INTD# link=3...||||.|.|||... bus: 0 device: 1 slot: 0 INTA# link=1...||||.|.|||... INTB# link=2...||||.|.|||... INTC# link=3...||||.|.|||... INTD# link=4...||||.|.|||... bus: 0 device: 19 slot: 0 INTA# link=1...||||.|.|||... INTB# link=2...||||.|.|||... INTC# link=3...||||.|.|||... INTD# link=4...||||.|.|||... bus: 0 device: 13 slot: 0 INTA# link=1...||||.|.|||... INTB# link=2...||||.|.|||... INTC# link=3...||||.|.|||... INTD# link=4...||||.|.|||... bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 Bus Device Function Slot Pin Link IRQ Vendor Product ----------------------------------------------------- 0 12 0 1 A 0 11 104c ac15 0 12 1 1 B 1 10 104c ac15 0 1 0 0 - - - 1039 0008 0 1 1 0 A X0 14x11 1039 5513 0 1 2 0 A X0 12x11 1039 7001 0 19 0 0 - - - 1039 0200 PCI IRQ map:.|.|||.......... Link->IRQ:[ 0->11 1->10 2->N 3->N ] # of bogus devices:0/4 ----------------------------------------------------- bridge0 primary=0 secondary=1 subordinate=1 bridge1 primary=0 secondary=2 subordinate=2 pcibios_fixup: Correct last bus # is 2. pci0 at mainbus0 Probing for devices on PCI bus 0: pchb0 at pci0 dev 0 func 0pcib0 at pci0 dev 1 func 0: SiS 85c503 vendor 0x1039 id 0x5513 at pci0 dev 1 func 1: not configured vendor 0x1039 id 0x7001 at pci0 dev 1 func 2: not configured cbb0 at pci0 dev 12 func 0 (TI1131), flags 3 cbb0: CardBus resister address 0x0 -> 0x68000000 intrpin A, intrtag 11 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=11 trigger=level ipl=bio cbb0: interrupting at irq 11 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68000000 02000000 10010100 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340010b 0x40: 00000000 00000001 00000000 00000000 0x80: 00043020 00000000 00000000 00000000 0x90: 00702800 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000820 00000000 00000000 ExCA regs: 84 0c 00 10 00 00 00 00 cardbus0 at cbb0 bus 1 device 0 cardbusattach: CardBus card found [0x2] cardbus_attach_card: cb0 start pccbb_power: CARDBUS_VCC_3V and CARDBUS_VPP_UC [1] cardbus_attach_card: Vendor 0x10b7, Product 0x5157, CIS 0x90 tuple: LINKTARGET len 5 0x 0: 13 3 43 49 53 tuple: MANFID len 6 0x 0: 20 4 1 1 57 51 tuple: CONFIG_CB len 8 0x 0: 4 6 3 1 0 0 0 0 tuple: CFTABLE_ENTRY_CB len 14 0x 0: 5 c 41 9a 1 b5 1e 1 55 2 30 ff ff 1 tuple: BAR len 8 0x 0: 7 6 11 0 40 0 0 0 tuple: VERS_1 len 54 0x 0: 15 34 5 0 33 43 6f 6d 20 43 6f 72 70 6f 72 61 0x10: 74 69 6f 6e 0 33 43 43 46 45 35 37 35 42 54 0 0x20: 4c 41 4e 20 43 61 72 64 62 75 73 20 43 61 72 64 0x30: 0 30 30 31 0 ff tuple: FUNCID len 4 0x 0: 21 2 6 1 tuple: CFTABLE_ENTRY_CB len 8 0x 0: 5 6 0 80 80 80 80 19 tuple: END len 1 xl0 at cardbus0 dev 0 function 0pccbb_io_open: 0x8300[0x2c] - 0x8380[0x30] pccbb_cardenable: command reg 0x2000007 pccbb_cardenable: command reg 0x2000007 3Com 3C575BTX (cyclone)xl0: Ethernet address: 00:00:86:33:58:10 pccbbattach: found cardbus pcmcia0 at cbb0 slot 0 cbb1 at pci0 dev 12 func 1 (TI1131), flags 3 cbb1: CardBus resister address 0x0 -> 0x68010000 intrpin B, intrtag 10 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=10 trigger=level ipl=bio cbb1: interrupting at irq 10 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68010000 02000000 10020200 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340020a 0x40: 00000000 00000001 00000000 00000000 0x80: 00041020 00000000 00000000 00000000 0x90: 00702800 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000106 00000000 00000000 ExCA regs: 84 00 00 10 00 00 00 00 cardbus1 at cbb1 bus 2 device 1 pccbbattach: found cardbus pcmcia1 at cbb1 slot 1 vga1 at pci0 dev 19 func 0: SiS model 0200 VGA-compatible display device isa0 at pcib0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support sc0 at isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at isa0 port 0x3f8-0x3ff irq 4sio0: configured irq 4 not in bitmap of probed irqs 0 intr_establish:irq=4 trigger=level ipl=bio sio0: type 8250 sio0: configured irq 3 not in bitmap of probed irqs 0 vga0 at isa0 npx0 at isa0 irq 13: INT 16 interface apm0 at isa0: found APM BIOS version 1.2 atkbdc0 at isa0 atkbd0 at isa0 irq 1 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 intr_establish:irq=6 trigger=edge ipl=bio : FIFO enabled, 8 bytes threshold fd0 at fdc0 drive 0: 1.44MB 3.5in wdc0 at isa0 irq 14 wd0 at wdc0 unit 0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S isapnp0: no ISA Plug 'n Play devices found changing root device to wd0s1a WARNING: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 13:47:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 5302514DFD for ; Sat, 3 Apr 1999 13:47:40 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10TYEW-00074g-00; Sat, 3 Apr 1999 16:45:40 -0500 To: UCHIYAMA Yasushi Cc: freebsd-mobile@freebsd.org From: "Gary Palmer" Subject: Re: 3com 575 In-reply-to: Your message of "Sun, 04 Apr 1999 02:28:59 +0900." <19990404022859A.uch@nop.or.jp> Date: Sat, 03 Apr 1999 16:45:40 -0500 Message-ID: <27197.923175940@noop.colo.erols.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org UCHIYAMA Yasushi wrote in message ID <19990404022859A.uch@nop.or.jp>: > Thank you for testing my patch. Thanks for working on this :) > Your machines' default PCI configuration register setting is not > correct.(but almost PCI-CardBus bridge are so.) Why am I not surprised. > Because PCI bus > enumeration is bogus, configuration cycle didn't come down to PCI bus > #1,2(cbb0,cbb1) so didn't find 3c575. (but found Intel chip on bus #0). > > cardbus0 at cbb0 bus 0 device 0 > cardbus1 at cbb1 bus 0 device 1 > should be > cardbus0 at cbb0 bus 1 device 0 > cardbus1 at cbb1 bus 2 device 1 > > Please change sys/i386/pci/pcibios.c to ftp://ftp.nop.or.jp/users/uch/PCMCIA/ > FreeBSD/pcibios.c > Then, Let me see its dmesg. Enclosed > And 3C575BTX support is not completed(This card needs CardBus specific change > in if_xl.c). > 3C575TX is more stable. It seems to work now ... thanks. Yours, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 128118784 (125116K bytes) Preloaded elf kernel "kernel.3.1" at 0xf025e000. mainbus0 (root) BIOS32 rev. 0 found at 0xffe90 PCI BIOS at 0xf0000-0x100000 entry point: 0xfbcde rev. 2.1 config mechanism: [1][x] special cycle: [x][x] last bus#:00 PCI only IRQ bitmap:................ bus: 0 device: 7 slot: 0 INTA# link=100.|.............. INTB# link=101|............... INTC# link=98......|......... INTD# link=99....|........... bus: 0 device: 2 slot: 0 INTA# link=96....|........... pcibios_get_intr_routing: interrupt routing map is broken. bus: 0 device: 3 slot: 0 INTA# link=99....|........... INTB# link=99....|........... bus: 0 device: 13 slot: 0 INTA# link=98||.||||.|||||... bus: 1 device: 1 slot: 0 INTA# link=98||.||||.|||||... INTB# link=97||.||||.|||||... pcibios_get_intr_routing: interrupt routing map is broken. bus: 1 device: 5 slot: 0 INTA# link=98||.||||.|||||... bus: 1 device: 7 slot: 0 INTA# link=98||.||||.|||||... bus: 1 device: 8 slot: 0 INTA# link=98||.||||.|||||... bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 bus: 0 device: 0 slot: 0 Bus Device Function Slot Pin Link IRQ Vendor Product ----------------------------------------------------- 0 7 0 0 - - - 8086 7110 0 7 1 0 - - - 8086 7111 0 7 2 0 D 3 11 8086 7112 0 7 3 0 - - - 8086 7113 0 3 0 0 A 3 11 104c ac15 0 3 1 0 B 3 11 104c ac15 PCI IRQ map:....|........... Link->IRQ:[ 0->N 1->N 2->N 3->11 ] # of bogus devices:0/3 ----------------------------------------------------- bridge0 primary=0 secondary=1 subordinate=1 bridge1 primary=0 secondary=2 subordinate=2 pcibios_fixup: Correct last bus # is 2. pci0 at mainbus0 Probing for devices on PCI bus 0: pchb0 at pci0 dev 0 func 0: Intel 82443BX host to PCI bridge (AGP disabled) vga1 at pci0 dev 2 func 0: NeoMagic NM2160 laptop SVGA controller cbb0 at pci0 dev 3 func 0 (TI1131), flags 3 cbb0: CardBus resister address 0x0 -> 0x68000000 intrpin A, intrtag 11 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=11 trigger=level ipl=bio cbb0: interrupting at irq 11 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68000000 02000000 10010100 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340010b 0x40: 00741028 00000001 00000000 00000000 0x80: 00243024 00000000 00000000 00000000 0x90: 0070aa00 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000820 00000000 00000000 ExCA regs: 84 0c 00 10 00 00 00 00 cardbus0 at cbb0 bus 1 device 0 cardbusattach: CardBus card found [0x2] cardbus_attach_card: cb0 start pccbb_power: CARDBUS_VCC_3V and CARDBUS_VPP_UC [1] cardbus_attach_card: Vendor 0x10b7, Product 0x5157, CIS 0x90 tuple: LINKTARGET len 5 0x 0: 13 3 43 49 53 tuple: MANFID len 6 0x 0: 20 4 1 1 57 51 tuple: CONFIG_CB len 8 0x 0: 4 6 3 1 0 0 0 0 tuple: CFTABLE_ENTRY_CB len 14 0x 0: 5 c 41 9a 1 b5 1e 1 55 2 30 ff ff 1 tuple: BAR len 8 0x 0: 7 6 11 0 40 0 0 0 tuple: VERS_1 len 54 0x 0: 15 34 5 0 33 43 6f 6d 20 43 6f 72 70 6f 72 61 0x10: 74 69 6f 6e 0 33 43 43 46 45 35 37 35 42 54 0 0x20: 4c 41 4e 20 43 61 72 64 62 75 73 20 43 61 72 64 0x30: 0 30 30 31 0 ff tuple: FUNCID len 4 0x 0: 21 2 6 1 tuple: CFTABLE_ENTRY_CB len 8 0x 0: 5 6 0 80 80 80 80 19 tuple: END len 1 xl0 at cardbus0 dev 0 function 0pccbb_io_open: 0x8300[0x2c] - 0x8380[0x30] pccbb_cardenable: command reg 0x2000007 pccbb_cardenable: command reg 0x2000007 3Com 3C575BTX (cyclone)xl0: Ethernet address: 00:10:4b:e2:fb:a1 pccbbattach: found cardbus pcmcia0 at cbb0 slot 0 cbb1 at pci0 dev 3 func 1 (TI1131), flags 3 cbb1: CardBus resister address 0x0 -> 0x68010000 intrpin B, intrtag 11 CardBus latency time 0x10 PCI latency time 0x20 ExCA regs: 0x803: 10 0x805: 00 0x81e: 00 intr_establish:irq=11 trigger=level ipl=bio cbb1: interrupting at irq 11 PCI config regs: 0x00: ac15104c 02000007 06070001 00822008 0x10: 68010000 02000000 10020200 fffff000 0x20: 00000000 fffff000 00000000 fffffffc 0x30: 00000000 fffffffc 00000000 0340020b 0x40: 00741028 00000001 00000000 00000000 0x80: 00241024 00000000 00000000 00000000 0x90: 0070aa00 00000000 00000000 00000000 0xa0: 00000000 00000000 00000000 00000000 socket regs: 00000000 00000006 30000106 00000000 00000000 ExCA regs: 84 00 00 10 00 00 00 00 cardbus1 at cbb1 bus 2 device 1 pccbbattach: found cardbus pcmcia1 at cbb1 slot 1 pcib0 at pci0 dev 7 func 0: Intel 82371AB PCI to ISA bridge trigger setting:(0e, 1e, 2e, 3e->4e->5e->6e->7e->8e, 9e->10e->11l->l, 12e->13e, 14e->15e->) vendor 0x8086 id 0x7111 at pci0 dev 7 func 1: not configured uhci0 at pci0 dev 7 func 2: Intel 82371AB/EB USB Host Controller intr_establish:irq=11 trigger=level ipl=bio usb0 at uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chipset0 at pci0 dev 7 func 3: Intel 82371AB Power management controller isa0 at pcib0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support sc0 at isa0 sc0: VGA color <16 virtual consoles, flags=0x0> vga0 at isa0 npx0 at isa0 irq 13: INT 16 interface apm0 at isa0: found APM BIOS version 1.2 atkbdc0 at isa0 atkbd0 at isa0 irq 1 psm0 at isa0 irq 12 intr_establish:irq=12 trigger=level ipl=bio : model Generic PS/2 mouse, device ID 0 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 intr_establish:irq=6 trigger=edge ipl=bio : FIFO enabled, 8 bytes threshold wdc0 at isa0 irq 14 wd0 at wdc0 unit 0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S isapnp0: no ISA Plug 'n Play devices found changing root device to wd0s2a - cardbus_intr_establish: irq 11 intr_establish:irq=11 trigger=level ipl=net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 14:33:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id B081914D85 for ; Sat, 3 Apr 1999 14:33:27 -0800 (PST) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id OAA09495; Sat, 3 Apr 1999 14:31:24 -0800 (PST) (envelope-from gfish@uniqsite.com) Date: Sat, 3 Apr 1999 14:31:24 -0800 (PST) From: Gold Fish To: Steve Price Cc: mobile@FreeBSD.ORG Subject: Re: 3Com 3C575 PCMCIA Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 2 Apr 1999, Steve Price wrote: > This card won't work at present. It is a CardBus (32-bit PCMCIA) > card and FreeBSD doesn't (yet) have a driver for it. > > -steve > What about PAO? Does PAO support this card? I've been following mobile list but gets more confused. For example, you said it's not support but another person (I think he is the PAO people) said a patch to 2.8 would fix it? I am on 3.1 now but I will downgrade it to 2.8 if necessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 15:51:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 4F3A514E56 for ; Sat, 3 Apr 1999 15:51:46 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id RAA05996; Sat, 3 Apr 1999 17:49:48 -0600 (CST) Date: Sat, 3 Apr 1999 17:49:48 -0600 (CST) From: Steve Price To: Gold Fish Cc: mobile@FreeBSD.ORG Subject: Re: 3Com 3C575 PCMCIA Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 3 Apr 1999, Gold Fish wrote: # > This card won't work at present. It is a CardBus (32-bit PCMCIA) # > card and FreeBSD doesn't (yet) have a driver for it. # > # > -steve # # What about PAO? Does PAO support this card? I hear it might. There are some patches floating around that some have reported to work with this card. What I was trying to save above is that no standard, unpatched version of FreeBSD has support for this card. And since you asked if this "card was supported", the answer is no with a twist. If you want to patch your kernel and help debug a work-in-progress, then by all means please do. Since you say that you've been following the mobile list for awhile you have undoubtly seen the patch. So if you feel up to it, grab the patch and try it out. If you don't want to do this, then the answer is still "FreeBSD doesn't (yet) have a driver for this card". :) # I've been following mobile list but gets more confused. For example, you # said it's not support but another person (I think he is the PAO people) # said a patch to 2.8 would fix it? # # I am on 3.1 now but I will downgrade it to 2.8 if necessary. Actually I think the patch floating around works on 3.1 too, so downgrading may not be necessary. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 3 19: 8:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 4D62C14D91 for ; Sat, 3 Apr 1999 19:08:15 -0800 (PST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id MAA03904; Sun, 4 Apr 1999 12:06:19 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-mobile@freebsd.org Cc: gfish@uniqsite.com Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: 3Com 3C575 PCMCIA Card From: Tomoaki NISHIYAMA In-Reply-To: References: X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990404120617U.tomoaki@moss.nibb.ac.jp> Date: Sun, 04 Apr 1999 12:06:17 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 15 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Gold Fish Subject: Re: 3Com 3C575 PCMCIA Card Date: Sat, 3 Apr 1999 14:31:24 -0800 (PST) Message-ID: gfish> What about PAO? Does PAO support this card? No, PAO does not support CardBus cards. Newconfig is working on the CardBus and you may have noticed the mails by Gary Palmer and UCHIYAMA Yasushi. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 4 4:43: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 24D8B14DA6 for ; Sun, 4 Apr 1999 04:42:59 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id UAA04459; Sun, 4 Apr 1999 20:41:01 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-mobile@FreeBSD.ORG Cc: listmail@helena.callcenter.systemhaus.net Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: pcmcia ethernet installation trouble From: Tomoaki NISHIYAMA In-Reply-To: <199904031558.RAA23491@helena.otelo-call.de> References: <199904031558.RAA23491@helena.otelo-call.de> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990404204100B.tomoaki@moss.nibb.ac.jp> Date: Sun, 04 Apr 1999 20:41:00 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 27 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Christoph Weber-Fahr Subject: Re: pcmcia ethernet installation trouble Date: Sat, 3 Apr 1999 17:58:46 +0200 (MET DST) Message-ID: <199904031558.RAA23491@helena.otelo-call.de> listmail> - I have not got a single response or comment to my first posting. listmail> Is there some Information missing, could I add further Information listmail> to shed light on this issue ? If you have another machine already running PAO, please post the result of "pccardc dumpcis". If it is not possible, please disable those devices that may conflict to the network card and pcic, at BIOS setup and kernel configuration (boot with -c). This mean disabling all the devices that is not related to the installation such as sio, lpt, sound card, and so on. Test for different io address and irq for the pccard, which you would be asked by the installer. listmail> > But ed0 doesn't appear in the list of available devices when choosing listmail> > installation media. By this do you mean that after selecting ftp, you find lpt and sio but not ed? Am I right in this point? -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 4 13:59:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id 2361F14E9F for ; Sun, 4 Apr 1999 13:59:53 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA019489476; Sun, 4 Apr 1999 16:57:56 -0400 Subject: X on Toshiba 500CDT To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Sun, 4 Apr 1999 16:57:55 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 768 Message-Id: <19990404205955.2361F14E9F@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to set my Toshiba 00CDT up as my wife's computer, now that I have an HP Omnibook 7100. I am usning 3.1-STABLE. I believe that the LCD display can do 1024x768. Does anyone have a working XF86Config file for this machine? I would _greatly_ appreciate a copy of a working one. Thanks. -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 4 16:33:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 5897614F11 for ; Sun, 4 Apr 1999 16:33:43 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id RAA08255 for ; Sun, 4 Apr 1999 17:36:33 -0600 (MDT) Message-Id: <199904042336.RAA08255@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: freebsd-mobile@FreeBSD.ORG (FreeBSD Mobile List) Subject: Toshiba Portege 7020CT experiences. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Apr 1999 17:36:32 -0600 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm collecting what I've learned about running FreeBSD on my Toshiba Portege 7020CT laptop. The site includes kernel config, XF86Config, etc. http://www.freebsd.org/~fsmp/fbsdportege/ (ps. thats not a real 7020CT in the picture, probably a 70??, but its close) -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 4 16:58:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 6A5771523D for ; Sun, 4 Apr 1999 16:58:40 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (638 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 4 Apr 1999 16:56:42 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sun, 4 Apr 1999 16:56:42 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Passe Cc: freebsd-mobile@FreeBSD.ORG (FreeBSD Mobile List) Subject: Sony Vaio 505TX References: <199904042336.RAA08255@Ilsa.StevesCafe.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm collecting what I've learned about running FreeBSD on my > Toshiba Portege 7020CT laptop. The site includes kernel config, > XF86Config, etc. > http://www.freebsd.org/~fsmp/fbsdportege/ i am doing the same for the sony vaio 505tx. http://psg.com/~randy/vaio/ randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 5 8:25:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from garfield.ee.ncku.edu.tw (garfield.ee.ncku.edu.tw [140.116.72.219]) by hub.freebsd.org (Postfix) with ESMTP id E044E14C91 for ; Mon, 5 Apr 1999 08:25:09 -0700 (PDT) (envelope-from tung@garfield.ee.ncku.edu.tw) Received: (from tung@localhost) by garfield.ee.ncku.edu.tw (8.9.2/8.9.2) id XAA54167 for freebsd-mobile@FreeBSD.ORG; Mon, 5 Apr 1999 23:23:27 +0800 (CST) (envelope-from tung) Date: Mon, 5 Apr 1999 23:23:27 +0800 From: Chung-Kie Tung To: freebsd-mobile@FreeBSD.ORG Subject: Thanks to all, my CirrusLogic 6729/6730 works! Message-ID: <19990405232327.A54149@garfield.ee.ncku.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi.... Thanks to everyone who ever helped me. My notebook with CirrusLogin 6729/6730 pcic finally works. I use PAO3-beta package and change the port of pcic0 to 0xfcfc, then everything is okay... Thanks to all! tung@garfield.ee.ncku.edu.tw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 5 8:56:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9108314BE7 for ; Mon, 5 Apr 1999 08:56:40 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id IAA25536; Mon, 5 Apr 1999 08:54:34 -0700 (PDT) Message-Id: <199904051554.IAA25536@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Sat, 03 Apr 1999 11:43:25 +0900." <199904030243.LAA06995@chandra.eatell.msr.prug.or.jp> X-Url: http://www.isi.edu/~faber Date: Mon, 05 Apr 1999 08:54:34 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- NAKAGAWA Yoshihisa wrote: >> Someone with a 6729 try applying this patch to pcic_p.[ch] (i.e., cd > >Probably same initialize code is working with O2 micro OZ6729/6730. > >> + io_port = PCIC_INDEX_0 + num6729 * CLPD6729_NUM_REGS; > >Cirrus chip has 4byte boundary. First chip is 0x3e0, second chip >is 0x3e4, ... Thanks. Corrected. > >Using hard code PCIC_INDEX_0 is dirty. > >This code is always re-setup ioports, if BIOS setup it, it should >be use. Because, BIOS is resource management for the machine. It's a dirty world. How can I tell the difference between an uninitialized chip and one that the BIOS has initialized? I would be happy to use the BIOS values if I could identify them. Also the 3.1 pcic code seems to always look for the card at PCIC_INDEX_0 (Nate, Nick, did I read that right?). I agree that it would be better to be more general, but I don't want to rewrite pcic.c. > >> + if (unit == 1) >> + num6729++; > >What's ? CL-PD6729 is not multi-function. That's actually supposed to look for a second card, but it's in the wrong place. Thanks for catching it. > >> printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", > >CL-PD6729 is not CardBus controller. :-) Can you tell I cut and pasted some of this code :-) Changed. Here's an updated patch. Has anyone other than Chung-Kie Tung tried this? He had some problems with it that I'm running down, and I'm interested to see if others have the same ones. *** pcic_p.c.orig Sun Dec 13 22:32:57 1998 - --- pcic_p.c Mon Apr 5 07:51:13 1999 *************** *** 48,53 **** - --- 48,54 ---- static void pcic_pci_attach(pcici_t, int); static void pd6832_legacy_init(pcici_t tag, int unit); + static void pd6729_init(pcici_t tag, int unit); static struct pci_device pcic_pci_driver = { "pcic", *************** *** 97,102 **** - --- 98,106 ---- case PCI_DEVICE_ID_PCIC_CLPD6832: pd6832_legacy_init(config_id, unit); break; + case PCI_DEVICE_ID_PCIC_CLPD6729: + pd6729_init(config_id, unit); + break; } if (bootverbose) { *************** *** 191,196 **** - --- 195,236 ---- if (bootverbose) printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", + io_port); + } + /* + * Set up the CL-PD6729 This routine is called once per PCMCIA socket. + */ + static void + pd6729_init(pcici_t tag, int unit) + { + u_short io_port; /* the io_port to map this slot on */ + static int num6729 = 0; /* The number of 6832s initialized */ + + if (unit == 1) + num6729++; + + /* + * Some BIOS leave the i/o address uninitialized. This + * insures that the PD6729 puts itself where the driver will + * look. We assume that multiple 6829's should be laid out + * sequentially. (the extra 2 is because each register is 2 + * bytes wide) + */ + io_port = PCIC_INDEX_0 + num6729 * CLPD6729_NUM_REGS *2; + + /* + * Configure the I/O window to contain CLPD6832_NUM_REGS + * words. + */ + pci_conf_write(tag, CLPD6729_BASE0, io_port | 1); + + /* + * Set default operating mode (I/O port space) + */ + pci_conf_write(tag, PCI_COMMAND_STATUS_REG, CLPD6729_COMMAND_DEFAULTS ); + + if (bootverbose) + printf("PC-card 16bit I/O address [0x%x]\n", io_port); } #endif /* NPCI > 0 */ *** pcic_p.h.orig Tue Jan 20 13:11:03 1998 - --- pcic_p.h Fri Apr 2 10:56:24 1999 *************** *** 52,54 **** - --- 52,62 ---- #define CLPD6832_NUM_REGS 2 /* End of CL-PD6832 defines */ + /* CL-PD6729 defines */ + #define CLPD6729_BASE0 0x0010 + + /* Configuration constants */ + #define CLPD6729_COMMAND_DEFAULTS 0x00000041 + #define CLPD6729_NUM_REGS 2 + + /* End of CL-PD6832 defines */ -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwjcuYb4eisfQ5rpAQGX/AP/WAzPDpT+K/7D5vPwN+lImNb76Mc11oeY OrQ9lJ4nQ6DWQz9Ogo99iGARD+H3fQxb+e8dj9x24yb37GECdY8FIHTYB+RL3ZFW VXUScrrTJHDtIWM+QDjzt/yM+uyXICbU0uWVFU5jt6vu7/vEP3HzYs5pGxyIKguW iDFmlUymHbQ= =ObxD -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 5 16:50:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id CB1D214FA4 for ; Mon, 5 Apr 1999 16:50:20 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id QAA15480 for ; Mon, 5 Apr 1999 16:48:21 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Mon, 5 Apr 1999 16:48:21 -0700 (PDT) From: Gold Fish To: mobile@freebsd.org Subject: 32-Bit card on a 16-Bit PCMCIA bus Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi: Still working on my 3Com 575 TX card. I noticed something last night: the Toshiba 460CDT Bios says it supports 16-Bit PCIC or 16-Bit Card BUS. If the card is a 32-Bit genuine Card BUS NIC, my assumption is that it will not run on Toshiba 460. Hope I am wrong. Feed back? Anyone? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 5 20:21:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 7116C14BF1 for ; Mon, 5 Apr 1999 20:21:36 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA00779; Tue, 6 Apr 1999 12:17:19 +0900 (JST) Message-Id: <199904060317.MAA00779@chandra.eatell.msr.prug.or.jp> To: Ted Faber Cc: Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Mon, 05 Apr 1999 08:54:34 MST." <199904051554.IAA25536@boreas.isi.edu> Date: Tue, 06 Apr 1999 12:17:19 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It's a dirty world. How can I tell the difference between an > uninitialized chip and one that the BIOS has initialized? > I would be happy to use the BIOS values if I could identify them. For example, Chandra has two PCIC. One is RF5C296 that true ISA PCIC, at 0x3e2. Another is TI PCI1130 that CardBus controller, at 0x3e4 for legacy mode. If multi PCIC exist and these are over two types, Ted's code not work correct. It should be use BIOS setup for PnP, if it can. > Also the 3.1 pcic code seems to always look for the card at > PCIC_INDEX_0 (Nate, Nick, did I read that right?). I agree that it > would be better to be more general, but I don't want to rewrite pcic.c. It should be modifiy ... like PAO. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 5 20:57:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from thyme.cisco.com (thyme.cisco.com [171.69.43.12]) by hub.freebsd.org (Postfix) with ESMTP id 516CF14D00 for ; Mon, 5 Apr 1999 20:57:12 -0700 (PDT) (envelope-from shibumi@cisco.com) Received: from miranda-bsd.cisco.com (dhcp-sjc5-107-233.cisco.com [171.71.107.233]) by thyme.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) with ESMTP id UAA03977 for ; Mon, 5 Apr 1999 20:55:14 -0700 (PDT) Received: from localhost by miranda-bsd.cisco.com (8.8.8) id UAA05832; Mon, 5 Apr 1999 20:55:11 -0700 (PDT) Message-Id: <199904060355.UAA05832@miranda-bsd.cisco.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-mobile@freebsd.org Subject: Re: IBM Thinkpad MWave modem In-reply-to: Your message of "Wed, 24 Feb 1999 15:57:22 PST." <3.0.32.19990224155651.009d9b60@blueneptune.com> Reply-To: shibumi@cisco.com X-Disclaimer: Unless otherwise noted below, this is not a policy statement Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Apr 1999 20:55:11 -0700 From: "Kenton A. Hoover" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No, its not possible at this point in time. On Wed, 24 Feb 1999 15:57:22 PST, Sendmail channeled Alan DuBoff saying: > Should have put this in my last message, but I also have an internal MWave > modem in my ThinkPad. Is it possible to use this modem with FreeBSD? > > I did receive some info to setup my Motorola Montana modem, although I > don't have it setup yet, so I'm not counting on using the MWave, since > nothing supports it except win and os/2, and with IBM's direction lately I > would expect to see Linux drivers before FreeBSD. | Kenton A. Hoover Network Team Manager | shibumi@cisco.com | | Engineering Computer Services | | | Cisco Systems, Inc. | +1.408.526.5249 | |===================== http://www.shockwave.org/~shibumi ====================| | Dr. Evil: Scott, I want you to meet Daddy's nemesis, Austin Powers. | | Scott Evil: What? Are you feeding him? Why don't you just kill him? | | Dr. Evil: I have an even better idea. I'm going to place him in an | | easily escapable situation involving an overly elaborate | | and exotic death. | | -- Austin Powers, International Man of Mystery (1997) | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 0:14:41 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hermes.axis.de (hermes.axis.de [194.163.241.7]) by hub.freebsd.org (Postfix) with SMTP id DECF31518A for ; Tue, 6 Apr 1999 00:14:29 -0700 (PDT) (envelope-from maret@axis.de) Received: from erlangen01.axis.de by hermes.axis.de via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 6 Apr 1999 07:12:42 UT Received: (private information removed) Message-ID: <91DA20EC3C3DD211833400A0245A4EA907A9C8@erlangen01.axis.de> From: maret@axis.de To: freebsd-mobile@freebsd.org Subject: PCMCIA-Slots? Date: Tue, 6 Apr 1999 09:12:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, sorry, this is a bit off-topic, but i hope you can help me or point me to some good URL: I want to buy a PCMCIA Network Card which is reported to work with at least PAO. Unfotunately I don't really know the differences between the different PCCARD-Slots and Hardware. Can ne1 explain me what the differences between Slot 1, Slot 2, Slot3 and Cardbus are? Are there any more other hardware versions? I have a Cirrus Logic PD6729/6730 Controller. I know from other postings here in the list that this one only works with PAO + Patch. Anyway - could I for example use a cardbus card with this controller? Thanks, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 0:42:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 9DC101556C for ; Tue, 6 Apr 1999 00:42:24 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id QAA01112; Tue, 6 Apr 1999 16:39:27 +0900 (JST) Message-Id: <199904060739.QAA01112@chandra.eatell.msr.prug.or.jp> To: maret@axis.de Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCMCIA-Slots? In-reply-to: Your message of "Tue, 06 Apr 1999 09:12:29 +0200." <91DA20EC3C3DD211833400A0245A4EA907A9C8@erlangen01.axis.de> Date: Tue, 06 Apr 1999 16:39:25 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a Cirrus Logic PD6729/6730 Controller. I know from other postings > here in the list that this one only works with PAO + Patch. Anyway - could > I for example use a cardbus card with this controller? No. CL-PD6729/6730 is 16bit PC-Card controller, not CardBus controller. So, CardBus card can't use. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 3:15:12 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id CC92714C25 for ; Tue, 6 Apr 1999 03:15:06 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id MAA26359 for ; Tue, 6 Apr 1999 12:13:08 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma026357; Tue, 6 Apr 99 12:13:02 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id MAA01075 for freebsd-mobile@freebsd.org; Tue, 6 Apr 1999 12:13:01 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904061013.MAA01075@helena.otelo-call.de> Subject: Re: pcmcia ethernet installation trouble In-Reply-To: <19990404204100B.tomoaki@moss.nibb.ac.jp> from Tomoaki NISHIYAMA at "Apr 4, 99 08:41:00 pm" To: tomoaki@biol.s.u-tokyo.ac.jp (Tomoaki NISHIYAMA) Date: Tue, 6 Apr 1999 12:12:07 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > If you have another machine already running PAO, please post > the result of "pccardc dumpcis". Unfortunately I don't have one. > If it is not possible, please disable those devices that may conflict > to the network card and pcic, at BIOS setup and kernel configuration > (boot with -c). This mean disabling all the devices that is not related > to the installation such as sio, lpt, sound card, and so on. Hm.... did this. No effect. Well, of course the dialog is now different - it says 'no network device available'. > Test for different io address and irq for the pccard, which > you would be asked by the installer. I did. No change. > By this do you mean that after selecting ftp, you find lpt and sio but not ed? > Am I right in this point? This is coorect. As long as they are activated, of course, see above. There is debug output on the second console screen. Anything to look for ? Regards Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10: 3:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id D993215214 for ; Tue, 6 Apr 1999 10:03:13 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA23812; Tue, 6 Apr 1999 10:01:04 -0700 (PDT) Message-Id: <199904061701.KAA23812@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Tue, 06 Apr 1999 12:17:19 +0900." <199904060317.MAA00779@chandra.eatell.msr.prug.or.jp> X-Url: http://www.isi.edu/~faber Date: Tue, 06 Apr 1999 10:01:04 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- NAKAGAWA Yoshihisa wrote: >> It's a dirty world. How can I tell the difference between an >> uninitialized chip and one that the BIOS has initialized? >> I would be happy to use the BIOS values if I could identify them. > >For example, Chandra has two PCIC. One is RF5C296 that true ISA >PCIC, at 0x3e2. Another is TI PCI1130 that CardBus controller, at >0x3e4 for legacy mode. I had never heard of that arrangement, but I'll look into making my code work for it. Thanks. > >If multi PCIC exist and these are over two types, Ted's code not >work correct. It should be use BIOS setup for PnP, if it can. I agree in principle, but let me think about how to implement that. Suggestions are welcome, of course. > >> Also the 3.1 pcic code seems to always look for the card at >> PCIC_INDEX_0 (Nate, Nick, did I read that right?). I agree that it >> would be better to be more general, but I don't want to rewrite pcic.c. > >It should be modifiy ... like PAO. I feel uncomfortable about modifying that code without some indication from Nate, or our new chieftan Scott, that such a modification would be accepted. I really don't want to waste time on code that will never see the tree. I do think that setting up the pcic code to take a port at kernel config time is a reasonable thing to do. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwo9z4b4eisfQ5rpAQEjsQQAmbaKgbq1YYwoYkd1+PyOh7zb8MNfPP/P q0Dg9h6piuJWr8d46ALbS532lFgHfRsDJ9Jxknz6hp6DihwGBXHA2ug16u2AxJ8o R9/6P4qjxIAKW5edKk5Eue6lsz+UxxihiZX0dVe7778O6DeLy8+yW9kXHnXkL7mP NOkmEV7bzUk= =si9p -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10: 5:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id B5D7715097 for ; Tue, 6 Apr 1999 10:05:17 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA23905; Tue, 6 Apr 1999 10:03:14 -0700 (PDT) Message-Id: <199904061703.KAA23905@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: maret@axis.de Cc: freebsd-mobile@freebsd.org Subject: Re: PCMCIA-Slots? In-Reply-To: Your message of "Tue, 06 Apr 1999 09:12:29 +0200." <91DA20EC3C3DD211833400A0245A4EA907A9C8@erlangen01.axis.de> X-Url: http://www.isi.edu/~faber Date: Tue, 06 Apr 1999 10:03:13 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- maret@axis.de wrote: >I have a Cirrus Logic PD6729/6730 Controller. I know from other postings >here in the list that this one only works with PAO + Patch. Anyway - could >I for example use a cardbus card with this controller? Hey, want to try the patch to 3.1 that I posted yesterday, and tell me what happens? (I.e., send me a full dmesg and maybe a verbose one if it fails?) I'd appreciate it if you can. Thanks. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwo+UYb4eisfQ5rpAQEeFwP8CHicD6eQDpE8bHmbuyLXcuViHTQLq+1X p7J+td+NrAP/oZ2gMGA6/4nkFYs1Rx30aUASUvgHabkAaG5kSfkL9Nfv+BSo0LIi i1W8HWPhVmk8HnTjs+6ZWrq801hPv+10boOhSPiTm597ETI/9bsn/1xHnkDlFleQ UjCBFmKH4/8= =BbwV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10: 5:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 210E515097 for ; Tue, 6 Apr 1999 10:05:45 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA23131; Tue, 6 Apr 1999 11:03:37 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA16410; Tue, 6 Apr 1999 11:03:36 -0600 Date: Tue, 6 Apr 1999 11:03:36 -0600 Message-Id: <199904061703.LAA16410@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: NAKAGAWA Yoshihisa , Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904061701.KAA23812@boreas.isi.edu> References: <199904060317.MAA00779@chandra.eatell.msr.prug.or.jp> <199904061701.KAA23812@boreas.isi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> Also the 3.1 pcic code seems to always look for the card at > >> PCIC_INDEX_0 (Nate, Nick, did I read that right?). I agree that it > >> would be better to be more general, but I don't want to rewrite pcic.c. > > > >It should be modifiy ... like PAO. > > I do think that setting up the pcic code to take a port at kernel > config time is a reasonable thing to do. You wouldn't get any argument from anyone, but how to do it? Making the PCIC an ISA device is unacceptable, and using an 'option' doesn't allow the user to set it without recompiling the kernel. Possibly a boot time option, but I don't like those much either since it can't be done in 'userconfig'. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:11:41 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 818941562C for ; Tue, 6 Apr 1999 10:11:35 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA24369; Tue, 6 Apr 1999 10:09:30 -0700 (PDT) Message-Id: <199904061709.KAA24369@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Tue, 06 Apr 1999 11:03:36 MDT." <199904061703.LAA16410@mt.sri.com> X-Url: http://www.isi.edu/~faber Date: Tue, 06 Apr 1999 10:09:30 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Nate Williams wrote: >> I do think that setting up the pcic code to take a port at kernel >> config time is a reasonable thing to do. > >You wouldn't get any argument from anyone, but how to do it? Making the >PCIC an ISA device is unacceptable, That was my first thought. Why is it unacceptable? (I just don't know, and it may help me come up with a better idea.) > and using an 'option' doesn't allow >the user to set it without recompiling the kernel. Well, yeah, but you can't reset an ISA device's port without doing that either, so at least it's no worse than an ISA device. But I know you don't want to add any options to the code, so that's that. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwo/yYb4eisfQ5rpAQFAKwP/aFH3IFWh/Lmpc76nc+P8N//UZVeYBybo FnCIcFT10KX8I4/8oREjuoKI3mAWafqbXi/lNBl+AZpynYDOKDzYxYz+HXZbCmfm OmGZxnlGduJW+AvQc8ahX+OrBKu9iXjovL0mmFXG5rR3xG7U18ptNw1piayI3T8V qExYnjp0oAk= =U+kA -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:13:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id E19EF15677 for ; Tue, 6 Apr 1999 10:13:36 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA23215; Tue, 6 Apr 1999 11:11:30 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA16507; Tue, 6 Apr 1999 11:11:29 -0600 Date: Tue, 6 Apr 1999 11:11:29 -0600 Message-Id: <199904061711.LAA16507@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: Nate Williams , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904061709.KAA24369@boreas.isi.edu> References: <199904061703.LAA16410@mt.sri.com> <199904061709.KAA24369@boreas.isi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> I do think that setting up the pcic code to take a port at kernel > >> config time is a reasonable thing to do. > > > >You wouldn't get any argument from anyone, but how to do it? Making the > >PCIC an ISA device is unacceptable, > > That was my first thought. Why is it unacceptable? (I just don't > know, and it may help me come up with a better idea.) Because as you can tell, the PCIC code is *NOT* ISA specific. It's ISA-like, but not ISA specific. The code has no ISA code in it, except to deal with ISA devices (if it does, it should be removed). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:24:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from shrimp.baynetworks.com (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (Postfix) with ESMTP id 7197614F88 for ; Tue, 6 Apr 1999 10:24:30 -0700 (PDT) (envelope-from bwithrow@engeast.BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by shrimp.baynetworks.com (8.9.1/8.9.1) with ESMTP id NAA09359; Tue, 6 Apr 1999 13:20:09 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id NAA15212; Tue, 6 Apr 1999 13:19:36 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.68.38]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id NAA10064; Tue, 6 Apr 1999 13:21:59 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.8/8.8.8) with ESMTP id NAA08063; Tue, 6 Apr 1999 13:21:40 -0400 (EDT) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199904061721.NAA08063@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ted Faber Cc: NAKAGAWA Yoshihisa , Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Message from Ted Faber of "Tue, 06 Apr 1999 10:01:04 PDT." <199904061701.KAA23812@boreas.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 13:21:40 -0400 From: Robert Withrow Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org faber@ISI.EDU said: :- I had never heard of that arrangement, but I'll look into making my :- code work for it. Thanks. Another arrangement exists on my SOLO 9100, which has two Cirrus 6730 cardbus controllers on the laptop (which FreeBSD runs in pc-card mode) and 1 Cirrus 6729 in the docking station. The probe needs to support essentially arbitrary collections of pc-card and cardbus controllers... -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:27:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 8535F15214 for ; Tue, 6 Apr 1999 10:27:27 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA25490; Tue, 6 Apr 1999 10:25:23 -0700 (PDT) Message-Id: <199904061725.KAA25490@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Tue, 06 Apr 1999 11:11:29 MDT." <199904061711.LAA16507@mt.sri.com> X-Url: http://www.isi.edu/~faber Date: Tue, 06 Apr 1999 10:25:22 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Nate Williams wrote: >> That was my first thought. Why is it unacceptable? (I just don't >> know, and it may help me come up with a better idea.) > >Because as you can tell, the PCIC code is *NOT* ISA specific. It's >ISA-like, but not ISA specific. The code has no ISA code in it, except >to deal with ISA devices (if it does, it should be removed). Point made. I see a sysctl variable (I think) in the probe routine used to allow the suer to select the management irq. How about adding one or more to select the IO ports for the controller? - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwpDgYb4eisfQ5rpAQECegQAhCR0yflIA6400/fkOvlie8eTchgl097A IkUSPk3CUb8xYmbsONGnSH1W+dVKDgIYmJ9cPkLnnDEoZzW8Mcxp19Ue9XX0UcPP mC9F7/xpuw9eapDfKK6hHpOTadydGN2n1cHgvLZnJ2QDeUfVPj/HBynwALOOIvQK 4qxaFyfZkaQ= =BQdS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:34:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C795815214 for ; Tue, 6 Apr 1999 10:34:42 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA23401; Tue, 6 Apr 1999 11:32:32 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA16641; Tue, 6 Apr 1999 11:32:31 -0600 Date: Tue, 6 Apr 1999 11:32:31 -0600 Message-Id: <199904061732.LAA16641@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: Nate Williams , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904061725.KAA25490@boreas.isi.edu> References: <199904061711.LAA16507@mt.sri.com> <199904061725.KAA25490@boreas.isi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> That was my first thought. Why is it unacceptable? (I just don't > >> know, and it may help me come up with a better idea.) > > > >Because as you can tell, the PCIC code is *NOT* ISA specific. It's > >ISA-like, but not ISA specific. The code has no ISA code in it, except > >to deal with ISA devices (if it does, it should be removed). > > Point made. > > I see a sysctl variable (I think) in the probe routine used to allow > the suer to select the management irq. How about adding one or more > to select the IO ports for the controller? This was my idea about a 'boot' config line. The problems with this solution is: 1) It assumes there is one PCIC controller. (The existing code has the same problem) 2) It not 'boot-time' configurable. It requires you to edit a file and then reboot the box before the change can take place. However, it is a better solution than a kernel option, but I don't know how to make it 'create' sysctl variables on the fly based on how many PCIC controllers are seen. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:48:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 044F314E3E for ; Tue, 6 Apr 1999 10:48:21 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA11686; Wed, 7 Apr 1999 02:46:07 +0900 (JST) Message-ID: <370A4782.B3C61AB7@newsguy.com> Date: Wed, 07 Apr 1999 02:42:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Nate Williams Cc: Ted Faber , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? References: <199904061711.LAA16507@mt.sri.com> <199904061725.KAA25490@boreas.isi.edu> <199904061732.LAA16641@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > > I see a sysctl variable (I think) in the probe routine used to allow > > the suer to select the management irq. How about adding one or more > > to select the IO ports for the controller? Is this the same variable mentioned in loader(8)? > This was my idea about a 'boot' config line. The problems with this > solution is: > > 1) It assumes there is one PCIC controller. (The existing code has the > same problem) > 2) It not 'boot-time' configurable. It requires you to edit a file and > then reboot the box before the change can take place. Sure it is configurable at boot time. Stop the loader, set the variable, proceed. Something like the visual userconfig can be written, at the time it becomes an issue. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 10:53:43 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 6B41A14BF5 for ; Tue, 6 Apr 1999 10:53:41 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA27663; Tue, 6 Apr 1999 10:51:37 -0700 (PDT) Message-Id: <199904061751.KAA27663@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Tue, 06 Apr 1999 11:32:31 MDT." <199904061732.LAA16641@mt.sri.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 10:51:37 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: >This was my idea about a 'boot' config line. The problems with this >solution is: > >1) It assumes there is one PCIC controller. (The existing code has the > same problem) >2) It not 'boot-time' configurable. It requires you to edit a file and > then reboot the box before the change can take place. There's a kld version of the pcic code, right? Can we use that to our advantage? I.e. boot set sysctl variables load the kld We could then set up 2 variables, current unit number and current io port. The on load the kld reads the variables, sets its unit number and io port appropraitely and starts up. The sequence for multiple pcics then looks like boot set sysctls for 1st controller load 1st controller set sysctls for 2nd controller load 2nd controller etc. I think that allows each driver to continue to think that there's one pcic. I haven't checked the code to be sure that it would work, though. For one thing, I'm not sure how it allocates irqs, and certainly don't want it stepping on itself. I'm not sure how the PCI code interfaces with the kld stuff, but I doubt that it (currently) reprobes the PCI bus when a kld is loaded. We may be able to get around this by leaving one version oc the pcic driver in the kernel, but it's probably neater to create a device that only initializes the PCI pcics, leaving them in an appropriate configuration for the dynamically loaded pcic klds to find them. Of course, that idea may be hacky enough that its better to just bite the bullet, and try to get the pcic code to be aware of multiple pcics directly. ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 12: 0: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 31F2914F27 for ; Tue, 6 Apr 1999 11:59:59 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA24094; Tue, 6 Apr 1999 12:57:54 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA17068; Tue, 6 Apr 1999 12:57:53 -0600 Date: Tue, 6 Apr 1999 12:57:53 -0600 Message-Id: <199904061857.MAA17068@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Daniel C. Sobral" Cc: Nate Williams , Ted Faber , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <370A4782.B3C61AB7@newsguy.com> References: <199904061711.LAA16507@mt.sri.com> <199904061725.KAA25490@boreas.isi.edu> <199904061732.LAA16641@mt.sri.com> <370A4782.B3C61AB7@newsguy.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I see a sysctl variable (I think) in the probe routine used to allow > > > the suer to select the management irq. How about adding one or more > > > to select the IO ports for the controller? > > Is this the same variable mentioned in loader(8)? ???? > > This was my idea about a 'boot' config line. The problems with this > > solution is: > > > > 1) It assumes there is one PCIC controller. (The existing code has the > > same problem) > > 2) It not 'boot-time' configurable. It requires you to edit a file and > > then reboot the box before the change can take place. > > Sure it is configurable at boot time. Stop the loader, set the > variable, proceed. > > Something like the visual userconfig can be written, at the time it > becomes an issue. I don't think it's justifiable to have a 2-stage configuration. Either we use userconfig as it's written now, or we use the boot configuration stuff. Mixing/matching things only serves to confuse users. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 12: 7:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 5177114E7F for ; Tue, 6 Apr 1999 12:07:31 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA24163; Tue, 6 Apr 1999 13:05:28 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA17132; Tue, 6 Apr 1999 13:05:28 -0600 Date: Tue, 6 Apr 1999 13:05:28 -0600 Message-Id: <199904061905.NAA17132@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: Nate Williams , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904061751.KAA27663@boreas.isi.edu> References: <199904061732.LAA16641@mt.sri.com> <199904061751.KAA27663@boreas.isi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Nate Williams wrote: > >This was my idea about a 'boot' config line. The problems with this > >solution is: > > > >1) It assumes there is one PCIC controller. (The existing code has the > > same problem) > >2) It not 'boot-time' configurable. It requires you to edit a file and > > then reboot the box before the change can take place. > > There's a kld version of the pcic code, right? Yes, but it doesn't work correctly because of missing functionality in the KLD implementation. However, your ideas are sound, and a step in the right direction. > We could then set up 2 variables, current unit number and current io > port. The on load the kld reads the variables, sets its unit number > and io port appropraitely and starts up. The sequence for multiple > pcics then looks like > > boot > set sysctls for 1st controller > load 1st controller > set sysctls for 2nd controller > load 2nd controller How do you know how many controllers exist so you can load them? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 13: 1:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 34E6B15701 for ; Tue, 6 Apr 1999 13:01:20 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA18794; Wed, 7 Apr 1999 04:59:10 +0900 (JST) Message-ID: <370A62BD.B19F89DB@newsguy.com> Date: Wed, 07 Apr 1999 04:38:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Nate Williams Cc: Ted Faber , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? References: <199904061711.LAA16507@mt.sri.com> <199904061725.KAA25490@boreas.isi.edu> <199904061732.LAA16641@mt.sri.com> <370A4782.B3C61AB7@newsguy.com> <199904061857.MAA17068@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > I don't think it's justifiable to have a 2-stage configuration. Either > we use userconfig as it's written now, or we use the boot configuration > stuff. Mixing/matching things only serves to confuse users. That much is true. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 13: 1:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6B13515702 for ; Tue, 6 Apr 1999 13:01:24 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA18804; Wed, 7 Apr 1999 04:59:15 +0900 (JST) Message-ID: <370A642C.85C5484E@newsguy.com> Date: Wed, 07 Apr 1999 04:44:44 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ted Faber Cc: Nate Williams , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? References: <199904061751.KAA27663@boreas.isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Faber wrote: > > There's a kld version of the pcic code, right? Can we use that to our It seems it doesn't work though. Even though there were reports of it been succesfully used. > > > boot > set sysctl variables > load the kld > > We could then set up 2 variables, current unit number and current io > port. The on load the kld reads the variables, sets its unit number > and io port appropraitely and starts up. The sequence for multiple > pcics then looks like > > boot > set sysctls for 1st controller > load 1st controller > set sysctls for 2nd controller > load 2nd controller > > etc. Looks terrible to me. :-) I rather have it done through loader: loader kernel load pcic irq=NN io=NNNN ... load pcic irq=NN io=NNNN ... But, then again, I work with loader, so I'm biased... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 13: 6:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 88236156FA for ; Tue, 6 Apr 1999 13:06:55 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA24846; Tue, 6 Apr 1999 14:04:50 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA17396; Tue, 6 Apr 1999 14:04:49 -0600 Date: Tue, 6 Apr 1999 14:04:49 -0600 Message-Id: <199904062004.OAA17396@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Daniel C. Sobral" Cc: Ted Faber , Nate Williams , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <370A642C.85C5484E@newsguy.com> References: <199904061751.KAA27663@boreas.isi.edu> <370A642C.85C5484E@newsguy.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > There's a kld version of the pcic code, right? Can we use that to our > > It seems it doesn't work though. Even though there were reports of > it been succesfully used. If you stand on your head while chanting 'KLD rules' 10 times, all the while sprinkling fairy dust on a toad it'll work right. :) :) :) :) Nate ps. I forgot one minor detail. It must be a Tuesday when you do this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 19:23:10 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id E6AB9154D4 for ; Tue, 6 Apr 1999 19:23:06 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA145921666; Tue, 6 Apr 1999 22:21:06 -0400 Subject: XF86Config help with Toshiba 500CDT To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Tue, 6 Apr 1999 22:21:06 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 934 Message-Id: <19990407022306.E6AB9154D4@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could someoen plase give me some guidence on how to write XF86Config files for internal LCD displays? Aparaently no one has a working config for a Toshiba 500CDT, or at least my searches have all come up empty. I have X working on it using the XF86SVGA server, and an external monitor, but no luck with the internal LCD yeat, and thats what I really need to work. I have nevr gotten one of these to work, so any help or pointers to docs would be appreciated. -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 23: 5:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.178.182]) by hub.freebsd.org (Postfix) with ESMTP id E426415256 for ; Tue, 6 Apr 1999 23:05:17 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id NAA02710; Wed, 7 Apr 1999 13:24:46 +0800 (CST) (envelope-from robinson) Date: Wed, 7 Apr 1999 13:24:46 +0800 (CST) From: Michael Robinson Message-Id: <199904070524.NAA02710@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG, stanb@awod.com Subject: Re: XF86Config help with Toshiba 500CDT In-Reply-To: <19990407022306.E6AB9154D4@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Stan Brown" writes: > Could someoen plase give me some guidence on how to write XF86Config > files for internal LCD displays? Find something from the Internet close to what you've got, and then play with the modelines until you get something that works. > Aparaently no one has a working config for a Toshiba 500CDT, or at > least my searches have all come up empty. This is from my 510CDT. If it doesn't work, play with the the modelines until it does. -Michael Robinson # XF86Config auto-generated by XF86Setup # # Copyright (c) 1996 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # See 'man XF86Config' for info on the format of this file Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/URW" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/100dpi" EndSection Section "ServerFlags" EndSection Section "Keyboard" Protocol "Standard" XkbRules "xfree86" XkbModel "everex" XkbLayout "us" XkbOptions "ctrl:nocaps" EndSection Section "Pointer" Protocol "SysMouse" Device "/dev/sysmouse" # Protocol "PS/2" # Device "/dev/psm0" # Protocol "Microsoft" # Device "/dev/cuaa0" Emulate3Timeout 50 Emulate3Buttons EndSection Section "Monitor" Identifier "Primary Monitor" VendorName "Unknown" ModelName "Unknown" HorizSync 31.5-53.7 VertRefresh 60-85 # Modeline "1024x768" 65.00 1024 1032 1176 1344 768 771 777 806 -hsync -vsync # Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync # Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 #ModeLine "800x600" 50.5 800 856 976 1040 600 637 643 666 Modeline "800x600" 40.30 800 840 968 1056 600 601 605 628 # Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync # Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync # Modeline "512x384" 20.16 512 528 592 640 384 385 388 404 -hsync -vsync # Modeline "480x300" 29.95 480 504 584 624 300 319 322 333 doublescan # Modeline "400x300" 25.00 400 424 488 520 300 319 322 333 doublescan # Modeline "320x240" 15.75 320 336 384 400 240 244 246 262 doublescan # Modeline "320x200" 12.59 320 336 384 400 200 204 205 225 doublescan EndSection Section "Device" Identifier "Primary Card" VendorName "Unknown" BoardName "Chips & Technologies CT65550" # Option "noaccel" # Option "no_bitblt" # Option "xaa_no_color_exp" # Option "xaa_benchmark" # Option "sw_cursor" # Option "sync_on_green" # Option "fast_dram" # Option "use_vclk1" # Textclockfreq 25.175 # Option "nolinear" # MemBase 0x03b00000 # Device section for C&T cards. # Option "suspend_hack" # Option "STN" # Option "no_stretch" # Option "no_center" # Option "use_modeline" # Option "fix_panel_size" # videoram 512 EndSection Section "Screen" Driver "Accel" Device "Primary Card" Monitor "Primary Monitor" SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection EndSection Section "Screen" Driver "Mono" Device "Primary Card" Monitor "Primary Monitor" SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection EndSection Section "Screen" Driver "VGA2" Device "Primary Card" Monitor "Primary Monitor" SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection EndSection Section "Screen" Driver "VGA16" Device "Primary Card" Monitor "Primary Monitor" SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection EndSection Section "Screen" Driver "SVGA" Device "Primary Card" Monitor "Primary Monitor" DefaultColorDepth 16 SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 16 # Virtual 1024 768 ViewPort 0 0 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection SubSection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200" EndSubSection EndSection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 6 23: 8:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hermes.axis.de (hermes.axis.de [194.163.241.7]) by hub.freebsd.org (Postfix) with SMTP id 548BA15256 for ; Tue, 6 Apr 1999 23:08:11 -0700 (PDT) (envelope-from maret@axis.de) Received: from erlangen01.axis.de by hermes.axis.de via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 7 Apr 1999 06:06:14 UT Received: (private information removed) Message-ID: <91DA20EC3C3DD211833400A0245A4EA907A9D0@erlangen01.axis.de> From: maret@axis.de To: freebsd-mobile@freebsd.org Subject: PAO questions Date: Wed, 7 Apr 1999 08:06:11 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, is there a mailing list for PAO? What happens if I do a cvsup on 3.1 Stable? I think I have to do a 'make all' again in my /usr/src/PAO3 directory. But will PAO then still work or is it just supposed to work with the 3.1 Release version? Bye, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 7 0:23:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id B5C2414C1C for ; Wed, 7 Apr 1999 00:23:37 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id JAA07317; Wed, 7 Apr 1999 09:21:37 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id JAA30484; Wed, 7 Apr 1999 09:21:36 +0200 (CEST) Date: Wed, 7 Apr 1999 09:21:36 +0200 From: Frank Louwers To: maret@axis.de Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO questions Message-ID: <19990407092136.B30263@zeus.rug.ac.be> References: <91DA20EC3C3DD211833400A0245A4EA907A9D0@erlangen01.axis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <91DA20EC3C3DD211833400A0245A4EA907A9D0@erlangen01.axis.de>; from maret@axis.de on Wed, Apr 07, 1999 at 08:06:11AM +0200 X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 07, 1999 at 08:06:11AM +0200, maret@axis.de wrote: > Hi, > > is there a mailing list for PAO? Correction: your question should have been: is there a ENGLISH mailing list for PAO? I know there is a japanese one ... Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 7 8:56:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 50800157E7 for ; Wed, 7 Apr 1999 08:56:22 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id IAA18684; Wed, 7 Apr 1999 08:54:18 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Wed, 7 Apr 1999 08:54:18 -0700 (PDT) From: Golden Fischer To: Michael Robinson Cc: freebsd-mobile@FreeBSD.ORG, stanb@awod.com Subject: Re: XF86Config help with Toshiba 500CDT In-Reply-To: <199904070524.NAA02710@netrinsics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My 460 has the same chipset. So the following should work for you. # $XFree86: xc/programs/Xserver/hw/xfree86/XF86Conf.cpp,v 3.29 1996/12/23 06:30:30 dawes Exp $ # # Copyright (c) 1994 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # $XConsortium: XF86Conf.cpp /main/22 1996/10/23 11:43:51 kaleb $ # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. This man page is installed as /usr/X11R6/man/man5/XF86Config.5x # ********************************************************************** # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # For OSs that support Dynamically loaded modules, ModulePath can be # used to set a search path for the modules. This is currently supported # for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown # here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Module section -- this is an optional section which is used to specify # which dynamically loadable modules to load. Dynamically loadable # modules are currently supported only for Linux ELF, FreeBSD 2.x # and NetBSD 1.x. Currently, dynamically loadable modules are used # only for some extended input (XInput) device drivers. # ********************************************************************** # # Section "Module" # # This loads the module for the Joystick driver # # Load "xf86Jstk.so" # # EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # DontZoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. # AllowNonLocalXvidtune # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # DisableModInDev # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # AllowNonLocalModInDev EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Keyboard section # ********************************************************************** Section "Keyboard" Protocol "Standard" # when using XQUEUE, comment out the above line, and uncomment the # following line # Protocol "Xqueue" AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be required # when using pre-R6 clients # ServerNumLock # Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)) # Xleds 1 2 3 # To set the LeftAlt to Meta, RightAlt key to ModeShift, # RightCtl key to Compose, and ScrollLock key to ModeLock: # LeftAlt Meta # RightAlt ModeShift # RightCtl Compose # ScrollLock ModeLock # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel "pc102" # If you have a Microsoft Natural keyboard, you can use: # XkbModel "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout "de" # or: # XkbLayout "de" # XkbVariant "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions "ctrl:swapcaps" # These are the default XKB settings for XFree86 # XkbRules "xfree86" # XkbModel "pc101" # XkbLayout "us" # XkbVariant "" # XkbOptions "" EndSection # XF86Config (excerpt) Section "Pointer" Protocol "PS/2" Device "/dev/mouse" Emulate3Timeout 50 Emulate3Buttons EndSection Section "Monitor" Identifier "Laptop Screen" VendorName "Toshiba" ModelName "DD-STN" HorizSync 31.5-48.5 VertRefresh 40-75 # VESA 800x600@60Hz Non-Interlaced mode Horizontal Sync = 37.9kHz Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync # VESA 640x480@72Hz Non-Interlaced mode Horizontal Sync = 37.9kHz Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 EndSection Section "Device" Identifier "Chips & Technologies CT65550" VendorName "Chips & Technologies" BoardName "CT65550" EndSection Section "Screen" Driver "SVGA" Device "Chips & Technologies CT65550" Monitor "Laptop Screen" BlankTime 2 SuspendTime 5 OffTime 10 DefaultColorDepth 16 SubSection "Display" Depth 8 Modes "800x600" ViewPort 0 0 EndSubSection SubSection "Display" Depth 16 Modes "800x600" ViewPort 0 0 EndSubSection SubSection "Display" Depth 24 Modes "800x600" ViewPort 0 0 EndSubSection SubSection "Display" Depth 32 Modes "800x600" ViewPort 0 0 EndSubSection EndSection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 1:47:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 0102E158A5 for ; Thu, 8 Apr 1999 01:47:39 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id RAA02125; Thu, 8 Apr 1999 17:43:36 +0900 (JST) Message-Id: <199904080843.RAA02125@chandra.eatell.msr.prug.or.jp> To: Nate Williams Cc: Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Tue, 06 Apr 1999 11:32:31 CST." <199904061732.LAA16641@mt.sri.com> Date: Thu, 08 Apr 1999 17:43:35 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This was my idea about a 'boot' config line. The problems with this > solution is: > > 1) It assumes there is one PCIC controller. (The existing code has the > same problem) > 2) It not 'boot-time' configurable. It requires you to edit a file and > then reboot the box before the change can take place. PAO people thinking PCIC problem below: #Thanks nomads-ML people translate this message. - PCIC is an ISA device. PCIC handles bus, yet the bus is not the bus PCIC belongs to. Please note that a PCIC is an ISA device and a bridge between ISA bus and PC Card bus. Also, if you see codes on NetBSD, bus dependent code and handling bridge is different. - sysctl is the last way to go. It can't work unless the module is loaded after boot. There are also other problems loading the driver with current KLD. - User configuration method dependent on KLD or boot loader is wrong solution. It should be independent from them. - It is clearly wrong to specify the management irq by sysctl. - It is clear that you should consider multiple PCICs. Machines with more than one PCIC are not singular. Any code that does not take the fact into account is apparently wrong. - It is a bad way to handle resources by hard coding. A way for the user to change the resources is must. UserConfig is the available solution, now. - The method used by PAO is the right way to go, although native probe/attach codes for PCI PCIC and CardBus controllers is yet to be written. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 3:24:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id 0AE2D1533D for ; Thu, 8 Apr 1999 03:24:25 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA121786944; Thu, 8 Apr 1999 06:22:24 -0400 Subject: Toshiba 5000CDT LCD screen resolution? To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Thu, 8 Apr 1999 06:22:23 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1051 Message-Id: <19990408102426.0AE2D1533D@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to get 3.-2-STABLE working on a Toshiba 500CDT. Two people have both sent me XF86Config files, and I greatly appreciate there help on this. I would like to confirm one thing that both of these people seem to thinks is correct. Is the max resolutin of the 500CDT's internbal LCD display really 800x600? This seems strange as it's not a "standard" resolutinon, that I am aware of. Thanks for any info on this, the Toshiba docs that I have are very confusioing, they even imply that it will do 1280x1024, at least in interlaced. This does not seem correct either. -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 5:59:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B6D251516B for ; Thu, 8 Apr 1999 05:59:48 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA11089; Thu, 8 Apr 1999 21:57:31 +0900 (JST) Message-ID: <370C9C63.B5506516@newsguy.com> Date: Thu, 08 Apr 1999 21:09:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? References: <199904080843.RAA02125@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > > - PCIC is an ISA device. PCIC handles bus, yet the bus is not the > bus PCIC belongs to. Please note that a PCIC is an ISA device and > a bridge between ISA bus and PC Card bus. Also, if you see codes > on NetBSD, bus dependent code and handling bridge is different. I just wish this PCIC is ISA/PCIC is not ISA would get settled... Can anyone on the not ISA camp *PROVE* it is not an ISA device? If it is not an ISA device, it ought to be possible to show a case A where an ISA device behaves in such an such way and PCIC does not. > - sysctl is the last way to go. It can't work unless the module is > loaded after boot. There are also other problems loading the > driver with current KLD. That is incorrect. It can be set through loader at load time. This is not hypothetical, it is the present state for PCIC. > - User configuration method dependent on KLD or boot loader is > wrong solution. It should be independent from them. Why? By the same token, I suggest that configuration method should be independent of anything you suggest. You did not justify your position, so I don't need to justify mine. So I suggest you justify your positions whenever you out-rule a possible solution. > - It is clearly wrong to specify the management irq by sysctl. Err... a lot of people don't see this way, so it might be wrong, but it sure is not clear. Justify. > - It is a bad way to handle resources by hard coding. A way for > the user to change the resources is must. UserConfig is the > available solution, now. Ideally, userconfig should go away. It relies on the kernel being running already, which is a bad thing. > - The method used by PAO is the right way to go, although native > probe/attach codes for PCI PCIC and CardBus controllers is yet to > be written. Justify. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 8:56:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id B320914C30 for ; Thu, 8 Apr 1999 08:56:15 -0700 (PDT) (envelope-from earnoth@UDel.Edu) Received: from lapdog.duch.udel.edu (lapdog.duch.udel.edu [128.175.54.5]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id LAA13695; Thu, 8 Apr 1999 11:54:19 -0400 (EDT) Date: Thu, 8 Apr 1999 11:57:48 -0400 (EDT) From: "Eric I. Arnoth" X-Sender: earnoth@lapdog.duch.udel.edu To: Stan Brown Cc: FreeBSD Mobile List Subject: Re: Toshiba 5000CDT LCD screen resolution? In-Reply-To: <19990408102426.0AE2D1533D@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 8 Apr 1999, Stan Brown wrote: > I would like to confirm one thing that both of these people seem to > thinks is correct. Is the max resolutin of the 500CDT's internbal LCD > display really 800x600? This seems strange as it's not a "standard" > resolutinon, that I am aware of. It certainly is a "standard" resolution. My last two laptops have both been 800x600, and I know of some earlier monitors and video cards that had such a resolution for the max. > Thanks for any info on this, the Toshiba docs that I have are very > confusioing, they even imply that it will do 1280x1024, at least in > interlaced. This does not seem correct either. I've wondered about this myself, but I've never pursued the matter. I wonder if it's either a generic manual that was written to cover all models, or if driving the lcd&chip at that level is only possible with their proprietary drivers. In Windows I wasn't able to set my own display (Satellite 4010CDS) to that level, so I'm betting it's a generic manual. What experiences do others have on this? I'm sure I'm wrong in at least *part* of this, but such is my experience on the matter to the present. -Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 8:59:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id E0BFB14BED for ; Thu, 8 Apr 1999 08:59:12 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id IAA20834; Thu, 8 Apr 1999 08:57:02 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Thu, 8 Apr 1999 08:57:02 -0700 (PDT) From: Golden Fischer To: Stan Brown Cc: FreeBSD Mobile List Subject: Re: Toshiba 5000CDT LCD screen resolution? In-Reply-To: <19990408102426.0AE2D1533D@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 8 Apr 1999, Stan Brown wrote: > > Thanks for any info on this, the Toshiba docs that I have are very > confusioing, they even imply that it will do 1280x1024, at least in > interlaced. This does not seem correct either. > > I would think you'll be able to do 1280x1024 when you are NOT using the LCP display. At work we have a bunch of Toshiba 46(7)0 that ran Winslow$ 95, and it only displays 1280x1024 in a virtual desktop mode. I am pretty sure the chipset supports 1280 mode if you use a REAL SVGA monitor. You didn't say whether you use an external display. Fischer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 11:28:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id DF02014C8A for ; Thu, 8 Apr 1999 11:28:37 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA19595; Thu, 8 Apr 1999 11:26:23 -0700 (PDT) Message-Id: <199904081826.LAA19595@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: NAKAGAWA Yoshihisa , Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Thu, 08 Apr 1999 21:09:07 +0900." <370C9C63.B5506516@newsguy.com> X-Url: http://www.isi.edu/~faber Date: Thu, 08 Apr 1999 11:26:23 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- "Daniel C. Sobral" wrote: >NAKAGAWA Yoshihisa wrote: >> >> - PCIC is an ISA device. PCIC handles bus, yet the bus is not the >> bus PCIC belongs to. Please note that a PCIC is an ISA device and >> a bridge between ISA bus and PC Card bus. Also, if you see codes >> on NetBSD, bus dependent code and handling bridge is different. > >I just wish this PCIC is ISA/PCIC is not ISA would get settled... >Can anyone on the not ISA camp *PROVE* it is not an ISA device? If >it is not an ISA device, it ought to be possible to show a case A >where an ISA device behaves in such an such way and PCIC does not. I'm not in either camp. There's probably a way to make the pcic driver work either way, and I'm underinformed on the background of the design decisions in question. I think the issue of is it or isn't it is most germane to whether we can supply the ISA irq and port on a config line, as we can for the devices that are definitely ISA drivers. Presumably using that configuration mechanism means tying it to the kernel data structures for ISA devices, and herein lies the problem. Nate, is that where the problems arise? Can you clarify? I ask for your opinion because you understand the ramifications of those ties better than I do. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwz0zob4eisfQ5rpAQGojwQAo19DkTNKrDq32Pqahy0MvuH/IZV/l/41 Pvg9ov/53GyaQx3Wv7VCJNo1qAN+CynXZXiS7Kgr99JnfdcNjOIpYIoeTdlDvhr1 W4fq/1ZDYi682B0M+pGjoA8DNqCH8JiEdGsK8RNHKX/+iZeDeluvd/j7oYnPlrNf VXjKuPjiXQk= =jA4b -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 11:34:51 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C373014E47 for ; Thu, 8 Apr 1999 11:34:35 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA15145; Thu, 8 Apr 1999 12:32:16 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA28406; Thu, 8 Apr 1999 12:32:15 -0600 Date: Thu, 8 Apr 1999 12:32:15 -0600 Message-Id: <199904081832.MAA28406@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: "Daniel C. Sobral" , NAKAGAWA Yoshihisa , Nate Williams , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904081826.LAA19595@boreas.isi.edu> References: <370C9C63.B5506516@newsguy.com> <199904081826.LAA19595@boreas.isi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think the issue of is it or isn't it is most germane to whether we > can supply the ISA irq and port on a config line, as we can for the > devices that are definitely ISA drivers. Presumably using that > configuration mechanism means tying it to the kernel data structures > for ISA devices, and herein lies the problem. What he said. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 11:41: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id EEEBD15845 for ; Thu, 8 Apr 1999 11:40:58 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA20241; Thu, 8 Apr 1999 11:38:47 -0700 (PDT) Message-Id: <199904081838.LAA20241@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: "Daniel C. Sobral" , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Your message of "Thu, 08 Apr 1999 12:32:15 MDT." <199904081832.MAA28406@mt.sri.com> X-Url: http://www.isi.edu/~faber Date: Thu, 08 Apr 1999 11:38:47 -0700 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Nate Williams wrote: [ >> is me] >> I think the issue of is it or isn't it is most germane to whether we >> can supply the ISA irq and port on a config line, as we can for the >> devices that are definitely ISA drivers. Presumably using that >> configuration mechanism means tying it to the kernel data structures >> for ISA devices, and herein lies the problem. > >What he said. Ummm, not that I dislike being agreed with, but can you tell us a little more about those problems? Even one example would help. Sorry if I'm being dense. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNwz3tob4eisfQ5rpAQG89wP/WYaGIOzohwYaist5V1mgUcsR8lYuNFR9 tJs/fgf/KWtzZRLH+1HKeyVO4nd3givLDYeCN/JWw/rrVk2xRHwxsdFwlk/cyCgb M8Ir3EjZ7G/Mmt7cFR0WyKK5n6t29WIWEWivu+GSVqUf0l4ehjNTsGp1dQA1LJHP pHLd1MutCbg= =bNk2 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 12: 8: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from falcon.sourcee.com (falcon2.sourcee.com [12.11.131.185]) by hub.freebsd.org (Postfix) with ESMTP id 60CCB15AE4 for ; Thu, 8 Apr 1999 12:08:03 -0700 (PDT) (envelope-from evan@falcon.sourcee.com) Received: (from evan@localhost) by falcon.sourcee.com (8.9.1/8.9.1) id PAA19992 for freebsd-mobile@freebsd.org; Thu, 8 Apr 1999 15:06:03 -0400 (EDT) Date: Thu, 8 Apr 1999 15:06:03 -0400 From: Evan Tsoukalas To: freebsd-mobile@freebsd.org Subject: 3CXE589ET PCMCIA card Message-ID: <19990408150603.A19363@falcon.sourcee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: email message X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Can anyone tell me if a 3Com 3CXE589ET Ethernet pcmcia card is supported under 3.1-Release? If it is, can I use the generic pccard kernel support, or would I need to compile it with the zp0 driver? If it isn't supported, can anyone give me a model that is supported? I would greatly appreciate any assistance in this matter. -- Regards, Evan Tsoukalas Systems Administrator Source Electronics Corporation evan@sourcee.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 12:21:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from banzai.lovett.com (banzai.lovett.com [38.155.241.3]) by hub.freebsd.org (Postfix) with ESMTP id 27B8B14DC9 for ; Thu, 8 Apr 1999 12:21:40 -0700 (PDT) (envelope-from ade@lovett.com) Received: from ade by banzai.lovett.com with local (Exim 2.12 #1) id 10VKKW-0005Yp-00; Thu, 8 Apr 1999 14:19:12 -0500 Date: Thu, 8 Apr 1999 14:19:12 -0500 From: Ade Lovett To: Evan Tsoukalas Cc: freebsd-mobile@freebsd.org Subject: Re: 3CXE589ET PCMCIA card Message-ID: <19990408141912.F21172@remarq.com> References: <19990408150603.A19363@falcon.sourcee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990408150603.A19363@falcon.sourcee.com>; from Evan Tsoukalas on Thu, Apr 08, 1999 at 03:06:03PM -0400 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 08, 1999 at 03:06:03PM -0400, Evan Tsoukalas wrote: > > Can anyone tell me if a 3Com 3CXE589ET Ethernet pcmcia card is supported under > 3.1-Release? If it is, can I use the generic pccard kernel support, > or would I need to compile it with the zp0 driver? The simple answer is "try it and see" :) > If it isn't supported, can anyone give me a model that is supported? My 3C589D worked fine with both zp0 and the pccard stuff in 3.1-RELEASE and above. Though now we have the Xircom Realport cards working, see http://www.freebsd-uk.eu.org/~scott/xe_drv/ for details, you might want to consider getting one of those and doing away with all those other horrible pc-cards that have dongles/x-jacks/other breakables. "All" we need now is multifunction card support.. *ducks-and-runs* :) -aDe -- Ade Lovett, RemarQ Communities, Inc., San Jose, CA. mailto:ade@remarq.com http://www.remarq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 12:43:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 76EAB14EDC for ; Thu, 8 Apr 1999 12:43:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01072; Thu, 8 Apr 1999 12:38:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904081938.MAA01072@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: NAKAGAWA Yoshihisa , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Thu, 08 Apr 1999 21:09:07 +0900." <370C9C63.B5506516@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Apr 1999 12:38:36 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > NAKAGAWA Yoshihisa wrote: > > > > - PCIC is an ISA device. PCIC handles bus, yet the bus is not the > > bus PCIC belongs to. Please note that a PCIC is an ISA device and > > a bridge between ISA bus and PC Card bus. Also, if you see codes > > on NetBSD, bus dependent code and handling bridge is different. > > I just wish this PCIC is ISA/PCIC is not ISA would get settled... > Can anyone on the not ISA camp *PROVE* it is not an ISA device? If > it is not an ISA device, it ought to be possible to show a case A > where an ISA device behaves in such an such way and PCIC does not. It's not "an ISA device". Specifically, it's "not an ISA device" in the same way that the NE2000 is "not an ISA device". ISA refers to the electrical bus used to connect to the device. Most modern PCICs are actually compatability-mode implementations inside PCI-connected devices. More significantly, however, the issue is "the PCIC does not need to be treated as an ISA device", and "it is more useful to treat the PCIC as a bridge between the nexus and the PCCARD bus". Treating the PCIC like an ISA device just makes things more difficult. > > - sysctl is the last way to go. It can't work unless the module is > > loaded after boot. There are also other problems loading the > > driver with current KLD. > > That is incorrect. It can be set through loader at load time. This > is not hypothetical, it is the present state for PCIC. They're actually quite right here. However, the IRQ should not need to be set. It should be automatically determined. Arguing about how to set it is wrong. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 13: 5:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id BC50614E51 for ; Thu, 8 Apr 1999 13:05:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA01215; Thu, 8 Apr 1999 13:00:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904082000.NAA01215@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ted Faber Cc: Nate Williams , "Daniel C. Sobral" , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Thu, 08 Apr 1999 11:38:47 PDT." <199904081838.LAA20241@boreas.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Apr 1999 13:00:53 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> I think the issue of is it or isn't it is most germane to whether we > >> can supply the ISA irq and port on a config line, as we can for the > >> devices that are definitely ISA drivers. Presumably using that > >> configuration mechanism means tying it to the kernel data structures > >> for ISA devices, and herein lies the problem. > > > >What he said. > > Ummm, not that I dislike being agreed with, but can you tell us a > little more about those problems? Even one example would help. The problem is that with the static configuration technologies (config, newconfig) under discussion, there is an array of per-bus data structures constructed at compile-time containing the parametric information. By making the pcic driver an ISA driver, you tie it to the data structure that config generates. This is a fundamental problem with our current bus code. Because there must be one instance of this structure per instance of the device, you can't dynamically create new instances when you discover more pcics. Because the supporting code for these structures doesn't understand things arriving and leaving at arbitrary times, you can't support dynamism. The "new bus" philosophy on this is to write code which knows how to find the pcics, and attach the driver to whichever point the bridge is logically connected. The major point of contention at the moment seems to rest around how you pass per-instance parameters to the driver, to tell it where to put the pcic (I/O, interrupt resources). I don't think that this should actually be an issue - we should be able to determine these numbers automatically. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 13:40:51 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 70830152AE for ; Thu, 8 Apr 1999 13:40:48 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA22109 for ; Thu, 8 Apr 1999 14:38:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: (from imp@localhost) by harmony.village.org (8.9.3/8.8.3) id OAA07337 for mobile@freebsd.org; Thu, 8 Apr 1999 14:40:16 -0600 (MDT) Date: Thu, 8 Apr 1999 14:40:16 -0600 (MDT) From: Warner Losh Message-Id: <199904082040.OAA07337@harmony.village.org> To: mobile@freebsd.org Subject: Sony VAIO? Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does FreeBSD run on the VAIO line of computers? I got a call from the shop I took mine to and they offered me a replacement for the 50CT I have that was a VAIO. I'll see which type of VAIO, but it isn't the one with the little camera :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 13:43:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 13364152AB for ; Thu, 8 Apr 1999 13:43:38 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (432 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 8 Apr 1999 13:41:38 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 8 Apr 1999 13:41:38 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@freebsd.org Subject: Re: Sony VAIO? References: <199904082040.OAA07337@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does FreeBSD run on the VAIO line of computers? yes, see http://psg.com/~randy/vaio/ randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 14:16:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CD22415420 for ; Thu, 8 Apr 1999 14:16:51 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA22200; Thu, 8 Apr 1999 15:14:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA07568; Thu, 8 Apr 1999 15:16:18 -0600 (MDT) Message-Id: <199904082116.PAA07568@harmony.village.org> To: Randy Bush Subject: Re: Sony VAIO? Cc: mobile@freebsd.org In-reply-to: Your message of "Thu, 08 Apr 1999 13:41:38 PDT." References: <199904082040.OAA07337@harmony.village.org> Date: Thu, 08 Apr 1999 15:16:18 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Randy Bush writes: : yes, see http://psg.com/~randy/vaio/ This page is for a Sony Vaio 505TX. The unit in question is a 505TS. What's the difference between them? Looks like a bigger disk and a better screen on the TX. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 14:51:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 37F4F14BD6 for ; Thu, 8 Apr 1999 14:51:14 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (654 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 8 Apr 1999 14:49:14 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 8 Apr 1999 14:49:14 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@freebsd.org Subject: Re: Sony VAIO? References: <199904082040.OAA07337@harmony.village.org> <199904082116.PAA07568@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This page is for a Sony Vaio 505TX. The unit in question is a 505TS. > What's the difference between them? Looks like a bigger disk and a > better screen on the TX. my _guess_ is that the /etc/XF86Config is the only difference. rnady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 16:50:44 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id 7C787152AC for ; Thu, 8 Apr 1999 16:50:39 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA186485311; Thu, 8 Apr 1999 19:48:31 -0400 Subject: The continuing saga of X and the Toshiba 500CDT To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Thu, 8 Apr 1999 19:48:30 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1291 Message-Id: <19990408235040.7C787152AC@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to everyone who has provided help with this. However the final soultion is still eluding me :-( I beleive that the maximum resolutin that I can get from the interanl LCD on this machine is 800x600. I have a nice confiiguration for external monitor with this card. What I don;t have is an 800x600 modelin that does what i want. I do have one that gets the internal display up, but I find myselef in a virtual display that appears to be about 1024x768, and this is _without_ declaring a virtual size in XF86Config. The 1024x768 display config for the external monitor works, but of course I can't see all of it, but it's not virtual either. Since I am goiing to run a virtul window manage on this, I really can't use a virtual server screen. How can I be geting a virtual screen withou calling for it? -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 20:25:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [202.99.58.245]) by hub.freebsd.org (Postfix) with ESMTP id A514E14E77 for ; Thu, 8 Apr 1999 20:25:04 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id LAA47682 for freebsd-mobile@FreeBSD.ORG; Fri, 9 Apr 1999 11:04:57 +0800 (CST) (envelope-from robinson) Date: Fri, 9 Apr 1999 11:04:57 +0800 (CST) From: Michael Robinson Message-Id: <199904090304.LAA47682@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG Subject: PCIC (was Re: Any success) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: >However, the IRQ should not need to be set. It should be automatically >determined. Arguing about how to set it is wrong. I'm not quite clear on this. Do you mean: "There is no theoretical reason why a user should have to set a PCIC IRQ." or: "There exists a foolproof method for automatically determining the proper PCIC IRQ on all hardware supported by FreeBSD, and someone should implement that method." -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 20:47:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6CDAC14BDD for ; Thu, 8 Apr 1999 20:47:31 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA21633; Fri, 9 Apr 1999 12:45:09 +0900 (JST) Message-ID: <370D774B.1DC704C5@newsguy.com> Date: Fri, 09 Apr 1999 12:43:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: NAKAGAWA Yoshihisa , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? References: <199904081938.MAA01072@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > ISA refers to the electrical bus used to connect to the device. Most > modern PCICs are actually compatability-mode implementations inside > PCI-connected devices. > > More significantly, however, the issue is "the PCIC does not need to be > treated as an ISA device", and "it is more useful to treat the PCIC as > a bridge between the nexus and the PCCARD bus". > > Treating the PCIC like an ISA device just makes things more difficult. Just to clear a doubt here, it seems they were talking about the PCIC *bus* being an ISA device, not a pcmcia card. You are talking about the same thing, right? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 8 21: 4:12 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 9CA9014EB5 for ; Thu, 8 Apr 1999 21:04:09 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA02750; Fri, 9 Apr 1999 12:58:51 +0900 (JST) Message-Id: <199904090358.MAA02750@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Thu, 08 Apr 1999 12:38:36 MST." <199904081938.MAA01072@dingo.cdrom.com> Date: Fri, 09 Apr 1999 12:58:51 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It's not "an ISA device". > > Specifically, it's "not an ISA device" in the same way that the NE2000 > is "not an ISA device". I disagree. ISA PCIC is ISA device with PCMCIA bus. For example, SCSI cards are ISA/PCI/PCMCIA/... device. It handled by FreeBSD, as ISA/PCI/PCMCIA/... device. SCSI is bus, PCMCIA is bus, it same case. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 1:37:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 3F50714DED for ; Fri, 9 Apr 1999 01:37:14 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA30418; Fri, 9 Apr 1999 09:36:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 9 Apr 1999 09:36:59 +0100 (BST) From: Doug Rabson To: Mike Smith Cc: Ted Faber , Nate Williams , "Daniel C. Sobral" , NAKAGAWA Yoshihisa , Nick Sayer , freebsd-mobile@freebsd.org Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904082000.NAA01215@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 8 Apr 1999, Mike Smith wrote: > > >> I think the issue of is it or isn't it is most germane to whether we > > >> can supply the ISA irq and port on a config line, as we can for the > > >> devices that are definitely ISA drivers. Presumably using that > > >> configuration mechanism means tying it to the kernel data structures > > >> for ISA devices, and herein lies the problem. > > > > > >What he said. > > > > Ummm, not that I dislike being agreed with, but can you tell us a > > little more about those problems? Even one example would help. > > The problem is that with the static configuration technologies (config, > newconfig) under discussion, there is an array of per-bus data > structures constructed at compile-time containing the parametric > information. > > By making the pcic driver an ISA driver, you tie it to the data > structure that config generates. This is a fundamental problem with > our current bus code. > > Because there must be one instance of this structure per instance of > the device, you can't dynamically create new instances when you > discover more pcics. Because the supporting code for these structures > doesn't understand things arriving and leaving at arbitrary times, you > can't support dynamism. > > The "new bus" philosophy on this is to write code which knows how to > find the pcics, and attach the driver to whichever point the bridge is > logically connected. > > The major point of contention at the moment seems to rest around how > you pass per-instance parameters to the driver, to tell it where to put > the pcic (I/O, interrupt resources). I don't think that this should > actually be an issue - we should be able to determine these numbers > automatically. The current code has an abstraction system for resources which allows the driver to just ask for its memory region (or whatever) and let the parent device (pcic, cardbus etc) handle the request in an appropriate fashion. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 2:18: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 4C85815000 for ; Fri, 9 Apr 1999 02:18:00 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id SAA03116; Fri, 9 Apr 1999 18:13:05 +0900 (JST) Message-Id: <199904090913.SAA03116@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: Ted Faber , Nate Williams , "Daniel C. Sobral" , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Thu, 08 Apr 1999 13:00:53 MST." <199904082000.NAA01215@dingo.cdrom.com> Date: Fri, 09 Apr 1999 18:13:04 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org # Thanks advice and translate nomads ML people! > The problem is that with the static configuration technologies (config, > newconfig) under discussion, there is an array of per-bus data > structures constructed at compile-time containing the parametric > information. It is incorrect. We already explain, some times. Newconfig *is* both dynamic and static configuration technology. > By making the pcic driver an ISA driver, you tie it to the data > structure that config generates. This is a fundamental problem with > our current bus code. > > Because there must be one instance of this structure per instance of > the device, you can't dynamically create new instances when you > discover more pcics. Because the supporting code for these structures > doesn't understand things arriving and leaving at arbitrary times, you > can't support dynamism. Of cource, newconfig framework adopted in 4.4BSD, BSD/OS, NetBSD and OpenBSD supports dynamic device instance creation. Also detaching is supported. What is the problem of newconfig aproach ? > The "new bus" philosophy on this is to write code which knows how to > find the pcics, and attach the driver to whichever point the bridge is > logically connected. > > The major point of contention at the moment seems to rest around how > you pass per-instance parameters to the driver, to tell it where to put > the pcic (I/O, interrupt resources). I don't think that this should > actually be an issue - we should be able to determine these numbers > automatically. The "newconfig" supports these, and already coded and working! Of cource in the "newconfig" project, we will do, - Separate PCIC code into three parts: ISA frontend, PCI frontend and bus independent backend. # using NetBSD pcmcia support code, and *native* CardBus # support code. - ISA frontend supports ISA PCICs on ISA buses and PCI PCICs' ISA PCIC compatible mode. # "PCI PCICs' ISA PCIC compatible mode" means BIOS setuped # Legacy compatible mode. Some CardBus bridge, it can't # probe PCI bus in this mode. - PCI frontend supports PCICs on PCI buses for *native* CardBus support. - Supports dynamic configuration for both ISA frontend and PCI frontend. Naturally it is clear that can do fully automatic configuration in PCI frontend only. - There *is* already working code and you can get it! (The UserConfig facility is not supported yet.) - Are there any problem handling PCIC as ISA device ? -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 14: 8: 7 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id 052C116043 for ; Fri, 9 Apr 1999 14:07:48 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA136829590; Fri, 9 Apr 1999 13:39:50 -0400 Subject: Seperate X configs for internal display, and monitor? To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Fri, 9 Apr 1999 13:39:49 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1593 Message-Id: <19990409210751.052C116043@hub.freebsd.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org First, tahnks to all the helpful people wha have provided tremndous ammounts of help in working through getting XFree86 set up for my Toshiba Tecra 500CDT. Now on to what I hope the final issue is. The maximum resolution that I appear to be able to get on the internal LCD display is 800x600, so be it. However I sometimes usethis machine with an external disply that can use much higher resolutin. The internal graphic hardware can slo support this higher resolutin. I intended to simply define the needed resolutins in XF86Confg, and use [CTRL} {ALT} + to swithc as needed. The problem with this scheme is that XF86 then gives me a virtual screen the size of the mximum resolutin defined (EG 1024x768). Since I am going to use a virtual window manager (FVWM) this does not work very well :-( Som here is the question. Is there some way that I can: 1. Use alternate XF86Config files for the 2 scenario, and 2. Detect the presence or absence of the monitor, to make this swithc automaticly? I wo8ld envison only going to/from the monitor at boot time? Sugestiosn? And again, thanks for all the help. -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 15:39:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id C7E7D14C0C for ; Fri, 9 Apr 1999 15:39:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA00799; Fri, 9 Apr 1999 15:37:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904092237.PAA00799@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Robinson Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCIC (was Re: Any success) In-reply-to: Your message of "Fri, 09 Apr 1999 11:04:57 +0800." <199904090304.LAA47682@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Apr 1999 15:37:04 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith writes: > >However, the IRQ should not need to be set. It should be automatically > >determined. Arguing about how to set it is wrong. > > I'm not quite clear on this. Do you mean: > > "There is no theoretical reason why a user should have to set a PCIC IRQ." > > or: > > "There exists a foolproof method for automatically determining the proper > PCIC IRQ on all hardware supported by FreeBSD, and someone should implement > that method." Both. The "automatic" method may require user help in the form of parametric information, but it should in no way be pcic-specific. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 15:43:54 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id C606B14DD2 for ; Fri, 9 Apr 1999 15:43:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA00883; Fri, 9 Apr 1999 15:38:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904092238.PAA00883@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Mike Smith , NAKAGAWA Yoshihisa , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 09 Apr 1999 12:43:07 +0900." <370D774B.1DC704C5@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Apr 1999 15:38:05 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote: > > > > ISA refers to the electrical bus used to connect to the device. Most > > modern PCICs are actually compatability-mode implementations inside > > PCI-connected devices. > > > > More significantly, however, the issue is "the PCIC does not need to be > > treated as an ISA device", and "it is more useful to treat the PCIC as > > a bridge between the nexus and the PCCARD bus". > > > > Treating the PCIC like an ISA device just makes things more difficult. > > Just to clear a doubt here, it seems they were talking about the > PCIC *bus* being an ISA device, not a pcmcia card. You are talking > about the same thing, right? No. The PCCARD bus is not an ISA device, nor is it an ISA bus. But I was referring to the pcic device itself, which is also not an ISA device. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 15:49:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6716714A12 for ; Fri, 9 Apr 1999 15:49:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA00954; Fri, 9 Apr 1999 15:43:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904092243.PAA00954@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 09 Apr 1999 12:58:51 +0900." <199904090358.MAA02750@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Apr 1999 15:43:33 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > It's not "an ISA device". > > > > Specifically, it's "not an ISA device" in the same way that the NE2000 > > is "not an ISA device". > > I disagree. ISA PCIC is ISA device with PCMCIA bus. By definition, an ISA PCIC is an ISA device. But a PCI PCIC is not an ISA device, even though it is logically identical. My point is that it is not useful to treat the PCIC as an ISA device. It should be treated as a bus bridge. > For example, SCSI cards are ISA/PCI/PCMCIA/... device. It handled > by FreeBSD, as ISA/PCI/PCMCIA/... device. SCSI is bus, PCMCIA is > bus, it same case. This is unrelated to the claim that the PCIC is an ISA device. You need to think about a bus hierarchy, not simply ISA or PCI or PCCARD. A SCSI pccard may give a bus hierarchy of nexus/PCI/PCCARD/SCSI if the PCIC is on the PCI bus, or nexus/ISA/PCCARD/SCSI if it is an ISA device. We need to treat these accordingly, and in the first case it is _not_ valid to consider the PCIC as "an ISA device". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 9 18:38:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from snowflake.apdata.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 64855150F3 for ; Fri, 9 Apr 1999 18:38:29 -0700 (PDT) (envelope-from kirk@snowflake.apdata.com.au) Received: from snowflake.apdata.com.au (remote224.apdata.com.au [192.168.255.224]) by snowflake.apdata.com.au (8.9.3/8.8.5) with ESMTP id LAA56197 for ; Sat, 10 Apr 1999 11:06:14 +0930 (CST) Message-ID: <370EAA8B.1856C64D@snowflake.apdata.com.au> Date: Sat, 10 Apr 1999 11:04:03 +0930 From: Kirk McDonald X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG Subject: Lucent IEEE 802.11 Wavelan cards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, I have used the non IEEE 802.11 Wavelan card with great success under BSD. I am wondering if any work is being done to upgrade or produce another driver that works with IEE 802.11 cards. Regards Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 0:21:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 261E114D51 for ; Sat, 10 Apr 1999 00:21:37 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id QAA06015; Sat, 10 Apr 1999 16:17:37 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: mike@smith.net.au Cc: y-nakaga@nwsl.mesh.ad.jp, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? From: Tomoaki NISHIYAMA In-Reply-To: <199904092243.PAA00954@dingo.cdrom.com> References: <199904092243.PAA00954@dingo.cdrom.com> <199904090913.SAA03116@chandra.eatell.msr.prug.or.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990410161736W.tomoaki@moss.nibb.ac.jp> Date: Sat, 10 Apr 1999 16:17:36 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 38 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Mike Smith Subject: Re: Any success with CirrusLogic 6729/6730??? Date: Fri, 09 Apr 1999 15:43:33 -0700 Message-ID: <199904092243.PAA00954@dingo.cdrom.com> mike> By definition, an ISA PCIC is an ISA device. But a PCI PCIC is not an mike> ISA device, even though it is logically identical. Newconfig people did not say PCI PCIC should be treated as ISA device, but they said that ISA PCIC and PCI PCIC in compatibility mode should be treated as ISA device, and that PCI PCIC in native mode should be treated as PCI device. mike> My point is that it is not useful to treat the PCIC as an ISA device. mike> It should be treated as a bus bridge. A bus bridge(PCIC) between ISA and PCMCIA is an ISA device. A bus bridge connected to PCI is a PCI device. They did not deny to treat PCIC as a bus bridge, but said that a bus bridge is a device in itself. mike> A SCSI pccard may give a bus hierarchy of nexus/PCI/PCCARD/SCSI if the mike> PCIC is on the PCI bus, or nexus/ISA/PCCARD/SCSI if it is an ISA mike> device. We need to treat these accordingly, and in the first case it mike> is _not_ valid to consider the PCIC as "an ISA device". If the pcic is in compatibility mode, then the PCIC should be treated as ISA device, because it works as if it were nexus/ISA/PCCARD/SCSI. If the pcic is in native mode then the PCIC is considered a PCI device. This is why the pcic code is to be separated into three parts as Nakagawa said. y-nakaga> - Separate PCIC code into three parts: ISA frontend, PCI y-nakaga> frontend and bus independent backend. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 3: 0:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from relay2.eunet.fr (relay2.eunet.fr [192.134.192.149]) by hub.freebsd.org (Postfix) with SMTP id EB18E15024 for ; Sat, 10 Apr 1999 03:00:46 -0700 (PDT) (envelope-from fla@laissus.fr) Received: from mailhub.laissus.fr (gw-laissus.laissus.fr) by relay2.eunet.fr (5.65c8d/96.05.03) via EUnet-France id AA01802; Sat, 10 Apr 1999 11:58:32 +0200 (MET) Received: from myriade.laissus.fr by mailhub.laissus.fr with SMTP (1.37.109.4/fla-2.1) id AA02322; Sat, 10 Apr 99 11:56:54 +0200 Received: by myriade.laissus.fr Date: Sat, 10 Apr 1999 11:56:44 +0200 From: Francois LAISSUS To: freebsd-mobile@freebsd.org Subject: Dell Latitude LT Message-Id: <19990410115644.A21044@myriade.laissus.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 2.2.8-RELEASE Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm trying to install 3.1 on a new Dell Latitute LT. This nice laptop is powered by a pentium MMX 266. 1) First try with external CD-ROM plugged trough a special PC card provided by Dell. It boots normaly but says it can't find any CDROM devices when I choose "install from CD-ROM". 2) Second try with external floppy. It boots normaly from the two floppies but stills the same trouble as above when I choose install from CD-ROM. 3) Third try whith 3Com Etherlink III 589C and boot floppies, it recognizes the network card (driver zp0) but stills enable to use it after configuration (link is up, that's all). I have the same trouble with 2.2.8. I've tried successfully the same test with an old (3 years old) Dell's mobile "Latitude Xpi 133 ST"... ;-( Any suggestions welcome, thank you. Francois To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 9:43:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS23.kng.mesh.ad.jp [133.205.214.23]) by hub.freebsd.org (Postfix) with ESMTP id 0EE311512A for ; Sat, 10 Apr 1999 09:43:29 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA06276; Sat, 10 Apr 1999 12:07:07 +0900 (JST) Message-Id: <199904100307.MAA06276@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 09 Apr 1999 15:43:33 MST." <199904092243.PAA00954@dingo.cdrom.com> Date: Sat, 10 Apr 1999 12:07:06 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This is unrelated to the claim that the PCIC is an ISA device. You > need to think about a bus hierarchy, not simply ISA or PCI or PCCARD. No, PCIC is bus controller, like SCSI controller. So, bus side is PCCARD, but controller side is bus depend device, ISA, PCI, ... So, same matter with SCSI. "treat the PCIC as an ISA device" is first step, like wd driver. PCI native driver is second step. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 14:39:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1A3D614D22 for ; Sat, 10 Apr 1999 14:39:33 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA30094 for ; Sat, 10 Apr 1999 15:37:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA00752 for ; Sat, 10 Apr 1999 15:36:59 -0600 (MDT) Message-Id: <199904102136.PAA00752@harmony.village.org> To: mobile@freebsd.org Subject: Testing/review wanted Date: Sat, 10 Apr 1999 15:36:59 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've modified Soren's new ata code to work with ata flash memory (and hopefully pcmcia based ata controllers). However, since I only have one ata flash card, I've been able to do limited testing. Please find enclosed diffs against today's -current that I'd like people to test and/or review. I've not done anything with card unloading yet. Also, I've not tried to implement Microsoft's Flash File System (mffs), but I did find it documented on a MS web page the other day with a disclaimer saying that they won't litigate against anybody using the informtaion in that document. Comments? Warner Index: dev/ata/ata-all.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/ata/ata-all.c,v retrieving revision 1.6 diff -d -u -r1.6 ata-all.c --- ata-all.c 1999/04/10 18:53:35 1.6 +++ ata-all.c 1999/04/10 20:55:33 @@ -33,6 +33,7 @@ #include "isa.h" #include "pci.h" #include "atadisk.h" +#include "card.h" #include #include #include @@ -53,6 +54,12 @@ #include #include #include +#if NCARD > 0 +#include +#include +#include +#include +#endif /* misc defines */ #define UNIT(dev) (dev>>3 & 0x1f) /* assume 8 minor # per unit */ @@ -71,6 +78,11 @@ static void ata_pciattach(pcici_t, int32_t); static void promise_intr(int32_t); #endif +#if NCARD > 0 +static int ata_pccard_init(struct pccard_devinfo *); +static void ata_pccard_unload(struct pccard_devinfo *); +static int ata_pccard_intr(struct pccard_devinfo *); +#endif static int32_t ata_probe(int32_t, int32_t, int32_t, pcici_t, int32_t *); static void ataintr(int32_t); @@ -262,6 +274,41 @@ } #endif +#if NCARD > 0 +PCCARD_MODULE(ata, ata_pccard_init, ata_pccard_unload, ata_pccard_intr, + 0, bio_imask); + +static int +ata_pccard_init(struct pccard_devinfo *devi) +{ + if (ata_isaprobe(&devi->isahd) == 0) + return ENXIO; + if (ata_isaattach(&devi->isahd) == 0) + return ENXIO; + printf("ata-pcmcia%d at 0x%x irq %d on pcmcia\n", + devi->isahd.id_unit, devi->isahd.id_iobase, ffs(devi->isahd.id_irq)); + /* + * probe the ata bus for atapi disks and old ata disks/flash cards + */ + atapi_attach_ctlr(atadevices[devi->isahd.id_unit]); + ad_attach_ctlr(atadevices[devi->isahd.id_unit]); + return 0; +} + +static void +ata_pccard_unload(struct pccard_devinfo *devi) +{ + printf("ata%d: unload -- unsupproted nop\n", devi->isahd.id_unit); +} + +static int +ata_pccard_intr(struct pccard_devinfo *devi) +{ + ataintr(devi->isahd.id_unit); + return 1; +} +#endif + static int32_t ata_probe(int32_t ioaddr, int32_t altioaddr, int32_t bmaddr, pcici_t tag, int32_t *unit) @@ -382,7 +429,7 @@ scp->devices |= ATA_ATAPI_SLAVE; } if (status0 != 0x00 && !(scp->devices & ATA_ATAPI_MASTER)) { - outb(scp->ioaddr + ATA_DRIVE, (ATA_D_IBM | ATA_MASTER)); + outb(scp->ioaddr + ATA_DRIVE, (ATA_D_IBM | ATA_MASTER)); DELAY(1); outb(scp->ioaddr + ATA_ERROR, 0x58); outb(scp->ioaddr + ATA_CYL_LSB, 0xa5); @@ -430,7 +477,10 @@ u_int8_t status; static int32_t intr_count = 0; - if (unit < 0 || unit > atanlun) { +#ifdef ATA_DEBUG + printf("ataintr: entered unit=%d\n", unit); +#endif + if (unit < 0 || unit > atanlun || atadevices[unit] == NULL) { printf("ataintr: unit %d unusable\n", unit); return; } Index: dev/ata/ata-disk.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.6 diff -d -u -r1.6 ata-disk.c --- ata-disk.c 1999/04/10 18:53:35 1.6 +++ ata-disk.c 1999/04/10 20:56:40 @@ -97,6 +97,100 @@ static int32_t adnlun = 0; /* number of config'd drives */ static struct intr_config_hook *ad_attach_hook; +void +ad_attach_ctlr(struct ata_softc *sc) +{ + struct ad_softc *adp; + int32_t dev, secsperint; + int8_t model_buf[40+1]; + int8_t revision_buf[8+1]; + + for (dev=0; dev<2; dev++) { + if (sc->devices & (dev ? ATA_ATA_SLAVE : ATA_ATA_MASTER)) { +#ifdef ATA_STATIC_ID + adnlun = dev + sc->unit * 2; +#endif + adp = adtab[adnlun]; + if (adp) { + printf("ad%d: unit already attached\n", adnlun); + continue; + } + if (!(adp = malloc(sizeof(struct ad_softc), M_DEVBUF, M_NOWAIT))) { + printf("ad%d: failed to allocate driver storage\n", adnlun); + continue; + } + bzero(adp, sizeof(struct ad_softc)); + adp->controller = sc; + adp->unit = (dev == 0) ? ATA_MASTER : ATA_SLAVE; + adp->lun = adnlun; + if (ad_getparam(adp)) { +#if ATA_DEBUG + printf("ata%d: device at %d not a disk", sc->unit, dev); +#endif + free(adp, M_DEVBUF); + continue; + } + adp->cylinders = adp->ata_parm->cylinders; + adp->heads = adp->ata_parm->heads; + adp->sectors = adp->ata_parm->sectors; + adp->total_secs = adp->cylinders * adp->heads * adp->sectors; + if (adp->cylinders == 16383 && + adp->total_secs < adp->ata_parm->lbasize) { + adp->total_secs = adp->ata_parm->lbasize; + adp->cylinders = adp->total_secs/(adp->heads*adp->sectors); + } + + /* support multiple sectors / interrupt ? */ + adp->transfersize = DEV_BSIZE; + secsperint = min(adp->ata_parm->nsecperint, 16); + + if (!ata_command(adp->controller, adp->unit, ATA_C_SET_MULTI, + 0, 0, 0, 0, secsperint, ATA_WAIT_INTR) && + ata_wait(adp->controller, adp->unit, ATA_S_DRDY) >= 0) + adp->transfersize *= secsperint; + + bpack(adp->ata_parm->model, model_buf, sizeof(model_buf)); + bpack(adp->ata_parm->revision, revision_buf, sizeof(revision_buf)); + printf("ad%d: <%s/%s> ATA-%c disk at ata%d as %s\n", + adnlun, + model_buf, revision_buf, + ad_version(adp->ata_parm->versmajor), + sc->unit, + (adp->unit == ATA_MASTER) ? "master" : "slave "); + printf("ad%d: %luMB (%u sectors), " + "%u cyls, %u heads, %u S/T, %u B/S\n", + adnlun, + adp->total_secs / ((1024L * 1024L) / DEV_BSIZE), + adp->total_secs, + adp->cylinders, + adp->heads, + adp->sectors, + DEV_BSIZE); + printf("ad%d: %d secs/int, %d depth queue \n", + adnlun, adp->transfersize / DEV_BSIZE, + adp->ata_parm->queuelen & 0x1f); + devstat_add_entry(&adp->stats, "ad", adnlun, DEV_BSIZE, + DEVSTAT_NO_ORDERED_TAGS, + DEVSTAT_TYPE_DIRECT | DEVSTAT_TYPE_IF_IDE, + 0x180); +#ifdef DEVFS + adp->cdevs_token = devfs_add_devswf(&ad_cdevsw, + dkmakeminor(adp->lun, 0, 0), + DV_CHR, + UID_ROOT, GID_OPERATOR, + 0640, "rad%d", adp->lun); + adp->bdevs_token = devfs_add_devswf(&ad_cdevsw, + dkmakeminor(adp->lun, 0, 0), + DV_BLK, + UID_ROOT, GID_OPERATOR, + 0640, "ad%d", adp->lun); +#endif + bufq_init(&adp->queue); + adtab[adnlun++] = adp; + } + } +} + static __inline int apiomode(struct ata_params *ap) { @@ -132,112 +226,11 @@ static void ad_attach(void *notused) { - struct ad_softc *adp; - int32_t ctlr, dev, secsperint; - int8_t model_buf[40+1]; - int8_t revision_buf[8+1]; + int32_t ctlr; /* now, run through atadevices and look for ATA disks */ - for (ctlr=0; ctlrdevices & - (dev ? ATA_ATA_SLAVE : ATA_ATA_MASTER)) { -#ifdef ATA_STATIC_ID - adnlun = dev + ctlr * 2; -#endif - adp = adtab[adnlun]; - if (adp) - printf("ad%d: unit already attached\n", adnlun); - if (!(adp = malloc(sizeof(struct ad_softc), - M_DEVBUF, M_NOWAIT))) { - printf("ad%d: failed to allocate driver storage\n", adnlun); - continue; - } - bzero(adp, sizeof(struct ad_softc)); - adp->controller = atadevices[ctlr]; - adp->unit = (dev == 0) ? ATA_MASTER : ATA_SLAVE; - adp->lun = adnlun; - if (ad_getparam(adp)) { - free(adp, M_DEVBUF); - continue; - } - adp->cylinders = adp->ata_parm->cylinders; - adp->heads = adp->ata_parm->heads; - adp->sectors = adp->ata_parm->sectors; - adp->total_secs = adp->cylinders * adp->heads * adp->sectors; - if (adp->cylinders == 16383 && - adp->total_secs < adp->ata_parm->lbasize) { - adp->total_secs = adp->ata_parm->lbasize; - adp->cylinders = adp->total_secs/(adp->heads*adp->sectors); - } - if (adp->ata_parm->atavalid & ATA_FLAG_54_58 && - adp->ata_parm->lbasize) - adp->flags |= AD_F_USE_LBA; - - /* use multiple sectors/interrupt if device supports it */ - adp->transfersize = DEV_BSIZE; - secsperint = min(adp->ata_parm->nsecperint, 16); - - if (!ata_command(adp->controller, adp->unit, ATA_C_SET_MULTI, - 0, 0, 0, secsperint, 0, ATA_WAIT_INTR) && - ata_wait(adp->controller, adp->unit, ATA_S_DRDY) >= 0) - adp->transfersize *= secsperint; - - /* use DMA if drive & controller supports it */ - if (!ata_dmainit(adp->controller, adp->unit, - apiomode(adp->ata_parm), - wdmamode(adp->ata_parm), - udmamode(adp->ata_parm))) - adp->flags |= AD_F_DMA_ENABLED; - - bpack(adp->ata_parm->model, model_buf, sizeof(model_buf)); - bpack(adp->ata_parm->revision, revision_buf, - sizeof(revision_buf)); - printf("ad%d: <%s/%s> ATA-%c disk at ata%d as %s\n", - adnlun, - model_buf, revision_buf, - ad_version(adp->ata_parm->versmajor), - ctlr, - (adp->unit == ATA_MASTER) ? "master" : "slave "); - printf("ad%d: %luMB (%u sectors), " - "%u cyls, %u heads, %u S/T, %u B/S\n", - adnlun, - adp->total_secs / ((1024L * 1024L) / DEV_BSIZE), - adp->total_secs, - adp->cylinders, - adp->heads, - adp->sectors, - DEV_BSIZE); - printf("ad%d: piomode=%d, dmamode=%d, udmamode=%d\n", - adnlun, - apiomode(adp->ata_parm), - wdmamode(adp->ata_parm), - udmamode(adp->ata_parm)); - printf("ad%d: %d secs/int, %d depth queue, %s mode\n", - adnlun, adp->transfersize / DEV_BSIZE, - adp->ata_parm->queuelen & 0x1f, - (adp->flags & AD_F_DMA_ENABLED) ? "DMA" :"PIO"); - devstat_add_entry(&adp->stats, "ad", adnlun, DEV_BSIZE, - DEVSTAT_NO_ORDERED_TAGS, - DEVSTAT_TYPE_DIRECT | DEVSTAT_TYPE_IF_IDE, - 0x180); -#ifdef DEVFS - adp->cdevs_token = devfs_add_devswf(&ad_cdevsw, - dkmakeminor(adp->lun, 0, 0), - DV_CHR, - UID_ROOT, GID_OPERATOR, - 0640, "rad%d", adp->lun); - adp->bdevs_token = devfs_add_devswf(&ad_cdevsw, - dkmakeminor(adp->lun, 0, 0), - DV_BLK, - UID_ROOT, GID_OPERATOR, - 0640, "ad%d", adp->lun); -#endif - bufq_init(&adp->queue); - adtab[adnlun++] = adp; - } - } + for (ctlr=0; ctlrdevices & - (dev ? ATA_ATAPI_SLAVE : ATA_ATAPI_MASTER)) { - if (!(atp = malloc(sizeof(struct atapi_softc), - M_DEVBUF, M_NOWAIT))) { - printf("atapi: failed to allocate driver storage\n"); - continue; - } - bzero(atp, sizeof(struct atapi_softc)); - atp->controller = atadevices[ctlr]; - atp->unit = (dev == 0) ? ATA_MASTER : ATA_SLAVE; - if (atapi_getparam(atp)) { - free(atp, M_DEVBUF); - continue; - } + for (dev=0; dev<2; dev++) { + if (sc->devices & + (dev ? ATA_ATAPI_SLAVE : ATA_ATAPI_MASTER)) { + if (!(atp = malloc(sizeof(struct atapi_softc), + M_DEVBUF, M_NOWAIT))) { + printf("atapi: failed to allocate driver storage\n"); + continue; + } + bzero(atp, sizeof(struct atapi_softc)); + atp->controller = sc; + atp->unit = (dev == 0) ? ATA_MASTER : ATA_SLAVE; + if (atapi_getparam(atp)) { + free(atp, M_DEVBUF); + continue; + } - switch (atp->atapi_parm->device_type) { + switch (atp->atapi_parm->device_type) { #if NATAPICD > 0 - case ATAPI_TYPE_CDROM: - if (acdattach(atp)) - goto notfound; - break; + case ATAPI_TYPE_CDROM: + if (acdattach(atp)) + goto notfound; + break; #endif #if NATAPIFD > 0 - case ATAPI_TYPE_DIRECT: - if (afdattach(atp)) - goto notfound; - break; + case ATAPI_TYPE_DIRECT: + if (afdattach(atp)) + goto notfound; + break; #endif #if NATAPIST > 0 - case ATAPI_TYPE_TAPE: - if (astattach(atp)) - goto notfound; - break; + case ATAPI_TYPE_TAPE: + if (astattach(atp)) + goto notfound; + break; #endif notfound: - default: - bpack(atp->atapi_parm->model, model_buf, sizeof(model_buf)); - bpack(atp->atapi_parm->revision, revision_buf, - sizeof(revision_buf)); - printf("atapi: <%s/%s> %s device at ata%d as %s " - "- NO DRIVER!\n", - model_buf, revision_buf, - atapi_type(atp->atapi_parm->device_type), - ctlr, - (dev) ? "slave" : "master "); - free(atp, M_DEVBUF); - } - } - } + default: + bpack(atp->atapi_parm->model, model_buf, sizeof(model_buf)); + bpack(atp->atapi_parm->revision, revision_buf, + sizeof(revision_buf)); + printf("atapi: <%s/%s> %s device at ata%d as %s " + "- NO DRIVER!\n", + model_buf, revision_buf, + atapi_type(atp->atapi_parm->device_type), + sc->unit, + (dev) ? "slave" : "master "); + free(atp, M_DEVBUF); + } + } + } +} + +static void +atapi_attach(void *notused) +{ + int32_t ctlr; + + /* now, run through atadevices and look for ATAPI devices */ + for (ctlr=0; ctlr; Sat, 10 Apr 1999 21:03:01 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id MAA02992; Sun, 11 Apr 1999 12:00:47 +0800 (CST) (envelope-from robinson) Date: Sun, 11 Apr 1999 12:00:47 +0800 (CST) From: Michael Robinson Message-Id: <199904110400.MAA02992@netrinsics.com> To: imp@harmony.village.org, mobile@FreeBSD.ORG Subject: Re: Testing/review wanted In-Reply-To: <199904102136.PAA00752@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh writes: >I've modified Soren's new ata code to work with ata flash memory (and >hopefully pcmcia based ata controllers). However, since I only have >one ata flash card, I've been able to do limited testing. Please find >enclosed diffs against today's -current that I'd like people to test >and/or review. What are the chances that your modified versions of Soren's code will work in -stable? Is there a known procedure for doing this? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 21: 4:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 91AF514DFC for ; Sat, 10 Apr 1999 21:04:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA30877; Sat, 10 Apr 1999 22:02:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA01979; Sat, 10 Apr 1999 22:01:59 -0600 (MDT) Message-Id: <199904110401.WAA01979@harmony.village.org> To: Michael Robinson Subject: Re: Testing/review wanted Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Apr 1999 12:00:47 +0800." <199904110400.MAA02992@netrinsics.com> References: <199904110400.MAA02992@netrinsics.com> Date: Sat, 10 Apr 1999 22:01:59 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904110400.MAA02992@netrinsics.com> Michael Robinson writes: : What are the chances that your modified versions of Soren's code will work : in -stable? Is there a known procedure for doing this? Zero. Soren's code isn't in stable. PAO has patches for the wd driver that could be merged into -stable, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 21:21:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2C37A15118 for ; Sat, 10 Apr 1999 21:21:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA30917 for ; Sat, 10 Apr 1999 22:19:14 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA02071 for ; Sat, 10 Apr 1999 22:19:02 -0600 (MDT) Message-Id: <199904110419.WAA02071@harmony.village.org> To: mobile@freebsd.org Subject: Flash fs spec Date: Sat, 10 Apr 1999 22:19:01 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've found one spec on flash fs, which I'll call msffs, at microsoft's web site. This spec dates from 1994 and appears to be the only spec for msffs available. It specifies the gross 8.3 filenames. I was wondering if anybody knew of a newer version of this, or if this representation is even used today. The flash card that I got from Nate doesn't seem to have any reasonable data on it for me to look at. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 21:27:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [202.99.58.9]) by hub.freebsd.org (Postfix) with ESMTP id 2508D15118 for ; Sat, 10 Apr 1999 21:27:16 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id MAA03941 for freebsd-mobile@FreeBSD.ORG; Sun, 11 Apr 1999 12:25:26 +0800 (CST) (envelope-from robinson) Date: Sun, 11 Apr 1999 12:25:26 +0800 (CST) From: Michael Robinson Message-Id: <199904110425.MAA03941@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG Subject: Re: PCIC (was Re: Any success) In-Reply-To: <199904092237.PAA00799@dingo.cdrom.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: >> "There is no theoretical reason why a user should have to set a PCIC IRQ." >> or: >> "There exists a foolproof method for automatically determining the proper >> PCIC IRQ on all hardware supported by FreeBSD, and someone should implement >> that method." > >Both. > >The "automatic" method may require user help in the form of parametric >information, but it should in no way be pcic-specific. So presumably new-bus has a method for providing parametric IRQ allocation information for specific ISA devices in general, and as soon as new-bus is working this whole problem will go away. -Michael Robinson P.S. Right now, though, it seems we have a pcic-specific method for assigning IRQs (sysctl), and a non-pcic-specific method for assigning IRQs for all other devices that require "user help" (are there any devices besides ISA devices that require manual IRQ assignment?). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 22: 2: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [202.99.58.9]) by hub.freebsd.org (Postfix) with ESMTP id 6F55D14D39 for ; Sat, 10 Apr 1999 22:01:58 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id MAA05258; Sun, 11 Apr 1999 12:59:56 +0800 (CST) (envelope-from robinson) Date: Sun, 11 Apr 1999 12:59:56 +0800 (CST) From: Michael Robinson Message-Id: <199904110459.MAA05258@netrinsics.com> To: imp@harmony.village.org, mobile@FreeBSD.ORG Subject: Re: Flash fs spec In-Reply-To: <199904110419.WAA02071@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh writes: >This spec dates from 1994 and appears to be the only spec >for msffs available. It specifies the gross 8.3 filenames. I was >wondering if anybody knew of a newer version of this, or if this >representation is even used today. FWIW, I always mount the SmartMedia cards from my Olympus as '-t msdos', and have no problems with interoperability. They look just like big MS-DOS floppy disks as far as FreeBSD is concerned. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 22: 3:51 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 09DC415429 for ; Sat, 10 Apr 1999 22:03:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA31008; Sat, 10 Apr 1999 23:01:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA02306; Sat, 10 Apr 1999 23:01:16 -0600 (MDT) Message-Id: <199904110501.XAA02306@harmony.village.org> To: NAKAGAWA Yoshihisa Subject: Re: Any success with CirrusLogic 6729/6730??? Cc: Mike Smith , Ted Faber , Nate Williams , "Daniel C. Sobral" , Nick Sayer , freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 09 Apr 1999 18:13:04 +0900." <199904090913.SAA03116@chandra.eatell.msr.prug.or.jp> References: <199904090913.SAA03116@chandra.eatell.msr.prug.or.jp> Date: Sat, 10 Apr 1999 23:01:16 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nakagawa-san arigato gozaimasu. gomen nasai. watashi wa nihongo ga wakarimasen.[*] Thank you for taking the time to translate your thoughts into English. I know how hard the language barrier can be. In message <199904090913.SAA03116@chandra.eatell.msr.prug.or.jp> NAKAGAWA Yoshihisa writes: : - Separate PCIC code into three parts: ISA frontend, PCI : frontend and bus independent backend. I think this is another way of saying that a pcic device has either a ISA attachment, or a PCI attachment. pcic devices support pcmcia bus(es) being attached to them. This sounds exactly like the current situation wrt scsi cards. A bt device has isa and pci attachments, and supports scsi bus(es) being attach to that card. Of course other nexus hierarchies are possible. What makes things worse is that some devices that can act like the current pcic can also act like a device which can attach cardbus cards to. And sometimes those devices can be in compatibility mode, which only adds to the confusion. Warner [*] I'm hoping to say, in japanese written in romanji, "I'm very sorry. I can't speak Japanese, yet." I've started learning, but still have a long ways to go... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 22: 6:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9B7F314F98 for ; Sat, 10 Apr 1999 22:06:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA31022; Sat, 10 Apr 1999 23:03:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA02349; Sat, 10 Apr 1999 23:03:32 -0600 (MDT) Message-Id: <199904110503.XAA02349@harmony.village.org> To: Michael Robinson Subject: Re: Flash fs spec Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Apr 1999 12:59:56 +0800." <199904110459.MAA05258@netrinsics.com> References: <199904110459.MAA05258@netrinsics.com> Date: Sat, 10 Apr 1999 23:03:32 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904110459.MAA05258@netrinsics.com> Michael Robinson writes: : FWIW, I always mount the SmartMedia cards from my Olympus as '-t msdos', : and have no problems with interoperability. They look just like big MS-DOS : floppy disks as far as FreeBSD is concerned. I have heard that is the case also. I'd like to have a file system that is more friendly to the underlying FLASH than FAT would be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 10 22:56:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (unknown [131.112.126.30]) by hub.freebsd.org (Postfix) with ESMTP id 095E814C1E for ; Sat, 10 Apr 1999 22:56:19 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA07577; Sun, 11 Apr 1999 14:52:53 +0900 (JST) Message-Id: <199904110552.OAA07577@chandra.eatell.msr.prug.or.jp> To: Warner Losh Cc: Mike Smith , Ted Faber , Nate Williams , "Daniel C. Sobral" , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Sat, 10 Apr 1999 23:01:16 CST." <199904110501.XAA02306@harmony.village.org> Date: Sun, 11 Apr 1999 14:52:51 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > gomen nasai. watashi wa nihongo ga wakarimasen.[*] Good japanese, don't care. I can't use English well, also. We can communicate, but shaky English. > What makes things worse is that some devices that can act like the > current pcic can also act like a device which can attach cardbus cards > to. And sometimes those devices can be in compatibility mode, which > only adds to the confusion. plain FreeBSD and current PAO, Now these are Legacy commpatible mode only. Newconfig project already support *native* CardBus, it is another project of PAO. Its code is share with NetBSD CardBus support. # current FreeBSD PC-Card support code is very confusion, so we # re-build PC-Card support with NetBSD PC-Card support code and # CardBus support code. newconfig CardBus configuration: pcic0 at isa? iobase 0x3e0 membase 0xd0000 memsize 0x4000 pcic1 at isa? iobase 0x3e2 membase 0xd4000 memsize 0x4000 # ISA PCIC controller # (include CardBus bridge legacymode) cbb* at pci? dev ? func ? # PCI-CardBus bridges cardbus* at cbb? slot ? # CardBus support pcmcia* at cbb? socket ? # PCMCIA support with CardBus bridge # native CardBus mode pcmcia* at pcic? controller ? socket ? # PCMCIA support with ISA PCIC # (or CardBus controller legacy mode) # currently support drivers (NetBSD driver base, for sample implement) # PC-Card network interfaces ep* at pcmcia? function ? # 3Com 3c589 and 3c562 Ethernet fe* at pcmcia? function ? # MB8696x based Ethernet ne* at pcmcia? function ? # NE2000-compatible Ethernet sn* at pcmcia? function ? # Megahertz Ethernet # CardBus-Card network interfaces ep* at cardbus? dev ? func ? # 3Com 3c575TX Ethernet xl* at cardbus? dev ? func ? # 3Com 3c575TX and 3c575BTX Ethernet -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 0:33:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (unknown [131.112.126.30]) by hub.freebsd.org (Postfix) with ESMTP id 5C11D14BF4 for ; Sun, 11 Apr 1999 00:33:19 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id QAA07786; Sun, 11 Apr 1999 16:30:19 +0900 (JST) Message-Id: <199904110730.QAA07786@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Fri, 09 Apr 1999 15:38:05 MST." <199904092238.PAA00883@dingo.cdrom.com> Date: Sun, 11 Apr 1999 16:30:18 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > No. The PCCARD bus is not an ISA device, nor is it an ISA bus. But I > was referring to the pcic device itself, which is also not an ISA > device. This message is opinions of PAO and newconfig people (me too): --- An ISA PCIC is undoubtedly an ISA device from the hardware's point of view. It has an ISA bus interface, and is connected to an ISA bus side of a PCI<->ISA bus bridge (south bridge). Why do you call it as "not an ISA device" ? As we repeatedly said, We are going to treat a PCI PCIC as a PCI device, and an ISA PCIC as an ISA device. This has several merits as below: - This is a natural abstraction which matches hardware connection topology. - We can apply UserConfig to an ISA PCIC. (PAO can use it.) - FreeBSD's current pcic code doesn't work with the machines which has both an ISA PCIC and a PCI PCIC. The notebooks which has this problem are populer in Japan. In our method, this problem goes away. Why do you ignore the hardware connection topology, and stick to "an PCIC is NOT an ISA device" ? What is the reason ? -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 1: 0:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C918B14DE1 for ; Sun, 11 Apr 1999 01:00:40 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA99310; Sun, 11 Apr 1999 09:58:19 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904110758.JAA99310@freebsd.dk> Subject: Re: Testing/review wanted In-Reply-To: <199904110401.WAA01979@harmony.village.org> from Warner Losh at "Apr 10, 1999 10: 1:59 pm" To: imp@harmony.village.org (Warner Losh) Date: Sun, 11 Apr 1999 09:58:19 +0200 (CEST) Cc: robinson@netrinsics.com, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > In message <199904110400.MAA02992@netrinsics.com> Michael Robinson writes: > : What are the chances that your modified versions of Soren's code will work > : in -stable? Is there a known procedure for doing this? > > Zero. Soren's code isn't in stable. PAO has patches for the wd > driver that could be merged into -stable, however. Well, I have at least two reports of my driver working butifully under 3.1-STABLE. Just take everything from /sys/dev/ata/ and the relevant parts of /sys/i386/conf{files.i386/devices.i386) and you are in business... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 16:17:44 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3955A14C11 for ; Sun, 11 Apr 1999 15:53:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA32397; Sun, 11 Apr 1999 12:13:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA04341; Sun, 11 Apr 1999 12:13:42 -0600 (MDT) Message-Id: <199904111813.MAA04341@harmony.village.org> To: NAKAGAWA Yoshihisa Subject: Re: Any success with CirrusLogic 6729/6730??? Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Apr 1999 16:30:18 +0900." <199904110730.QAA07786@chandra.eatell.msr.prug.or.jp> References: <199904110730.QAA07786@chandra.eatell.msr.prug.or.jp> Date: Sun, 11 Apr 1999 12:13:42 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904110730.QAA07786@chandra.eatell.msr.prug.or.jp> NAKAGAWA Yoshihisa writes: : Why do you ignore the hardware connection topology, and stick to : "an PCIC is NOT an ISA device" ? What is the reason ? I'm curious about this as well. It seems pretty clear to me in the work I've done on the laptops I've had that PCIC is indeed a bridge device that has an ISA or PCI attachment. I do think that the "new bus" stuff that is being worked on will make many of these arguments go away. It is like newconfig, only more dynamic and flexible (in a very brief nutshell). I'll be getting a new laptop on Monday that has CardBus in it, and I'd like to see CardBus support. I'll be taking a look at the work that has been done in this area with an eye towards including it FreeBSD's mainline, likely with any changes needed for it to work with newbus. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 16:18:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CE0BA15A04 for ; Sun, 11 Apr 1999 16:05:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA06142; Sun, 11 Apr 1999 12:59:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904111959.MAA06142@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Sun, 11 Apr 1999 16:30:18 +0900." <199904110730.QAA07786@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Apr 1999 12:59:41 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > An ISA PCIC is undoubtedly an ISA device from the hardware's point of > view. It has an ISA bus interface, and is connected to an ISA bus side > of a PCI<->ISA bus bridge (south bridge). > Why do you call it as "not an ISA device" ? > > Why do you ignore the hardware connection topology, and stick to > "an PCIC is NOT an ISA device" ? What is the reason ? I don't. You do. A PCIC is not an ISA device. An ISA-connected PCIC is an ISA device. A PCI-connected PCIC is a PCI device. An EISA-connected PCIC is an EISA device. A USB-connected PCIC is a USB device. A SCSI-connected PCIC is a SCSI device. This is the point I have been trying to make all along. I think your misunderstanding is that you read "a PCIC is not an ISA device" as "a PCIC cannot be an ISA device", but all it means is "a PCIC is not always an ISA device". In logical notation, {x} E {pcic devices} !-> {x} E {isa devices} (The fact that x is a pcic device does not mean that x is an ISA device.) I also find the newconfig configuration file syntax abhorrent, which is what I mean by "not dynamic". To build pcic support into a kernel using new-bus, one needs: controller pcic0 Even this is redundant if the driver is loaded as a KLD. Bus attachments are not specified in the configuration file (and shouldn't be). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 18:59:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id D3D1314FC0 for ; Sun, 11 Apr 1999 18:59:31 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id KAA08664; Mon, 12 Apr 1999 10:53:45 +0900 (JST) Message-Id: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Sun, 11 Apr 1999 12:59:41 MST." <199904111959.MAA06142@dingo.cdrom.com> Date: Mon, 12 Apr 1999 10:53:44 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I don't. You do. You are miss-understanding. I'm not saying "any time PCIC is ISA device". I'm saying "ISA-connected PCIC is handled by ISA device driver". > I also find the newconfig configuration file syntax abhorrent, which is > what I mean by "not dynamic". To build pcic support into a kernel > using new-bus, one needs: newconfig is not only static. > controller pcic0 It is TOO BAD. User-configuration is MUST. This point is worst point of new-bus. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 19:23:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CEC5B14BF4 for ; Sun, 11 Apr 1999 19:23:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA01729; Sun, 11 Apr 1999 19:18:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904120218.TAA01729@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Mon, 12 Apr 1999 10:53:44 +0900." <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Apr 1999 19:18:01 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > controller pcic0 > > It is TOO BAD. User-configuration is MUST. This point is worst > point of new-bus. This is specifically why we still use hint information from the configuration file. The goal, however, is to get away from compiling that hint information into the kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 20:17:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 69756151F3 for ; Sun, 11 Apr 1999 20:17:18 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id UAA12323 for ; Sun, 11 Apr 1999 20:07:56 -0700 (PDT) Date: Sun, 11 Apr 1999 20:07:56 -0700 (PDT) From: Annelise Anderson To: mobile@freebsd.org Subject: Floppies with Pccard Support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From andrsn@andrsn.stanford.edu Sun Apr 11 20:03:46 1999 Date: Sun, 11 Apr 1999 19:58:02 -0700 (PDT) From: Annelise Anderson To: mobile-freebsd@freebsd.org Subject: Floppies with Pccard Support I built a 3.1-RELEASE and made some install floppies (kern.flp and mfsroot.flp) with pccard support. No guarantees here, and they don't work quite as I'd like, since at least on my laptop, the pccard interface doesn't show up on the list of available network interfaces--but it works nevertheless. They are available on my anon ftp server at andrsn.stanford.edu, if you want to try them, in the pub/floppies directory. There's also a README (pretty essential); and I would think it would be helpful to be familiar with pccard stuff in general to use them effectively. I did a how-to on pccards that's on http://andrsn.stanford.edu/FreeBSD that might help if you're new to this. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 21:45:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.173.0]) by hub.freebsd.org (Postfix) with ESMTP id 47BB314E21 for ; Sun, 11 Apr 1999 21:45:07 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id MAA19124 for freebsd-mobile@freebsd.org; Mon, 12 Apr 1999 12:29:45 +0800 (CST) (envelope-from robinson) Date: Mon, 12 Apr 1999 12:29:45 +0800 (CST) From: Michael Robinson Message-Id: <199904120429.MAA19124@netrinsics.com> To: freebsd-mobile@freebsd.org Subject: PCIC again (was: Any success) In-Reply-To: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa writes: >> controller pcic0 > >It is TOO BAD. User-configuration is MUST. This point is worst >point of new-bus. Actually, compensating for the language barrier, I think this should be written something like: "That's very elegant, Mike. How does the user provide parametric configuration information under new-bus, though, to handle hardware special cases that cannot be determined automatically?" -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 22: 1: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 96D3C14E21 for ; Sun, 11 Apr 1999 22:01:02 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id NAA24629; Mon, 12 Apr 1999 13:58:39 +0900 (JST) Date: Mon, 12 Apr 1999 13:58:39 +0900 (JST) Message-Id: <199904120458.NAA24629@afs.ntc.mita.keio.ac.jp> To: andrsn@andrsn.stanford.edu Cc: mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: Floppies with Pccard Support In-Reply-To: Your message of "Mon, 12 Apr 1999 12:07:56 JST". From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article andrsn@andrsn.stanford.edu writes: >> I built a 3.1-RELEASE and made some install floppies >> (kern.flp and mfsroot.flp) with pccard support. No guarantees >> here, and they don't work quite as I'd like, since at least >> on my laptop, the pccard interface doesn't show up on the list >> of available network interfaces--but it works nevertheless. I also built 3.1-RELEASE (with PAO3) boot.flp, kern.flp, and mfsroot.flp this morning. This problem (about interface detection) comes from release/sysinstall/devices.c and I've fixed it, I will put it somewhere when I finished the test of it. I rewrited most of pccard support in PAO2 boot.flp. The diffs against the original source is too smaller than PAO2 boot.flp. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 22:12:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 8704014C18 for ; Sun, 11 Apr 1999 22:12:44 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA08934; Mon, 12 Apr 1999 14:08:51 +0900 (JST) Message-Id: <199904120508.OAA08934@chandra.eatell.msr.prug.or.jp> To: Michael Robinson Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCIC again (was: Any success) In-reply-to: Your message of "Mon, 12 Apr 1999 12:29:45 +0800." <199904120429.MAA19124@netrinsics.com> Date: Mon, 12 Apr 1999 14:08:49 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > "That's very elegant, Mike. How does the user provide parametric > configuration information under new-bus, though, to handle hardware > special cases that cannot be determined automatically?" hum... I don't think "new-bus is elegant". I think "newconfig is elegant". Because, new-bus configuration has not bus connection information. Automatically configuration only. Some case, automatically configuration not working, so statically configuration is need. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 11 22:46:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 8F1D015175 for ; Sun, 11 Apr 1999 22:46:14 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id OAA11879; Mon, 12 Apr 1999 14:41:39 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: y-nakaga@nwsl.mesh.ad.jp Cc: mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? From: Tomoaki NISHIYAMA In-Reply-To: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> References: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990412144137C.tomoaki@moss.nibb.ac.jp> Date: Mon, 12 Apr 1999 14:41:37 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 29 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: NAKAGAWA Yoshihisa Subject: Re: Any success with CirrusLogic 6729/6730??? Date: Mon, 12 Apr 1999 10:53:44 +0900 Message-ID: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> y-nakaga> > I don't. You do. y-nakaga> y-nakaga> You are miss-understanding. Now, we are in agreement that an ISA PCIC is an ISA device and that a PCI PCIC is a PCI device. That is good enough and it's no use to discuss about who is responsible for the misunderstanding. We should go to the next major difference between new-bus and newconfig. As far as I understand, new-bus strategy is to put all the information of connection between bus and devices in individual device drivers, while newconfig strategy is to put the information in a file outside the kernel. Both are to put information of bus-device connection outside the kernel. The difference is where to put it. The reason why newconfig will put the information in a file is to make the user-configuration easier. The reason of new-bus to put the information in individual driver is to make it easier to load the module dynamic. Is this recognition right? I would like to hear from both sides. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 1: 1:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 59C9E1547C for ; Mon, 12 Apr 1999 01:01:32 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id QAA09135; Mon, 12 Apr 1999 16:54:25 +0900 (JST) Message-Id: <199904120754.QAA09135@chandra.eatell.msr.prug.or.jp> To: Mike Smith Cc: "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Sun, 11 Apr 1999 19:18:01 MST." <199904120218.TAA01729@dingo.cdrom.com> Date: Mon, 12 Apr 1999 16:54:25 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This is specifically why we still use hint information from the > configuration file. The goal, however, is to get away from compiling > that hint information into the kernel. # newconfig members' (me too) opinion below: Our newconfig is better than yours new-bus in this point. Newconfig supports both dynamic configration and static configuration, so newconfig can do what new-bus can do, and also newconfig can support particular configurations which new-bus can't. (e.g. specially tuned kernel for particular purpose.) Also, in newconfig case, we don't have to load the code which support an ISA PCIC, if only an PCI PCIC code is needed, because we split an PCIC driver to three part, an ISA attachment, an PCI attachment, and bus independent shared part. In new-bus case, we suppose that you have to load both the code which supports an PCI PCIC and the code which supports an ISA PCIC. So, newconfig kernel is smaller and faster to boot and more dynamic than new-bus. Especially because new-bus doesn't have the feature to treat the shared part of the device driver like this. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 3:14:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C22C14D23 for ; Mon, 12 Apr 1999 03:14:34 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA42976; Mon, 12 Apr 1999 11:06:31 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 11:06:30 +0100 (BST) From: Doug Rabson To: NAKAGAWA Yoshihisa Cc: Michael Robinson , freebsd-mobile@freebsd.org Subject: Re: PCIC again (was: Any success) In-Reply-To: <199904120508.OAA08934@chandra.eatell.msr.prug.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, NAKAGAWA Yoshihisa wrote: > > "That's very elegant, Mike. How does the user provide parametric > > configuration information under new-bus, though, to handle hardware > > special cases that cannot be determined automatically?" > > hum... I don't think "new-bus is elegant". I think "newconfig is > elegant". Because, new-bus configuration has not bus > connection information. Automatically configuration only. > > Some case, automatically configuration not working, so statically > configuration is need. Then we agree :-) Probe hints for non-pnp busses (ISA mainly) are needed. That and building the Makefile is all we use config(8) for. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 3:15:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 00659150B6 for ; Mon, 12 Apr 1999 03:15:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA42949; Mon, 12 Apr 1999 11:00:45 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 11:00:45 +0100 (BST) From: Doug Rabson To: Tomoaki NISHIYAMA Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@freebsd.org Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <19990412144137C.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, Tomoaki NISHIYAMA wrote: > From: NAKAGAWA Yoshihisa > Subject: Re: Any success with CirrusLogic 6729/6730??? > Date: Mon, 12 Apr 1999 10:53:44 +0900 > Message-ID: <199904120153.KAA08664@chandra.eatell.msr.prug.or.jp> > > y-nakaga> > I don't. You do. > y-nakaga> > y-nakaga> You are miss-understanding. > Now, we are in agreement that an ISA PCIC is an ISA device > and that a PCI PCIC is a PCI device. > That is good enough and it's no use to discuss about > who is responsible for the misunderstanding. > > We should go to the next major difference between new-bus and newconfig. > As far as I understand, new-bus strategy is to put all the information > of connection between bus and devices in individual device drivers, > while newconfig strategy is to put the information in a file outside > the kernel. Both are to put information of bus-device connection > outside the kernel. The difference is where to put it. > The reason why newconfig will put the information in a file > is to make the user-configuration easier. > The reason of new-bus to put the information in individual driver > is to make it easier to load the module dynamic. > Is this recognition right? I would like to hear from both sides. This is right. The reason device attachment points are not specified in the config file is that I don't think the user should need to care how the hardware in their machine works in order to get FreeBSD working. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 3:20:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 700CF15319 for ; Mon, 12 Apr 1999 03:20:32 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA42969; Mon, 12 Apr 1999 11:03:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 11:03:44 +0100 (BST) From: Doug Rabson To: NAKAGAWA Yoshihisa Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@freebsd.org Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <199904120754.QAA09135@chandra.eatell.msr.prug.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, NAKAGAWA Yoshihisa wrote: > > This is specifically why we still use hint information from the > > configuration file. The goal, however, is to get away from compiling > > that hint information into the kernel. > > # newconfig members' (me too) opinion below: > > Our newconfig is better than yours new-bus in this point. > Newconfig supports both dynamic configration and static configuration, > so newconfig can do what new-bus can do, and also newconfig can > support particular configurations which new-bus can't. > (e.g. specially tuned kernel for particular purpose.) I would be interested in a specific example here. I don't understand what kind of tuning you are suggesting. > > Also, in newconfig case, we don't have to load the code which support > an ISA PCIC, if only an PCI PCIC code is needed, because we split an > PCIC driver to three part, an ISA attachment, an PCI attachment, and > bus independent shared part. In new-bus case, we suppose that you > have to load both the code which supports an PCI PCIC and the code > which supports an ISA PCIC. So, newconfig kernel is smaller and > faster to boot and more dynamic than new-bus. > Especially because new-bus doesn't have the feature to treat the > shared part of the device driver like this. This is not correct. A driver can be trivially split up into attachment points and implementations. The interface definition system can actually make this easier (IMHO of course). The mcclock driver in FreeBSD/alpha (derived from the NetBSD driver) does this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 3:22: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 2B1D41534E for ; Mon, 12 Apr 1999 03:22:06 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id TAA12436; Mon, 12 Apr 1999 19:19:46 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-mobile@freebsd.org Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, dfr@nlsystems.com Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? From: Tomoaki NISHIYAMA In-Reply-To: References: X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990412191944E.tomoaki@moss.nibb.ac.jp> Date: Mon, 12 Apr 1999 19:19:44 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 34 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Doug Rabson Subject: Re: Any success with CirrusLogic 6729/6730??? Date: Mon, 12 Apr 1999 11:00:45 +0100 (BST) Message-ID: dfr> > The reason why newconfig will put the information in a file dfr> > is to make the user-configuration easier. dfr> > The reason of new-bus to put the information in individual driver dfr> > is to make it easier to load the module dynamic. dfr> > Is this recognition right? I would like to hear from both sides. dfr> dfr> This is right. dfr> dfr> The reason device attachment points are not specified in the config file dfr> is that I don't think the user should need to care how the hardware in dfr> their machine works in order to get FreeBSD working. dfr> Hearing the discussion in Japanese, the files file in newconfig is not only used for user configuration, but is essential to guarantee the modularity of the drivers. We would have separate modules for bus interface and bus independent part of a device driver. This is important because a device may be connected to different device and thus there is bus dependent and independent codes. Bus independent code should be the same for different interfaces. Now my question is if new-bus architecture provides a framework to separate the bus interface and bus independent part of a device driver. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 4:13:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id ADE4A154D3 for ; Mon, 12 Apr 1999 04:13:38 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id UAA12521; Mon, 12 Apr 1999 20:06:32 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: dfr@nlsystems.com Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? From: Tomoaki NISHIYAMA In-Reply-To: References: X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990412200631T.tomoaki@moss.nibb.ac.jp> Date: Mon, 12 Apr 1999 20:06:31 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 17 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Doug Rabson Subject: Re: Any success with CirrusLogic 6729/6730??? Date: Mon, 12 Apr 1999 11:03:44 +0100 (BST) Message-ID: dfr> This is not correct. A driver can be trivially split up into attachment dfr> points and implementations. The interface definition system can actually dfr> make this easier (IMHO of course). The mcclock driver in FreeBSD/alpha dfr> (derived from the NetBSD driver) does this. More precicely, is the split driver *dynamically* loadable? The bus independent part, mcclock.c seemes to be linked statically, putting aside whethere there is any merit to load the clock dynamically. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 7:16:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 20B5114FA3 for ; Mon, 12 Apr 1999 07:16:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id QAA17330; Mon, 12 Apr 1999 16:14:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id QAA06548; Mon, 12 Apr 1999 16:14:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: Flash fs spec In-reply-to: Your message of "Sat, 10 Apr 1999 22:19:01 MDT." <199904110419.WAA02071@harmony.village.org> Date: Mon, 12 Apr 1999 16:14:10 +0200 Message-ID: <6546.923926450@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Search for "FTL" which is "Flash Translation Layer" or something... In message <199904110419.WAA02071@harmony.village.org>, Warner Losh writes: > >I've found one spec on flash fs, which I'll call msffs, at microsoft's >web site. This spec dates from 1994 and appears to be the only spec >for msffs available. It specifies the gross 8.3 filenames. I was >wondering if anybody knew of a newer version of this, or if this >representation is even used today. The flash card that I got from >Nate doesn't seem to have any reasonable data on it for me to look >at. > >Warner > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-mobile" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 7:44:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.174.3]) by hub.freebsd.org (Postfix) with ESMTP id 1925B14E0C for ; Mon, 12 Apr 1999 07:44:10 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id WAA00575 for freebsd-mobile@freebsd.org; Mon, 12 Apr 1999 22:42:04 +0800 (CST) (envelope-from robinson) Date: Mon, 12 Apr 1999 22:42:04 +0800 (CST) From: Michael Robinson Message-Id: <199904121442.WAA00575@netrinsics.com> To: freebsd-mobile@freebsd.org Subject: new-bus/newconfig (was: Any success) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: >The reason device attachment points are not specified in the config file >is that I don't think the user should need to care how the hardware in >their machine works in order to get FreeBSD working. There's that "should" again. I think people generally agree that it would be nice if users did not need to know anything about their hardware to get FreeBSD working. I think people also generally agree that there are many common situations where users will not, in fact, be able to get FreeBSD working if they do not know how their hardware works, or if they are not able to communicate that knowledge to the device configuration code. I don't think people generally understand, though, exactly how new-bus addresses the manual configuration problem, nor do people generally understand exactly how newconfig handles the automatic configuration problem. Could we get specific details on these specific points from the respective designers? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 8:50:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from iglou.com (iglou3.iglou.com [192.107.41.6]) by hub.freebsd.org (Postfix) with ESMTP id 8C59F15570 for ; Mon, 12 Apr 1999 08:50:23 -0700 (PDT) (envelope-from patrick@cre8tivegroup.com) Received: from [204.255.227.76] (helo=gateway.cre8tivegroup.com) by iglou.com with esmtp (8.9.1/8.9.1) id 10Wiw4-0005sy-00; Mon, 12 Apr 1999 11:47:45 -0400 Content-Length: 1026 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <6546.923926450@critter.freebsd.dk> Date: Mon, 12 Apr 1999 11:47:46 -0400 (EDT) From: Patrick Gardella To: Warner Losh Subject: Re: Flash fs spec Cc: mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a side note, How do you use a flash disk on a laptop. Everywhere I've read says "use it like a floppy", but how do I get that far? I've got it configured with TrueFFS/FTL (http://www.m-sys.com/download.htm) but I can't get FreeBSD to see it. dumpcis doesn't show anything for this card... Patrick In message <199904110419.WAA02071@harmony.village.org>, Warner Losh writes: > >I've found one spec on flash fs, which I'll call msffs, at >microsoft's >web site. This spec dates from 1994 and appears to be the only spec >for msffs available. It specifies the gross 8.3 filenames. I was >wondering if anybody knew of a newer version of this, or if this >representation is even used today. The flash card that I got from >Nate doesn't seem to have any reasonable data on it for me to look >at. > >Warner --- Patrick S. Gardella Director of Web Development The Creative Group 1-800-804-0783 ext 29 606-858-8029 (fax) http://www.cre8tivegroup.com PGP Key ID 0xEE2D47A9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 9: 9:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Bespin.worldnet.net (bespin.worldnet.net [195.3.3.4]) by hub.freebsd.org (Postfix) with ESMTP id B991115525 for ; Mon, 12 Apr 1999 09:09:21 -0700 (PDT) (envelope-from pcasidy@worldnet.fr) Received: from greatoak.home (p14-001.province.worldnet.fr [195.3.14.1]) by Bespin.worldnet.net (8.8.8/8.8.8) with ESMTP id SAA12036 for ; Mon, 12 Apr 1999 18:04:42 +0200 (CEST) Received: (from pcasidy@localhost) by greatoak.home (8.8.8/8.8.8) id SAA02668 for freebsd-mobile@freebsd.org; Mon, 12 Apr 1999 18:08:55 +0200 (CEST) (envelope-from pcasidy) Message-Id: <199904121608.SAA02668@greatoak.home> Date: Mon, 12 Apr 1999 18:08:55 +0200 (CEST) From: Philippe CASIDY Subject: What about a 3Com 3c589EC To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, My kernel is 3.1R with the upgrade package. I have recently bought a 3Com Megahertz 3Com 3c589EC. This is a 3C589E + combo adaptator for Base10/Base2. I have modified the pccard.conf (copied the settings for 3C589D) and booted! And I have a "driver allocation failed for 3Com" One strange behavior is that when I insert the card, I have the following message: /kernel: Card inserted, slot 3 slot3!??? If I replace the 3C589E by a 3C589D (also with a combo connector), I just have the message about the card being inserted! But I have nothing more with 'ifconfig -a'. I have to reboot to have "driver allocation failed for 3Com Corporation" Please help, I am in the big ... if neither 589D nor 589E works!!! Phil. P.S.: on box is written "Linux" and several line under "Advanced networking OS". ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 9:57:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (Postfix) with ESMTP id F376214EF4 for ; Mon, 12 Apr 1999 09:57:38 -0700 (PDT) (envelope-from bwithrow@engeast.BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id MAA07081; Mon, 12 Apr 1999 12:57:04 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id MAA10613; Mon, 12 Apr 1999 12:52:16 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.68.38]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id MAA15163; Mon, 12 Apr 1999 12:54:42 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.8/8.8.8) with ESMTP id MAA29439; Mon, 12 Apr 1999 12:54:09 -0400 (EDT) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199904121654.MAA29439@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: NAKAGAWA Yoshihisa , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: Message from Mike Smith of "Fri, 09 Apr 1999 15:43:33 PDT." <199904092243.PAA00954@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Apr 1999 12:54:09 -0400 From: Robert Withrow Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org mike@smith.net.au said: :- My point is that it is not useful to treat the PCIC as an ISA device. :- It should be treated as a bus bridge. That is the key point, I think. That is, incidentally, exactly how Windows treats it also... -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 11:20:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id BAB0A14D6D for ; Mon, 12 Apr 1999 11:20:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA43813; Mon, 12 Apr 1999 19:20:55 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 19:20:54 +0100 (BST) From: Doug Rabson To: Tomoaki NISHIYAMA Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-Reply-To: <19990412200631T.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, Tomoaki NISHIYAMA wrote: > From: Doug Rabson > Subject: Re: Any success with CirrusLogic 6729/6730??? > Date: Mon, 12 Apr 1999 11:03:44 +0100 (BST) > Message-ID: > > dfr> This is not correct. A driver can be trivially split up into attachment > dfr> points and implementations. The interface definition system can actually > dfr> make this easier (IMHO of course). The mcclock driver in FreeBSD/alpha > dfr> (derived from the NetBSD driver) does this. > More precicely, is the split driver *dynamically* loadable? > The bus independent part, mcclock.c seemes to be linked statically, > putting aside whethere there is any merit to load the clock dynamically. A split driver can be dynamically loaded by using the dependancy mechanism on the KLD modules. Imagine a device foo which support pci and isa attachments. One could build three modules: foo.ko containing the core driver functionality foo_isa.ko probe/attach for isa bus foo_pci.ko probe/attach for pci bus The two bus-specific modules would depend on the foo.ko module ensuring that it is loaded automatically if either bus-specific module is used. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 11:41:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 3B95E14D0F for ; Mon, 12 Apr 1999 11:41:23 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id UAA22911; Mon, 12 Apr 1999 20:38:18 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma022909; Mon, 12 Apr 99 20:38:08 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id UAA21125; Mon, 12 Apr 1999 20:38:08 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904121838.UAA21125@helena.otelo-call.de> Subject: Re: pcmcia ethernet installation trouble In-Reply-To: <19990410171843M.tomoaki@moss.nibb.ac.jp> from Tomoaki NISHIYAMA at "Apr 10, 99 05:18:43 pm" To: tomoaki@biol.s.u-tokyo.ac.jp (Tomoaki NISHIYAMA) Date: Mon, 12 Apr 1999 20:38:07 +0200 (MET DST) Cc: freebsd-mobile@freebsd.org, bsd-nomads@clave.gr.jp X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, > From: Christoph Weber-Fahr [trying to install from boot-pao.flp (2.2.8) via a Fiberline FL-4680 ethernet card on a Toshiba T1910. Problem is - ed0 doesn't turn up as a device in the setup dialogue] > > Hi, > > There is debug output on the second console screen. Anything to look for ? > What is on the screen? [writtten down from screen. Typos are mine] DEBUG: ioctl(3,TIOCCONS,NULL)=0 (success) Card Inserted, slot0 DEBUG: Term = cons25 Code 240, not found Code 240, not found code unknown, ignored DEBUG: found a network device named lp0 DEBUG: found a floppy device for /dev/fd0 DEBUG: found a disk device named wd0 DEBUG: found a dos partition wd0s2 on drive wd0 > Do you have any information on what the pcic chip is? Unfortunately not. I don't have manuals of the machine, and the manual Text on Toshiba's Web Site doesn't say much either: PCMCIA slot: 14.5mm PCMCIA Version 2.01 compliant slot supports [Illustration] Type I, II, or III cards, such as modems and removable hard disk drives. Maximum slot thickness: 16mm > And if you have any operating system, maybe windows, on the machine, > can you tell what the pcic is recognized by the system? I have W95 OSR2 there. It says: Standard PCMCIA Driver. I did not find a more pricise information. Is there a place where it gives more information ? > You may also check what irq and address they are assigned? 11, 3E0-3E1 > And the next question is how do you know that the card is > recognized and assined to ed0. After asking for the usual parameters and the initialization phase it opens a window saying (second line: ... assigned to ed0). > Finally, please mail these to bsd-nomads@clave.gr.jp, Done (note cc:). Regards, and thanks in advance, Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 11:48:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 198B5155B8 for ; Mon, 12 Apr 1999 11:48:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 2CB331F4F; Tue, 13 Apr 1999 02:45:56 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Tomoaki NISHIYAMA , y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, dcs@newsguy.com, nate@mt.sri.com, faber@ISI.EDU, nsayer@quack.kfu.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Mon, 12 Apr 1999 19:20:54 +0100." Date: Tue, 13 Apr 1999 02:45:56 +0800 From: Peter Wemm Message-Id: <19990412184558.2CB331F4F@spinner.netplex.com.au> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > On Mon, 12 Apr 1999, Tomoaki NISHIYAMA wrote: > > dfr> This is not correct. A driver can be trivially split up into attachme nt > > dfr> points and implementations. The interface definition system can actua lly > > dfr> make this easier (IMHO of course). The mcclock driver in FreeBSD/alph a > > dfr> (derived from the NetBSD driver) does this. > > More precicely, is the split driver *dynamically* loadable? > > The bus independent part, mcclock.c seemes to be linked statically, > > putting aside whethere there is any merit to load the clock dynamically. > > A split driver can be dynamically loaded by using the dependancy mechanism > on the KLD modules. Imagine a device foo which support pci and isa > attachments. One could build three modules: > > foo.ko containing the core driver functionality > foo_isa.ko probe/attach for isa bus > foo_pci.ko probe/attach for pci bus > > The two bus-specific modules would depend on the foo.ko module ensuring > that it is loaded automatically if either bus-specific module is used. Of course, it can go in one module or component as well, for example: /* * ISA can be attached to a PCI-ISA bridge or directly to the nexus. */ DRIVER_MODULE(isa, isab, isa_driver, isa_devclass, 0, 0); DRIVER_MODULE(isa, nexus, isa_driver, isa_devclass, 0, 0); Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 12:28:41 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 76BD2158F1 for ; Mon, 12 Apr 1999 12:28:31 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA45774; Mon, 12 Apr 1999 20:29:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 20:29:52 +0100 (BST) From: Doug Rabson To: Michael Robinson Cc: freebsd-mobile@freebsd.org Subject: Re: new-bus/newconfig (was: Any success) In-Reply-To: <199904121442.WAA00575@netrinsics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, Michael Robinson wrote: > Doug Rabson writes: > >The reason device attachment points are not specified in the config file > >is that I don't think the user should need to care how the hardware in > >their machine works in order to get FreeBSD working. > > There's that "should" again. > > I think people generally agree that it would be nice if users did not need > to know anything about their hardware to get FreeBSD working. I think people > also generally agree that there are many common situations where users will > not, in fact, be able to get FreeBSD working if they do not know how their > hardware works, or if they are not able to communicate that knowledge to the > device configuration code. > > I don't think people generally understand, though, exactly how new-bus > addresses the manual configuration problem, nor do people generally understand > exactly how newconfig handles the automatic configuration problem. > > Could we get specific details on these specific points from the respective > designers? Manual configuration is done via 'probe hints' which are currently prepared by config(8) but could be changed in the future to be loaded from a text file by the bootstrap. A probe hint is just a familiar device instance declaration, e.g.: controller ppc0 at isa? port ? tty irq 7 This information is stored in a very simple 'database' (I use the word extremely loosely) which is bus-architecture neutral. As the ISA bus device is probed, it queries the database for a list of devices to probe. The same database could be easily used for 'device wiring' e.g. making sure the fxp device at pci bus 0, slot 7 is always given unit 0 might look like this (if I implement this feature): device fxp0 at pci0 slot 7 -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 13:34:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Bespin.worldnet.net (bespin.worldnet.net [195.3.3.4]) by hub.freebsd.org (Postfix) with ESMTP id 4BE8214CC2 for ; Mon, 12 Apr 1999 13:34:53 -0700 (PDT) (envelope-from pcasidy@worldnet.fr) Received: from greatoak.home (p14-030.province.worldnet.fr [195.3.14.30]) by Bespin.worldnet.net (8.8.8/8.8.8) with ESMTP id WAA18207 for ; Mon, 12 Apr 1999 22:30:12 +0200 (CEST) Received: (from pcasidy@localhost) by greatoak.home (8.8.8/8.8.8) id WAA10354 for freebsd-mobile@FreeBSD.ORG; Mon, 12 Apr 1999 22:34:26 +0200 (CEST) (envelope-from pcasidy) Message-Id: <199904122034.WAA10354@greatoak.home> Date: Mon, 12 Apr 1999 22:34:26 +0200 (CEST) From: Philippe CASIDY Subject: Fwd: Re: What about a 3Com 3c589EC To: freebsd-mobile@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ------ Forwarded message ------ From: Philippe CASIDY Subject: Re: What about a 3Com 3c589EC Date: Mon, 12 Apr 1999 22:16:17 +0200 (CEST) To: scott@dcs.qmw.ac.uk Cc: freebsd-mobile@FreeBSD.OR On 12 Apr, Scott Mitchell wrote: > You may have been bitten by the (im)famous 'pcic double loading' bug. You Yes I remind something about that in previous mails! I will check that. > As for the allocation failure, you need to make sure you're giving pccardd > the correct information. Run 'pccardc dumpcis', and look for tuple code > 0x15 in the ream of output that should be produced. For example, on my > Xircom CE3 card, I see the following: > I have done that, otherwise I would have a message about no entry in the database (or something similar). In fact, for the moment, I am trying to get the 3C589D working using the ep driver as I used to do with 2.2.8R. I have been able to make it recognize (as the 589E too with a little hack in if_zp.c ) with zp driver but not with the ep one! Thanks! Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 14:22: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 58BF714E6F for ; Mon, 12 Apr 1999 14:22:02 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id D73151F4F; Tue, 13 Apr 1999 05:19:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa Cc: Mike Smith , "Daniel C. Sobral" , Nate Williams , Ted Faber , Nick Sayer , freebsd-mobile@FreeBSD.ORG Subject: Re: Any success with CirrusLogic 6729/6730??? In-reply-to: Your message of "Mon, 12 Apr 1999 16:54:25 +0900." <199904120754.QAA09135@chandra.eatell.msr.prug.or.jp> Date: Tue, 13 Apr 1999 05:19:41 +0800 From: Peter Wemm Message-Id: <19990412211943.D73151F4F@spinner.netplex.com.au> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > > This is specifically why we still use hint information from the > > configuration file. The goal, however, is to get away from compiling > > that hint information into the kernel. > > # newconfig members' (me too) opinion below: > > Our newconfig is better than yours new-bus in this point. > Newconfig supports both dynamic configration and static configuration, > so newconfig can do what new-bus can do, and also newconfig can > support particular configurations which new-bus can't. > (e.g. specially tuned kernel for particular purpose.) This is not correct. Perhaps you are misunderstanding what we're trying to do. Under newconfig, the static (or fixed) configuration is compiled into the binaries. What we're trying to do is get that out of the binaries and get the information from elsewhere. Part of that can come from probing, part comes from the drivers themselves (they know what they can attach to), and part comes from the fixed configuration fetched from somewhere else. In our case, this would probably come from the loader(8) as a plain text file in /boot. In other words, we would not be loosing any ability to specify particular configurations or to lock down unit numbers etc, but with new-bus you would not have to recompile the kernel to change an IRQ for an ISA card, you would just edit /boot/isa.conf or something like that. In fact, we can probably change the configuration at runtime for things like isa cards. Imagine a generic NE2000 card without PnP that you are not sure of the settings. Suppose you take a guess and when the system boots, it doesn't find it because you guessed the wrong IO port. Since the static/ fixed/whatever ISA config would have been loaded and would be changeable at runtime, it would be possible to change the base port and force a reprobe with the new settings. You could try several times before guessing right, without any kernel recompiles or reboots. You could then update the static/fixed config in /boot/isa.conf for the next time. > Also, in newconfig case, we don't have to load the code which support > an ISA PCIC, if only an PCI PCIC code is needed, because we split an > PCIC driver to three part, an ISA attachment, an PCI attachment, and > bus independent shared part. In new-bus case, we suppose that you > have to load both the code which supports an PCI PCIC and the code > which supports an ISA PCIC. So, newconfig kernel is smaller and > faster to boot and more dynamic than new-bus. It's the same as new-bus, there is no difference at all. You can have the bus-specific parts in seperate modules and use the dependencies to load it with a single command. Or, if you want to keep the number of modules minimized, you can put them all in the same module. You have the choice. For a single kernel image, the present config(8) skeleton doesn't know about 'and' clauses, but this would be fixed at some point. (ie: if the buslogic driver is split into bt.c, bt_isa.c bt_pci.c bt_eisa.c, config isn't smart enough to know that 'controller bt0' when you don't have an eisa bus then you can leave out the bt_eisa.c component. The present hack is to use an #ifdef, but that isn't very good. This will get revisited. This is a weakness in the config(8) hack, not a weakness in new-bus.) > Especially because new-bus doesn't have the feature to treat the > shared part of the device driver like this. Yes it does.. The kld loader was originally written with dependency support with things like this in mind. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 12 18:41:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id E680314DA0 for ; Mon, 12 Apr 1999 18:41:28 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id KAA06547; Tue, 13 Apr 1999 10:39:07 +0900 (JST) Date: Tue, 13 Apr 1999 10:39:07 +0900 (JST) Message-Id: <199904130139.KAA06547@afs.ntc.mita.keio.ac.jp> To: andrsn@andrsn.stanford.edu, mobile@freebsd.org Cc: hosokawa@ntc.keio.ac.jp Subject: Re: Floppies with Pccard Support In-Reply-To: Your message of "Mon, 12 Apr 1999 13:58:39 JST". <199904120458.NAA24629@afs.ntc.mita.keio.ac.jp> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199904120458.NAA24629@afs.ntc.mita.keio.ac.jp> hosokawa@ntc.keio.ac.jp writes: >> I also built 3.1-RELEASE (with PAO3) boot.flp, kern.flp, and >> mfsroot.flp this morning. This problem (about interface detection) >> comes from release/sysinstall/devices.c and I've fixed it, I will put >> it somewhere when I finished the test of it. I put these files at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/boot.flp ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/kern.flp ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/mfsroot.flp And, I also put PAO binary distribution files at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/paobin/ ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/paosrc/ and the tarball of these distribution files at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/paodist.tar I'll put the source tarball later. This floppy uses a very small patch to sysinstall and -z option (wait until pccard slots are initialized, and be a daemon) of PAO pccardd. These patches are too small and I want to merge them to -current. I'll post the patch against -current to -mobile later. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 13 5:22:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from iglou.com (iglou1.iglou.com [192.107.41.3]) by hub.freebsd.org (Postfix) with ESMTP id 068F7155A3; Tue, 13 Apr 1999 05:22:43 -0700 (PDT) (envelope-from patrick@cre8tivegroup.com) Received: from [204.255.227.70] (helo=gateway.cre8tivegroup.com) by iglou.com with esmtp (8.9.1/8.9.1) id 10X2Ao-00052S-00; Tue, 13 Apr 1999 08:20:15 -0400 Content-Length: 2718 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904130620.CAA04175@pinky.us.net> Date: Tue, 13 Apr 1999 08:20:11 -0400 (EDT) From: Patrick Gardella To: Brian Skrab Subject: RE: PCMCIA in a Notebook ??? Cc: freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Apr-99 Brian Skrab wrote: > Hello, > >I have a Fujitsu notebook with a fresh copy of FreeBSD 2.2.8 >installed on it. I have a D-Link DFE-650 10/100 PCMCIA NIC sitting >in one of the card slots, but cannot figure out how to get FreeBSD >to detect it. Should I try to find a way to set the resources on >the card? Is there some special tweak that's needed to get FreeBSD >to detect PCMCIA cards? Does FreeBSD even support PCMCIA NICs? Do >I need a new "supported" NIC? Yes, PCMCIA NICs are supported in FreeBSD. You need to configure /etc/pccard.conf to make the card work. And make sure you have support compiled into the kernel: # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? Finally, in /etc/rc.conf, you have to enable pccard: pccard_enable="YES" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ifconfig="change to match your card" # Specialized pccard ethernet configuration (or NO). However, your NIC is not listed in the pccard.conf.sample file, so that means no one has tried it and if they have, they might not have gotten it to work. So will yours work? Maybe. You'll have to try it. Do all the above and then start working on making it work. To see if it will work, run: pccardc dumpcis > pccard.info This will dump the card information to a file pccard.info. In there, you will see tuples describing different configuration possibilities. (My laptop is at home or I would include one.) Look for one like 0x20 (may be a different number). It will tell you an IRQ, and other information. The card identifier at the top will tell you what it refers to itself as. Use these to make your configuration in /etc/pccard.conf. As an example, my Accton 2216 has a configuration of: card "ACCTON" "EN2216-PCMCIA-ETHERNET" config 0x20 "ed0" 10 insert echo Accton 2216 inserted insert /etc/pccard_ether ed0 remove echo Accton 2216 removed remove /sbin/ifconfig ed0 delete You may have to try other ethernet drivers than "ed0" to make it work. But if its an NE 2000 compatible, ed0 is a good place to start. One other thing, the configuration of the card must match whats in the kernel. So if you have IRQ 10 in the kernel and IRQ 7 in the /etc/pccard.conf, it won't work. I've cross posted this to -mobile, since that's the place to ask for laptop support. Patrick --- Patrick S. Gardella Director of Web Development The Creative Group 1-800-804-0783 ext 29 606-858-8029 (fax) http://www.cre8tivegroup.com PGP Key ID 0xEE2D47A9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 13 10: 0:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Bespin.worldnet.net (bespin.worldnet.net [195.3.3.4]) by hub.freebsd.org (Postfix) with ESMTP id F09F914D53 for ; Tue, 13 Apr 1999 10:00:30 -0700 (PDT) (envelope-from pcasidy@worldnet.fr) Received: from greatoak.home (p15-217.province.worldnet.fr [195.3.15.217]) by Bespin.worldnet.net (8.8.8/8.8.8) with ESMTP id SAA16393; Tue, 13 Apr 1999 18:55:49 +0200 (CEST) Received: (from pcasidy@localhost) by greatoak.home (8.8.8/8.8.8) id SAA00570; Tue, 13 Apr 1999 18:41:38 +0200 (CEST) (envelope-from pcasidy) Message-Id: <199904131641.SAA00570@greatoak.home> Date: Tue, 13 Apr 1999 18:41:38 +0200 (CEST) From: Philippe CASIDY Subject: Solve! (was: Re: What about a 3Com 3c589EC) To: scott@dcs.qmw.ac.uk Cc: freebsd-mobile@FreeBSD.ORG In-Reply-To: <19990412173659.J1478@dcs.qmw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12 Apr, Scott Mitchell wrote: > On Mon, Apr 12, 1999 at 06:08:55PM +0200, Philippe CASIDY wrote: >> Hello, >> >> My kernel is 3.1R with the upgrade package. >> I have recently bought a 3Com Megahertz 3Com 3c589EC. This is a 3C589E >> + combo adaptator for Base10/Base2. >> >> I have modified the pccard.conf (copied the settings for 3C589D) and >> booted! >> >> And I have a "driver allocation failed for 3Com" >> >> One strange behavior is that when I insert the card, I have the >> following message: >> /kernel: Card inserted, slot 3 >> I am able to make 3C589D and 3C589EC under 2.2.8R. My problem was that the controller eisa0 was missing in my configuration file! Now, I have upgraded from 3.1R to 2.2.8R ( ;-) ) I have to upgrade once again from 2.2.8R to 3.1R. I am curious to know I there was a way to make it work without eisa0 ? Thanks. Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 13 12:42:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hewassoc-bh.hewitt.com (hewassoc-bh.hewitt.com [204.167.173.66]) by hub.freebsd.org (Postfix) with ESMTP id 29E3814F0D for ; Tue, 13 Apr 1999 12:42:35 -0700 (PDT) (envelope-from JWVEHRS@hewitt.com) Received: (from uucp@localhost) by hewassoc-bh.hewitt.com (8.8.8/8.6.11) id OAA02096 for ; Tue, 13 Apr 1999 14:40:13 -0500 (CDT) Received: from l98ong6.hewitt.com(207.122.224.2) by hewassoc-bh.hewitt.com via smap (4.1) id xmak29067; Tue, 13 Apr 99 14:35:38 -0500 Received: by l98ong6.hewitt.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 86256752.006BA4F5 ; Tue, 13 Apr 1999 14:35:45 -0500 X-Lotus-FromDomain: HEWITT ASSOCIATES NA From: "Jeff Vehrs" To: freebsd-mobile@freebsd.org Message-ID: <86256752.006A4C42.00@l98ong6.hewitt.com> Date: Tue, 13 Apr 1999 14:34:35 -0500 Subject: Thinkpad 560 -- 2.2.6 ==> 2.2.8 or 3.1?? Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I finally installed 2.2.6-RELEASE on the laptop Thinkpad 560 via floppy disks & lp0. Whew! I just updated ports - that's an easy one. Now, I'd like to know what's the correct procedure to update 2.2.6 ==> either 2.2.8 or 3.1 via CVSup. Also, do I have to reinstall PAO after make world or upgrade? This is my vision of update my laptop from 2.2.6-RELEASE to 2.2.8-STABLE. 1. update my system via CVsup with tag=RELENG_2_2 2. make world 3. use /stand/sysinstall to reinstall PAO stuff 4. reboot Will that works? Or, is there a better alternative? Thanks. // Jeff // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 13 13:58:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 2655114EAC for ; Tue, 13 Apr 1999 13:58:02 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id OAA03905; Tue, 13 Apr 1999 14:53:01 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Tue, 13 Apr 1999 14:53:01 -0600 (MDT) From: Brian Handy To: Jeff Vehrs Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 560 -- 2.2.6 ==> 2.2.8 or 3.1?? In-Reply-To: <86256752.006A4C42.00@l98ong6.hewitt.com> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >This is my vision of update my laptop from 2.2.6-RELEASE to 2.2.8-STABLE. > > 1. update my system via CVsup with tag=RELENG_2_2 > 2. make world > 3. use /stand/sysinstall to reinstall PAO stuff > 4. reboot >Will that works? Or, is there a better alternative? I'm running several TP560's on 2.2-STABLE, and none of them require PAO. So, Yes it Works. Good luck, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 8:47:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (Postfix) with ESMTP id B39F2152B7 for ; Wed, 14 Apr 1999 08:47:47 -0700 (PDT) (envelope-from rsmith@trltech.co.uk) Received: from trltech.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id QAA13809 for ; Wed, 14 Apr 1999 16:45:23 +0100 (BST) (envelope-from rsmith@trltech.co.uk) Message-ID: <3714B870.B1AC213D@trltech.co.uk> Date: Wed, 14 Apr 1999 16:46:56 +0100 From: Richard Smith Reply-To: richard@jezebel.demon.co.uk Organization: http://www.trltech.co.uk/ X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "FreeBSD, Mobile" Subject: Cirrus Logic 6729/6730 port address? Content-Type: multipart/mixed; boundary="------------17AA852D3B0A270FEDBB2CED" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------17AA852D3B0A270FEDBB2CED Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello again, After advice from Chung-Kie Tung, I have installed the PAO3-beta package. However, my controller does not appear to be at the default port addresses or at the 0xfcfc port address that was successful for Chung-Kie Tung. I have attached my dmesg.boot file in the hope that it may help to determine where I am likely to find the controller. Any other suggestions also welcome :) Thanks, Richard. --------------17AA852D3B0A270FEDBB2CED Content-Type: text/plain; charset=us-ascii; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #4: Tue Apr 13 16:36:48 BST 1999 richard@notebook.wan:/usr/src/sys/compile/NOTEBOOK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (120.27-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 38129664 (37236K bytes) Preloaded elf kernel "kernel" at 0xf02b7000. Probing for devices on PCI bus 0: chip0: rev 0xb0 on pci0.0.0 vga0: rev 0x00 on pci0.17.0 chip1: rev 0xb2 on pci0.18.0 ide_pci0: rev 0x10 on pci0.18.1 pcic0: rev 0xfe int a irq 255 on pci0.23.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 777MB (1591632 sectors), 1579 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordis acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 on isa ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 ep0 not found at 0x300 sn0 not found at 0x300 wlp0 not found at 0x300 cnw0 not found at 0x300 pcic0 not found at 0x3e0 pcic0 not found at 0x3e4 pcic1 not found at 0x3e2 pcic1 not found at 0x3e4 pcic0 not found at 0xfcfc vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 joy0 at 0x201 on isa joy0: joystick Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a --------------17AA852D3B0A270FEDBB2CED-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 10: 4:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 3F44214DC5 for ; Wed, 14 Apr 1999 10:04:43 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id JAA04134; Wed, 14 Apr 1999 09:56:25 -0700 (PDT) Date: Wed, 14 Apr 1999 09:56:25 -0700 (PDT) From: Annelise Anderson To: Patrick Gardella Cc: Brian Skrab , freebsd-mobile@FreeBSD.ORG Subject: RE: PCMCIA in a Notebook ??? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote up a short how-to on getting pccards to work that's on my web page at http://andrsn.stanford.edu/FreeBSD/pccards.html. Annelise On Tue, 13 Apr 1999, Patrick Gardella wrote: > > On 13-Apr-99 Brian Skrab wrote: > > Hello, > > > >I have a Fujitsu notebook with a fresh copy of FreeBSD 2.2.8 > >installed on it. I have a D-Link DFE-650 10/100 PCMCIA NIC sitting > >in one of the card slots, but cannot figure out how to get FreeBSD > >to detect it. Should I try to find a way to set the resources on > >the card? Is there some special tweak that's needed to get FreeBSD > >to detect PCMCIA cards? Does FreeBSD even support PCMCIA NICs? Do > >I need a new "supported" NIC? > > Yes, PCMCIA NICs are supported in FreeBSD. > > You need to configure /etc/pccard.conf to make the card work. And make > sure you have support compiled into the kernel: > > # PCCARD (PCMCIA) support > controller card0 > device pcic0 at card? > device pcic1 at card? > > Finally, in /etc/rc.conf, you have to enable pccard: > > pccard_enable="YES" # Set to YES if you want to configure PCCARD > devices. > pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory > address. > pccard_ifconfig="change to match your card" # Specialized pccard > ethernet configuration (or NO). > > However, your NIC is not listed in the pccard.conf.sample file, so that > means no one has tried it and if they have, they might not have gotten > it to work. So will yours work? Maybe. You'll have to try it. Do > all the above and then start working on making it work. > > To see if it will work, run: > pccardc dumpcis > pccard.info > > This will dump the card information to a file pccard.info. In there, > you will see tuples describing different configuration possibilities. > (My laptop is at home or I would include one.) > > Look for one like 0x20 (may be a different number). It will tell you > an IRQ, and other information. The card identifier at the top will > tell you what it refers to itself as. Use these to make your > configuration in /etc/pccard.conf. As an example, my Accton 2216 has a > configuration of: > > card "ACCTON" "EN2216-PCMCIA-ETHERNET" > config 0x20 "ed0" 10 > insert echo Accton 2216 inserted > insert /etc/pccard_ether ed0 > remove echo Accton 2216 removed > remove /sbin/ifconfig ed0 delete > > You may have to try other ethernet drivers than "ed0" to make it work. > But if its an NE 2000 compatible, ed0 is a good place to start. > > One other thing, the configuration of the card must match whats in the > kernel. So if you have IRQ 10 in the kernel and IRQ 7 in the > /etc/pccard.conf, it won't work. > > I've cross posted this to -mobile, since that's the place to ask for > laptop support. > > Patrick > > --- > Patrick S. Gardella Director of Web Development > The Creative Group 1-800-804-0783 ext 29 606-858-8029 (fax) > http://www.cre8tivegroup.com PGP Key ID 0xEE2D47A9 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 10:53:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hewassoc-bh.hewitt.com (hewassoc-bh.hewitt.com [204.167.173.66]) by hub.freebsd.org (Postfix) with ESMTP id E6ADA15400 for ; Wed, 14 Apr 1999 10:53:18 -0700 (PDT) (envelope-from JWVEHRS@hewitt.com) Received: (from uucp@localhost) by hewassoc-bh.hewitt.com (8.8.8/8.6.11) id MAA02576; Wed, 14 Apr 1999 12:50:56 -0500 (CDT) Received: from l98ong6.hewitt.com(207.122.224.2) by hewassoc-bh.hewitt.com via smap (4.1) id xmac00185; Wed, 14 Apr 99 12:48:48 -0500 Received: by l98ong6.hewitt.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 86256753.0061E628 ; Wed, 14 Apr 1999 12:49:19 -0500 X-Lotus-FromDomain: HEWITT ASSOCIATES NA From: "Jeff Vehrs" To: handy@lambic.physics.montana.edu Cc: freebsd-mobile@freebsd.org Message-ID: <86256753.006060CD.00@l98ong6.hewitt.com> Date: Wed, 14 Apr 1999 12:48:13 -0500 Subject: Re: Thinkpad 560 -- 2.2.6 ==> 2.2.8 or 3.1?? Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> and none of them require PAO. << Without PAO?!! Wow. I need PAO to get my modem, Megahertz XJ4336-CC4336, to work. Oh, since we have the same kind of laptop, TP560. Did you see the error message during the bootup? Syslog 128 code(something likes that). I was able to stop it by remove the modem card before the bootup. Were you able to remove this error problem permanently? Anyway, I'm still not comfortable with it. I've tried it once. It didn't work well after 'make world'. I guess I'll keep trying until I get it. Thanks for your quick reply. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 11: 2:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id CAE4D15057 for ; Wed, 14 Apr 1999 11:02:25 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id LAA08841; Wed, 14 Apr 1999 11:57:22 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Wed, 14 Apr 1999 11:57:22 -0600 (MDT) From: Brian Handy To: Jeff Vehrs Cc: freebsd-mobile@freebsd.org Subject: Re: Thinkpad 560 -- 2.2.6 ==> 2.2.8 or 3.1?? In-Reply-To: <86256753.006060CD.00@l98ong6.hewitt.com> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> and none of them require PAO. << > >Without PAO?!! Wow. I need PAO to get my modem, Megahertz XJ4336-CC4336, to >work. Really? Huh...I think I've used this modem. I see an entry for it in /etc/pccard.conf.sample even. How about sending me the output of 'pccard dumpcis'? I don't remember the syslog 123 code error, I wonder if I didn't read far enough. Re-send that too and I'll think about it. May have to wait a day or two if I don't immediately figure it out -- I'm on travel tomorrow and pretty much unavailable until Sunday, but this should Just Work. In fact, I went through a phase with my machines (I have a couple of desktops) where the *only* box that would successfully complete a 'make world' was the laptop... :-) Talk to you soon! Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 13:30: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moran.grauel.com (moran.grauel.com [199.233.104.44]) by hub.freebsd.org (Postfix) with ESMTP id 465E415867 for ; Wed, 14 Apr 1999 13:30:01 -0700 (PDT) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.2) id PAA02328; Wed, 14 Apr 1999 15:27:50 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14100.64070.526973.198789@moran.grauel.com> Date: Wed, 14 Apr 1999 15:27:50 -0500 (EST) To: freebsd-mobile@freebsd.org Subject: ActionTec DataLink modem and a new laptop: FreeBSD 3.1 X-Mailer: VM 6.70 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm feeling particularly dense right now, so I'm asking for help. I just got a new BSI laptop and an ActionTec DataLink V.90 modem, and I can't seem to make it work. Are there step-by-step instructions anywhere? This is the first time I've tried to use a pc-card (I've never felt the urge for a laptop before), and I'm not familiar enough with them to figure out where I'm going wrong. I've disabled the infra-red port since I can't (currently) use it under FreeBSD, and I believe I've got everything configured appropriately (I've copied /etc/pccard.conf.sample to /etc/pccard.conf, since this modem is listed), and pccardd identifies the modem card whenever I reboot. However, attempting to use it (via kermit, on /dev/cuaa1) seems to disable my keyboard. I can switch virtual terminals, but nothing I type ever appears anywhere. I've removed (per the comments at the beginning of pccard.conf.sample) the entry for irq 5. Am I just doing something stupid, or should I be installing PAO? Any help (including pointers to documentation) would be greatly appreciated. If it's something more than my ignorance, I'll be happy to post configuration files/dmesg output on request. TIA. - Rich -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 14:34:42 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from k12-nis-2.bbn.com (K12-NIS-2.BBN.COM [128.89.6.195]) by hub.freebsd.org (Postfix) with ESMTP id 71D3D15915; Wed, 14 Apr 1999 14:34:35 -0700 (PDT) (envelope-from dm@k12-nis-2.bbn.com) Received: from k12-nis-2.bbn.com (dm@LOCALHOST.BBN.COM [127.0.0.1]) by k12-nis-2.bbn.com (8.9.0/8.9.0) with ESMTP id RAA06351; Wed, 14 Apr 1999 17:31:03 -0400 (EDT) Message-Id: <199904142131.RAA06351@k12-nis-2.bbn.com> To: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Reply-To: dm@bbn.com Date: Wed, 14 Apr 1999 17:31:03 -0400 From: david mankins Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just installed 3.1-RELEASE on a system that was running 2.2.8 (with KAME's IPSEC) quite happily. The machine is a Hitachi Visionbook Pro 7560 (a laptop). The kernel that comes off the 3.1 CDROM works fine, except it's missing Advanced Power Management, and I prefer to suspend my computer before putting it into the bag instead of halting it. So I recompiled a kernel, copying GENERIC to APM and enabling APM but making no other changes. *That* kernel comes up and says: Apr 9 20:28:59 rsm /kernel: display device> rev 0xc2 on pci0.2.0 Apr 9 20:28:59 rsm /kernel: chip3: rev 0x01 int a irq 10 on pci0.10.0 Apr 9 20:28:59 rsm /kernel: chip4: rev 0x01 int b irq 255 on pci0.10.1 Apr 9 20:28:59 rsm /kernel: lnc1: rev 0x16 int a irq 10 on pci0.11.0 Apr 9 20:28:59 rsm /kernel: lnc1: Memory allocated above 16Mb limit This message about 16Mb is new, the off-the-CDROM kernel didn't print it (and I never saw it while running 2.2.8). Since this is a PCI device it ought not matter? (That's what the comment in the device driver says, anyway.) Apr 9 20:28:59 rsm /kernel: lnc1: PCnet-PCI II address 00:00:e1:09:7b:87 Apr 9 20:28:59 rsm /kernel: Probing for devices on PCI bus 1: Apr 9 20:28:59 rsm /kernel: Probing for devices on PCI bus 2: Apr 9 20:28:59 rsm /kernel: Probing for devices on the ISA bus: Apr 9 20:28:59 rsm /kernel: sc0 on isa .... Once the system comes up, the lnc driver is very unhappy: Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 11 times Apr 9 20:29:01 rsm /kernel: lnc1: Device timeout -- Resetting Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 2 times Apr 9 20:29:01 rsm /kernel: lnc Apr 9 20:29:01 rsm /kernel: 1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 21 times Apr 9 20:29:01 rsm /kernel: lnc1: Missed p Apr 9 20:29:01 rsm /kernel: acket -- no receive buffer Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer and I can't get much in the way of network traffic in or out. - What is the config file for the kernel that comes on the CDROM? Isn't it GENERIC? - Does anyone have a fix for this? - david mankins (dm@bbn.com, dm@world.std.com, phone(US): 617-873-2873) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 14:37:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from k12-nis-2.bbn.com (K12-NIS-2.BBN.COM [128.89.6.195]) by hub.freebsd.org (Postfix) with ESMTP id 2CE9315824; Wed, 14 Apr 1999 14:37:33 -0700 (PDT) (envelope-from dm@k12-nis-2.bbn.com) Received: from k12-nis-2.bbn.com (dm@LOCALHOST.BBN.COM [127.0.0.1]) by k12-nis-2.bbn.com (8.9.0/8.9.0) with ESMTP id RAA06454; Wed, 14 Apr 1999 17:34:02 -0400 (EDT) Message-Id: <199904142134.RAA06454@k12-nis-2.bbn.com> To: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: lnc1: Memory allocated above 16Mb limit/Hitachi visionbook Reply-To: dm@bbn.com Date: Wed, 14 Apr 1999 17:34:01 -0400 From: david mankins Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [I apologize for sending this message out without a subject line --- dm] I've just installed 3.1-RELEASE on a system that was running 2.2.8 (with KAME's IPSEC) quite happily. The machine is a Hitachi Visionbook Pro 7560 (a laptop). The kernel that comes off the 3.1 CDROM works fine, except it's missing Advanced Power Management, and I prefer to suspend my computer before putting it into the bag instead of halting it. So I recompiled a kernel, copying GENERIC to APM and enabling APM but making no other changes. *That* kernel comes up and says: Apr 9 20:28:59 rsm /kernel: display device> rev 0xc2 on pci0.2.0 Apr 9 20:28:59 rsm /kernel: chip3: rev 0x01 int a irq 10 on pci0.10.0 Apr 9 20:28:59 rsm /kernel: chip4: rev 0x01 int b irq 255 on pci0.10.1 Apr 9 20:28:59 rsm /kernel: lnc1: rev 0x16 int a irq 10 on pci0.11.0 Apr 9 20:28:59 rsm /kernel: lnc1: Memory allocated above 16Mb limit This message about 16Mb is new, the off-the-CDROM kernel didn't print it (and I never saw it while running 2.2.8). Since this is a PCI device it ought not matter? (That's what the comment in the device driver says, anyway.) Apr 9 20:28:59 rsm /kernel: lnc1: PCnet-PCI II address 00:00:e1:09:7b:87 Apr 9 20:28:59 rsm /kernel: Probing for devices on PCI bus 1: Apr 9 20:28:59 rsm /kernel: Probing for devices on PCI bus 2: Apr 9 20:28:59 rsm /kernel: Probing for devices on the ISA bus: Apr 9 20:28:59 rsm /kernel: sc0 on isa .... Once the system comes up, the lnc driver is very unhappy: Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 11 times Apr 9 20:29:01 rsm /kernel: lnc1: Device timeout -- Resetting Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 2 times Apr 9 20:29:01 rsm /kernel: lnc Apr 9 20:29:01 rsm /kernel: 1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer Apr 9 20:29:01 rsm last message repeated 21 times Apr 9 20:29:01 rsm /kernel: lnc1: Missed p Apr 9 20:29:01 rsm /kernel: acket -- no receive buffer Apr 9 20:29:01 rsm /kernel: lnc1: Missed packet -- no receive buffer and I can't get much in the way of network traffic in or out. - What is the config file for the kernel that comes on the CDROM? Isn't it GENERIC? - Does anyone have a fix for this? - david mankins (dm@bbn.com, dm@world.std.com, phone(US): 617-873-2873) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 16:55:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by hub.freebsd.org (Postfix) with ESMTP id D5A5814DB4 for ; Wed, 14 Apr 1999 16:55:51 -0700 (PDT) (envelope-from michaelr@cisco.com) Received: from cowboy-mr (cowboy-mr.cisco.com [171.70.244.188]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id QAA06080 for ; Wed, 14 Apr 1999 16:53:29 -0700 (PDT) Message-Id: <4.1.19990414164301.00a347d0@pita.cisco.com> X-Sender: michaelr@pita.cisco.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 14 Apr 1999 16:53:24 -0700 To: freebsd-mobile@FreeBSD.ORG From: Michael Reilly Subject: IBM TP 600 In-Reply-To: <36F3F170.6A0B8C36@tinker.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have instructions for installing 2.2.8 or 3.1 on an IBM ThinkPad 600? FreeBSD seems to have problems with the unique memory structure of this machine and so freezes during or shortly after boot. Usually there are three - four beeps before the freeze. My machine has 128MB of memory. When I couldn't get FreeBSD installed I tried BSDI. It failed in the same way until BSDI's tech support told me the MEMSIZ switch is needed at boot time - you specify a value for memory size which is at least 640 kb less than the actual memory installed in the machine. BSDI now runs without any problems FWIW - The comment from the BSDI tech support person was that he thought IBM had 0 bytes of memory on the system board instead of the usual 640kb and that a portion of the extended memory is used as the lower 640 kb by tricks in the hardware. Hence the memory probe during boot finds extended memory which is actually in use by the machine as the bottom 640kb. I'd like to run FreeBSD on my TP 600 but so far no luck. Thanks for any help, michael ---- Michael Reilly michaelr@cisco.com Cisco Systems - Santa Cruz, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 19: 5:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235]) by hub.freebsd.org (Postfix) with ESMTP id 843E714C4F for ; Wed, 14 Apr 1999 19:05:32 -0700 (PDT) (envelope-from nadas@raleigh.ibm.com) Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48]) by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id WAA23124; Wed, 14 Apr 1999 22:03:03 -0400 Received: from roundout (lig32-227-29-135.us.lig-dial.ibm.com [32.227.29.135]) by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with SMTP id WAA35990; Wed, 14 Apr 1999 22:03:02 -0400 Message-Id: <199904150203.WAA35990@rtpmail02.raleigh.ibm.com> From: "Stephen Nadas" To: freebsd-mobile@FreeBSD.ORG, Michael Reilly Date: Wed, 14 Apr 1999 21:56:39 -0400 MIME-Version: 1.0 Content-type: text/enriched; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: IBM TP 600 Reply-To: nadas@raleigh.ibm.com In-reply-to: <4.1.19990414164301.00a347d0@pita.cisco.com> References: <36F3F170.6A0B8C36@tinker.com> X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael, you can try the following (i've not tried it on a 600... so your mileage may vary) -Steve Nadas From: 0000,0000,8000Self < To: 0000,0000,8000Greg Lehey < Subject: 0000,0000,8000Re: System freezes on reboot Copies to: 0000,0000,8000freebsd-mobile@FreeBSD.ORG,Patrick Seal <,Ralf Meyer < Send reply to: 0000,0000,8000nadas@raleigh.ibm.com Date sent: 0000,0000,8000Tue, 16 Mar 1999 23:17:17 -0500 I believe I had this problem w/770 on 2.2.8 with 96MB. I had remove a SIMM, then gen with options "MAXMEM=(97728)" where 97728 is what the bios reports when system powers up to get this to work. do make install, halt, reinstall simm and all is well (no more intermittant freezes) there are some related posts in the mobile archives (look for thinkpad or 770 I forget which) I suspect some weirdness in the IBM bios as 96*1024 != 97728 Regards, Steve Nadas Date sent: Wed, 17 Mar 1999 11:37:26 +1030 From: Greg Lehey <<0000,8000,0000grog@lemis.com> To: Patrick Seal <<0000,8000,0000patseal@hyperhost.net>, Ralf Meyer <<0000,8000,0000ralf@thp.Uni-Duisburg.DE> Copies to: 0000,8000,0000freebsd-questions@FreeBSD.ORG, 0000,8000,0000freebsd- mobile@FreeBSD.ORG Subject: Re: System freezes on reboot Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia 7F00,0000,0000> On Tuesday, 16 March 1999 at 16:28:54 -0500, Patrick Seal wrote: > > > > On Tue, 16 Mar 1999, Ralf Meyer wrote: > > > >> Hello, > >> > >> I encounter the following problem with FreeBSD 3.1 on a ThinkPad 770ED: > >> The machine has 128 MB of RAM. However, if I let FreeBSD determine the > >> amount of RAM or set MAXMEM=128*1024, the machine freezes on every > >> reboot attempt. Occasionally it also freezes during normal operation. > >> Freezing means that even the (so-called) power switch does not work > >> and I have to press the reset button with the help of a ballpen. > >> > >> One solution of the problem is to set the amount of RAM to 96 MB in > >> the kernel configuration file. In that case none of the problems shows > >> up. However I would prefer using the full memory as well as > >> understanding the problem. Is this a known problem? Is it a ThinkPad > >> specific problem? Might there be a memory defect? > >> > >> Opinions, solutions and suggestions are appreciated. > > > > Hmm, Interesting. My Dell Latitude Freezes during a reboot, so does > > someone else's Latitude I know. I never thought that I might be the > > MAXMEM. > > I think you missed the point that Ralf was disabling 32 MB of memory > in order to get it to work at all. > > > I have it in my kernel and my Laptop freezes too. > > > > Any developers have any ideas? > > ISTR hearing something about this before. If you don't get any > answers from the mailing lists, you should enter a PR. man send-pr > for further details. > > Greg > -- > See complete headers for address, home page and phone numbers > finger 0000,8000,0000grog@lemis.com7F00,0000,0000 for PGP public key > > > To Unsubscribe: send mail to 0000,8000,0000majordomo@FreeBSD.org 7F00,0000,0000> with "unsubscribe freebsd-mobile" in the body of the message > Date sent: Wed, 14 Apr 1999 16:53:24 -0700 To: freebsd-mobile@FreeBSD.ORG From: Michael Reilly < Subject: IBM TP 600 7F00,0000,0000> Does anyone have instructions for installing 2.2.8 or 3.1 on an IBM > ThinkPad 600? FreeBSD seems to have problems with the unique memory > structure of this machine and so freezes during or shortly after boot. > Usually there are three - four beeps before the freeze. > > My machine has 128MB of memory. > > When I couldn't get FreeBSD installed I tried BSDI. It failed in the same > way until BSDI's tech support told me the MEMSIZ switch is needed at boot > time - you specify a value for memory size which is at least 640 kb less > than the actual memory installed in the machine. BSDI now runs without any > problems > > FWIW - The comment from the BSDI tech support person was that he thought > IBM had 0 bytes of memory on the system board instead of the usual 640kb > and that a portion of the extended memory is used as the lower 640 kb by > tricks in the hardware. Hence the memory probe during boot finds extended > memory which is actually in use by the machine as the bottom 640kb. > > I'd like to run FreeBSD on my TP 600 but so far no luck. > > Thanks for any help, > > michael > ---- > Michael Reilly michaelr@cisco.com > Cisco Systems - Santa Cruz, CA > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > ip: nadas@raleigh.ibm.com / VM: nadas at rtp/notes: nadas@ibmusm23 +1-919-254-2363 / Tieline: 8-444-2363 / Fax: use X-5483 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 21:14:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 0C14115016 for ; Wed, 14 Apr 1999 21:14:50 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA24842; Wed, 14 Apr 1999 22:12:29 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA09393; Wed, 14 Apr 1999 22:12:28 -0600 Date: Wed, 14 Apr 1999 22:12:28 -0600 Message-Id: <199904150412.WAA09393@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Reilly Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: IBM TP 600 In-Reply-To: <4.1.19990414164301.00a347d0@pita.cisco.com> References: <36F3F170.6A0B8C36@tinker.com> <4.1.19990414164301.00a347d0@pita.cisco.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone have instructions for installing 2.2.8 or 3.1 on an IBM > ThinkPad 600? I just installed FreeBSD 2.2.8 on my TP600E, and it worked fine. However, I needed to make sure APM was disabled or it hangs. I'll look into why that is, but for now it installs. > FreeBSD seems to have problems with the unique memory > structure of this machine and so freezes during or shortly after boot. > Usually there are three - four beeps before the freeze. I am seeing that occasionally, but I don't know what's happening. It'll run fine for 2-3 hours, and then beep 4 times and lockup. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 14 23:32:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id B78AE14F06 for ; Wed, 14 Apr 1999 23:32:38 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA12583; Thu, 15 Apr 1999 08:30:16 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA38627; Thu, 15 Apr 1999 08:30:14 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904150630.IAA38627@greenpeace.grondar.za> To: Richard J Kuhns Cc: freebsd-mobile@freebsd.org Subject: Re: ActionTec DataLink modem and a new laptop: FreeBSD 3.1 In-Reply-To: Your message of " Wed, 14 Apr 1999 15:27:50 EST." <14100.64070.526973.198789@moran.grauel.com> References: <14100.64070.526973.198789@moran.grauel.com> Date: Thu, 15 Apr 1999 08:30:10 +0200 From: Mark Murray Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard J Kuhns wrote: > I've disabled the infra-red port since I can't (currently) use it under > FreeBSD, and I believe I've got everything configured appropriately (I've > copied /etc/pccard.conf.sample to /etc/pccard.conf, since this modem is > listed), and pccardd identifies the modem card whenever I reboot. However, > attempting to use it (via kermit, on /dev/cuaa1) seems to disable my > keyboard. I can switch virtual terminals, but nothing I type ever > appears anywhere. I've removed (per the comments at the beginning of > pccard.conf.sample) the entry for irq 5. I met that problem with that modem. It frequently misprobes as a 8250 UART instead of as a 16550, and when that happens, the machine hangs on first access. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 1: 0:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (Postfix) with ESMTP id 20091150A8 for ; Thu, 15 Apr 1999 01:00:43 -0700 (PDT) (envelope-from rsmith@trltech.co.uk) Received: from trltech.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id IAA17286 for ; Thu, 15 Apr 1999 08:58:24 +0100 (BST) (envelope-from rsmith@trltech.co.uk) Message-ID: <37159C7C.567A7ECF@trltech.co.uk> Date: Thu, 15 Apr 1999 08:59:56 +0100 From: Richard Smith Reply-To: richard@jezebel.demon.co.uk Organization: http://www.trltech.co.uk/ X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "FreeBSD, Mobile" Subject: Re: Cirrus Logic 6729/6730 port address? References: <3714B870.B1AC213D@trltech.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Many thanks to Alexey V. Zaitsev, who suggested I try port address 0x3000, which I am glad to say has worked :) Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 2: 8: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id D18481514F for ; Thu, 15 Apr 1999 02:07:59 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id SAA00522; Thu, 15 Apr 1999 18:05:28 +0900 (JST) Message-Id: <199904150905.SAA00522@chandra.eatell.msr.prug.or.jp> To: richard@jezebel.demon.co.uk Cc: "FreeBSD, Mobile" Subject: Re: Cirrus Logic 6729/6730 port address? In-reply-to: Your message of "Wed, 14 Apr 1999 16:46:56 +0100." <3714B870.B1AC213D@trltech.co.uk> Date: Thu, 15 Apr 1999 18:05:26 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > After advice from Chung-Kie Tung, I have installed the PAO3-beta > package. However, my controller does not appear to be at the default > port addresses or at the 0xfcfc port address that was successful for > Chung-Kie Tung. Please boot with "-v" boot option, you can get boot message like below: pcic0 rev 254 class 60500 int a irq ?? on pci0:19:0 mapreg[10] type=5 addr=0000fcfc size=0004. ~~~~~~~~ bus = 0, slot = 19, func = 0 This case addr is 0xfcfc, so use port at 0xfcfc. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 3:45:10 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (Postfix) with ESMTP id 1136914E9F for ; Thu, 15 Apr 1999 03:44:59 -0700 (PDT) (envelope-from rsmith@trltech.co.uk) Received: from trltech.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id LAA17685; Thu, 15 Apr 1999 11:41:09 +0100 (BST) (envelope-from rsmith@trltech.co.uk) Message-ID: <3715C2A3.F01C711F@trltech.co.uk> Date: Thu, 15 Apr 1999 11:42:43 +0100 From: Richard Smith Reply-To: richard@jezebel.demon.co.uk Organization: http://www.trltech.co.uk/ X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: "FreeBSD, Mobile" Subject: Re: Cirrus Logic 6729/6730 port address? References: <199904150905.SAA00522@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > > Please boot with "-v" boot option, you can get boot message like > below: _That_ was the vital piece of information that's been eluding me. Thanks, Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 6:56:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (Postfix) with SMTP id 81E3014FB4 for ; Thu, 15 Apr 1999 06:56:13 -0700 (PDT) (envelope-from alexandr@mail.eecis.udel.edu) Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa09812; 15 Apr 1999 09:53 EDT To: Michael Reilly Cc: freebsd-mobile@freebsd.org Subject: RE: IBM TP 600 Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Message-Id: <19990415135618.81E3014FB4@hub.freebsd.org> Date: Thu, 15 Apr 1999 06:56:18 -0700 (PDT) From: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In Reply to Your Message of Wed, 14 Apr 1999 16: 53:24 PDT Date: Thu, 15 Apr 1999 09:53:36 -0400 From: Jerry Alexandratos Message-ID: <199904150953.aa09812@mail.eecis.udel.edu> Michael Reilly says: : Does anyone have instructions for installing 2.2.8 or 3.1 on an IBM : ThinkPad 600? FreeBSD seems to have problems with the unique memory : structure of this machine and so freezes during or shortly after boot. : Usually there are three - four beeps before the freeze. : : My machine has 128MB of memory. Ahhh. On all the 600 & 600E's I've installed on, I found that memory above 64M wasn't probed correctly. So, I removed all the memory above 64M and then installed and built a custom kernel with MAXMEM=(1024 * actual memory on the machine -1M). Where'd I pull that number from? Well, I noticed that when the machine boots up, that's how much memory the memory check shows. Though, what the guy at BSDI says makes perfect sense. Personally, I'm not sure why, but it works. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 21:55:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6369914DBD for ; Thu, 15 Apr 1999 21:55:14 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA47358 for ; Thu, 15 Apr 1999 22:52:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA06457 for ; Thu, 15 Apr 1999 22:52:38 -0600 (MDT) Message-Id: <199904160452.WAA06457@harmony.village.org> To: mobile@freebsd.org Subject: laptop install disk Date: Thu, 15 Apr 1999 22:52:38 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has any thought been given to integrating the PAO patches needed to get sysinstall to cope with pccardd and the like and including a configuration for that in src/release? I'm installing on a Sony VAIO right now, and am using the PAO boot disk with the 2.2.8-RELEASE to get myself going.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 22: 1:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id A315B14DBD for ; Thu, 15 Apr 1999 22:01:08 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id NAA16695; Fri, 16 Apr 1999 13:58:28 +0900 (JST) Date: Fri, 16 Apr 1999 13:58:28 +0900 (JST) Message-Id: <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> To: imp@harmony.village.org Cc: mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: laptop install disk In-Reply-To: Your message of "Fri, 16 Apr 1999 13:52:38 JST". <199904160452.WAA06457@harmony.village.org> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199904160452.WAA06457@harmony.village.org> imp@harmony.village.org writes: >> Has any thought been given to integrating the PAO patches needed to >> get sysinstall to cope with pccardd and the like and including a >> configuration for that in src/release? I'm installing on a Sony VAIO >> right now, and am using the PAO boot disk with the 2.2.8-RELEASE to >> get myself going.... To merge PAO2 sysinstall patch is too difficult and needs many features only exist on PAO. PAO3 sysinstall patch is relatively smaller and uses only one feature of PAO (-z option of pccardd). So I think it's very easy to port (and merge) it to -current. I'll provide sysinstall laptop support patch against -current. I'll put the PAO3 boot.flp sources at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE today. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 22: 5: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 2474214DBD for ; Thu, 15 Apr 1999 22:04:59 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id OAA16870; Fri, 16 Apr 1999 14:02:35 +0900 (JST) Date: Fri, 16 Apr 1999 14:02:35 +0900 (JST) Message-Id: <199904160502.OAA16870@afs.ntc.mita.keio.ac.jp> To: hosokawa@ntc.keio.ac.jp Cc: imp@harmony.village.org, mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: laptop install disk In-Reply-To: Your message of "Fri, 16 Apr 1999 13:58:28 JST". <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> hosokawa@ntc.keio.ac.jp writes: >> PAO3 sysinstall patch is relatively smaller and uses only one feature >> of PAO (-z option of pccardd). So I think it's very easy to port (and Oops, sorry it also uses -i option of pccardd, but it's not an essential feature. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 22: 8: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ED82C14DBD for ; Thu, 15 Apr 1999 22:07:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA47430; Thu, 15 Apr 1999 23:05:21 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA06572; Thu, 15 Apr 1999 23:05:19 -0600 (MDT) Message-Id: <199904160505.XAA06572@harmony.village.org> To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Subject: Re: laptop install disk Cc: mobile@freebsd.org In-reply-to: Your message of "Fri, 16 Apr 1999 13:58:28 +0900." <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> References: <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> Date: Thu, 15 Apr 1999 23:05:19 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> HOSOKAWA Tatsumi writes: : PAO3 sysinstall patch is relatively smaller and uses only one feature : of PAO (-z option of pccardd). So I think it's very easy to port (and : merge) it to -current. I'll provide sysinstall laptop support patch : against -current. I have the PAO3 stuff on my disk as of yesterday. I'll have to take a look at the -z option to pccardd. : I'll put the PAO3 boot.flp sources at : ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE today. I'll have to download those as well, since they don't appear (at first glance anyway) to be in the PAO3 stuff I have. I don't want to slow down the download I already have going, since it is only 10 minutes away from being done. I think this would be a good thing to integrate into -current and 3.x -stable's sysinstall. I guess I better ask Jordan what he thinks, since he's basically keeper of sysinstall these days. I know there is a new install on the horizon, but if we get these changes into the current sysinstall, then it would be easier to get the functionality in the new install ;-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 23:16:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CAD7C14E44 for ; Thu, 15 Apr 1999 23:16:37 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA61247; Thu, 15 Apr 1999 23:14:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: imp@harmony.village.org, mobile@FreeBSD.ORG Subject: Re: laptop install disk In-reply-to: Your message of "Fri, 16 Apr 1999 13:58:28 +0900." <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> Date: Thu, 15 Apr 1999 23:14:22 -0700 Message-ID: <61245.924243262@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > PAO3 sysinstall patch is relatively smaller and uses only one feature > of PAO (-z option of pccardd). So I think it's very easy to port (and > merge) it to -current. I'll provide sysinstall laptop support patch > against -current. I'd be happy to incorporate this if it's not too intrusive. We'll need to add pccardd to the mfsroot floppy, of course, but I don't think that's too much trouble given the increased space we now have available. Just let me know how I can help. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 15 23:17:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3B40C14E44 for ; Thu, 15 Apr 1999 23:17:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA61262; Thu, 15 Apr 1999 23:15:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Warner Losh Cc: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi), mobile@FreeBSD.ORG Subject: Re: laptop install disk In-reply-to: Your message of "Thu, 15 Apr 1999 23:05:19 MDT." <199904160505.XAA06572@harmony.village.org> Date: Thu, 15 Apr 1999 23:15:08 -0700 Message-ID: <61260.924243308@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think this would be a good thing to integrate into -current and 3.x > -stable's sysinstall. I guess I better ask Jordan what he thinks, > since he's basically keeper of sysinstall these days. I know there is > a new install on the horizon, but if we get these changes into the The new sysinstall is far enough on the horizon that adding this and DHCP client capability is still on my list for sysinstall. I'm resigned to the fact that there's quite a bit of life left in that damn thing. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 0: 4:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7EDE215162 for ; Fri, 16 Apr 1999 00:04:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA47764; Fri, 16 Apr 1999 01:01:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA07309; Fri, 16 Apr 1999 01:01:47 -0600 (MDT) Message-Id: <199904160701.BAA07309@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: laptop install disk Cc: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi), mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 15 Apr 1999 23:14:22 PDT." <61245.924243262@zippy.cdrom.com> References: <61245.924243262@zippy.cdrom.com> Date: Fri, 16 Apr 1999 01:01:47 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <61245.924243262@zippy.cdrom.com> "Jordan K. Hubbard" writes: : I'd be happy to incorporate this if it's not too intrusive. We'll : need to add pccardd to the mfsroot floppy, of course, but I don't : think that's too much trouble given the increased space we now have : available. Just let me know how I can help. OK. I'll look at adding this. The -z option looks nearly trivial to add to pccardd in -current. I'll know more about this as soon as I get my laptop up to -current. I'll also look at the changes that Hosokawa-san puts up on daemon to see how hard sysinstall will be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 0:37: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 9A2721503F for ; Fri, 16 Apr 1999 00:36:57 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id QAA18400; Fri, 16 Apr 1999 16:34:31 +0900 (JST) Date: Fri, 16 Apr 1999 16:34:31 +0900 (JST) Message-Id: <199904160734.QAA18400@afs.ntc.mita.keio.ac.jp> To: hosokawa@ntc.keio.ac.jp Cc: imp@harmony.village.org, mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: laptop install disk In-Reply-To: Your message of "Fri, 16 Apr 1999 13:58:28 JST". <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> hosokawa@ntc.keio.ac.jp writes: >> I'll put the PAO3 boot.flp sources at >> ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE today. I've put the source diff's. ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE/paoflp-src-19990416.tar.gz It has patch to src/release and etc/etc.i386/MAKEDEV. I want to add card2 and card3 device files to ./MAKEDEV all. There're machines that have more than three PC-card slots. (for example, Digital Hinote Ultra+CDROM station, RIOS Chandra, etc.) If there's no objection, I'll cvs commit MAKEDEV. -- HOSOKAWA, Tatsumi Information Technology Center Keio University hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 8:36: 7 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 702ED158E8 for ; Fri, 16 Apr 1999 08:35:57 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA09941; Fri, 16 Apr 1999 09:33:32 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA17217; Fri, 16 Apr 1999 09:33:32 -0600 Date: Fri, 16 Apr 1999 09:33:32 -0600 Message-Id: <199904161533.JAA17217@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: imp@harmony.village.org, mobile@FreeBSD.ORG Subject: Re: laptop install disk In-Reply-To: <199904160734.QAA18400@afs.ntc.mita.keio.ac.jp> References: <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> <199904160734.QAA18400@afs.ntc.mita.keio.ac.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I want to add card2 and card3 device files to ./MAKEDEV all. > There're machines that have more than three PC-card slots. > (for example, Digital Hinote Ultra+CDROM station, RIOS Chandra, etc.) > If there's no objection, I'll cvs commit MAKEDEV. None from me. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 9:20:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id CC31E14D35 for ; Fri, 16 Apr 1999 09:19:58 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id SAA10246 for ; Fri, 16 Apr 1999 18:17:34 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma010244; Fri, 16 Apr 99 18:17:32 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id SAA02434 for freebsd-mobile@freebsd.org; Fri, 16 Apr 1999 18:17:32 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904161617.SAA02434@helena.otelo-call.de> Subject: Fiberline Ethernet, part two To: freebsd-mobile@freebsd.org Date: Fri, 16 Apr 1999 18:17:31 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, some days ago I aked here about my installation troubles with FreeBSD, various PAO boot floppies and a Fiberline Ethernet PCMCIA card. Well, I gave up on that and took the lp0 route. Now I have 2.2.8-RELEASE on the Laptop in question, and can't get the card to work, either. It is the 'driver allocation failed' problem which hints, according to net.wisdom derived from dejanews, to a resource conflict. But there is none - at least I don't see it. There is no fancy=20 builtin hardware. Just Ide controller, 1 Serial, 1 Parallel, Floppy, Keyboard, Ps2 Mouse.=20 I append a few diagnostic points - maybe someone here has an Idea. Excerpt from dmesg, booted with -v: ------------------ FreeBSD 2.2.8-RELEASE #0: Thu Apr 15 20:28:13 CEST 1999 [...] ed0 not found at 0x300 [...] apm0 on isa apm: found APM BIOS version 1.0 imasks: bio c0084040, tty c0070092, net c0070092 PC-Card Intel 82365 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ed sio [...] Card inserted, slot 0 --------------------- pccard.conf: --------------------- # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 3 5 10 11 13 15 # Available memory slots memory 0xd4000 96k #Fiberline FL-4680 Ethernet card "Ethernet" "Adapter" config 0x1 "ed0" ? insert echo Fiberline Ethernet inserted insert /etc/pccard_ether ed0 remove echo Fiberline removed remove /sbin/ifconfig ed0 delete --------------------- Excerpt from kernel konfig file --------------------- controller card0 device pcic0 at card? device pcic1 at card? device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr --------------------- pccardc dumpcis: --------------------- Code 240 not found Code 240 not found code Unknown ignored Configuration data for card in slot 0 Tuple #1, code =3D 0x1 (Common memory descriptor), length =3D 5 000: d4 0a 53 e9 ff Common memory device information: Device number 1, type Function specific, WPS =3D OFF Speed =3D 100nS, Memory block size =3D 8Kb, 2 units Device number 2, type FLASH EEPROM, WPS =3D OFF Speed =3D 150nS, Memory block size =3D 2Kb, 30 units Tuple #2, code =3D 0x17 (Attribute memory descriptor), length =3D 3 000: 53 09 ff Attribute memory device information: Device number 1, type FLASH EEPROM, WPS =3D OFF Speed =3D 150nS, Memory block size =3D 2Kb, 2 units Tuple #3, code =3D 0x20 (Manufacturer ID), length =3D 4 000: 49 01 ab c1 PCMCIA ID =3D 0x149, OEM ID =3D 0xc1ab Tuple #4, code =3D 0x15 (Version 1 info), length =3D 26 000: 04 01 45 74 68 65 72 6e 65 74 00 41 64 61 70 74 010: 65 72 00 32 2e 30 00 ff 00 ff Version =3D 4.1, Manuf =3D [Ethernet],card vers =3D [Adapter] Addit. info =3D [2.0],[=FF] Tuple #5, code =3D 0x1a (Configuration map), length =3D 5 000: 01 06 d0 0f 0b Reg len =3D 2, config register addr =3D 0xfd0, last config =3D 0x6 Registers: XX-X----=20 Tuple #6, code =3D 0x1b (Configuration entry), length =3D 7 000: c0 81 18 45 30 fc be Config index =3D 0x0(default) Interface byte =3D 0x81 (I/O) wait signal supported Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: Pulse IRQ level =3D 5 Tuple #7, code =3D 0x1b (Configuration entry), length =3D 7 000: 01 08 ca 60 00 03 1f Config index =3D 0x1 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start =3D 0x300 block length =3D 0x20 Tuple #8, code =3D 0x1b (Configuration entry), length =3D 7 000: 02 08 ca 60 20 03 1f Config index =3D 0x2 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start =3D 0x320 block length =3D 0x20 Tuple #9, code =3D 0x1b (Configuration entry), length =3D 7 000: 03 08 ca 60 40 03 1f Config index =3D 0x3 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start =3D 0x340 block length =3D 0x20 Tuple #10, code =3D 0x1b (Configuration entry), length =3D 7 000: 04 08 ca 60 80 03 1f Config index =3D 0x4 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start =3D 0x380 block length =3D 0x20 Tuple #11, code =3D 0x1b (Configuration entry), length =3D 7 000: 05 08 ca 60 00 02 1f Config index =3D 0x5 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start =3D 0x200 block length =3D 0x20 Tuple #12, code =3D 0x21 (Functional ID), length =3D 2 000: 06 00 Network/LAN adapter Tuple #13, code =3D 0x14 (No link), length =3D 0 Tuple #14, code =3D 0x0 (Null tuple), length =3D 9 000: 57 42 4c 41 4e 39 32 36 ff Tuple #15, code =3D 0xff (Terminator), length =3D 0 1 slots found --------------------- Excerpt from /var/log/messages after starting pccardd --------------------- Apr 16 18:13:33 pollux pccardd[271]: driver allocation failed for Ethernet Apr 16 18:13:33 pollux pccardd[271]: pccardd started --------------------- Regards Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 10: 0:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 159011515B for ; Fri, 16 Apr 1999 10:00:05 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id SAA10390; Fri, 16 Apr 1999 18:57:06 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma010388; Fri, 16 Apr 99 18:57:01 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id SAA02539; Fri, 16 Apr 1999 18:57:01 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904161657.SAA02539@helena.otelo-call.de> Subject: Re: Fiberline Ethernet, part two In-Reply-To: <19990416124023.A3265@stat.Duke.EDU> from Sean O'Connell at "Apr 16, 99 12:40:23 pm" To: sean@stat.Duke.EDU Date: Fri, 16 Apr 1999 18:57:01 +0200 (MET DST) Cc: freebsd-mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, > On 1999 Apr 16, Christoph Weber-Fahr (aka listmail@helena.callcenter.systemhaus.net) wrote: > > > > I append a few diagnostic points - maybe someone here has an Idea. > > > > Excerpt from dmesg, booted with -v: > > ------------------ > > FreeBSD 2.2.8-RELEASE #0: Thu Apr 15 20:28:13 CEST 1999 > > [...] > > ed0 not found at 0x300 > > [...] > > apm0 on isa > > apm: found APM BIOS version 1.0 > > imasks: bio c0084040, tty c0070092, net c0070092 > > PC-Card Intel 82365 (5 mem & 2 I/O windows) > > pcic: controller irq 3 > > Initializing PC-card drivers: ed sio > > [...] > > Card inserted, slot 0 > > --------------------- > > pccard.conf: > > --------------------- > > # Generally available IO ports > > io 0x240-0x360 > > # Generally available IRQs (Built-in sound-card owners remove 5) > > irq 3 5 10 11 13 15 > > # Available memory slots > > memory 0xd4000 96k > > > > #Fiberline FL-4680 Ethernet > > card "Ethernet" "Adapter" > > config 0x1 "ed0" ? > > insert echo Fiberline Ethernet inserted > > insert /etc/pccard_ether ed0 > > remove echo Fiberline removed > > remove /sbin/ifconfig ed0 delete > > > > device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr > > I see several reasons: > > 1) it will try to use irq 3 because of the ? in the pccard.conf > (first available), but irq 3 is being used by your pccard controller > == allocation error > > Change the irq in /etc/pccard.conf > > irq 5 10 11 (only include 5 if it genuinely is free) I had a 5 there previously. Doesn't work as well. > 2) ed0 is using irq5 ... does your laptop have a sound card? No. That's a Toshiba T1910 - nothing fancy. Not even a colour display. > 3) if irq 10 is avalailable, i'd use that to avoid #2 I tried that as well, but... > device ed0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector edintr ...not in the kernel file but only in the kernel config at startup. Is there a problem with this (do I _have_ to use the entry in the kernel config file at compile time) ? Regards Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 10:15:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id B4ED115962 for ; Fri, 16 Apr 1999 10:15:20 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id CAA21791; Sat, 17 Apr 1999 02:12:46 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: listmail@helena.callcenter.systemhaus.net Cc: freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Fiberline Ethernet, part two From: Tomoaki NISHIYAMA In-Reply-To: <199904161617.SAA02434@helena.otelo-call.de> References: <199904161617.SAA02434@helena.otelo-call.de> <199904161657.SAA02539@helena.otelo-call.de> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990417021245Y.tomoaki@moss.nibb.ac.jp> Date: Sat, 17 Apr 1999 02:12:45 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 41 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Christoph Weber-Fahr Subject: Fiberline Ethernet, part two Date: Fri, 16 Apr 1999 18:17:31 +0200 (MET DST) Message-ID: <199904161617.SAA02434@helena.otelo-call.de> listmail> Now I have 2.2.8-RELEASE on the Laptop in question, and can't get listmail> the card to work, either. It is the 'driver allocation failed' listmail> problem which hints, according to net.wisdom derived from dejanews, listmail> to a resource conflict. Yes, this happens when you don't have an appropriate free irq. Can you figure out which irq should be used by the card? From: Christoph Weber-Fahr Subject: Fiberline Ethernet, part two Date: Fri, 16 Apr 1999 18:17:31 +0200 (MET DST) Message-ID: <199904161617.SAA02434@helena.otelo-call.de> listmail> #Fiberline FL-4680 Ethernet listmail> card "Ethernet" "Adapter" listmail> config 0x1 "ed0" ? usually the config line seems to be written as config default "ed0" any ^^^ note that "?" is not used in sample configuration file. Knowing that windows used irq 11 it may help to specify explicitly config 0x1 "ed0" 11 listmail> ...not in the kernel file but only in the kernel config at startup. Is listmail> there a problem with this (do I _have_ to use the entry in the kernel listmail> config file at compile time) ? No, you don't have to specify them in the kernel config. They are ignored. By the way, do you mention the pure 2.2.8 release or 2.2.8 release with PAO? I'm not sure how match of the PAO integrated to 2.2.8 release and I am using 2.2.7 release with PAO patch. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 10:17:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 1C45A1515B for ; Fri, 16 Apr 1999 10:17:49 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id KAA03702; Fri, 16 Apr 1999 10:07:19 -0700 (PDT) Date: Fri, 16 Apr 1999 10:07:18 -0700 (PDT) From: Annelise Anderson To: Christoph Weber-Fahr Cc: sean@stat.Duke.EDU, freebsd-mobile@FreeBSD.ORG Subject: Re: Fiberline Ethernet, part two In-Reply-To: <199904161657.SAA02539@helena.otelo-call.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You probably need the line ether 0x81 in the pccard.conf definition. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 10:33:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 24B6A14E53 for ; Fri, 16 Apr 1999 10:33:52 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id CAA21847; Sat, 17 Apr 1999 02:31:22 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: tomoaki@biol.s.u-tokyo.ac.jp Cc: listmail@helena.callcenter.systemhaus.net, freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Fiberline Ethernet, part two From: Tomoaki NISHIYAMA In-Reply-To: <19990417021245Y.tomoaki@moss.nibb.ac.jp> References: <199904161617.SAA02434@helena.otelo-call.de> <199904161657.SAA02539@helena.otelo-call.de> <19990417021245Y.tomoaki@moss.nibb.ac.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990417023121E.tomoaki@moss.nibb.ac.jp> Date: Sat, 17 Apr 1999 02:31:21 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 20 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Tomoaki NISHIYAMA Subject: Re: Fiberline Ethernet, part two Date: Sat, 17 Apr 1999 02:12:45 +0900 Message-ID: <19990417021245Y.tomoaki@moss.nibb.ac.jp> tomoaki> Knowing that windows used irq 11 it may help to specify explicitly tomoaki> config 0x1 "ed0" 11 Another way that may worth to try is setting the irq for pcic to 11 in kernel config at boot time. According to PAO-FAQ there is some NE2000 compatible cards that require a flags of 0x10. This means to write the line config 0x1 "ed0" any 0x10 -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 10:48:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from spork.cs.unm.edu (spork.cs.unm.edu [198.59.151.21]) by hub.freebsd.org (Postfix) with ESMTP id A52D715064 for ; Fri, 16 Apr 1999 10:48:08 -0700 (PDT) (envelope-from colinj@cs.unm.edu) Received: from waimea.cs.unm.edu ([198.83.92.103]) by spork.cs.unm.edu with esmtp (Exim 2.12 #3) id 10YCgU-0003Bh-00 for freebsd-mobile@freebsd.org; Fri, 16 Apr 1999 11:45:46 -0600 Received: from localhost (colinj@localhost) by waimea.cs.unm.edu (980427.SGI.8.8.8/8.8.8) with ESMTP id LAA86191 for ; Fri, 16 Apr 1999 11:45:33 -0600 (MDT) (envelope-from colinj@cs.unm.edu) X-Authentication-Warning: waimea.cs.unm.edu: colinj owned process doing -bs Date: Fri, 16 Apr 1999 11:45:27 -0600 From: Colin Eric Johnson To: freebsd-mobile@freebsd.org Subject: PAO, SCSI and Adaptec 1460? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was taking a look at the PAO page today and noticed that there was not a floppy image for 3.1. I then checked the list of supported cards and found the following: ----------------------------------------------------------------------- Current Status ----------------------------------------------------------------------- Type Card Status Driver ----------------------------------------------------------------------- . . . SCSI Adaptec SlimSCSI APA-1460 OK aic Adaptec SlimSCSI APA-1460A OK aic Adaptec SlimSCSI APA-1460AJ OK aic Adaptec SlimSCSI APA-1460B OK aic Adaptec SlimSCSI APA-1460J OK aic I'm wondering if someone can confirm that the PAO installation does work with the Adaptec SlimSCSI APA-1460* card(s). I have one and would love to be able to use it under FreeBSD but up until now the aic driver was not supported as it had not made it onto the CAM bus. Has this changed? Does the PAO installation include support of the aic driver? thanks. Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ In order to be in brilliant you gotta be in touch with the universe - Kevin Klein, "The January Man" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 11: 2: 6 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from spork.cs.unm.edu (spork.cs.unm.edu [198.59.151.21]) by hub.freebsd.org (Postfix) with ESMTP id 9ABE115064 for ; Fri, 16 Apr 1999 11:02:03 -0700 (PDT) (envelope-from colinj@cs.unm.edu) Received: from waimea.cs.unm.edu ([198.83.92.103]) by spork.cs.unm.edu with esmtp (Exim 2.12 #3) id 10YCtx-0003Iw-00 for freebsd-mobile@freebsd.org; Fri, 16 Apr 1999 11:59:41 -0600 Received: from localhost (colinj@localhost) by waimea.cs.unm.edu (980427.SGI.8.8.8/8.8.8) with ESMTP id LAA42317 for ; Fri, 16 Apr 1999 11:59:29 -0600 (MDT) (envelope-from colinj@cs.unm.edu) X-Authentication-Warning: waimea.cs.unm.edu: colinj owned process doing -bs Date: Fri, 16 Apr 1999 11:59:24 -0600 From: Colin Eric Johnson To: freebsd-mobile@freebsd.org Subject: Re: PAO, SCSI and Adaptec 1460? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 16 Apr 1999, Colin Eric Johnson wrote: > > I was taking a look at the PAO page today and noticed that there was not a > floppy image for 3.1. I then checked the list of supported cards and found > the following: And if I had done a little more reading I would have found that the list with the PAO3 source code doesn't include the SCSI cards so this might be clue for me ;-( Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ Pro-Accordion And I Vote! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 11: 5:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 04240159BD for ; Fri, 16 Apr 1999 11:05:32 -0700 (PDT) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id LAA10509; Fri, 16 Apr 1999 11:02:53 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id LAA25554; Fri, 16 Apr 1999 11:02:51 -0700 X-Authentication-Warning: shell2.aracnet.com: beattie owned process doing -bs Date: Fri, 16 Apr 1999 11:02:51 -0700 (PDT) From: Brian Beattie To: Colin Eric Johnson Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO, SCSI and Adaptec 1460? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 16 Apr 1999, Colin Eric Johnson wrote: > > I was taking a look at the PAO page today and noticed that there was not a > floppy image for 3.1. I then checked the list of supported cards and found you say there was NOT a floppy image? I would then take it that PAO does not yet work with 3.x. > the following: ... > SCSI > Adaptec SlimSCSI APA-1460B OK aic ... > > I'm wondering if someone can confirm that the PAO installation does work > with the Adaptec SlimSCSI APA-1460* card(s). I have one and would love to > be able to use it under FreeBSD but up until now the aic driver was not > supported as it had not made it onto the CAM bus. Has this changed? Does > the PAO installation include support of the aic driver? > > thanks. > As far as I know, I am the only person working on the aic driver for CAM, it is not yet done. It may be that PAO supports the aic driver under the older SCSI framework. If somebody has an aic driver working under CAM I'd love to hear about it. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 11:33:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (Postfix) with SMTP id 0610414E63 for ; Fri, 16 Apr 1999 11:33:08 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 26288 invoked by uid 4); 16 Apr 1999 18:30:53 -0000 Received: (qmail 36067 invoked from network); 16 Apr 1999 18:20:45 -0000 Received: from localhost.cloud.rain.com (HELO grey.cloud.rain.com) (127.0.0.1) by localhost.cloud.rain.com with SMTP; 16 Apr 1999 18:20:45 -0000 To: freebsd-mobile@FreeBSD.ORG Subject: laptop SCSI References: In-reply-to: Your message of Fri, 16 Apr 1999 11:02:51 PDT. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <36063.924286845.1@grey.cloud.rain.com> Date: Fri, 16 Apr 1999 11:20:45 -0700 Message-ID: <36064.924286845@grey.cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Speaking of laptop SCSI -- does anyone know if a Jaz traveller will work with something like a tape drive? I seem to need to hook a tape drive to my laptop about once a month to save the day by running "dd", so I don't dare upgrade to CAM until I can be fairly sure I can get at tape some way or another. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 11:42:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 92D0614FD6 for ; Fri, 16 Apr 1999 11:42:09 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id UAA10734; Fri, 16 Apr 1999 20:39:03 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma010732; Fri, 16 Apr 99 20:38:57 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id UAA02904; Fri, 16 Apr 1999 20:38:57 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904161838.UAA02904@helena.otelo-call.de> Subject: Re: Fiberline Ethernet, part two In-Reply-To: <19990417023121E.tomoaki@moss.nibb.ac.jp> from Tomoaki NISHIYAMA at "Apr 17, 99 02:31:21 am" To: tomoaki@biol.s.u-tokyo.ac.jp (Tomoaki NISHIYAMA) Date: Fri, 16 Apr 1999 20:38:57 +0200 (MET DST) Cc: freebsd-mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, > From: Tomoaki NISHIYAMA > > According to PAO-FAQ there is some NE2000 compatible cards that require > a flags of 0x10. Yep! This did the trick. It now works ... sort of. (Argh! Since I hadn't used PAO here I hadn't bothered examining its FAQ closely enough). According to the FAQ this forces the driver not to use shared memory. In tests this gives me between 300 and 600 KBps. Is this to be expected via PCMCIA, or should it be faster ? Also, > From: Annelise Anderson > > You probably need the line > > ether 0x81 > > in the pccard.conf definition. Hm.... /var/log/messages says: Apr 16 19:53:40 pollux /kernel: Card inserted, slot 0 Apr 16 19:53:50 pollux /kernel: ed0: address 00:e0:98:17:21:de, type NE2000 (16 bit) That looks reasonable, and works, too. Finally, Tomoaki NISHIYAMA wrote: > By the way, do you mention the pure 2.2.8 release or 2.2.8 release with PAO? > I'm not sure how match of the PAO integrated to 2.2.8 release and > I am using 2.2.7 release with PAO patch. This is 2.2.8-RELEASE without PAO. I thought trying without it first, since I had to install without it anyway. The pao kernel images, as distributed from the pao web site, suffer from the 'malloc wrapped' kzip kernel image corruption problem. Installing from them (via lp0) gave me numerous strange effects like hanging installation, aborted installations, SIG11s and so on. After changing to the standard release floppy I had no problem whatsoever. Is PAO worth installing now that my card works without it ? Regards Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 13:51:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id CAA71159C4 for ; Fri, 16 Apr 1999 13:51:25 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA12505; Fri, 16 Apr 1999 14:49:01 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA19049; Fri, 16 Apr 1999 14:48:59 -0600 Date: Fri, 16 Apr 1999 14:48:59 -0600 Message-Id: <199904162048.OAA19049@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: Michael Reilly , freebsd-mobile@FreeBSD.ORG Subject: Re: IBM TP 600 In-Reply-To: <199904150412.WAA09393@mt.sri.com> References: <36F3F170.6A0B8C36@tinker.com> <4.1.19990414164301.00a347d0@pita.cisco.com> <199904150412.WAA09393@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Does anyone have instructions for installing 2.2.8 or 3.1 on an IBM > > ThinkPad 600? > > I just installed FreeBSD 2.2.8 on my TP600E, and it worked fine. > However, I needed to make sure APM was disabled or it hangs. I'll look > into why that is, but for now it installs. I found out why. It was for the same reason that everyone else has problems, and it's due to the memory sizing being wrong. Once I set it to the correct size, the box has been *ROCK SOLID*. I am *VERY* pleased with this box. It's faster than my 300Mhz box for compiles (the laptop has a 366Mhz chip), although for disk I/O SCSI still kicks it's butt. The only issue I have left is to get the CardBus code working in PCMCIA mode. I've got it hacked to have my 3Com card working with the zp driver, but it's very fragile, and I need to make it work with regular PCMCIA support. In short, it's highly recommended, and will be even more recommended once I get the CardBus stuff figured out. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 22:27:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 3970B14F4A for ; Fri, 16 Apr 1999 22:27:54 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id OAA25344; Sat, 17 Apr 1999 14:25:22 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: colinj@cs.unm.edu Cc: freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: PAO, SCSI and Adaptec 1460? From: Tomoaki NISHIYAMA In-Reply-To: References: <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990417142521D.tomoaki@moss.nibb.ac.jp> Date: Sat, 17 Apr 1999 14:25:21 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 34 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Colin Eric Johnson Subject: PAO, SCSI and Adaptec 1460? Date: Fri, 16 Apr 1999 11:45:27 -0600 Message-ID: colinj> colinj> I was taking a look at the PAO page today and noticed that there was not a colinj> floppy image for 3.1. I then checked the list of supported cards and found colinj> the following: you can find the floppy at From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Subject: Re: laptop install disk Date: Fri, 16 Apr 1999 13:58:28 +0900 (JST) Message-ID: <199904160458.NAA16695@afs.ntc.mita.keio.ac.jp> hosokawa> I'll put the PAO3 boot.flp sources at hosokawa> ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/PAO/flp/3.1-RELEASE today. colinj> I'm wondering if someone can confirm that the PAO installation does work colinj> with the Adaptec SlimSCSI APA-1460* card(s). I have one and would love to colinj> be able to use it under FreeBSD but up until now the aic driver was not colinj> supported as it had not made it onto the CAM bus. Has this changed? Does colinj> the PAO installation include support of the aic driver? As far as I know, no scsi pccard is supported by PAO3, which is why I don't upgrade to 3.1 release. The document aplies to PAO2 -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 16 23:52:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (207-229-148-171.d.enteract.com [207.229.148.171]) by hub.freebsd.org (Postfix) with ESMTP id 26F5714D22 for ; Fri, 16 Apr 1999 23:52:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA01364; Fri, 16 Apr 1999 23:49:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904170649.XAA01364@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Trost Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: laptop SCSI In-reply-to: Your message of "Fri, 16 Apr 1999 11:20:45 PDT." <36064.924286845@grey.cloud.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Apr 1999 23:49:52 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Speaking of laptop SCSI -- does anyone know if a Jaz traveller will work > with something like a tape drive? I seem to need to hook a tape drive > to my laptop about once a month to save the day by running "dd", so I > don't dare upgrade to CAM until I can be fairly sure I can get at tape > some way or another. I've used the Jaz traveller with a variety of SCSI devices; modulo the performance issues, it "just works". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 1:26:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id D082614C8F for ; Sat, 17 Apr 1999 01:26:46 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id KAA31776 for ; Sat, 17 Apr 1999 10:24:23 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id KAA04973 for freebsd-mobile@freebsd.org; Sat, 17 Apr 1999 10:24:22 +0200 (CEST) Date: Sat, 17 Apr 1999 10:24:22 +0200 From: Frank Louwers To: freebsd-mobile@freebsd.org Subject: IBM TP 760: X messed up on resume Message-ID: <19990417102422.B4796@zeus.rug.ac.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have been running FBSD 3.1-RELEASE for a few days now on a IBM ThinkPad 760CD, and it runs great! (Even better with PAO3-BETA!). There is one annoying problem: if my active virtual term is the X-windows, and I go into suspend mode, and resume, X is all messed up. I can switch to a VT, but if I go back to X, it remains messed up. (Note that I do not have this problem if I switch to a VT before going into suspend) .... Any suggestions? THnx, Frank Louwers PS/ it is the same in 3.1 and in 3.1 + PAO3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 2:15: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 0858A14D79 for ; Sat, 17 Apr 1999 02:14:57 -0700 (PDT) (envelope-from Alain.Thivillon@hsc.fr) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) by itesec.hsc.fr (Postfix) with ESMTP id E21DC10E31; Sat, 17 Apr 1999 11:12:32 +0200 (CEST) Received: by yoko.hsc.fr (Postfix snapshot-19990409, from userid 1001) id 7199D12FCD2; Sat, 17 Apr 1999 11:12:24 +0200 (CEST) Date: Sat, 17 Apr 1999 11:12:24 +0200 From: Alain Thivillon To: Frank Louwers Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: IBM TP 760: X messed up on resume Message-ID: <19990417111224.B19953@yoko.hsc.fr> References: <19990417102422.B4796@zeus.rug.ac.be> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.1i In-Reply-To: <19990417102422.B4796@zeus.rug.ac.be>; from Frank Louwers on Sat, Apr 17, 1999 at 10:24:22AM +0200 X-Organization: Herve Schauer Consultants Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Louwers écrivait (wrote) : > There is one annoying problem: if my active virtual term is the X-windows, and > I go into suspend mode, and resume, X is all messed up. I can switch to a VT, > but if I go back to X, it remains messed up. I have same problem with Xfree 3.3.3.1 on Tohisba Tecra 780DVD. The only solution i have found is to switch mode (using Ctrl+Alt+, ie on Toshiba Ctrl+Alt+Fn+M) 3 three times to come back to 1024x768, and display generally comes back. > PS/ it is the same in 3.1 and in 3.1 + PAO3 This is an Xfree Problem, not PAO. I imagie Xfree does not provide good apm hooks to restore display. -- Alain Thivillon -+- Alain.Thivillon@hsc.fr -+- Hervé Schauer Consultants Pgp Key ID: 0x57155CC9 AT1718 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 2:31:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 1577814C07 for ; Sat, 17 Apr 1999 02:31:46 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id SAA25684; Sat, 17 Apr 1999 18:29:18 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: listmail@helena.callcenter.systemhaus.net Cc: freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Fiberline Ethernet, part two From: Tomoaki NISHIYAMA In-Reply-To: <199904161838.UAA02904@helena.otelo-call.de> References: <199904161838.UAA02904@helena.otelo-call.de> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990417182917T.tomoaki@moss.nibb.ac.jp> Date: Sat, 17 Apr 1999 18:29:17 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 19 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Christoph Weber-Fahr Subject: Re: Fiberline Ethernet, part two Date: Fri, 16 Apr 1999 20:38:57 +0200 (MET DST) Message-ID: <199904161838.UAA02904@helena.otelo-call.de> listmail> In tests this gives me between 300 and 600 KBps. Is this to be listmail> expected via PCMCIA, or should it be faster ? It is likely that its working well. listmail> Is PAO worth installing now that my card works without it ? Perhaps not necessary, but if the only card to be used were a network card, I would use 3.1 RELEASE or 3.1-STABLE. I stay 2.2 for the SCSI card, and love PAO for SCSI_DETACH. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 7:24:25 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id 43F9A150FD for ; Sat, 17 Apr 1999 07:24:22 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id QAA07369; Sat, 17 Apr 1999 16:21:53 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id QAA08195; Sat, 17 Apr 1999 16:21:52 +0200 (CEST) Date: Sat, 17 Apr 1999 16:21:52 +0200 From: Frank Louwers To: Alain Thivillon Cc: freebsd-mobile@FreeBSD.ORG Subject: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume Message-ID: <19990417162152.A8150@zeus.rug.ac.be> References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990417111224.B19953@yoko.hsc.fr>; from Alain Thivillon on Sat, Apr 17, 1999 at 11:12:24AM +0200 X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 17, 1999 at 11:12:24AM +0200, Alain Thivillon wrote: > I have same problem with Xfree 3.3.3.1 on Tohisba Tecra 780DVD. The only > solution i have found is to switch mode (using Ctrl+Alt+, ie on > Toshiba Ctrl+Alt+Fn+M) 3 three times to come back to 1024x768, and > display generally comes back. Thank you will try that ... I now discovered another problem: the hibernation won't work :-( I created a hibernation file (after the disks were partitioned, and after the freebsd install), and it works in Win95, but in FBSD the machine just gives 3 ugly beeps, so I think it can't find the hibernation file ... Any suggestions? Frank > > PS/ it is the same in 3.1 and in 3.1 + PAO3 > > This is an Xfree Problem, not PAO. I imagie Xfree does not provide good > apm hooks to restore display. Yes, but there is an extra kernel option in PAO3 that is supposed to "kick X-windows" if this happens ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 12: 7:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A4CA014C23 for ; Sat, 17 Apr 1999 12:07:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA53907 for ; Sat, 17 Apr 1999 13:04:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA20871 for ; Sat, 17 Apr 1999 13:05:16 -0600 (MDT) Message-Id: <199904171905.NAA20871@harmony.village.org> To: mobile@freebsd.org Subject: Sony VAIO suspend Date: Sat, 17 Apr 1999 13:05:16 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you send me the output of fdisk? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 15:25:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 0FF3C14EB4 for ; Sat, 17 Apr 1999 15:25:52 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 14530 invoked from network); 17 Apr 1999 22:23:28 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 17 Apr 1999 22:23:28 -0000 Date: Sat, 17 Apr 1999 17:23:28 -0500 (CDT) From: John Sconiers To: freebsd-mobile@freebsd.org Subject: -current PAO Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to run -current on my Laptop (Dell Latitude CPi) and have been looking for a -current version of PAO. Will PAO 3.x work with -current. I had freebsd 3.1-release working however I'd like to make the big jump to -current if PAO will work with it. JOHN PS: If your looking for testers I'm open to that as well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 18:21:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 38CE614EE9; Sat, 17 Apr 1999 18:21:11 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2RSVNTSL>; Sun, 18 Apr 1999 02:16:52 +0100 Message-ID: From: paul@originative.co.uk To: dm@bbn.com, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: RE: lnc1: Memory allocated above 16Mb limit/Hitachi visionbook Date: Sun, 18 Apr 1999 02:16:51 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: david mankins [mailto:dm@k12-nis-2.bbn.com] > Sent: 14 April 1999 22:34 > To: freebsd-questions@freebsd.org; freebsd-mobile@freebsd.org > Subject: lnc1: Memory allocated above 16Mb limit/Hitachi visionbook > > > This message about 16Mb is new, the off-the-CDROM kernel didn't print > it (and I never saw it while running 2.2.8). Since this is a PCI > device it ought not matter? (That's what the comment in the device > driver says, anyway.) I've commited a fix for this problem. The lnc driver should now work as before. Paul Richards Originative Solutions Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 18:30:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id CFABC14EE9 for ; Sat, 17 Apr 1999 18:30:16 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA00761; Sun, 18 Apr 1999 10:27:39 +0900 (JST) To: John Sconiers Cc: freebsd-mobile@freebsd.org In-reply-to: jrs's message of Sat, 17 Apr 1999 17:23:28 EST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: -current PAO Date: Sun, 18 Apr 1999 10:27:39 +0900 Message-ID: <757.924398859@coconut.itojun.org> From: Jun-ichiro itojun Hagino Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'd like to run -current on my Laptop (Dell Latitude CPi) and have been >looking for a -current version of PAO. Will PAO 3.x work with -current. >I had freebsd 3.1-release working however I'd like to make the big jump to >-current if PAO will work with it. Just give it a try... There was success report (after some patches by hand) on 3.1-STABLE. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 22: 6:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D75B150AB for ; Sat, 17 Apr 1999 22:06:34 -0700 (PDT) (envelope-from randy@psg.com) Received: by roam.psg.com id m10YjkV-00000BC; Sat, 17 Apr 1999 22:04:07 -0700 (PDT) (Smail3.2.0.101#2) Message-Id: Date: Sat, 17 Apr 1999 22:04:07 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@freebsd.org Subject: Re: Sony VAIO suspend References: <199904171905.NAA20871@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you > send me the output of fdisk? roam.psg.com:/var/spool/smail/input# fdisk ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=839 heads=240 sectors/track=63 (15120 blks/cyl) parameters to be used for BIOS calculations are: cylinders=839 heads=240 sectors/track=63 (15120 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 11,(DOS or Windows 95 with 32 bit FAT) start 63, size 5125617 (2502 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 338/ sector 63/ head 239 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 5125680, size 7272720 (3551 Meg), flag 80 (active) beg: cyl 339/ sector 1/ head 0; end: cyl 819/ sector 63/ head 239 The data for partition 3 is: The data for partition 4 is: sysid 160,(unknown) start 12398400, size 272160 (132 Meg), flag 0 beg: cyl 820/ sector 1/ head 0; end: cyl 837/ sector 63/ head 239 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 17 22:13:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6495E150AB for ; Sat, 17 Apr 1999 22:13:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA55011; Sat, 17 Apr 1999 23:10:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA05043; Sat, 17 Apr 1999 23:11:17 -0600 (MDT) Message-Id: <199904180511.XAA05043@harmony.village.org> To: Randy Bush Subject: Re: Sony VAIO suspend Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Sat, 17 Apr 1999 22:04:07 PDT." References: <199904171905.NAA20871@harmony.village.org> Date: Sat, 17 Apr 1999 23:11:17 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Randy Bush writes: : > Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you : > send me the output of fdisk? Damn. That's what I have. What did you do? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 6:49:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 861F614C80 for ; Sun, 18 Apr 1999 06:49:21 -0700 (PDT) (envelope-from randy@psg.com) Received: by roam.psg.com id m10YruQ-00000BC; Sun, 18 Apr 1999 06:46:54 -0700 (PDT) (Smail3.2.0.101#2) Message-Id: Date: Sun, 18 Apr 1999 06:46:54 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: Sony VAIO suspend References: <199904171905.NAA20871@harmony.village.org> <199904180511.XAA05043@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you >>> send me the output of fdisk? > Damn. That's what I have. What did you do? build an apm kernel? see http://psg.com/~randy/vaio/ randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 12:16:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id EE3CB14D98 for ; Sun, 18 Apr 1999 12:16:15 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA01708; Sun, 18 Apr 1999 13:13:41 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA25056; Sun, 18 Apr 1999 13:13:40 -0600 Date: Sun, 18 Apr 1999 13:13:40 -0600 Message-Id: <199904181913.NAA25056@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Frank Louwers Cc: Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume In-Reply-To: <19990417162152.A8150@zeus.rug.ac.be> References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> <19990417162152.A8150@zeus.rug.ac.be> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > solution i have found is to switch mode (using Ctrl+Alt+, ie on > > Toshiba Ctrl+Alt+Fn+M) 3 three times to come back to 1024x768, and > > display generally comes back. > > Thank you will try that ... > > I now discovered another problem: the hibernation won't work :-( I don't think hibernation works on any OS but the Win9X series. I'm almost positive it doesn't even work on NT. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 13:12:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id 979CC15054 for ; Sun, 18 Apr 1999 13:12:34 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id WAA20445; Sun, 18 Apr 1999 22:10:07 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id WAA07668; Sun, 18 Apr 1999 22:10:07 +0200 (CEST) Date: Sun, 18 Apr 1999 22:10:07 +0200 From: Frank Louwers To: Nate Williams Cc: Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume Message-ID: <19990418221006.A7648@zeus.rug.ac.be> References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> <19990417162152.A8150@zeus.rug.ac.be> <199904181913.NAA25056@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904181913.NAA25056@mt.sri.com>; from Nate Williams on Sun, Apr 18, 1999 at 01:13:40PM -0600 X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 18, 1999 at 01:13:40PM -0600, Nate Williams wrote: > > > solution i have found is to switch mode (using Ctrl+Alt+, ie on > > > Toshiba Ctrl+Alt+Fn+M) 3 three times to come back to 1024x768, and > > > display generally comes back. > > > > Thank you will try that ... > > > > I now discovered another problem: the hibernation won't work :-( > > I don't think hibernation works on any OS but the Win9X series. I'm > almost positive it doesn't even work on NT. the hibernation problem is solved: i deleted the hibern file and recreated it ... dunno why it didn't work first, but now it does ... Frank > > > Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 13:15:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 1BA8F15054 for ; Sun, 18 Apr 1999 13:15:43 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA02110; Sun, 18 Apr 1999 14:13:15 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA25262; Sun, 18 Apr 1999 14:13:14 -0600 Date: Sun, 18 Apr 1999 14:13:14 -0600 Message-Id: <199904182013.OAA25262@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Frank Louwers Cc: Nate Williams , Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume In-Reply-To: <19990418221006.A7648@zeus.rug.ac.be> References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> <19990417162152.A8150@zeus.rug.ac.be> <199904181913.NAA25056@mt.sri.com> <19990418221006.A7648@zeus.rug.ac.be> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > solution i have found is to switch mode (using Ctrl+Alt+, ie on > > > > Toshiba Ctrl+Alt+Fn+M) 3 three times to come back to 1024x768, and > > > > display generally comes back. > > > > > > Thank you will try that ... > > > > > > I now discovered another problem: the hibernation won't work :-( > > > > I don't think hibernation works on any OS but the Win9X series. I'm > > almost positive it doesn't even work on NT. > > the hibernation problem is solved: i deleted the hibern file and recreated it > ... dunno why it didn't work first, but now it does ... Great! However, that means I need to figure out why it's never worked on my box now. ;) ;) ;) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 16:56:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id E136014CB3 for ; Sun, 18 Apr 1999 16:56:50 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 14956 invoked from network); 18 Apr 1999 23:54:24 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 18 Apr 1999 23:54:24 -0000 Date: Sun, 18 Apr 1999 18:54:24 -0500 (CDT) From: John Sconiers To: Jun-ichiro itojun Hagino Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: -current PAO ( nic support) In-Reply-To: <757.924398859@coconut.itojun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >I'd like to run -current on my Laptop (Dell Latitude CPi) and have been > >looking for a -current version of PAO. Will PAO 3.x work with -current. > >I had freebsd 3.1-release working however I'd like to make the big jump to > >-current if PAO will work with it. > > Just give it a try... There was success report (after some patches by > hand) on 3.1-STABLE. One more question. I have two netowrk cards a: 3com Megahertz 10/100 PC Card model 3CXFE575BT 3com 10/100 model 3CCFE57BT-D 3com multifunction 10/100 + 56K model 3CCFEM556 and a 3com Megahertz 56K modem model 3ccm156 I looked at the FAQ and other info. These cards are ( or appear to be) not supported. Are any of these cards simular to other supported cards.....??? Which one do you think I would have a greater chance of success with. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 18: 8: 0 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 83DEC14F2B for ; Sun, 18 Apr 1999 18:07:56 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA14052; Mon, 19 Apr 1999 10:03:31 +0900 (JST) To: Frank Louwers Cc: Nate Williams , Alain Thivillon , freebsd-mobile@FreeBSD.ORG In-reply-to: frank's message of Sun, 18 Apr 1999 22:10:07 +0200. <19990418221006.A7648@zeus.rug.ac.be> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume Date: Mon, 19 Apr 1999 10:03:31 +0900 Message-ID: <14048.924483811@coconut.itojun.org> From: Jun-ichiro itojun Hagino Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to be late: >> I don't think hibernation works on any OS but the Win9X series. I'm >> almost positive it doesn't even work on NT. >the hibernation problem is solved: i deleted the hibern file and recreated it >... dunno why it didn't work first, but now it does ... Or, you can craete hybernation partition at the end of disk using phdisk.exe (or something like that). In this case you don't need Windows partition at all. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 18 18:25:43 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 74B3814CAA for ; Sun, 18 Apr 1999 18:25:40 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA14279; Mon, 19 Apr 1999 10:23:12 +0900 (JST) To: John Sconiers Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: jrs's message of Sun, 18 Apr 1999 18:54:24 EST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: -current PAO ( nic support) Date: Mon, 19 Apr 1999 10:23:11 +0900 Message-ID: <14275.924484991@coconut.itojun.org> From: Jun-ichiro itojun Hagino Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Just give it a try... There was success report (after some patches by >> hand) on 3.1-STABLE. >One more question. I have two netowrk cards a: >3com Megahertz 10/100 PC Card model 3CXFE575BT >3com 10/100 model 3CCFE57BT-D >3com multifunction 10/100 + 56K model 3CCFEM556 >and a 3com Megahertz 56K modem model 3ccm156 >I looked at the FAQ and other info. These cards are ( or appear to be) >not supported. Are any of these cards simular to other supported >cards.....??? Which one do you think I would have a greater chance of >success with. The modem (3ccm156) should be okay. Other ones I can't tell... PAO3 guys didn't have a chance to test those yet, I think. (CardBus and/or multifunction are the hard ones, and does those cards fit into both of them?) itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 3:28: 7 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 142D414EB5 for ; Mon, 19 Apr 1999 03:28:04 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id LAA00459; Mon, 19 Apr 1999 11:20:07 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990417111224.B19953@yoko.hsc.fr> Date: Mon, 19 Apr 1999 11:20:05 +0100 (IST) From: "Steve O'Hara-Smith" To: Alain Thivillon Subject: Re: IBM TP 760: X messed up on resume Cc: freebsd-mobile@FreeBSD.ORG, Frank Louwers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Apr-99 Alain Thivillon wrote: > Frank Louwers écrivait (wrote) : > >> There is one annoying problem: if my active virtual term is the >> X-windows, and >> I go into suspend mode, and resume, X is all messed up. I can switch >> to a VT, >> but if I go back to X, it remains messed up. I've had similar problems with laptops, one common fix is to flip to monitor mode and back again. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 19-Apr-99 Time: 11:19:13 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 3:31:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 4C9A714C80 for ; Mon, 19 Apr 1999 03:31:42 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id LAA00465; Mon, 19 Apr 1999 11:23:11 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14048.924483811@coconut.itojun.org> Date: Mon, 19 Apr 1999 11:23:10 +0100 (IST) From: "Steve O'Hara-Smith" To: Jun-ichiro itojun Hagino Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume Cc: freebsd-mobile@FreeBSD.ORG, Alain Thivillon , Nate Williams , Frank Louwers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 19-Apr-99 Jun-ichiro itojun Hagino wrote: > Sorry to be late: > Sorry to be even later :) On most (possibly all) laptops all that is needed is a partition of the right type (160) at the end of the disk. For some bioses on some drives LBA seems to be essential. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 19-Apr-99 Time: 11:21:06 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 4:17:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id 0207A14FBD for ; Mon, 19 Apr 1999 04:17:28 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id NAA10754; Mon, 19 Apr 1999 13:15:00 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id NAA17200; Mon, 19 Apr 1999 13:14:59 +0200 (CEST) Date: Mon, 19 Apr 1999 13:14:59 +0200 From: Frank Louwers To: "Steve O'Hara-Smith" Cc: Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: IBM TP 760: X messed up on resume Message-ID: <19990419131459.A17168@zeus.rug.ac.be> References: <19990417111224.B19953@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Steve O'Hara-Smith on Mon, Apr 19, 1999 at 11:20:05AM +0100 X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 19, 1999 at 11:20:05AM +0100, Steve O'Hara-Smith wrote: > > I've had similar problems with laptops, one common fix is to > flip to monitor mode and back again. thnx, that did the trick ... One annoying thing on this one, is that i first have to turn on numlock to do that, and numlock is above scroll lock, and shift-scroll lock seems to be a function ... Have to find out a way to create a decent keyboard map for X ... Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 7:54:36 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 43BF714C07 for ; Mon, 19 Apr 1999 07:54:31 -0700 (PDT) (envelope-from randy@psg.com) Received: by roam.psg.com id m10YsEe-00000BC; Sun, 18 Apr 1999 07:07:48 -0700 (PDT) (Smail3.2.0.101#2) Message-Id: Date: Sun, 18 Apr 1999 07:07:48 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: Sony VAIO suspend References: <199904171905.NAA20871@harmony.village.org> <199904180511.XAA05043@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you >>> send me the output of fdisk? > Damn. That's what I have. What did you do? btw, for me zzz is the fn-esc suspend, not the fn-f12 hibernate, aka suspend to disk. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 8: 6:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 120CA14C07 for ; Mon, 19 Apr 1999 08:06:51 -0700 (PDT) (envelope-from randy@psg.com) Received: by roam.psg.com id m10ZFaW-00000BC; Mon, 19 Apr 1999 08:03:56 -0700 (PDT) (Smail3.2.0.101#2) Message-Id: Date: Mon, 19 Apr 1999 08:03:56 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: Frank Louwers , Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> <19990417162152.A8150@zeus.rug.ac.be> <199904181913.NAA25056@mt.sri.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hibernation works fine on a vaio 505tx dual boot. see http://psg.com/~randy/vaio randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 10:12:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0C6C5155B8 for ; Mon, 19 Apr 1999 10:12:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA23527; Tue, 20 Apr 1999 02:09:56 +0900 (JST) Message-ID: <371B62ED.5F885C62@newsguy.com> Date: Tue, 20 Apr 1999 02:07:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Randy Bush Cc: Warner Losh , mobile@FreeBSD.ORG Subject: Re: Sony VAIO suspend References: <199904171905.NAA20871@harmony.village.org> <199904180511.XAA05043@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randy Bush wrote: > > >>> Has anybody gotten apm -z (aka zzz) to work on a vaio? If so, can you > >>> send me the output of fdisk? > > Damn. That's what I have. What did you do? > > btw, for me zzz is the fn-esc suspend, not the fn-f12 hibernate, aka suspend > to disk. ??? I know of stand by, suspend *and* hibernate. There is no "aka" in this. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 10:20:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id A95EB15524 for ; Mon, 19 Apr 1999 10:20:25 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id NAA13251 for ; Mon, 19 Apr 1999 13:05:08 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id NAA18099 for freebsd-mobile@FreeBSD.ORG; Mon, 19 Apr 1999 13:05:07 -0400 (EDT) Message-ID: <19990419130507.B3606@stat.Duke.EDU> Date: Mon, 19 Apr 1999 13:05:07 -0400 From: "Sean O'Connell" To: FreeBSD mobile Subject: pccardd and -stable Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All- I am running 3.1-STABLE as of April 14th on an HP Omnibook 900, and I am still having a few oddball problems: 1) using the apm command will cause a kernel panic - this happens with 2.2.8-Release, 3.1-Release, PAO3, and 3.1-stable 2) pccard will not recognize insertion of cards after the machine has booted or (if a card was in at boot time) reinsertion. It does not seem to matter whether or not I kill and restart pccardd or not. if I try to dumpcis, it just tells me that it has '2 slots'. Any suggestions/ideas? Thanks s -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 11:17:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 92C3B14DB2 for ; Mon, 19 Apr 1999 11:17:27 -0700 (PDT) (envelope-from andrsn@ANDRSN.STANFORD.EDU) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id LAA19826; Mon, 19 Apr 1999 11:00:20 -0700 (PDT) Date: Mon, 19 Apr 1999 11:00:20 -0700 (PDT) From: Annelise Anderson To: "Sean O'Connell" Cc: FreeBSD mobile Subject: Re: pccardd and -stable In-Reply-To: <19990419130507.B3606@stat.Duke.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It sounds like the pccard controller isn't working, even though pccardd is. I wrote a "how-to" on pccards that might help that's at http://andrsn.stanford.edu/FreeBSD/pccards.html, but actually you probably know all this stuff already. Annelise On Mon, 19 Apr 1999, Sean O'Connell wrote: > Hi All- > > I am running 3.1-STABLE as of April 14th on an HP Omnibook 900, and > I am still having a few oddball problems: > > 1) using the apm command will cause a kernel panic > > - this happens with 2.2.8-Release, 3.1-Release, PAO3, and 3.1-stable > > 2) pccard will not recognize insertion of cards after the machine > has booted or (if a card was in at boot time) reinsertion. It does > not seem to matter whether or not I kill and restart pccardd or not. > > if I try to dumpcis, it just tells me that it has '2 slots'. > > Any suggestions/ideas? > > Thanks > s > -- > ------------------------------------------------------------------------- > Sean O'Connell Email: sean@stat.Duke.EDU > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > Duke University Fax: (919) 684-8594 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 11:32: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2CFF014DDE for ; Mon, 19 Apr 1999 11:30:45 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA59245; Mon, 19 Apr 1999 12:28:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA25969; Mon, 19 Apr 1999 12:27:56 -0600 (MDT) Message-Id: <199904191827.MAA25969@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: Sony VAIO suspend Cc: Randy Bush , mobile@FreeBSD.ORG In-reply-to: Your message of "Tue, 20 Apr 1999 02:07:57 +0900." <371B62ED.5F885C62@newsguy.com> References: <371B62ED.5F885C62@newsguy.com> <199904171905.NAA20871@harmony.village.org> <199904180511.XAA05043@harmony.village.org> Date: Mon, 19 Apr 1999 12:27:56 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <371B62ED.5F885C62@newsguy.com> "Daniel C. Sobral" writes: : I know of stand by, suspend *and* hibernate. There is no "aka" in : this. suspend and hibernate are almost the same thing, and easily confused. Standby: keep state in memory, but assume lower power settings to conserve power, but keep transition to active state fast. suspend: Save state to disk, but keep the stuff in memory to allow fast recovery. Transition to hibernate after a while. Hibernate: save state to disk, if necessary, and assume the lowest possible power consumption state (not quite off, but as close as you can get with a soft power switch). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 11:44:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 6060114DDE for ; Mon, 19 Apr 1999 11:44:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA05117; Mon, 19 Apr 1999 20:41:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA19395; Mon, 19 Apr 1999 20:41:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: "Daniel C. Sobral" , Randy Bush , mobile@FreeBSD.ORG Subject: Re: Sony VAIO suspend In-reply-to: Your message of "Mon, 19 Apr 1999 12:27:56 MDT." <199904191827.MAA25969@harmony.village.org> Date: Mon, 19 Apr 1999 20:41:31 +0200 Message-ID: <19393.924547291@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904191827.MAA25969@harmony.village.org>, Warner Losh writes: >In message <371B62ED.5F885C62@newsguy.com> "Daniel C. Sobral" writes: >: I know of stand by, suspend *and* hibernate. There is no "aka" in >: this. > >suspend and hibernate are almost the same thing, and easily confused. Yes, indeed :-) Standby: keep CPU & clocks running at lowest possible speed. Possibly shut down non-state keeping parts of I/O devices (ie: spin down disk, turn off amplifier for sound, turn off backlight.) The machine is still alive and running. Batteries will last for some hours maybe a day. Most machines doesn this in multiple steps, with timeouts for screen, cpu and disk user-settable in the BIOS setup. Suspend: Stop the CPU & clocks. State still in RAM. Various IO device states stored in RAM and the devices turned off. Disks in SLEEP mode, if not downright turned off. Batteries will last for some days if not weeks. What most portables do when you "press the button". Hibernate: All state stored on disk (or other NV media). Entire machine turned off. Batteries can be removed. Disk can be transplanted to other but identical hardware and resumed there (!) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 11:55:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3F5D115731 for ; Mon, 19 Apr 1999 11:55:10 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA28293; Mon, 19 Apr 1999 20:51:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904191851.UAA28293@freebsd.dk> Subject: Re: Sony VAIO suspend In-Reply-To: <19393.924547291@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 19, 1999 8:41:31 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 19 Apr 1999 20:51:56 +0200 (CEST) Cc: imp@harmony.village.org, dcs@newsguy.com, randy@psg.com, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Poul-Henning Kamp wrote: > Standby: keep CPU & clocks running at lowest possible speed. > Possibly shut down non-state keeping parts of I/O devices (ie: spin > down disk, turn off amplifier for sound, turn off backlight.) The > machine is still alive and running. Batteries will last for some > hours maybe a day. Most machines doesn this in multiple steps, > with timeouts for screen, cpu and disk user-settable in the BIOS > setup. > > Suspend: Stop the CPU & clocks. State still in RAM. Various IO > device states stored in RAM and the devices turned off. Disks in > SLEEP mode, if not downright turned off. Batteries will last for > some days if not weeks. What most portables do when you "press > the button". > > Hibernate: All state stored on disk (or other NV media). Entire > machine turned off. Batteries can be removed. Disk can be > transplanted to other but identical hardware and resumed there (!) I think this is called supspend-to-disk on many machines, at least it is on the DELL's (and it works btw). (just to clobber up the terms) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 12: 8:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 34D63155EC; Mon, 19 Apr 1999 12:06:49 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id UAA15041; Mon, 19 Apr 1999 20:02:11 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA00637; Mon, 19 Apr 1999 19:15:18 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904191815.TAA00637@keep.lan.Awfulhak.org> Date: Mon, 19 Apr 1999 19:15:18 +0100 From: Brian Somers Subject: Re: HEADS UP!!!! Important instructions for -current users! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm , dfr@freebsd.org Cc: sos@FreeBSD.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 05:30:41 +0800." <19990416213043.95C7B1F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 19 Apr 1999 19:15:18 +0100 From: Brian Somers > As of a few minutes ago, a minimal set of changes to bring the so-calle= d > 'new-bus' functionality to the i386 kernel in -current. [.....] WOW ! All of a sudden ``halt -p'' works properly on my PCG-747 VIAO = notebook ! Also, S=F8ren's ATA DMA code has started to work... awesome ! Well done Doug & associates - and S=F8ren for the ATA stuff. > Cheers, > -Peter - -- = Brian Don't _EVER_ lose your sense of humour ! ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 12:33:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 52FA715268 for ; Mon, 19 Apr 1999 12:33:40 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id MAA06017 for ; Mon, 19 Apr 1999 12:31:11 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Mon, 19 Apr 1999 12:31:11 -0700 (PDT) From: Golden Fischer To: mobile@freebsd.org Subject: Lost connection after suspension Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The PAO3 beta code doesn't like my Toshiba 430 CDT laptop. Whenever I did a suspension (zzz to be exact), the laptop wakes up without network connection. Has anyone experienced same problem? BTW, the PAO3 code works for my Kingston KNE-PC2 card (but not my LinkSYS combo, still needs work here). Fischer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 17:32:10 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from pinky.us.net (pinky.us.net [198.240.73.64]) by hub.freebsd.org (Postfix) with ESMTP id 5EC6B15790 for ; Mon, 19 Apr 1999 17:32:02 -0700 (PDT) (envelope-from sillybug@pinky.us.net) Received: (from sillybug@localhost) by pinky.us.net (8.8.8/8.8.8) id UAA01570 for freebsd-mobile@freebsd.org; Mon, 19 Apr 1999 20:23:36 -0400 (EDT) (envelope-from sillybug) From: Brian Skrab Message-Id: <199904200023.UAA01570@pinky.us.net> Subject: Incorrect PCMCIA NIC Assignment... To: freebsd-mobile@freebsd.org Date: Mon, 19 Apr 1999 20:23:34 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm running into a snag with my PCMCIA ether card in my notebook. I've got FreeBSD 2.2.8 running, and pccardd setup with the configuration for my card, which it detects, but for some reason, the MAC address assigned to it is not what I believe the card is supposed to have. Please have a look at the output that I have included below. If you can provide any pointers toward fixing this, I would very much appreciate your help. This is what shows up on the console when I insert the card... Card inserted, slot 1 Apr 19 01:52:31 myname pccardd[43]: Ether=00:00:1a:05:01:20 Slot 1, unfielded interrupt (0) ed0: address aa:aa:aa:aa:aa:aa, type NE1000 (8 bit) The problem that I have with this is that the card is an NE2000 (16 bit) card, and that address doesn't look quite like it would work at all. Here's what ifconfig shows me... _$ ifconfig -a lp0: flags=8810 mtu 1500 tun0: flags=8010 mtu 1500 tun1: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ed0: flags=8843 mtu 1500 inet 10.0.0.101 netmask 0xffffff00 broadcast 10.0.0.255 ether aa:aa:aa:aa:aa:aa Again, that funky ether address. There is also an error that shows up on the console after the card has been in the slot for a while. Here it is, in case it might provide some insight into the cause of this problem... Apr 19 01:53:23 myname /kernel: ed0: NIC memory corrupt - invalid packet length 55295 As far as configuration goes, I have followed the instructions (provided by you good people) very closely, but I believe that I still may be missing something. Every set of instructions that I have received has made mention of dumping the pccard's information to a file. Well, here it is... Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: d1 3a ff Common memory device information: Device number 1, type Function specific, WPS = OFF Speed = 250nS, Memory block size = 8Kb, 8 units Tuple #2, code = 0x1c (Other conditions for common memory), length = 4 000: 01 d1 3a ff (MWAIT) Tuple #3, code = 0x17 (Attribute memory descriptor), length = 3 000: 41 00 ff Attribute memory device information: Device number 1, type EEPROM, WPS = OFF Speed = 250nS, Memory block size = 512b, 1 units Tuple #4, code = 0x20 (Manufacturer ID), length = 4 000: 49 01 30 02 PCMCIA ID = 0x149, OEM ID = 0x230 Tuple #5, code = 0x21 (Functional ID), length = 2 000: 06 01 Network/LAN adapter - POST initialize Tuple #6, code = 0x15 (Version 1 info), length = 38 000: 04 01 44 2d 4c 69 6e 6b 00 44 46 45 2d 36 35 30 010: 00 46 61 73 74 20 45 74 68 65 72 6e 65 74 00 ff 020: 00 00 00 00 00 00 Version = 4.1, Manuf = [D-Link],card vers = [DFE-650] Addit. info = [Fast Ethernet],[_] Tuple #7, code = 0x1a (Configuration map), length = 5 000: 01 20 00 04 0b Reg len = 2, config register addr = 0x400, last config = 0x20 Registers: XX-X---- Tuple #8, code = 0x1b (Configuration entry), length = 7 000: e0 81 18 45 30 fc be Config index = 0x20(default) Interface byte = 0x81 (I/O) wait signal supported Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: Pulse IRQ level = 5 Tuple #9, code = 0x14 (No link), length = 0 Tuple #10, code = 0xff (Terminator), length = 0 2 slots found I've been making mention of Tuple #4 in my pccard.conf file. In fact, here is the entry for this card... #D-Link DFE-650 Ethernet Card card "D-Link" "DFE-650" config 0x20 "ed0" 11 ether 0x81 insert echo D-Link DFE-650 inserted insert /etc/pccard_ether ed0 remove echo D-Link DFE-650 removed remove /sbin/ifconfig ed0 delete I have irq 11 compiled into the kernel as belonging to the ed0 card. I'm beginning to think that I've missed some small aspect of the configuration, but going back over the instructions, I believe that I have completed all of the steps. It's just getting the card working when it's detected that is giving me problems. If anyone can provide any suggestions on this situation, I'd be very appreciative. I'm really looking forward to getting FreeBSD completely working on this PC. Thank you all for your help, and patience. ~brian skrab To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 19:34:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 4FAF214DB4 for ; Mon, 19 Apr 1999 19:34:14 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id LAA00720; Tue, 20 Apr 1999 11:31:27 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: sillybug@pinky.us.net Cc: freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Incorrect PCMCIA NIC Assignment... From: Tomoaki NISHIYAMA In-Reply-To: <199904200023.UAA01570@pinky.us.net> References: <199904200023.UAA01570@pinky.us.net> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990420113126E.tomoaki@moss.nibb.ac.jp> Date: Tue, 20 Apr 1999 11:31:26 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 34 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Brian Skrab Subject: Incorrect PCMCIA NIC Assignment... Date: Mon, 19 Apr 1999 20:23:34 -0400 (EDT) Message-ID: <199904200023.UAA01570@pinky.us.net> sillybug> #D-Link DFE-650 Ethernet Card sillybug> card "D-Link" "DFE-650" sillybug> config 0x20 "ed0" 11 sillybug> ether 0x81 sillybug> insert echo D-Link DFE-650 inserted sillybug> insert /etc/pccard_ether ed0 sillybug> remove echo D-Link DFE-650 removed sillybug> remove /sbin/ifconfig ed0 delete Where does the 0x81 come from? The entry you should try at first is #D-Link DFE-650 Ethernet Card card "D-Link" "DFE-650" config default "ed0" any 0x10 insert echo D-Link DFE-650 inserted insert /etc/pccard_ether ed0 remove echo D-Link DFE-650 removed remove /sbin/ifconfig ed0 delete You can find a similar example in pccard.conf in pao228. # D-Link DE-650 Ethernet Card card "D-Link" "DE-650" config default "ed0" any 0x10 # New models of DE650 has no ether MAC address definition in CIS tupples. # If you have an older one, please uncomment the following line. # ether 0x40 00:80:c8 insert echo D-link DE-650 inserted insert /etc/pccard_ether $device remove echo D-link DE-650 removed remove /etc/pccard_ether_remove $device To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 19 21: 1: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 5169D15335 for ; Mon, 19 Apr 1999 21:01:03 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id UAA06816 for ; Mon, 19 Apr 1999 20:58:34 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Mon, 19 Apr 1999 20:58:34 -0700 (PDT) From: Golden Fischer To: mobile@freebsd.org Subject: Re: Lost connection after suspension (round 2) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 19 Apr 1999, me wrote: > > The PAO3 beta code doesn't like my Toshiba 430 CDT laptop. Whenever I did > a suspension (zzz to be exact), the laptop wakes up without network > connection. > > Has anyone experienced same problem? BTW, the PAO3 code works for my > Kingston KNE-PC2 card (but not my LinkSYS combo, still needs work here). > > Fischer > > I felt I was not providing enough information. I did a "pccard dumpcis" and this is what I get: Apr 19 19:48:04 squid /kernel: Card inserted, slot 1 Apr 19 19:48:48 squid pccardd[362]: Warning: REGEX error for"^(Combo PCMCIA EthernetCard (EC2T)" -- parentheses not balanced Apr 19 19:48:48 squid pccardd[362]: No card in database for "Linksys"("Combo PCMCIA EthernetCard (EC2T)") [2.0] [(null)] I've never seen a REGEX error before and would appreciate any help. Fischer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 7:24:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id B2ADC14EA6 for ; Tue, 20 Apr 1999 07:24:11 -0700 (PDT) (envelope-from earnoth@UDel.Edu) Received: from lapdog.duch.udel.edu (lapdog.duch.udel.edu [128.175.54.5]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id KAA16633; Tue, 20 Apr 1999 10:21:42 -0400 (EDT) Date: Tue, 20 Apr 1999 10:25:37 -0400 (EDT) From: "Eric I. Arnoth" X-Sender: earnoth@lapdog.duch.udel.edu To: Golden Fischer Cc: mobile@FreeBSD.ORG Subject: Re: Lost connection after suspension (round 2) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've had a similar problem, and it was fixed simply by doing an ifconfig. I don't know what the results of your pccard dumpsis means, but just rerunning ifconfig after unsuspending does the trick for me. (I have a Toshiba Satellite 4010CDS, btw). On Mon, 19 Apr 1999, Golden Fischer wrote: > On Mon, 19 Apr 1999, me wrote: > > > > > The PAO3 beta code doesn't like my Toshiba 430 CDT laptop. Whenever I did > > a suspension (zzz to be exact), the laptop wakes up without network > > connection. > > > > Has anyone experienced same problem? BTW, the PAO3 code works for my > > Kingston KNE-PC2 card (but not my LinkSYS combo, still needs work here). > > > > Fischer > > > > > > I felt I was not providing enough information. I did a "pccard dumpcis" > and this is what I get: > > > Apr 19 19:48:04 squid /kernel: Card inserted, slot 1 > Apr 19 19:48:48 squid pccardd[362]: Warning: REGEX error for"^(Combo PCMCIA > EthernetCard (EC2T)" -- parentheses not balanced > Apr 19 19:48:48 squid pccardd[362]: No card in database for "Linksys"("Combo > PCMCIA EthernetCard (EC2T)") [2.0] [(null)] > > I've never seen a REGEX error before and would appreciate any help. > > > Fischer > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 8:44:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 4CB98157DC for ; Tue, 20 Apr 1999 08:44:48 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id IAA07743 for ; Tue, 20 Apr 1999 08:42:19 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Tue, 20 Apr 1999 08:42:19 -0700 (PDT) From: Golden Fischer To: mobile@freebsd.org Subject: Re: Lost connection after suspension (round 2) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In my mail to the mobile list, I wrote: >>I felt I was not providing enough information. I did a "pccard dumpcis" >>and this is what I get: The pccard dumpcis would not generate that!!! It's from re-inserting the card. I must be tired... Sorry for misleading... Apr 19 19:48:04 squid /kernel: Card inserted, slot 1 Apr 19 19:48:48 squid pccardd[362]: Warning: REGEX error for"^(Combo PCMCIA EthernetCard (EC2T)" -- parentheses not balanced Apr 19 19:48:48 squid pccardd[362]: No card in database for "Linksys"("Combo PCMCIA EthernetCard (EC2T)") [2.0] [(null)] I've never seen a REGEX error before and would appreciate any help. Fischer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 9:11:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 4E3D814CEA for ; Tue, 20 Apr 1999 09:11:47 -0700 (PDT) (envelope-from earnoth@UDel.Edu) Received: from lapdog.duch.udel.edu (lapdog.duch.udel.edu [128.175.54.5]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id MAA04771; Tue, 20 Apr 1999 12:04:46 -0400 (EDT) Date: Tue, 20 Apr 1999 12:08:40 -0400 (EDT) From: "Eric I. Arnoth" X-Sender: earnoth@lapdog.duch.udel.edu To: Jun-ichiro itojun Hagino Cc: Frank Louwers , Nate Williams , Alain Thivillon , freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume In-Reply-To: <14048.924483811@coconut.itojun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 19 Apr 1999, Jun-ichiro itojun Hagino wrote: > Or, you can craete hybernation partition at the end of disk > using phdisk.exe (or something like that). In this case you don't > need Windows partition at all. This sorta relates to my problem. When I got my Toshiba Satellite 4010CDS, I repartitioned the disk with FIPS to accomodate FreeBSD. I left the unused 32MB partition at the end of the disk alone, simply resizing the Win partition, but then I upgraded my RAM to 96 MB, clearly too large for the current hibernation partition. Can I use FIPS to resize the FreeBSD partition appropriately, or will that destroy my install? How does FreeBSD react to being resized in such a manner? Is there some other way to do this? -Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 9:53:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 6AA3714C81 for ; Tue, 20 Apr 1999 09:53:06 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id RAA05785; Tue, 20 Apr 1999 17:44:42 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 20 Apr 1999 17:44:42 +0100 (IST) From: "Steve O'Hara-Smith" To: "Eric I. Arnoth" Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume Cc: freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Apr-99 Eric I. Arnoth wrote: > current hibernation partition. Can I use FIPS to resize the FreeBSD FIPS will trash your FreeBSD partition (or do nothing I'm not sure which) it certainly won't shrink it cleanly. > partition appropriately, or will that destroy my install? How does > FreeBSD react to being resized in such a manner? Is there some other > way > to do this? I have succesfully shrunk a FreeBSD partitition by: 1: Booting single user with all but / unmounted 2: Using dd to move (track by track) /usr and /var partitions down enough tracks to shrink my swap partition. I still have the shell script for this if you want to try this. 3: disklabel -e and very carefully put the new right information in. 4: Reboot and pray (one typo and you are hosed well and truly) This depends on the fact that the swap partition contains nothing of value. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 20-Apr-99 Time: 17:38:37 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 14: 1:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id 51EF415896 for ; Tue, 20 Apr 1999 14:01:33 -0700 (PDT) (envelope-from frank@zeus.rug.ac.be) Received: from zeus.rug.ac.be (frank@zeus.rug.ac.be [157.193.41.38]) by student.rug.ac.be (8.9.2/(Zeus-WPI)) with ESMTP id WAA32527 for ; Tue, 20 Apr 1999 22:59:04 +0200 (CEST) Received: (from frank@localhost) by zeus.rug.ac.be (8.9.2/8.9.2/ZeusWPI) id WAA11270 for freebsd-mobile@freebsd.org; Tue, 20 Apr 1999 22:59:04 +0200 (CEST) Date: Tue, 20 Apr 1999 22:59:04 +0200 From: Frank Louwers To: freebsd-mobile@freebsd.org Subject: Final (?) ThinkPad prob: the Fn key Message-ID: <19990420225903.A11233@zeus.rug.ac.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Useless-Header: this is a very stupid bandwith consuming line X-Operating-System: Unix Forever! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanx to everyone here that helped! FreeBSD is realy starting to run very good on my thinkpad. There is one annoying thing left, however: the Fn key doesn't seem to work? Any suggestions? Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 20 20:57:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 483E415085 for ; Tue, 20 Apr 1999 20:57:26 -0700 (PDT) (envelope-from gfish@uniqsite.com) Received: from localhost (gfish@localhost) by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id UAA19943; Tue, 20 Apr 1999 20:54:54 -0700 (PDT) (envelope-from gfish@uniqsite.com) Date: Tue, 20 Apr 1999 20:54:54 -0700 (PDT) From: Golden Fischer To: "Eric I. Arnoth" Cc: mobile@FreeBSD.ORG Subject: Re: Lost connection after suspension (round 2) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Apr 1999, Eric I. Arnoth wrote: > I've had a similar problem, and it was fixed simply by doing an ifconfig. > I don't know what the results of your pccard dumpsis means, but just > rerunning ifconfig after unsuspending does the trick for me. (I have a > Toshiba Satellite 4010CDS, btw). > It does not work for me though. Any more hints? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 1:13:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B671714C1E for ; Wed, 21 Apr 1999 01:13:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA65471 for ; Wed, 21 Apr 1999 02:10:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA09129 for ; Wed, 21 Apr 1999 02:10:44 -0600 (MDT) Message-Id: <199904210810.CAA09129@harmony.village.org> Subject: APM and newbus To: mobile@FreeBSD.ORG Date: Wed, 21 Apr 1999 02:10:44 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just corrected a bug in the newbus version of apm which had prevented me from suspending my Vaio 505-TS. In newbus there is a DEVICE_SUSPEND method which gets called and allows the callee to request a veto of the proposed suspend. It was alway returning veto, so suspend never worked. Now that I fixed this, my Vaio suspends nicely. I've kludged around this in the apm code until I can find the bug in the newbus code. Just wanted to let people know that this was the case. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 1:52:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from int-gw.staff.apnic.net (guardian.apnic.net [203.37.255.100]) by hub.freebsd.org (Postfix) with ESMTP id DCDEA14D75 for ; Wed, 21 Apr 1999 01:52:37 -0700 (PDT) (envelope-from bc-freebsd@vicious.dropbear.id.au) Received: (from mail@localhost) by int-gw.staff.apnic.net (8.9.1a/8.9.1) id IAA12923 for ; Wed, 21 Apr 1999 08:50:09 GMT Received: from julubu.staff.apnic.net(192.168.1.37) by rex.apnic.net via smap (V2.1) id xma012921; Wed, 21 Apr 99 18:49:41 +1000 Received: (from bc@localhost) by julubu.staff.apnic.net (8.8.7/SCO5) id SAA20648; Wed, 21 Apr 1999 18:49:41 +1000 (EST) X-Authentication-Warning: julubu.staff.apnic.net: bc set sender to bc-freebsd@vicious.dropbear.id.au using -f Date: Wed, 21 Apr 1999 18:49:41 +1000 (EST) From: Bruce Campbell To: freebsd-mobile@freebsd.org Subject: pccardd and ep0 (3c589D) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quick overview: 3.1-RELEASE kernel with ep0 on a laptop results in 'No buffer space available' when used with pccardd. 3c589D. Unloads ep0 right after getting mac address. Detail: Recently work has deigned to allocate myself with a humble HP Omnibook for my purposes. The FreeBSD 3.1-RELEASE GENERIC kernel works fine with the zp0 device, however of course the APM side of things doesn't work. Recompiling the kernel with the following added options to GENERIC: # APM support device apm0 at isa? flags 0x31 # PCMCIA support controller card0 device pcic0 at card? device pcic1 at card? options PCIC_RESUME_RESET # ep0 driver (3com) to work under pccardd device ep0 at isa? port 0x300 net irq 10 vector epintr # Disable the zp0 driver, we don't need it, use ep0 instead with # laptops (according to various gnats #s) # device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 # Reset various things after a resume options PSM_HOOKAPM # Hook the APM resume event, useful for some laptops options PSM_RESETAFTERSUSPEND # reset the device at the resume event options "CPU_SUSP_HLT" results in a kernel which can be suspended quite happily, which is the main thing I want. ep0 can be brought up and down quite happily, but when any traffic is sent over that link: ping: sendto: No buffer space available Patching if_ep.c results in the following messages in quick successions: ep0: entering ep_pccard_init ep0: utp/bnc[*UTP*] address xx:xx:xx:xx:xx:xx ep0: unload Huh? It unloads it right away? Return IRQ=10 pccardd[237]: driver allocation failed for 3Com Corporation The ep0 messages were inserted into ep_pccard_init() and ep_unload() (ep_attach() is the middle one). Either I'm missing something glaringly obvious which hasn't made it into gnats or the mailing lists, or there is something wrong with my hardware which triggers an unload straight away. Ideas? Known undocumented problem? Known documented problem to which I haven't found the document ;) ? --==-- Bruce. Frustrated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 2: 6:54 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freja.webgiro.com (unknown [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 92FD0150E0 for ; Wed, 21 Apr 1999 02:06:51 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id E03BC18C6; Wed, 21 Apr 1999 11:04:31 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id DD50149BE for ; Wed, 21 Apr 1999 11:04:31 +0200 (CEST) Date: Wed, 21 Apr 1999 11:04:26 +0200 (CEST) From: Andrzej Bialecki To: freebsd-mobile@freebsd.org Subject: Toshiba Portege 7020 & modem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm trying to convince my Toshiba to let me use its built-in V.90 modem, for now without results... It's a hardware modem, but Win98 shows it consumes many strange resources (several I/O and mem windows). Of course FreeBSD probe doesn't find it at all. Any clues? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 5:58:25 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (Postfix) with ESMTP id A7366151B4 for ; Wed, 21 Apr 1999 05:58:23 -0700 (PDT) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.2/8.9.2) with ESMTP id IAA76969; Wed, 21 Apr 1999 08:57:52 -0400 (EDT) (envelope-from oleg@ogurok.com) Date: Wed, 21 Apr 1999 08:57:51 -0400 (EDT) From: Oleg Ogurok To: Andrzej Bialecki Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Toshiba Portege 7020 & modem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It looks like toshiba puts Winmodems in all their laptops. I have Satellite 4080XCDT with the same modem. I also noticed that the modem doesn't work in MS-DOS, only in Windows. I guess we can conclude that it's a 'winmodem' and cannot be supported by FreeBSD. I sent a question to Toshiba, but didn't get response. Oleg Ogurok oleg@ogurok.com http://www.ogurok.com On Wed, 21 Apr 1999, Andrzej Bialecki wrote: > Hi, > > I'm trying to convince my Toshiba to let me use its built-in V.90 modem, > for now without results... It's a hardware modem, but Win98 shows it > consumes many strange resources (several I/O and mem windows). Of course > FreeBSD probe doesn't find it at all. > > Any clues? > > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 7:57:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7FF6914BE6 for ; Wed, 21 Apr 1999 07:57:27 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1982 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Wed, 21 Apr 1999 07:54:59 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Wed, 21 Apr 1999 07:54:59 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Campbell Cc: freebsd-mobile@freebsd.org Subject: Re: pccardd and ep0 (3c589D) References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Quick overview: > > 3.1-RELEASE kernel with ep0 on a laptop results in 'No buffer > space available' when used with pccardd. 3c589D. Unloads ep0 > right after getting mac address. > > Detail: > > Recently work has deigned to allocate myself with a humble HP Omnibook for > my purposes. The FreeBSD 3.1-RELEASE GENERIC kernel works fine with the > zp0 device, however of course the APM side of things doesn't work. > > Recompiling the kernel with the following added options to GENERIC: > > # APM support > device apm0 at isa? flags 0x31 > > # PCMCIA support > controller card0 > device pcic0 at card? > device pcic1 at card? > options PCIC_RESUME_RESET > > # ep0 driver (3com) to work under pccardd > device ep0 at isa? port 0x300 net irq 10 vector epintr > > # Disable the zp0 driver, we don't need it, use ep0 instead with > # laptops (according to various gnats #s) > # device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 > > # Reset various things after a resume > options PSM_HOOKAPM # Hook the APM resume event, useful for some laptops > options PSM_RESETAFTERSUSPEND # reset the device at the resume event > options "CPU_SUSP_HLT" > > > results in a kernel which can be suspended quite happily, which is the > main thing I want. ep0 can be brought up and down quite happily, but when > any traffic is sent over that link: > > ping: sendto: No buffer space available i am occasionally seeing the "No buffer space available" with zp0 on a sony vaio. have yet to localize, but seems to do with killing rdumps or other rmt processes. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Apr 21 18:53:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 87ADF1532C for ; Wed, 21 Apr 1999 18:52:43 -0700 (PDT) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.8.6/8.7.3) id VAA17849 for freebsd-mobile@freebsd.org; Wed, 21 Apr 1999 21:51:17 -0400 (EDT) Date: Wed, 21 Apr 1999 21:51:17 -0400 (EDT) From: Kent Hauser Message-Id: <199904220151.VAA17849@rtp.tfd.com> To: freebsd-mobile@freebsd.org Subject: IBM Thinkpad hardware config Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I've gotten FreeBSD 3.1 up & running great on my new TP600E. But there's one problem: I need to use the on-board serial port (DB9) & at boot it's turned off. There's a W98 "Thinkpad Config" program which somehow enables the serial port & other similar things. Does anyone know about a utility I can use under FreeBSD which would allow me to turn this port on? Extra info: The DB9 port is turned *off* at reset. This verified via an RS-232 datascope. ie the TD line goes to zero volts at reset (not +12 or -12) & stays there until the W98 pgm is run to enable it. Thanks in advance. Kent PS Pls respond directly as I'm off the list while travelling abroad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 22 23:43:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 358151514B for ; Thu, 22 Apr 1999 23:43:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA71641; Fri, 23 Apr 1999 00:40:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA04904; Fri, 23 Apr 1999 00:40:18 -0600 (MDT) Message-Id: <199904230640.AAA04904@harmony.village.org> To: Soren Schmidt Subject: Re: cvs commit: src/sys/alpha/isa isa.c src/sys/alpha/pci pcibus.c src/sys/cam cam_xpt.c src/sys/dev/ata ata-all.c src/sys/i386/ Cc: mobile@freebsd.org In-reply-to: Your message of "Thu, 22 Apr 1999 13:53:50 +0200." <199904221153.NAA36481@freebsd.dk> References: <199904221153.NAA36481@freebsd.dk> Date: Fri, 23 Apr 1999 00:40:18 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904221153.NAA36481@freebsd.dk> Soren Schmidt writes: : I did a quick fix for this, it works for me now... But doesn't work for me. I had to hack which interrupts were probed before it would work for me.... I think that argues against committing it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 1:55:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A752914BCC for ; Fri, 23 Apr 1999 01:55:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA38693; Fri, 23 Apr 1999 10:52:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904230852.KAA38693@freebsd.dk> Subject: Re: cvs commit: src/sys/alpha/isa isa.c src/sys/alpha/pci pcibus.c src/sys/cam cam_xpt.c src/sys/dev/ata ata-all.c src/sys/i386/ In-Reply-To: <199904230640.AAA04904@harmony.village.org> from Warner Losh at "Apr 23, 1999 0:40:18 am" To: imp@harmony.village.org (Warner Losh) Date: Fri, 23 Apr 1999 10:52:33 +0200 (CEST) Cc: mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > In message <199904221153.NAA36481@freebsd.dk> Soren Schmidt writes: > : I did a quick fix for this, it works for me now... > > But doesn't work for me. I had to hack which interrupts were probed > before it would work for me.... Hmm, what went wrong, I had problems with that too, but it was because it always found irq7 for use, and that wont work as it conflicts with the printerport (which is disabled or one cannot reboot :( ). > I think that argues against committing it. I never meant to, the pccard drivers should be converted to new-bus first, this was only a temporary solutions so that those (like me) running -current or their notebooks could get along.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 11:18:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id ECF3914F79 for ; Fri, 23 Apr 1999 11:18:03 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id OAA13689; Fri, 23 Apr 1999 14:15:32 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id OAA19877; Fri, 23 Apr 1999 14:15:32 -0400 (EDT) Message-ID: <19990423141531.R18610@stat.Duke.EDU> Date: Fri, 23 Apr 1999 14:15:31 -0400 From: "Sean O'Connell" To: Ira L Cooper Cc: FreeBSD mobile Subject: Re: Libretto 100CT. Reply-To: "Sean O'Connell" References: <199904231524.LAA05187@all-night-tool.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <199904231524.LAA05187@all-night-tool.mit.edu>; from Ira L Cooper on Fri, Apr 23, 1999 at 11:24:04AM -0400 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999 Apr 23, Ira L Cooper (aka ira@MIT.EDU) wrote: > > When I first upgraded my libretto 100CT to FreeBSD 3.1-STABLE, > I had a problem where it wouldn't detect the insertion and removal of > my PCMCIA cards, the following patch fixes this. > > I can't test any other fixes for a bit, because my libretto is > in for service right now. Note, this patch seems to enable polling of > the slots for all machines, there should be a better way. Ira- This seems to fix the problem I had with pccardd not detecting insertion and removal on an HP Omnibook 900 with stable. I sent a query to the list a few days ago. Thanks for doing this. Had you tried just forcing your pcic into polling mode straight off? I'll try setting machdep.pccard.pcic_irq=0 and see if that works too with kernel.old. Thanks, S -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 13: 9:26 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from arl-img-10.compuserve.com (arl-img-10.compuserve.com [149.174.217.140]) by hub.freebsd.org (Postfix) with ESMTP id B78D915238 for ; Fri, 23 Apr 1999 13:09:20 -0700 (PDT) (envelope-from 70673.3111@compuserve.com) Received: (from mailgate@localhost) by arl-img-10.compuserve.com (8.8.6/8.8.6/2.18) id QAA11230 for freebsd-mobile@freebsd.org; Fri, 23 Apr 1999 16:06:48 -0400 (EDT) Date: Fri, 23 Apr 1999 16:02:12 -0400 From: Jeffrey Vehrs <70673.3111@compuserve.com> Subject: prblm w/ X-Win/ blank?! To: Blind.Copy.Receiver@compuserve.com Message-ID: <199904231606_MC2-732A-3856@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's my info on Thinkpad 560: 120Mhz w/ 73Mb Ram 3Gb HD FreeBSD 2.2.6-RELEASE XFree86 3.3.3.1 XF86_SVGA <== default server XF86_VGA16 I've configured XFree86 thru xf86config. Piece of cake. I typed 'startx'. It gave me a blank screen(just black color). I was able to Crtl-Alt-F1 without a problem. It showed that X server did started. Back to VT4. Crtl-Del-Backspace(kill X server). Back to CLI. So, where can I trouble-shoot to solve the problem? Thanks in advance. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 15: 3: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from tardis.perspectives.net (unknown [63.66.225.69]) by hub.freebsd.org (Postfix) with ESMTP id EA7A014EC7 for ; Fri, 23 Apr 1999 15:02:55 -0700 (PDT) (envelope-from jerry.alexandratos@perspectives.net) Received: from localhost ([127.0.0.1] helo=tardis.perspectives.net) by tardis.perspectives.net with esmtp (Exim 2.12 #1) id 10anzf-0003qj-00 for freebsd-mobile@freebsd.org; Fri, 23 Apr 1999 18:00:19 -0400 To: freebsd-mobile@freebsd.org Subject: Newbus Woes Organization: Mos Eisley Candy Store MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14793.924904819.1@tardis.perspectives.net> Date: Fri, 23 Apr 1999 18:00:19 -0400 From: Jerry Alexandratos Message-Id: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org So, are pccards basically useless until pccard folds into the newbus scheme? Thanks. --Jerry name: Jerry Alexandratos || Open-Source software isn't a phone: 302.521.1018 || matter of life or death... email: jalexand@perspectives.net || ...It's much more important || than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 18:48: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id C526F14CDE for ; Fri, 23 Apr 1999 18:47:46 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp503.kt.rim.or.jp [202.247.140.153]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id KAA10576 for ; Sat, 24 Apr 1999 10:45:11 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id KAA00619 for ; Sat, 24 Apr 1999 10:45:09 +0900 (JST) Message-ID: <372121F9.D6256518@sky.rim.or.jp> Date: Sat, 24 Apr 1999 10:44:25 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD Mobile Subject: First draft of pccardc.8 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mr. Hiroki Sato is kind enouch to translate pccardc.8 into English from Japanese in PAO. Can someone review this? -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 19:16:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id 5225614C58 for ; Fri, 23 Apr 1999 19:16:48 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp376.kt.rim.or.jp [202.247.140.76]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id LAA13341 for ; Sat, 24 Apr 1999 11:14:16 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id LAA01931 for ; Sat, 24 Apr 1999 11:14:14 +0900 (JST) Message-ID: <372128CA.8B00E7E9@sky.rim.or.jp> Date: Sat, 24 Apr 1999 11:13:30 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD Mobile Subject: Re: First draft of pccardc.8 References: <372121F9.D6256518@sky.rim.or.jp> Content-Type: multipart/mixed; boundary="------------F889854A684D3E7EA1DE99E6" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------F889854A684D3E7EA1DE99E6 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Jun Kuriyama wrote: > Can someone review this? I don't know why I can mistake like this. :-) File is attached, now. -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG --------------F889854A684D3E7EA1DE99E6 Content-Type: text/plain; charset=iso-2022-jp; name="pccardc.8" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pccardc.8" .\" .\" Copyright (c) 1998 Toshihiko ARAI .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" Translated to English by Hiroki Sato .\" .\" $Id: pccardc.8,v 1.1 1999/04/17 11:12:47 kuriyama Exp $ .\" .Dd November 14, 1998 .Dt PCCARDC 8 .Os FreeBSD .Sh NAME .Nm pccardc .Nd PC-CARD (PCMCIA) management and monitoring tool .Sh SYNOPSIS .Nm pccardc Ar subcommand .Op Ar arg ... .Sh DESCRIPTION .Nm controls PC-CARD slots, configures and displays information about PCMCIA cards. The features of .Nm follow: .Bd -literal Subcommands: beep : Beep type dumpcis : Prints CIS for all cards enabler : Device driver enabler help : Prints command summary pccardmem : Allocate memory for pccard driver rdattr : Read attribute memory rdmap : Read pcic mappings rdreg : Read pcic register wrattr : Write byte to attribute memory wrreg : Write pcic register .Ed .Bl -enum .It .Nm beep Ar 0|1|2 .Pp specifies sound at a card insertion or removal. This corresponds to pccard_beep in .Xr rc.conf 5 . .Pp .Bl -tag -width Ds -compact .It Ar 0 silent mode .It Ar 1 simple beep mode .It Ar 2 melody mode .El .It .Nm dumpcis .Op Ar slot .Pp displays .Em CIS (Card Information Structure) tuple in EEPROM of a PC-CARD card. Slots to read can be specified in .Ar slot option. When no option supplied, it displays all of the available cards in the slots. .It .Nm enabler Ar slot driver .Op Fl m Ar card addr size .Op Fl a Ar iobase .Op Fl i Ar irq .Pp This is "point enabler" that can set parameters manually in order to enable a card, when .Xr pccardd 8 cannot allocate drivers to a PC-CARD card properly. Specify a PC-CARD slot in .Ar slot and a device name in .Ar driver . It probably needs some following options together. .Bl -tag -width Ds .It Fl m Ar card addr size maps shared-memory window of the card to host address. .Ar card is start address of shared-memory (hex), .Ar addr is address mapped to host-side (hex) and .Ar size is size of memory window (Kb). .It Fl a Ar iobase .Ar iobase specifies port number mapped to I/O window(hex) .It Fl i Ar irq .Ar irq specifies an IRQ used by an interruption from a card. Set an unused IRQ(between 1 and 15). .Pp Example: enabler 0 ed0 -m 2000 d4000 16 -a 300 -i 3 .El .Pp This probably has enabled to use some unrecognized cards with broken CIS tuple, and also useful for testing a card that has not reported yet. However, be careful that it frequently cannot manage to recognize it properly. .It .Nm help .Pp print help this command. .It .Nm pccardmem Ar addr .Pp specifies host address using PC-CARD controller(PCIC) as scratch-memory. Because PCIC needs continuous 16KB memory area, you can use following four addresses only. .Pp .Bl -tag -width 0xd0000 -compact .It Ar 0xd0000 0xd0000-0xd3fff (default) .It Ar 0xd4000 0xd4000-0xd7fff .It Ar 0xd8000 0xd8000-0xdbfff .It Ar 0xdc000 0xdc000-0xdffff .El .Pp You can write "DEFAULT" as 0xd0000. This feature corresponds to pccard_mem in .Xr rc.conf 5 . .It .Nm rdattr Ar slot offs length .Pp print hexdump of the card's EEPROM in the slot specified in .Ar slot . An offset address from the top and length in byte are specified in .Ar offs (hex) and .Ar length (hex). .It .Nm rdmap .Op Ar slot .Pp displays the configuration for PC-CARD slots, that are eight shared-memories and two addresses of I/O window mapped to the host. When .Ar slot option does not supplied, it displays information of all of slots in the system. .It .Nm rdreg .Op Ar slot .Pp displays 64 registers of a PC-CARD slot. When .Ar slot option does not supplied, it displays information of all of slots in the system. .It .Nm wrattr Ar slot offs value .Pp writes 1-byte to the card's EEPROM at an offset address from the top specified in .Ar offs (hex), with a value specified in .Ar value (hex). This is preserved after the card is removed. .It .Nm wrreg Ar slot reg value .Pp writes a register of a PC-CARD slot. Specify a PC-CARD slot in .Ar slot , a register number in .Ar reg (hex) and a value in .Ar value (hex). .El .Pp .Sh FILES .Bl -tag -width /etc/rc.conf -compact .It Pa /etc/rc.conf configuration file .El .Sh SEE ALSO .Xr rc.conf 5 , .Xr pccardd 8 .Sh AUTHORS Original version was written by .An Andrew McRae Aq andrew@mega.com.au . .An Tatsumi Hosokawa Aq hosokawa@mt.cs.keio.ac.jp fixed bugs and added some features. .Sh BUGS Have a enough care of using .Nm enabler and .Nm wrattr . It is possible that they make the system instable or damage the card. --------------F889854A684D3E7EA1DE99E6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 23 23:54:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E55A14D17 for ; Fri, 23 Apr 1999 23:54:11 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA75050; Sat, 24 Apr 1999 00:51:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA10613; Sat, 24 Apr 1999 00:51:25 -0600 (MDT) Message-Id: <199904240651.AAA10613@harmony.village.org> To: Soren Schmidt Subject: Re: cvs commit: src/sys/alpha/isa isa.c src/sys/alpha/pci pcibus.c src/sys/cam cam_xpt.c src/sys/dev/ata ata-all.c src/sys/i386/ Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Apr 1999 10:52:33 +0200." <199904230852.KAA38693@freebsd.dk> References: <199904230852.KAA38693@freebsd.dk> Date: Sat, 24 Apr 1999 00:51:24 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904230852.KAA38693@freebsd.dk> Soren Schmidt writes: : It seems Warner Losh wrote: : > In message <199904221153.NAA36481@freebsd.dk> Soren Schmidt writes: : > : I did a quick fix for this, it works for me now... : > : > But doesn't work for me. I had to hack which interrupts were probed : > before it would work for me.... : : Hmm, what went wrong, I had problems with that too, but it was because : it always found irq7 for use, and that wont work as it conflicts with : the printerport (which is disabled or one cannot reboot :( ). The machine hung solid when I didn't exclude irq 9. Don't know why. And I also had the machine panic 2/3 of the time when I eject the card :-(. Excellent motivation forme to work harder on the pcic/pccard conversion to newbus. The pcic code is somewhat a twisty maze of code to make things work. I think that it may be time to separate out some of the different bridge chips into their own drivers, but I'm not completely sure that would be best either. For the moment, I'm ignoring the pc98 stuff which makes it a lot easier to impelement. But it may be tough sledding to get all the current functionality integrated in a sane, extensible manner. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 7:44:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id A37C614CDF for ; Sat, 24 Apr 1999 07:44:22 -0700 (PDT) (envelope-from nrahlstr@mail.winternet.com) Received: from tundra.winternet.com (nrahlstr@tundra.winternet.com [198.174.169.11]) by icicle.winternet.com (8.9.3/8.9.3) with ESMTP id JAA09325 for ; Sat, 24 Apr 1999 09:44:21 -0500 (CDT) SMTP "HELO" (ESMTP) greeting from tundra.winternet.com But _really_ from :: nrahlstr@tundra.winternet.com [198.174.169.11] SMTP "MAIL From" = nrahlstr@mail.winternet.com (Nathan Ahlstrom) SMTP "RCPT To" = Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id JAA28828 for freebsd-mobile@freebsd.org; Sat, 24 Apr 1999 09:44:20 -0500 (CDT) Message-ID: <19990424094420.D27835@winternet.com> Date: Sat, 24 Apr 1999 09:44:20 -0500 From: Nathan Ahlstrom To: freebsd-mobile@freebsd.org Subject: pccard.conf PR conf/10277 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone commit this patch and close this PR (or just close it). http://www.freebsd.org/cgi/query-pr.cgi?pr=10277 Thanks. Nathan -- Nathan Ahlstrom FreeBSD: http://www.FreeBSD.org/ nrahlstr@winternet.com PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 8:32:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 47FA914E5F for ; Sat, 24 Apr 1999 08:32:46 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (787 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 24 Apr 1999 08:32:46 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 24 Apr 1999 08:32:46 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: i shrunk my screen! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org somehow i have gotten my vaio 505tx into a mode where o at boot and without X or Win98, the screen is much smaller and in the center of the LCD. i.e. the display area is about half LCD size o stays that way once logged in as a user, or running as root, or in single user o start X and it's fine, full screen o run Win98 and it's fine it's kinda like i have the default video mode farbled. but i do not know how to unfarble it. and i can find no FreeBSD or Win98 tools or hints. clues? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 8:42:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hyperhost.net (ether.lightrealm.com [207.159.132.5]) by hub.freebsd.org (Postfix) with ESMTP id 6038214F74 for ; Sat, 24 Apr 1999 08:42:52 -0700 (PDT) (envelope-from patseal@hyperhost.net) Received: from p1.a8.du.radix.net (p1.a8.du.radix.net [207.192.132.129]) by hyperhost.net (8.8.5/8.8.5) with ESMTP id LAA02301; Sat, 24 Apr 1999 11:42:22 -0400 (EDT) Date: Sat, 24 Apr 1999 11:41:18 -0400 (EDT) From: Patrick Seal To: Randy Bush Cc: FreeBSD Laptoppers Subject: Re: i shrunk my screen! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My Dell Latitude does that too. It's supposed to do that, but mine has a button I can push that streches it across the screen. Try some different video modes. #man vidcontrol ------------------------------------ _____________________________________ Patrick Seal |"Microsoft isn't evil, they just make | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds hosting and Design http://www.freebsd.org - http://www.linux.org On Sat, 24 Apr 1999, Randy Bush wrote: > somehow i have gotten my vaio 505tx into a mode where > o at boot and without X or Win98, the screen is much smaller and in the > center of the LCD. i.e. the display area is about half LCD size > o stays that way once logged in as a user, or running as root, or in > single user > o start X and it's fine, full screen > o run Win98 and it's fine > > it's kinda like i have the default video mode farbled. but i do not know > how to unfarble it. and i can find no FreeBSD or Win98 tools or hints. > > clues? > > randy > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 8:49:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 772D914F74 for ; Sat, 24 Apr 1999 08:49:14 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1283 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 24 Apr 1999 08:49:14 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 24 Apr 1999 08:49:14 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Patrick Seal Cc: FreeBSD Laptoppers Subject: Re: i shrunk my screen! References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> somehow i have gotten my vaio 505tx into a mode where >> o at boot and without X or Win98, the screen is much smaller and in the >> center of the LCD. i.e. the display area is about half LCD size >> o stays that way once logged in as a user, or running as root, or in >> single user >> o start X and it's fine, full screen >> o run Win98 and it's fine >> >> it's kinda like i have the default video mode farbled. but i do not know >> how to unfarble it. and i can find no FreeBSD or Win98 tools or hints. >> >> clues? > > My Dell Latitude does that too. It's supposed to do that, but mine has a > button I can push that streches it across the screen. Try some different > video modes. > > #man vidcontrol that's the syscons driver. this is more basic, like the mode the darn chip's in. it's 80x25, just very small chars. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 8:54:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from magoo.gshapiro.net (magoo.gshapiro.net [206.111.134.170]) by hub.freebsd.org (Postfix) with ESMTP id 08CF714F93 for ; Sat, 24 Apr 1999 08:54:30 -0700 (PDT) (envelope-from gshapiro@gshapiro.net) Received: (from gshapiro@localhost) by magoo.gshapiro.net (8.9.3/8.9.3) id IAA97916; Sat, 24 Apr 1999 08:54:23 -0700 (PDT) From: Gregory Neil Shapiro MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14113.59695.559208.573788@magoo.gshapiro.net> Date: Sat, 24 Apr 1999 08:54:23 -0700 (PDT) To: Randy Bush Cc: Patrick Seal , FreeBSD Laptoppers Subject: Re: i shrunk my screen! In-Reply-To: References: X-Mailer: VM 6.71 under 21.2 "Clio" XEmacs Lucid (beta12) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org randy> that's the syscons driver. this is more basic, like the mode the darn randy> chip's in. it's 80x25, just very small chars. For the Viao, I believe it's Fn-f to switch between full screen and small screen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 8:55:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 3816715042 for ; Sat, 24 Apr 1999 08:55:34 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (636 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 24 Apr 1999 08:55:33 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 24 Apr 1999 08:55:33 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Gregory Neil Shapiro Cc: FreeBSD Laptoppers Subject: Re: i shrunk my screen! References: <14113.59695.559208.573788@magoo.gshapiro.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > For the Viao, I believe it's Fn-f to switch between full screen and small > screen. YES! stoopid me! thank you! randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 17:33:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 252B014DB0 for ; Sat, 24 Apr 1999 17:33:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA78854; Sat, 24 Apr 1999 18:32:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01995; Sat, 24 Apr 1999 18:32:50 -0600 (MDT) Message-Id: <199904250032.SAA01995@harmony.village.org> To: Jerry Alexandratos Subject: Re: Newbus Woes Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Apr 1999 18:00:19 EDT." References: Date: Sat, 24 Apr 1999 18:32:50 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Jerry Alexandratos writes: : So, are pccards basically useless until pccard folds into the newbus : scheme? Yes and no. Soren has some patches that he posted to this list that help things. However, SIO uses the newbus stuff, and there is no newbus stuff working right now for pccard, so it won't work. zp works for me, and I've had ep working for me, but I get panics on card eject. I'm working on correcting the situation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 20: 0:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 5775914DE4 for ; Sat, 24 Apr 1999 20:00:36 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.webwizard.net.mx (8.9.3/8.9.3) with ESMTP id VAA01315; Sat, 24 Apr 1999 21:59:38 -0500 (CDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37228519.E25ACD0F@MexComUSA.net> Date: Sat, 24 Apr 1999 19:59:37 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Jerry Alexandratos , freebsd-mobile@FreeBSD.ORG Subject: Re: Newbus Woes References: <199904250032.SAA01995@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > In message Jerry Alexandratos writes: > : So, are pccards basically useless until pccard folds into the newbus > : scheme? > > Yes and no. Soren has some patches that he posted to this list that > help things. However, SIO uses the newbus stuff, and there is no > newbus stuff working right now for pccard, so it won't work. zp works > for me, and I've had ep working for me, but I get panics on card > eject. > > I'm working on correcting the situation. > > Warner Today's world and kernel, my pcmcia ed0 is recognized but panics and reboots when I try to configure it. My modem card is recognized but can't assign an IRQ. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Apr 24 23:38:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0258714D9B for ; Sat, 24 Apr 1999 23:38:20 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (9922 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 24 Apr 1999 23:38:20 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 24 Apr 1999 23:38:20 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: vaio 3.1-pao 3c589 in time warp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i built pao on a vaio 505tx over a 3.1-release (which worked well). but packets sent to the pao host seem to undergo massive delay before they are noticed. i.e. look at a steady ping to the pao host as viewed from another host on the same ether. oth:/usr/src# tcpdump host pao tcpdump: listening on fxp0 23:19:52.350165 oth.xy > pao.xy: icmp: echo request 23:19:53.359216 oth.xy > pao.xy: icmp: echo request 23:19:54.369256 oth.xy > pao.xy: icmp: echo request 23:19:55.379333 oth.xy > pao.xy: icmp: echo request 23:19:56.389334 oth.xy > pao.xy: icmp: echo request 23:19:57.399375 oth.xy > pao.xy: icmp: echo request 23:19:58.409410 oth.xy > pao.xy: icmp: echo request 23:19:59.419451 oth.xy > pao.xy: icmp: echo request 23:20:00.429497 oth.xy > pao.xy: icmp: echo request 23:20:01.439533 oth.xy > pao.xy: icmp: echo request 23:20:02.449578 oth.xy > pao.xy: icmp: echo request 23:20:03.459610 oth.xy > pao.xy: icmp: echo request 23:20:04.469691 oth.xy > pao.xy: icmp: echo request 23:20:05.479706 oth.xy > pao.xy: icmp: echo request 23:20:06.489730 oth.xy > pao.xy: icmp: echo request 23:20:07.499769 oth.xy > pao.xy: icmp: echo request 23:20:07.880098 pao.xy > oth.xy: icmp: echo reply 23:20:07.880194 pao.xy > oth.xy: icmp: echo reply 23:20:07.880293 pao.xy > oth.xy: icmp: echo reply 23:20:07.880392 pao.xy > oth.xy: icmp: echo reply 23:20:07.880489 pao.xy > oth.xy: icmp: echo reply 23:20:07.880588 pao.xy > oth.xy: icmp: echo reply 23:20:07.880687 pao.xy > oth.xy: icmp: echo reply 23:20:07.880789 pao.xy > oth.xy: icmp: echo reply 23:20:07.880882 pao.xy > oth.xy: icmp: echo reply 23:20:07.880982 pao.xy > oth.xy: icmp: echo reply 23:20:07.881088 pao.xy > oth.xy: icmp: echo reply 23:20:07.881183 pao.xy > oth.xy: icmp: echo reply 23:20:07.881276 pao.xy > oth.xy: icmp: echo reply 23:20:07.881375 pao.xy > oth.xy: icmp: echo reply 23:20:07.881473 pao.xy > oth.xy: icmp: echo reply 23:20:07.881571 pao.xy > oth.xy: icmp: echo reply 23:20:08.509806 oth.xy > pao.xy: icmp: echo request 23:20:09.519847 oth.xy > pao.xy: icmp: echo request 23:20:09.878312 pao.xy > oth.xy: icmp: echo reply 23:20:09.878408 pao.xy > oth.xy: icmp: echo reply 23:20:10.529884 oth.xy > pao.xy: icmp: echo request 23:20:11.539928 oth.xy > pao.xy: icmp: echo request 23:20:11.878364 pao.xy > oth.xy: icmp: echo reply 23:20:11.878458 pao.xy > oth.xy: icmp: echo reply 23:20:12.549980 oth.xy > pao.xy: icmp: echo request 23:20:13.560016 oth.xy > pao.xy: icmp: echo request all echo requests eventually get responses. it's just that they get very serious delay. here is the dmesg pao.xy:/root# dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Sat Apr 24 23:20:21 PDT 1999 root@pao.xy:/usr/src/sys/compile/PAO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (quarter-micron) (298.42-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x582 Stepping=2 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 127897600 (124900K bytes) Preloaded elf kernel "kernel" at 0xf0282000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x02 on pci0.7.3 vga0: rev 0x01 int a irq 9 on pci0.8.0 pcic0: rev 0x00 int a irq 255 on pci0.10.0 RL5C4XX PCI Config Reg: [CSC isa irq] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ep0 not found at 0x300 wlp0 not found at 0x300 pcic0 at 0x3e0-0x3e1 irq 11 on isa PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s2a Card inserted, slot 0 ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 and the syslog entry (line breaks added) is Apr 24 23:19:18 pao pccardd[55]: Card "3Com Corporation"("3C589") \ [TP/BNC LAN Card Ver. 2a] [000002] matched "3Com Corporation" \ ("3C589") [(null)] [(null)] i note that it does not say the 3c589's pccard.conf name, even though pccard.conf has logger entries # 3Com Etherlink III 3C589, 3C589B, 3C589C, 3C589D card "3Com Corporation" "3C589" config default "ep0" any insert logger -s 3Com Etherlink III inserted insert /etc/pccard_ether $device remove logger -s 3Com Etherlink III removed remove /etc/pccard_ether_remove $device a netstat (with network address disguised out of sick habits) shows no collisions or errors. and it does work well un-pao. pao.xy:/root# netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll tun0* 1500 0 0 0 0 0 lo0 16384 0 0 0 0 0 lo0 16384 127 127.0.0.1 0 0 0 0 0 ep0 1500 00.a0.24.ac.89.33 884 0 135 0 0 ep0 1500 666.42/24 666.42.0.38 884 0 135 0 0 it's like it's seeing, but not really seeing, the packets. pao.xy:/root# pccardc dumpcis 0 Configuration data for card in slot 0 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 65417, length 128, value is 0x0 Tuple #12, code = 0xff (Terminator), length = 0 1 slots found any clues appreciated. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 6:36: 4 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 4DA6F151D0; Sun, 25 Apr 1999 06:34:44 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id UAA07218; Sat, 24 Apr 1999 20:53:30 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Sat, 24 Apr 1999 20:53:29 -0500 (CDT) From: Douglas Carmichael To: hosokawa@jp.freebsd.org Cc: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: PAO3 can't recognize a USR/Megahertz PCMCIA modem on an NEC Versa LX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I installed PAO3 on my NEC Versa LX and tried to use a US Robotics PCMCIA modem, it recognized the modem card and allocated it (i.e. short two-beep sequence then a higher-pitched multi-beep sequence) , but when I tried a "cu -l /dev/cuaa3", I couldn't get an OK response from the modem and the response when receiving a character is very slow in cu. The strange thing is, the modem worked fine under FreeBSD 2.2.x with PAO for 2.2.x. What could be the problem? Here's my kernel configuration: machine "i386" cpu "I686_CPU" ident DCARMICH-FIXED maxusers 48 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console # If your laptop have not had Windoze95-Ready BIOS, please update it. # Such old BIOS'es sometimes have critical bugs at 32-bit protected # mode APM BIOS interface (which have not used by Windoze 3.1). # PC-card suspend/resume support (experimental) #options APM_PCCARD_RESUME options PCIC_RESUME_RESET # Keep power for serial cards when the system suspends # (If your machine hangs up when you try to suspend the system with # FAX/Modem PCMCIA card, uncomment this option). #options SIO_SUSP_KEEP_PWR # Detach SCSI devices when the SCSI card is removed #options SCSI_DETACH # Detach ATAPI devices when the ATA card is removed options ATAPI_DETACH # Japanese version of WaveLAN PCMCIA uses 2.4GHz band instead of 915MHz # band that US version uses. If you want to use Japanese version of # WaveLAN, uncomment this line, or edit the corresponding config entry # of /etc/pccard.conf. #options "WAVELAN_PCMCIA_24" # Suspend the system when the battery status is "Low" #options "APM_BATT_LOW_SUSPEND" # If you want to use NTP on laptop machines, uncomment the following # option. Current APM implementation affects NTP client. #options "APM_NO_CLOCK_ADJUST" # Some X-servers cannot survive suspend/resume on laptop. # This option kicks her when the system is resumed from suspended mode. #options SYSCONS_VTY_RESUME config kernel root on wd0 controller isa0 controller pci0 # Dont remove these two lines! pseudo-device card 1 # You must use "flags 0x1" when you don't hear any negotiation noise(?) # if you use modem card, or pccardd doesn't read cis tuple, tell you # 'No card in database for"(null)"("(null)")' in case of Cirrus Logic's # pcic is your PC. device pcic0 at isa? port 0x3e0 flags 0x1 irq 11 #device pcic0 at isa? port 0x3e4 irq 11 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM device wfd0 #IDE floppy (LS-120) # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS device sio0 at isa? port "IO_COM1" tty irq 4 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? net irq 7 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? pseudo-device loop pseudo-device sl 1 # DHCP uses BPF (Berkeley Packet Filter) pseudo-device bpfilter 4 # ijppp uses tun instead of ppp device pseudo-device vn 1 pseudo-device tun 4 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG # USB support #controller uhci0 #controller ohci0 #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device uhub0 #device ucom0 #device umodem0 #device hid0 #device ugen0 # #options USB_DEBUG #options USBVERBOSE dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #4: Sun Apr 25 07:51:00 CDT 1999 root@myname.my.domain:/usr/src/sys/compile/DCARMICH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (233.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff> real memory = 100663296 (98304K bytes) avail memory = 95416320 (93180K bytes) Preloaded elf kernel "kernel" at 0xf0245000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 vga0: rev 0xdc int a irq 10 on pci0.2.0 pcic0: rev 0x02 int a irq 255 on pci0.3.0 RL5C4XX PCI Config Reg: pcic1: rev 0x02 int b irq 255 on pci0.3.1 RL5C4XX PCI Config Reg: chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x02 on pci0.7.3 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 not found at 0x3f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 pcic0 at 0x3e0-0x3e1 irq 11 flags 0x1 on isa PC-Card ctlr(0) Ricoh RL5C478 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 changing root device to wd0s1a Card inserted, slot 0 sio3: type 16550A sio3: unload,gone Return IRQ=4 Card removed, slot 0 Card inserted, slot 0 Slot 0, unfielded interrupt (0) sio3: type 16550A sio3: unload,gone Return IRQ=4 Card removed, slot 0 Card inserted, slot 0 Slot 0, unfielded interrupt (0) sio3: type 16550A sio3: unload,gone Return IRQ=4 Card removed, slot 0 Card inserted, slot 0 Slot 0, unfielded interrupt (0) sio3: type 16550A sio3: unload,gone Return IRQ=4 Card removed, slot 0 pccard.conf: # PC-card sample configuration file # Tatsumi Hosokawa # # Removing all IRQ conflicts from this file can't be done because of some # IRQ-selfish PC-cards. So if you want to use some of these cards in # your machine, you will be forced to modify their IRQ parameters from # the following list. # # $Id: pccard.conf.sample,v 1.1.1.1.2.10.2.6.2.21.2.18 1999/03/17 14:29:45 toshi Exp $ # Generally available IO ports io 0x240-0x3ff # Generally available IRQs (DEPRECATED, USE OF THE OPTION IS DISCOURAGED) #irq 10 11 # Unavailable IRQs #ignirq 9 # refrain from using SoundBlaster's IRQ, by default. ignirq 5 3 # it may be helful for most of notebook PCs #ignirq 15 # Available memory slots memory 0xd4000 96k #----------------------------------------------------------------------- # Were not for special reasons, please add new entries at the top of # this file when you wrote new entries for unsupported cards. # And, if you succeed using new unsupported cards, please e-mail me # the new entries. # Tatsumi Hosokawa #----------------------------------------------------------------------- # ......... for unsupported cards ......... #----------------------------------------------------------------------- # Fast Ethernet Cards #----------------------------------------------------------------------- # PLANEX (PLANET) FNW-3600-T card "Fast Ethernet" "Adapter" config 0x1 "ed0" any insert logger -s PLANEX FNW-3600-T inserted insert /etc/pccard_ether $device remove logger -s PLANEX FNW-3600-T removed remove /etc/pccard_ether_remove $device # Laneed LD-10/100CD card "Laneed" "LD-10/100CD" config default "ed0" any insert logger -s Laneed LD-10/100CD inserted insert /etc/pccard_ether $device remove logger -s Laneed LD-10/100CD removed remove /etc/pccard_ether_remove $device # Linksys EtherFast 10/100 PC Card (NE2000 Compatible) card "Linksys" "EtherFast 10/100 PC Card \(PCMPC100\)" config default "ed0" any insert logger -s Linksys EtherFast 10/100 inserted insert /etc/pccard_ether $device remove logger -s Linksys EtherFast 10/100 removed remove /etc/pccard_ether_remove $device # Logitec LPM-LN100TX 100BASE-TX Ethernet LAN CARD card "Logitec" "LPM-LN100TX" config default "ed0" any insert logger -s Logitec LPM-LN100TX Ethernet inserted insert /etc/pccard_ether $device remove logger -s Logitec LPM-LN100TX Ethernet removed remove /etc/pccard_ether_remove $device # BayNetworks NETGEAR FA410TXC Fast Ethernet card "NETGEAR" "FA410TX" "Fast Ethernet" config default "ed0" any insert logger -s NETGEAR FA410TX inserted insert /etc/pccard_ether $device remove logger -s NETGEAR FA410TX removed remove /etc/pccard_ether_remove $device # Telecom Device SuperSocket RE550T card "Telecom Device K\.K\." "SuperSocket RE550T" config default "ed0" any insert logger -s Telecom Device SuperSocket RE550T inserted insert /etc/pccard_ether $device remove logger -s Telecom Device SuperSocket RE550T removed remove /etc/pccard_ether_remove $device # ONTEC LN-2221 10/100 Ethernet Adapter card "ONTEC & SMC" "LN-2221 Ethernet PCCard" config default "sn0" any insert logger -s ONTEC LN-2221 Ethernet inserted insert /etc/pccard_ether $device remove logger -s ONTEC LN-2221 Ethernet removed remove /etc/pccard_ether_remove $device # COREGA FastEther PCC-TX card "corega K.K." "corega FastEther PCC-TX" config default "ed0" any insert logger -s Corega FastEther PCC-TX inserted insert /etc/pccard_ether $device remove logger -s Corega FastEther PCC-TX removed remove /etc/pccard_ether_remove $device # I/O DATA PCET/TX card "IO DATA" "PCETTX" config default "ed0" any insert logger -s IO-DATA PCET/TX inserted insert /etc/pccard_ether $device remove logger -s IO-DATA PCET/TX removed remove /etc/pccard_ether_remove $device # CyQ've ELA-110 card "CyQ've" "ELA-110 10/100M LAN Card" config default "ed0" any insert logger -s "CyQ've ELA-100 10/100M LAN card inserted" insert /etc/pccard_ether $device remove logger -s "CyQ've ELA-100 10/100M LAN card removed" remove /etc/pccard_ether_remove $device # D-Link DFE-650 Ethernet Card card "D-Link" "DFE-650" config default "ed0" any 0x10 insert logger -s D-link DFE-650 inserted insert /etc/pccard_ether $device remove logger -s D-link DFE-650 removed remove /etc/pccard_ether_remove $device # MELCO LPC-TX card "MELCO/SMC" "LPC-TX" config default "sn0" any ether 0x4a 00:a0:dc insert logger -s MELCO/SMC LPC-TX inserted insert /etc/pccard_ether $device remove logger -s MELCO/SMC LPC-TX removed remove /etc/pccard_ether_remove $device #----------------------------------------------------------------------- # Ethernet Cards #----------------------------------------------------------------------- #IBM PCMCIA Ethernet I/II, RIOS PC CARD II ETHERNET card "IBM Corp\." "Ethernet" config default "ed0" any ether 0xff0 # 08:00:5a 00:04:ac 00:06:29 insert logger -s IBM PCMCIA Ethernet inserted insert /etc/pccard_ether $device remove logger -s IBM PCMCIA Ethernet removed remove /etc/pccard_ether_remove $device # Planet Smart COM 2000, Melco LPC-T card "PCMCIA" "UE2212" config default "ed0" any 0x10 ether 0xff0 00:00:e8 insert logger -s Planet Smart COM 2000 inserted insert /etc/pccard_ether $device remove logger -s Planet Smart COM 2000 removed remove /etc/pccard_ether_remove $device # Accton EN2212 card "ACCTON" "EN2212" config default "ed0" any 0x30 ether 0xff0 00:00:e8 insert logger -s Accton EN2212 inserted insert /etc/pccard_ether $device remove logger -s Accton EN2212 removed remove /etc/pccard_ether_remove $device # Planet Communications Ethernet Card ENW-3501-T card "IC-CARD+" "IC-CARD+" config default "ed0" any 0x10 insert logger -s Planet ENW-3501-T inserted insert /etc/pccard_ether $device remove logger -s Planet ENW-3501-T removed remove /etc/pccard_ether_remove $device # Planet Smart COM 3500, IC-Card Ethernet, SYSCOM SC100 Ethernet Card card "IC-CARD" "IC-CARD" config default "ed0" any 0x20 # config default "ed0" any 0x10 insert logger -s Planet Smart Com 3500 inserted insert /etc/pccard_ether $device remove logger -s Planet Smart Com 3500 removed remove /etc/pccard_ether_remove $device # 3Com Etherlink III 3C589, 3C589B, 3C589C, 3C589D card "3Com Corporation" "3C589" config default "ep0" any insert logger -s 3Com Etherlink III inserted insert /etc/pccard_ether $device remove logger -s 3Com Etherlink III removed remove /etc/pccard_ether_remove $device # 3Com Megahertz 3CXE589ET card "3Com" "Megahertz 589E" config default "ep0" any insert logger -s 3Com Megahertz 3C589E inserted insert /etc/pccard_ether $device remove logger -s 3Com Megahertz 3C589E removed remove /etc/pccard_ether_remove $device # Farallon EtherMac card "Farallon" "ENet" config default "ep0" any insert logger -s Farallon EtherMac inserted insert /etc/pccard_ether $device remove logger -s Farallon EtherMac removed remove /etc/pccard_ether_remove $device # Fujitsu FMV-J181 card "PCMCIA MBH10302" "01" config 0xc "fe0" any insert logger -s Fujitsu FMV-J181 inserted insert /etc/pccard_ether $device remove logger -s Fujitsu FMV-J181 removed remove /etc/pccard_ether_remove $device # NextCom J Link NC5310 card "NextComK\.K\." "NC5310 Ver1\.0.*" config 0x14 "fe0" any # config 0x1a "fe0" any insert logger -s NextCom J Link NC5310 inserted insert /etc/pccard_ether $device remove logger -s NextCom J Link NC5310 removed remove /etc/pccard_ether_remove $device # HITACHI HT-4840-11 card "HITACHI" "HT-4840-11" config 0x1a "fe0" any insert logger -s HITACHI HT-4840-11 inserted insert /etc/pccard_ether $device remove logger -s HITACHI HT-4840-11 removed remove /etc/pccard_ether_remove $device # CONTEC C-NET(PC)C Ethernet card "CONTEC Co\.,Ltd\." "C-NET\(PC\)C.*" config default "fe0" any ether 0x58 00:80:4c insert logger -s CONTEC C-NET inserted insert /etc/pccard_ether $device remove logger -s CONTEC C-NET removed remove /etc/pccard_ether_remove $device # TDK LAC-CD021, LAC-CD021A card "TDK" "LAC-CD02x" config default "fe0" any # These cards have same ID strings, and different MAC address # locations. ether 0x92 00:80:98 # LAC-CD021, LAC-021A ether 0x96 00:80:98 # LAC-CD021BX insert logger -s TDK LAC-CD021 inserted insert /etc/pccard_ether $device remove logger -s TDK LAC-CD021 removed remove /etc/pccard_ether_remove $device # Fujitsu FMV-J182, FMV-J182A card "FUJITSU" "LAN Card\(FMV-J182\)" config 0x32 "fe0" any # These cards have same ID strings, and different MAC address # locations. ether 0xf2c 00:00:0e #FMV-J182 ether 0x1cc 00:00:0e #FMV-J182A insert logger -s Fujitsu FMV-J182 inserted insert /etc/pccard_ether $device remove logger -s Fujitsu FMV-J182 removed remove /etc/pccard_ether_remove $device # Megahertz X-Jack Ethernet CC10BT/2 card "Megahertz" "CC10BT/2" config default "sn0" any ether attr2hex 00:00:86 insert logger -s Megahertz X-Jack Ethernet inserted insert /etc/pccard_ether $device remove logger -s Megahertz X-Jack Ethernet removed remove /etc/pccard_ether_remove $device # Megahertz Ethernet Adapter card "Megahertz" "ETHERNET ADAPTOR" config default "sn0" any ether attr2hex 00:00:86 insert logger -s Megahertz Ethernet inserted insert /etc/pccard_ether $device remove logger -s Megahertz Ethernet removed remove /etc/pccard_ether_remove $device # Dayna Communications CommuniCard E card "Dayna Communications, Inc\." "CommuniCard E" config default "ed0" any 0x10 ether 0x110 00:80:19 insert logger -s Dayna CommuniCard inserted insert /etc/pccard_ether $device remove logger -s Dayna CommuniCard remove remove /etc/pccard_ether_remove $device # GVC NIC-2000P Ethernet Card card "GVC" "NIC-2000p" config default "ed0" any 0x10 insert logger -s GVC NIC-200P inserted insert /etc/pccard_ether $device remove logger -s GVC NIC-200P removed remove /etc/pccard_ether_remove $device # No-brand NE-2000 compatible card card "PCMCIA" "ETHERNET V1.0" config default "ed0" any 0x10 ether 0xff0 # MAC address field should be filled insert logger -s PCMCIA ETHERNET V1.0 inserted insert /etc/pccard_ether $device remove logger -s PCMCIA ETHERNET V1.0 removed remove /etc/pccard_ether_remove $device # Eiger Labs Ethernet COMBO card "EIGER Labs Inc\." "Ethernet COMBO Card" config default "ed0" any 0x10 insert logger -s Eiger Labs Ethernet COMBO inserted insert /etc/pccard_ether $device remove logger -s Eiger Labs Ethernet COMBO inserted remove /etc/pccard_ether_remove $device # D-Link DE-650 Ethernet Card card "D-Link" "DE-650" config default "ed0" any 0x10 # New models of DE650 has no ether MAC address definition in CIS tupples. # If you have an older one, please uncomment the following line. # ether 0x40 00:80:c8 insert logger -s D-link DE-650 inserted insert /etc/pccard_ether $device remove logger -s D-link DE-650 removed remove /etc/pccard_ether_remove $device # National Semiconductor InfoMover 4100 card "National Semiconductor" "InfoMover 4100" config default "ed0" any ether 0xff0 08:00:17 insert logger -s National Semiconductor InfoMover inserted insert /etc/pccard_ether $device remove logger -s National Semiconductor InfoMover removed remove /etc/pccard_ether_remove $device # Accton EN2216 EtherCard card "ACCTON" "EN2216-PCMCIA-ETHERNET" config 0x22 "ed0" any 0x10 ether 0x1c0 00:00:e8 insert /etc/pccard_ether $device insert logger -s Accton EN2216 inserted remove /etc/pccard_ether_remove $device remove logger -s Accton EN2216 removed # Accton UE2216 Ethernet OEM card "PCMCIA" "PCMCIA-ETHERNET-CARD" config 0x22 "ed0" any 0x10 ether 0x1c0 00:00:e8 insert logger -s Accton UE2216 Ethernet inserted insert /etc/pccard_ether $device remove logger -s Accton UE2216 Ethernet removed remove /etc/pccard_ether_remove $device # NDC Instant-Link card "NDC" "Ethernet" config default "ed0" any 0x30 insert logger -s NDC Instant-Link inserted insert /etc/pccard_ether $device remove logger -s NDC Instant-Link removed remove /etc/pccard_ether_remove $device # Laneed PCMCIA Ethernet card. ELECOM LD-CDWA (DP83902A) card "MACNICA" "ME1-JEIDA" config default "ed0" any ether 0xb8 08:00:42 insert logger -s MACNICA PCMCIA Ethernet inserted insert /etc/pccard_ether $device remove logger -s MACNICA PCMCIA Ethernet removed remove /etc/pccard_ether_remove $device # Digital DEPCM-BA Ethernet card "DIGITAL" "DEPCM-XX" config default "ed0" any 0x10 insert logger -s Digital DEPCM-BA Ethernet inserted insert /etc/pccard_ether $device remove logger -s Digital DEPCM-BA Ethernet removed remove /etc/pccard_ether_remove $device # Matsushita Electric Industrial Co.,LTD. CF-VEL211P-B card "Matsushita Electric Industrial Co.,LTD." "CF-VEL211" config default "ed0" any ether 0xff0 00:80:45 insert logger -s Panasonic CF-VEL211 inserted insert /etc/pccard_ether $device remove logger -s Panasonic CF-VEL211 removed remove /etc/pccard_ether_remove $device # ADDTRON EP-210A card "EP-210 PCMCIA LAN CARD\." ".*" config default "ed0" any 0x10 ether 0x110 00:40:33 insert logger -s ADDTRON EP-210A inserted insert /etc/pccard_ether $device remove logger -s ADDTRON EP-210A removed remove /etc/pccard_ether_remove $device # PreMax PE-200 Ethernet Card card "PMX " "PE-200" config default "ed0" any 0x10 ether 0x7f0 00:20:e0 insert logger -s PREMAX PE-200 inserted insert /etc/pccard_ether $device remove logger -s PREMAX PE-200 removed remove /etc/pccard_ether_remove $device # No-brand NE2000 compatible card (FCC ID: LXLC1LANTB) card " " "Ethernet Combo card" config default "ed0" any 0x10 insert logger -s NE2000 compatible card inserted insert /etc/pccard_ether $device remove logger -s NE2000 compatible card removed remove /etc/pccard_ether_remove $device # RATOC REX-5588 (now testing...) card "PCMCIA LAN MBH10304 ES" " 01" # Kouji Yamamoto reported that # following entry worked with his REX-5588, but the card I borrowed # has no such config index on CIS tupple. Minor version problem? # # config 0x3a "fe0" 5 # ether 0x328 00:c0:d0 # # I tried to drive it by following entry on my DHU II, but it does # not work! # # config 0x1f "fe0" any config 0x3a "fe0" any # config 0x38 "fe0" any ether 0x32c 00:c0:d0 # many minor revs.... ether 0x328 00:c0:d0 ether 0x200 00:c0:d0 insert logger -s RATOC REX-5588 Ethernet inserted insert /etc/pccard_ether $device remove logger -s RATOC REX-5588 Ethernet removed remove /etc/pccard_ether_remove $device # SCM Ethernet Combo (*Not SMC :-)*) card "SCM" "Ethernet Combo card" config default "ed0" any 0x10 ether 0xff0 00:20:cb insert logger -s SCM Ethernet card inserted insert /etc/pccard_ether $device remove logger -s SCM Ethernet card removed remove /etc/pccard_ether_remove $device # Linksys Combo PCMCIA Ethernet Card card "LINKSYS" "E-CARD" config default "ed0" any 0x10 insert logger -s Linksys Combo Ethernet inserted insert /etc/pccard_ether $device remove logger -s Linksys Combo Ethernet removed remove /etc/pccard_ether_remove $device # Linksys Combo PCMCIA Ethernet Card card "Linksys" "Combo PCMCIA EthernetCard \(EC2T\)" config default "ed0" any 0x10 insert logger -s Linksys PCMCIA Ethernet inserted insert /etc/pccard_ether $device remove logger -s Linksys PCMCIA Ethernet removed remove /etc/pccard_ether_remove $device # I/O DATA PCLA/T card "I-O DATA" "PCLA" config default "ed0" any 0x10 ether 0x1c0 00:a0:b0 ether 0xff0 00:a0:b0 insert logger -s I-O DATA PCLA/T Ethernet inserted insert /etc/pccard_ether $device remove logger -s I-O DATA PCLA/T Ethernet removed remove /etc/pccard_ether_remove $device # I/O DATA PCLA/TE card "IO DATA" "PCLATE" config default "ed0" any 0x10 insert logger -s I-O DATA PCLA/TE Ethernet inserted insert /etc/pccard_ether $device remove logger -s I-O DATA PCLA/TE Ethernet removed remove /etc/pccard_ether_remove $device # Fujitsu Towa LA501 Ethernet card "FUJITSU TOWA" "LA501" config 0x29 "fe1" any 0x10 ether 0x332 00:00:0e insert logger -s Fujitsu Towa LA501 Ethernet inserted insert /etc/pccard_ether $device remove logger -s Fujitsu Towa LA501 Ethernet removed remove /etc/pccard_ether_remove $device # Grey Cell GCS2220 Ethernet Card card "Grey Cell" "GCS2220" config default "ed0" any 0x10 insert logger -s Grey Cell GCS2220 inserted insert /etc/pccard_ether $device remove logger -s Grey Cell GCS2220 removed remove /etc/pccard_ether_remove $device # Epson EEN10B Ethernet Card card "Seiko Epson Corp\." "Ethernet" config default "ed0" any 0x10 ether 0xff0 00:00:48 insert logger -s Epson EEN10B Ethernet Card inserted insert /etc/pccard_ether $device remove logger -s Epson EEN10B Ethernet Card removed remove /etc/pccard_ether_remove $device # COREGA Ethernet Card card "Corega,K\.K\." "\(Ethernet LAN Card\)" config default "ed0" any ether 0xff0 00:00:f4 insert logger -s Corega Ethernet inserted insert /etc/pccard_ether $device remove logger -s Corega Ethernet removed remove /etc/pccard_ether_remove $device # COREGA Ether PCC-T card "corega K.K." "corega Ether PCC-T" config default "ed0" any insert logger -s Corega Ether PCC-T inserted insert /etc/pccard_ether $device remove logger -s Corega Ether PCC-T removed remove /etc/pccard_ether_remove $device # Telecom Device SuperSocket RE450T card "Ethernet" "Adapter" config 0x3 "ed0" any # There's another minor revision of this card that has no MAC address in # CIS tupple. This revision does not require "ether" definition. If you # have it, please comment out the following line. ether 0x110 00:e0:98 # Please note that if the log message says that the MAC address of the # card is 00:00:00:00:00:00, please uncomment the "ether" definition again # and set it to proper value. insert logger -s Telecom Device SuperSocket RE450T inserted insert /etc/pccard_ether $device remove logger -s Telecom Device SuperSocket RE450T removed remove /etc/pccard_ether_remove $device # Telecom Device SuperSocket RE450T card "Telecom Device K.K." "SuperSocket RE450T" config default "ed0" any insert logger -s Telecom Device SuperSocket RE450T inserted insert /etc/pccard_ether $device remove logger -s Telecom Device SuperSocket RE450T removed remove /etc/pccard_ether_remove $device # RPTI EP401 Ethernet NE2000 compatible card "RPTI" "EP401 Ethernet NE2000 Compatible" config default "ed0" any insert logger -s RPTI EP401 Ethernet inserted insert /etc/pccard_ether $device remove logger -s RPTI EP401 Ethernet removed remove /etc/pccard_ether_remove $device # Nihon Unisys, Ltd. JPF0400-LAN card "Nihon Unisys, Ltd." "JPF0400-LAN" config default "ed0" any ether 0xff0 00:80:45 insert logger -s Nihon Unisys JPF0400-LAN inserted insert /etc/pccard_ether $device remove logger -s Nihon Unisys JPF0400-LAN removed remove /etc/pccard_ether_remove $device # Nihon Unisys, Ltd. JPF0400-ETH card "Nihon Unisys, Ltd." "JPF0400-ETH" config default "ed0" any ether 0xff0 00:80:45 insert logger -s Nihon Unisys JPF0400-ETH inserted insert /etc/pccard_ether $device remove logger -s Nihon Unisys JPF0400-ETH removed remove /etc/pccard_ether_remove $device # SURECOM EtherPerfect EP-427 Adapter card "TAMARACK" "Ethernet" config default "ed0" any ether attr2hex 00:47:43 insert logger -s SURECOM EtherPerfect EP-427 inserted insert /etc/pccard_ether $device remove logger -s SURECOM EtherPerfect EP-427 removed remove /etc/pccard_ether_remove $device # RATOC REX-R280 card "RATOC System Inc\." "10BASE_T CARD R280" config 0x3a "fe0" any ether 0x1fc 00:c0:d0 insert logger -s RATOC REX-R280 inserted insert /etc/pccard_ether $device remove logger -s RATOC REX-R280 removed remove /etc/pccard_ether_remove $device # D-Link DE-660 Ethernet Card card "D-Link" "DE-660" config default "ed0" any 0x10 insert logger -s D-link DE-660 inserted insert /etc/pccard_ether $device remove logger -s D-link DE-660 removed remove /etc/pccard_ether_remove $device # Allied Telesis Ethernet Card card "Allied Telesis,K\.K" "Ethernet LAN Card" config default "ed0" any 0x10 ether 0xff0 00:00:f4 insert logger -s Allied Telesis Ethernet Card inserted insert /etc/pccard_ether $device remove logger -s Allied Telesis Ethernet Card removed remove /etc/pccard_ether_remove $device # Toshiba Joho System PTJ-LAN/T card "TJ" "Ethernet" config default "ed0" any 0x10 insert logger -s TJ Ethernet card inserted insert /etc/pccard_ether $device remove logger -s TJ Ethernet card removed remove /etc/pccard_ether_remove $device # NextCom Next Hawk Etherneet Adapter card "NextCom K.K." "Next Hawk" config default "ed0" any insert logger -s NextCom Next Hawk Ethernet inserted insert /etc/pccard_ether $device remove logger -s NextCom Next Hawk Ethernet removed remove /etc/pccard_ether_remove $device # Logitec LPM-LN20T card "Logitec" "LPM-LN20T" config default "ed0" any insert logger -s Logitec LPM-LN20T inserted insert /etc/pccard_ether $device insert logger -s Logitec LPM-LN20T removed remove /etc/pccard_ether_remove $device # CentreCOM LA-PCM V2 card "Allied Telesis, K\.K\." "CentreCOM LA-PCM_V2" config 0x20 "ed0" any 0x10 insert logger -s CentreCOM LA-PCM V2 inserted insert /etc/pccard_ether $device remove logger -s CentreCOM LA-PCM V2 removed remove /etc/pccard_ether_remove $device # Map Japan MPL-972 card "2408LAN" "Ethernet" config default "ed0" any insert logger -s Map Japan MPL-972 inserted insert /etc/pccard_ether $device remove logger -s Map Japan MPL-972 removed remove /etc/pccard_ether_remove $device # EXPsys PCMCIA Ethernet Combo, Relia PCMCIA Ethernet card "PCMCIA LAN" "Ethernet" config default "ed0" any insert logger -s EXPsys Ethernet inserted insert /etc/pccard_ether $device remove logger -s EXPsys Ethernet removed remove /etc/pccard_ether_remove $device # CyQ've ELA-010 10BASE-T LAN Card card "CyQ've" "ELA-010" config default "ed0" any 0x10 insert logger -s CyQ\'ve ELA-010 LAN card inserted insert /etc/pccard_ether $device remove logger -s CyQ\'ve ELA-010 LAN card removed remove /etc/pccard_ether_remove $device # Billionton LNT-10TB card "Billionton" "LNT-10TB" config 0x20 "ed0" any insert logger -s Billionton LNT-10TB inserted. insert /etc/pccard_ether $device remove logger -s Billionton LNT-10TB removed. remove /etc/pccard_ether_remove $device # MELCO LPC2-T card "MELCO" "LPC2-T" config default "ed0" any insert logger -s MELCO LPC2-T inserted insert /etc/pccard_ether $device remove logger -s MELCO LPC2-T removed remove /etc/pccard_ether_remove $device # CNet PCMCIA PowerNIC CN40BC(BT) card "CNet" "CN40BC Ethernet" config default "ed0" any 0x10 insert logger -s CNet CN40BC inserted insert /etc/pccard_ether $device remove logger -s CNet CN40BC removed remove /etc/pccard_ether_remove $device # Kingston KNE-PCM/x Ethernet card "Kingston Technology Corp\." "EtheRx PC Card Ethernet.*" config default "ed0" any ether 0xff0 00:c0:f0 insert logger -s Kingston KNE-PCM/x Ethernet inserted insert /etc/pccard_ether $device remove logger -s Kingston KNE-PCM/x Ethernet removed remove /etc/pccard_ether_remove $device # NEC PC-9801N-J12 card "NEC" "PC-9801N-J12" config default "ed0" any ether 0xff0 00:00:4c insert logger -s NEC PC-9801N-J12 inserted insert /etc/pccard_ether $device remove logger -s NEC PC-9801N-J12 removed remove /etc/pccard_ether_remove $device #----------------------------------------------------------------------- # Modem Cards #----------------------------------------------------------------------- # Most of modem cards does not match these definitions. Please read # "wildcard entries" listed at the end of this file. #----------------------------------------------------------------------- # Omron MD24XCA FAX/Data Modem card "OMRON Corp\." "MD24XCA" config auto "sio3" pio reset 10000 insert logger -s OMRON MD24XCA Modem inserted remove logger -s OMRON MD24XCA Modem removed #----------------------------------------------------------------------- # ISDN Serial Cards #----------------------------------------------------------------------- # NTT-IT ThunderCard card "NTT Intelligent Technology Co., Ltd." "ThunderCard DD128" config auto "sio3" any 0x80 reset 1000 insert logger -s NTT-IT Thunder-card inserted remove logger -s NTT-IT Thunder-card removed #----------------------------------------------------------------------- # Digital Cellular Cards #----------------------------------------------------------------------- # NTT DoCoMo DATA/FAX Adapter card "NTT DoCoMo" "PCMCIA DATA/FAX.*" config auto "sio3" any 0x82 insert logger -s NTT DoCoMo DATA/FAX Adapter inserted remove logger -s NTT DoCoMo DATA/FAX Adapter removed # NTT DoCoMo Mobile D Card 96P1 card "NTT DoCoMo" "Mobile D Card 96P1" config auto "sio3" any 0x82 insert logger -s NTT DoCoMo Mobile D Card 96P1 Adapter inserted remove logger -s NTT DoCoMo Mobile D Card 96P1 Adapter removed #----------------------------------------------------------------------- # PHS Digital Communication Cards #----------------------------------------------------------------------- # NTT Personal Paldio Data/Fax Card DC-1S card "NTT Personal" "Paldio Data/Fax Card" "DC-1S" config auto "sio3" any 0x40000 insert logger -s NTT Personal Paldio Data/Fax Card DC-1S inserted remove logger -s NTT Personal Paldio Data/Fax Card DC-1S removed # NTT DoCoMo (formerly NTT Personal) Paldio 321S card "NTT Personal" "32K Paldio 321S PC CARD" config auto "sio3" any 0x40000 insert logger -s NTT Personal Paldio 321S PC Card inserted remove logger -s NTT Personal Paldio 321S PC Card removed #----------------------------------------------------------------------- # Misc. Serial Cards #----------------------------------------------------------------------- # Panasonic FM-RADIO card card "Panasonic" "CF-JVR101" config auto "sio3" pio insert logger -s Panasonic FM radio card inserted remove logger -s Panasonic FM radio card removed #----------------------------------------------------------------------- # SCSI Cards #----------------------------------------------------------------------- # Adaptec SlimSCSI card "Adaptec, Inc\." "APA-1460.*" config default "aic0" any insert logger -s Adaptec Slim SCSI inserted remove logger -s Adaptec Slim SCSI removed # New Media Corporation BASICS SCSI # (Do not put this entry under Bustoaster) card "BASICS by New Media Corporation" "SCSI Sym53C500" config 0x14 "ncv0" any insert logger -s New Media BASICS SCSI inserted remove logger -s New Media BASICS SCSI removed # NewMedia Bustoaster SCSI card "New Media" "SCSI" config 0x22 "aic0" any insert logger -s New Media Bus Toaster inserted remove logger -s New Media Bus Toaster removed # RATOC REX-5536AM, REX-9836A, ICM PSC-2401 SCSI # (Don't put this entry under REX5535 series!) # There's a buggy revision of this card which has broken CIS tupples. # if you can't use this card, please use the point enabler. (for example, # type "pccardc enabler 0 stg0 -a 0x4140 -i 5" from root command prompt) card "PCMCIA SCSI MBH10404" "01" config 0x37 "stg0" any insert logger -s RATOC REX-5536AM SCSI inserted remove logger -s RATOC REX-5536AM SCSI removed # RATOC REX-5535AC, REX-5535X, REX-9835X, REX-9835Z SCSI card "PCMCIA SCSI MBH1040" "01" config 0x3a "spc0" any insert logger -s RATOC REX-5535 SCSI inserted remove logger -s RATOC REX-5535 SCSI removed # RATOC REX-5536M card "PCMCIA SCSI2 CARD" "01" config 0x5 "stg0" any 0 insert logger -s RATOC REX-5536M SCSI inserted remove logger -s RATOC REX-5536M SCSI removed # RATOC REX-5536, Melco IFC-SC card "1195 RATOC System Inc\." "REX5536 SCSI2 CARD" config 0x7 "stg0" any 0 insert logger -s RATOC REX-5536 SCSI inserted remove logger -s RATOC REX-5536 SCSI removed # RATOC REX-9530 card "RATOC System Inc." "SCSI2 CARD.*" config default "ncv0" any 0x84d00000 insert logger -s RATOC REX-9530 SCSI inserted remove logger -s RATOC REX-9530 SCSI removed # IO DATA PCSC-DV # Macnica Miracle SCSI mPS100 card "MACNICA" "MIRACLE SCSI" "mPS100" "D.0" config 0x11 "ncv0" any 0xb6250000 insert logger -s MACNICA Miracle SCSI inserted remove logger -s MACNICA Miracle SCSI removed # Macnica Miracle SCSI-II mPS110 card "MACNICA" "MIRACLE SCSI-II mPS110" config 0x15 "ncv0" any 0 insert logger -s MACNICA Miracle SCSI-II inserted remove logger -s MACNICA Miracle SCSI-II removed # IBM SCSI PCMCIA Card card "IBM Corp\." "SCSI PCMCIA Card" config default "stg0" any insert logger -s IBM SCSI PCMCIA Card inserted remove logger -s IBM SCSI PCMCIA Card removed # Future Domain SCSI2GO card "Future Domain Corporation" "SCSI PCMCIA Credit Card Controller" config default "stg0" any insert logger -s Future Domain SCSI2GO inserted remove logger -s Future Domain SCSI2GO removed # KME (TAXAN ICD-400PN, etc.) card "KME" "KXLC002" config 0x26 "ncv0" any 0xb4d00000 insert logger -s KME SCSI PCMCIA Card inserted remove logger -s KME SCSI PCMCIA Card removed # Qlogic Fast SCSI card "QLOGIC CORPORATION" "pc05" config 0x2f "ncv0" any 0x84d00000 insert logger -s Qlogic Fast SCSI inserted remove logger -s Qlogic Fast SCSI removed # Media Intelligent SCSI-2 PC Card MSC-200 card "EPSON" "SCSI-2 PC Card SC200" config 0x12 "ncv0" any insert logger -s EPSON SCSI-2 PC Card MSC200 inserted remove logger -s EPSON SCSI-2 PC Card MSC200 removed # NEC PC-9801N-J03R card "NEC" "PC-9801N-J03R" config 0x15 "ncv0" any 0 insert logger -s NEC PC-9801N-J03R inserted remove logger -s NEC PC-9801N-J03R removed # NEC PC-9801N-J03 # (Don't put this entry previous to NEC PC-9801N-J03R) card "NEC" "PC-9801N-J03" config 0x15 "ncv0" any 0xb6000000 # (port 0x330 is used for MPU401 on Toshiba Libretto60) # config 0x11 "ncv0" any 0xb6000000 insert logger -s PC-9801N-J03 inserted remove logger -s PC-9801N-J03 removed # WORKBIT Ninja SCSI series card "WBT" "NinjaSCSI-3" config default "nin0" any insert logger -s Workbit NinjaSCSI-3 inserted remove logger -s Workbit NinjaSCSI-3 removed # Fujitsu Towa Electron SC501 SCSI (RATOC REX-5535 OEM) card "FUJITSU TOWA" "SC501" config 0x3a "spc0" any insert logger -s Fujitsu Towa SC501 SCSI inserted remove logger -s Fujitsu Towa SC501 SCSI removed #------------------------ untested ---------------------------- #------------------------ untested ---------------------------- # If these entry do not work, try other config index than default. # Please e-mail me whether it works or not. Thanks # Tatsumi Hosokawa card "MIDORI ELECTRONICS.*" "CN-SC43.*" config default "ncv0" any 0x80100000 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp card "EIger Labs" "PCMCIA-to-SCSI Adapter" config default "ncv0" any insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp card "SCSI PCMCIA Adapter Card" ".*" config 0x20 "stg0" any insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp card " SIMPLE TECHNOLOGY Corporation" "SCSI PCMCIA Credit Card Controller" config default "stg0" any insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp card "KME" "KXLC003" config 0x26 "ncv0" any 0xb4d00000 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp #----------------------------------------------------------------------- # ATAPI CD-ROM Cards #----------------------------------------------------------------------- # IO Data CBIDE (bundled with CDP-FX24, etc.) card "WIT" "IDE16" config default "wdc1" any insert logger -s IO Data CBIDE inserted remove logger -s IO Data CBIDE removed # DHU Mobile Media CD-ROM # (no hotplug support) card "Digital Equipment Corporation\." "Digital Mobile Media CD-ROM" config 0xb "wdc1" 15 # Caravelle PSC-IDE 6x ATAPI CD-ROM card "Caravelle" "PSC-IDE " config 0x2a "wdc1" any 0x1 insert logger -s Caravelle PSC-IDE card inserted remove logger -s Caravelle PSC-IDE card removed # IBM Portable 4X Speed CD-ROM Drive CD-400 card "IBM" "PCMCIA CD-ROM Drive CD-400" config 0x1 "wdc1" any 0x1000 cardio 0x250 0x20 insert logger -s IBM PCMCIA CD-ROM CD-400 inserted remove logger -s IBM PCMCIA CD-ROM CD-400 removed # IO Data PCIDEII (bundled with CDP-TX10, etc.) card "IO DATA" "PCIDEII" config default "wdc1" any insert logger -s IO Data PCIDEII inserted remove logger -s IO Data PCIDEII removed # IBM CD-20XSeries(IDE PC Card) card "IBM" "PCMCIA Portable CD-ROM Drive" config 0x1 "wdc1" any 0x1000 cardio 0x250 0x20 insert logger -s IBM CD-20XS inserted remove logger -s IBM CD-20XS removed # NOVAC Station Series card "PCMCIA" "CD-ROM" config default "wdc1" any insert logger -s Novac Station CD-ROM inserted remove logger -s Novac Station CD-ROM removed #----------------------------------------------------------------------- # Flash ATA Cards #----------------------------------------------------------------------- # SunDisk Flash ATA card "SunDisk" ".*" config 0x03 "wdc1" any insert logger -s SunDisk Flash ATA inserted remove logger -s SunDisk Flash ATA removed # Midori Elec. Flash ATA card "Midori Elec\." ".*FLASH.*" config 0x03 "wdc1" any insert logger -s Midori Flash ATA inserted remove logger -s Midori Flash ATA removed #----------------------------------------------------------------------- # ATA HDD Cards #----------------------------------------------------------------------- card "Maxtor" "MXL.*" config 0x03 "wdc1" any insert logger -s Maxtor ATA HDD inserted remove logger -s Maxtor ATA HDD removed #----------------------------------------------------------------------- # ATA External HDD Adapters #----------------------------------------------------------------------- # Greystone Diskdock card "GREYSTONE PERIPHERAL DISKDOCK" ".*" config default "wdc1" any insert logger -s Greystone Diskdock inserted remove logger -s Greystone Diskdock removed # card "INTEGRAL PERIPHERALS" "ATA CARD" config default "wdc1" any insert logger -s Integral Peripherals inserted remove logger -s Integral Peripherals removed # DATAFAB PCMMD2 card "DATAFAB" "PCMCIA-TO-IDE" config 0x1 "wdc1" any insert logger -s DATAFAB PCMMD2 inserted remove logger -s DATAFAB PCMMD2 removed # PCM250AM 2.5in HDD adapter card "PC CARD MANUFACTURER" "PCMCIA ATA/ATAPI Adapter" config 0xd "wdc1" any insert logger -s PCM250AM inserted remove logger -s PCM250AM removed # Sicon Peripheral PCMCIA ATA/ATAPI Adapter card "Sicon Peripheral" "PCMCIA ATA/ATAPI Adapter" config default "wdc1" any insert logger -s Sicon Peripherals inserted remove logger -s Sicon Peripherals removed # Microtech XpressDock card "Microtech International Inc\." "IDE PCCARD" config default "wdc1" any 0x2000 cardio 0x170 0x10 insert logger -s Microtech XpressDock inserted remove logger -s Microtech XpressDock removed #----------------------------------------------------------------------- # ATAPI LS120 Super Floppy Disk #----------------------------------------------------------------------- # LK-RM120 card "Panasonic" "LMEK0406" config 0x22 "wdc1" any 0x1 insert logger -s Panasonic LMEK0406 inserted remove logger -s Panasonic LMEK0406 removed #----------------------------------------------------------------------- # ATAPI ZIP Drive #----------------------------------------------------------------------- # CitiDISK & Addonics PocketZIP card "Shining" "PMIDE-ASC" config default "wdc1" any 0x2000 insert logger -s CitiDISK/PocketZIP inserted remove logger -s CitiDISK/PocketZIP removed #----------------------------------------------------------------------- # # Ongoing Projects ---- These entries are for ongoing projects of # our package. Most of these entries do not work. # #----------------------------------------------------------------------- #----------------------------------------------------------------------- # Sound cards #----------------------------------------------------------------------- # RATOC REX-5570 Sound Card card "1195 RATOC System Inc\." "REX5570 SOUND CARD" config default "opl0" any #----------------------------------------------------------------------- # Multifunction cards #----------------------------------------------------------------------- # Multifunction card support is still under development. If you want # to use them as modem only in conservative way, uncomment "modem-only" # definitions, comment-out multifunction definitions, and recompile # pccardd and kernel without MULTIFUNC option. (see # PAO-dir/usr.sbin/pccard/pccardd and PAO config file for details) # Tatsumi Hosokawa # APEX DATA MultiCard (as Modem only) card "APEX DATA" "MULTICARD" config 0xb "sio3" any insert logger -s APEX DATA MultiCard inserted as Modem remove logger -s APEX DATA MultiCard removed # Megahertz multifunction card: # The second multifunction definition does not work (under development). # if you want to use this card as modem, uncomment the first one. # Megahertz X-Jack Ethernet/Modem 14.4K (as Modem only) card "Megahertz" "XJEM1144/CCEM1144" config 0x27 "sio3" any insert logger -s Megahertz X-Jack Multifunction Card inserted as Modem. remove logger -s Megahertz X-Jack Multifunction Card removed. # Megahertz X-Jack Ethernet/Modem 14.4K #card "MEGAHERTZ" "XJEM1144/CCEM1144" # multifunc # config default "sn0" any # config 0x27 "sio3" shared # insert logger -s Megahertz X-Jack Multifunction Card inserted # remove logger -s Megahertz X-Jack Multifunction Card removed # TDK Multifunctioon Card (as Modem) card "TDK" "GlobalNetworker 3410/3412" config default "sio3" any insert logger -s TDK Multifunction Card inserted as Modem remove logger -s TDK Multifunction Card removed # Toshiba Modem/LAN card IPC5001B card "TOSHIBA" "Modem/LAN Card" config 0x25 "sio3" any insert logger -s TOSHIBA IPC5001B Multifunction Card inserted as Modem remove logger -s TOSHIBA IPC5001B Multifunction Card removed # Motorola Marine multifunction card (as modem) card "Motorola, Inc\." "MARINER MODEM/FAX/LAN" config 0x35 "sio3" any insert logger -s Motorola Marine inserted as Modem remove logger -s Motorola Marine removed # Xircom CreditCard Ethernet 10/100+ Modem 56 (as modem) card "Xircom" "CreditCard Ethernet" config 0x27 "sio3" any insert logger -s Xircom CEM56 Card inserted as Modem remove logger -s Xircom CEM56 Card removed # Intel EtherExpress(TM) PRO/100 LAN/Modem PC Card Adapter (as modem) card "Intel" "EtherExpress\(TM\) PRO/100 LAN/Modem PC Card Adapter" config 0x1f "sio3" any insert logger -s Intel EtherExpress PRO/100 LAN/Modem as Modem remove logger -s Intel EtherExpress PRO/100 LAN/Modem # RATOC REX-5572 (as SCSI only) card "RATOC System Inc\." "SOUND/SCSI2 CARD.*" config default "ncv0" any 0x84d00000 cardio 0x640 0x10 insert logger -s RATOC SOUND/SCSI2 REX-5572 inserted as SCSI remove logger -s RATOC SOUND/SCSI2 REX-5572 removed # IO DATA PCMF144/20 (as Flash ATA only) card "IO DATA" "ATA&MODEM" config 0x7 "wdc1" any insert logger -s IO DATA PCMF144/20 inserted as ATA remove logger -s IO DATA PCMF144/20 removed # Telecom Device SuperSocket LM336 (as Ethernet only) card "PCMCIAs" "LanModem" config default "ed0" any insert logger -s SuperSocket LM336 inserted as Ethernet insert /etc/pccard_ether $device remove logger -s SuperSocket LM336 removed remove /etc/pccard_ether_remove $device #----------------------------------------------------------------------- # Wireless LAN #----------------------------------------------------------------------- # NCR Wavelan PCMCIA # If you want to use Japanese version, uncomment the second config # line and comment-out the first line. card "NCR" "WaveLAN/PCMCIA" config default "wlp0" any # US version (915MHz) # config default "wlp0" any 0x01 # Japanese version (2.4GHz) ether wavelan insert logger -s NCR WaveLAN PCMCIA inserted insert /etc/pccard_ether $device remove logger -s NCR WaveLAN PCMCIA removed remove /etc/pccard_ether_remove $device # AT&T GIS Wavelan PCMCIA # If you want to use Japanese version, uncomment the second config # line and comment-out the first line. card "AT&T" "WaveLAN/PCMCIA" config default "wlp0" any # US version (915MHz) # config default "wlp0" any 0x01 # Japanese version (2.4GHz) ether wavelan insert logger -s AT\&T WaveLAN PCMCIA inserted insert /etc/pccard_ether $device remove logger -s AT\&T WaveLAN PCMCIA removed remove /etc/pccard_ether_remove $device # Digital RoamAbout/DS card "Digital" "RoamAbout/DS" config default "wlp0" any ether wavelan insert logger -s Digital RoamAbout/DS inserted insert /etc/pccard_ether $device remove logger -s Digital RoamAbout/DS removed remove /etc/pccard_ether_remove $device # NetWave AirSurfer # NOTE: For some machines, wait cycle for memory access is required. # you should change "0x40" on the last part of "cardmem" line to "0x44", # like: # cardmem 0xd4000 0x20000 0x9000 0x44 # IBM ThinkPads are known to require this change. card "Xircom" "CreditCard Netwave" config 0x01 "cnw0" any cardmem 0xd4000 0x20000 0x9000 0x40 # config 0x01 "cnw1" any # cardmem 0xdd000 0x20000 0x9000 0x40 ether 0x126 00:80:c7 00:20:d8 insert logger -s Netwave Ethernet inserted insert /etc/pccard_ether $device remove logger -s Netwave Ethernet removed remove /etc/pccard_ether_remove $device # Victor M-MOIL CARD card "JVC" "MiniMoil Ethernet Card" config 0x01 "sn0" any insert logger -s MiniMoil Ethernet inserted insert /etc/pccard_ether $device remove logger -s MiniMoil Ethernet removed remove /etc/pccard_ether_remove $device #----------------------------------------------------------------------- # Video Capture Cards #----------------------------------------------------------------------- # IBM Smart Capture Card card "IBM Corp\." "Video Capture" config default "scc0" pio cardmem 0xd4000 0x0 0x8000 insert logger -s Smart Capture Card inserted remove logger -s Smart Capture Card removed #----------------------------------------------------------------------- # Speech Synthesizer Cards #----------------------------------------------------------------------- # Hitachi microcomputer speech synthesizer card card "HITACHI MICROCOMPUTER SYSTEM LTD." "MSSHVPC02" config default "hss0" pio insert logger -s Hitachi microcomputer speech synthesizer inserted remove logger -s Hitachi microcomputer speech synthesizer removed #----------------------------------------------------------------------- # Joystick Port Cards #----------------------------------------------------------------------- card "IO DATA" "PCJOY" config default "joy0" pio # config 0x1 "joy0" pio # config 0x2 "joy0" pio insert logger -s IO DATA PCJOY inserted remove logger -s IO DATA PCJOY removed #----------------------------------------------------------------------- # Floppy Drive Cards #----------------------------------------------------------------------- # Libretto floppy drive. card "Y-E DATA" "External FDD" config 0x4 "fdc1" any insert logger -s Y-E DATA External FDD inserted remove logger -s Y-E DATA External FDD removed # ------------------------------------------------------------------- # # Experimental ---- If you have one of them, please e-mail me *WHETHER # IT WORKS OR NOT*. I wrote these entries by reading Linux PCMCIA driver # package. I've not tested them. I need results of your experiences. # Especially, if the ed_probe() is succeeded, it does not always mean # that probed MAC address is correct. If you have or if your friend # has these cards, send me the result of the results of # # pccardc dumpcis # and # pccardc rdattr 0 0 1000 (the first 0 means slot number) # # of these cards. I can write more accurate pccard.conf entries if I # can read these result. # # I NEED YOUR HELP!!!! # # Thanks. # # My e-mail address is hosokawa@jp.FreeBSD.org (Tatsumi Hosokawa) # # ------------------------------------------------------------------- #----------------------------------------------------------------------- # Ethernet Cards #----------------------------------------------------------------------- # CNet CN30BC Ethernet Card card "CNet.*" "CN30BC" config default "ed0" any 0x10 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # DataTrek NetCard card "DataTrek\." "NetCard" config default "ed0" any 0x10 ether 0xff0 00:20:e8 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # D-Link DE-650 Ethernet Card card ".*D-Link PC Ethernet Card.*" ".*" config default "ed0" any 0x10 ether 0x40 00:80:c8 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # D-Link DE-650 Ethernet Card card ".*" ".*D-Link PC Ethernet Card.*" config default "ed0" any 0x10 ether 0x40 00:80:c8 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Edimax Ethernet Combo card "Edimax Technology Inc\." "PCMCIA" config default "ed0" any 0x10 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # EP-210 Ethernet Card card "Ethernet PCMCIA adapter" "EP-210" config default "ed0" any 0x10 ether 0x110 00:40:33 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Katron PE-520 Ethernet Card card "KCI" "PE520 PCMCIA Ethernet Adapter" config default "ed0" any 0x10 ether 0x110 00:40:f6 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Linksys Ethernet Card card ".*E-CARD PC Ethernet Card.*" ".*" config default "ed0" any 0x10 insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Linksys Ethernet Card card ".*" ".*E-CARD PC Ethernet Card.*" config default "ed0" any 0x10 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Linksys Ethernet Card card "E-CARD" "E-CARD" config default "ed0" any 0x10 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Maxtech PCN2000 Ethernet card "MAXTECH" "PCN2000" config default "ed0" any 0x10 ether 0x5000 00:00:e8 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # NE2000 Compatible Ethernet Card card "NE2000 Compatible" "PCMCIA" config default "ed0" any 0x10 ether 0xff0 00:a0:0c insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # RPTI EP400 Ethernet Card card "RPTI LTD\." "EP400" config default "ed0" any 0x10 ether 0x110 00:40:95 insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # SMC EliteCard Ethernet card "SMC" "PCM Ethernet Adapter" config default "sn0" any ether attr2hex insert logger -s Untested card inserted. please e-mail the result to pao-report@clave.gr.jp insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # Socket EA LAN Adapter # This card should not work because of its broken DMA status register, # if you have this card, please fix this bug. card "Socket Communications Inc" "Socket EA PCMCIA LAN.*" # This card has broken CIS tupples # We can't use "default" config 0x1 "ed0" any 0x30 ether 0x4000 00:c0:1b insert /etc/pccard_ether $device remove /etc/pccard_ether_remove $device # ------------------------------------------------------------------- # # "Wildcard" entries # # ------------------------------------------------------------------- # GENERIC PCMCIA modem function serial config auto "sio3" any # config 0x23 "sio3" any # alternative definitions # config 0x21 "sio3" any # ......... # config 0x22 "sio3" any # config 0x23 "sio3" pio # config 0x21 "sio3" pio # config 0x22 "sio3" pio # config 0x23 "sio3" 5 # config 0x21 "sio3" 5 # config 0x22 "sio3" 5 # reset 100 # default reset 1000 # safety reset time # reset 10000 # for unstable cards insert logger -s PCMCIA Modem inserted remove logger -s PCMCIA Modem removed # GENERIC Flash ATA / ATA HDD function fixed_disk # config default "wdc1" 15 # config default "wdc1" any # config 0x03 "wdc1" 15 config 0x03 "wdc1" any insert logger -s Flash ATA / ATA HDD inserted remove logger -s Flash ATA / ATA HDD removed And here's the output of "pccardc dumpcis": Code 128 not found Code 128 not found code Unknown ignored Code 131 not found Code 131 not found code Unknown ignored Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x15 (Version 1 info), length = 50 000: 05 00 55 2e 53 2e 20 52 6f 62 6f 74 69 63 73 00 010: 58 4a 2f 43 43 31 35 36 30 00 4d 65 67 61 68 65 020: 72 74 7a 20 35 36 6b 62 70 73 20 4d 6f 64 65 6d 030: 00 ff Version = 5.0, Manuf = [U.S. Robotics], card vers = [XJ/CC1560] Addit. info = [Megahertz 56kbps Modem] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 02 01 2f 00 PCMCIA ID = 0x102, OEM ID = 0x2f Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 01 Serial port/modem - POST initialize Tuple #5, code = 0x1a (Configuration map), length = 5 000: 01 23 00 03 03 Reg len = 2, config register addr = 0x300, last config = 0x23 Registers: XX------ Tuple #6, code = 0x1b (Configuration entry), length = 16 000: e0 41 99 49 55 3e 3d aa 60 f8 03 07 30 ff ff 28 Config index = 0x20(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 3.5 x 100mA Power down supply current: 3.5 x 10mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #7, code = 0x1b (Configuration entry), length = 7 000: 21 08 aa 60 f8 02 07 Config index = 0x21 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #8, code = 0x1b (Configuration entry), length = 7 000: 22 08 aa 60 e8 03 07 Config index = 0x22 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #9, code = 0x1b (Configuration entry), length = 7 000: 23 08 aa 60 e8 02 07 Config index = 0x23 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #10, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 7c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even Data bit - 7bit,8bit, Stop bit - 1bit,1.5bit,2bit Tuple #11, code = 0x22 (Functional EXT), length = 9 000: 01 1f 0f 00 06 00 00 06 00 Modem interface capabilities: Tuple #12, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 02 b5 Data modem services available: Tuple #13, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 0f 00 02 00 b5 Fax1/modem services available: Tuple #14, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 0f 00 02 00 b5 Fax2/modem services available: Tuple #15, code = 0x0 (Null tuple), length = 10 000: 02 01 2f 00 21 00 00 00 00 ff Tuple #16, code = 0x0 (Null tuple), length = 14 000: 31 30 36 47 31 36 52 38 32 4b 4d 57 00 ff Tuple #17, code = 0x14 (No link), length = 0 Tuple #18, code = 0xff (Terminator), length = 0 2 slots found And here's rc.conf: #!/bin/sh # # This is rc.conf - a file full of useful variables that you can set # to change the default startup behavior of your system. You should # not edit this file! Put any overrides into one of the ${rc_conf_files} # instead and you will be able to update these defaults later without # spamming your local configuration information. # # All arguments must be in double or single quotes. # # $Id: rc.conf,v 1.1 1999/02/09 22:15:18 jkh Exp $ ############################################################## ### Important initial Boot-time options ##################### ############################################################## swapfile="NO" # Set to name of swapfile if aux swapfile desired. apm_enable="YES" # Set to YES if you want APM enabled. pccard_enable="YES" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ether="ed0 ep0 sn0 fe0" pccard_beep="2" ifconfig_common="DHCP" ifconfig_ed0=$ifconfig_common ifconfig_ep0=$ifconfig_common ifconfig_sn0=$ifconfig_common ifconfig_fe0=$ifconfig_common local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs. local_periodic="/usr/local/etc/periodic /usr/X11R6/etc/periodic" # periodic script dirs rc_conf_files="/etc/rc.conf /etc/rc.conf.local" ############################################################## ### Network configuration sub-section ###################### ############################################################## ### Basic network options: ### hostname="myname.my.domain" # Set this! nisdomainname="NO" # Set to NIS domain if using NIS (or NO). firewall_enable="NO" # Set to YES to enable firewall functionality firewall_type="UNKNOWN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display natd_enable="NO" # Enable natd (if firewall_enable == YES). natd_interface="fxp0" # Public interface to use with natd. natd_flags="" # Additional flags for natd. tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). network_interfaces="lo0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. # # If you have any sppp(4) interfaces above, you might also want to set # the following parameters. Refer to spppcontrol(8) for their meaning. sppp_interfaces="" # List of sppp interfaces. #sppp_interfaces="isp0" # example: sppp over ISDN #spppconfig_isp0="authproto=chap myauthname=foo myauthsecret='top secret' hisauthname=some-gw hisauthsecret='another secret'" ### Network daemon (miscellaneous) & NFS options: ### syslogd_enable="YES" # Run syslog daemon (or NO). syslogd_flags="" # Flags to syslogd (if enabled). inetd_enable="YES" # Run the network daemon dispatcher (or NO). inetd_flags="" # Optional flags to inetd. # # named. It may be possible to run named in a sandbox, man security for # details. # named_enable="NO" # Run named, the DNS server (or NO). named_program="named" # path to named, if you want a different one. named_flags="" # Flags for named #named_flags="-u bind -g bind" # Flags for named kerberos_server_enable="NO" # Run a kerberos master server (or NO). kadmind_server_enable="NO" # Run kadmind (or NO) -- do not run on # a slave kerberos server kerberos_stash="" # Is the kerberos master key stashed? rwhod_enable="NO" # Run the rwho daemon (or NO). rwhod_flags="" # Flags for rwhod amd_enable="NO" # Run amd service with $amd_flags (or NO). amd_flags="-a /net -c 1800 -k i386 -d my.domain -l syslog /host /etc/amd.map" amd_map_program="NO" # Can be set to "ypcat -k amd.master" nfs_client_enable="NO" # This host is an NFS client (or NO). nfs_client_flags="-n 4" # Flags to nfsiod (if enabled). nfs_access_cache="2" # Client cache timeout in seconds nfs_server_enable="NO" # This host is an NFS server (or NO). nfs_server_flags="-u -t -n 4" # Flags to nfsd (if enabled). mountd_flags="-r" # Flags to mountd (if NFS server enabled). nfs_reserved_port_only="NO" # Provide NFS only on secure port (or NO). rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="YES" # Run NFS rpc.statd if nfs_server (or NO). portmap_enable="YES" # Run the portmapper service (or NO). portmap_flags="" # Flags to portmap (if enabled). rpc_ypupdated_enable="NO" # Run if NIS master and SecureRPC (or NO). keyserv_enable="NO" # Run the SecureRPC keyserver (or NO). keyserv_flags="" # Flags to keyserv (if enabled). rarpd_enable="NO" # Run rarpd (or NO). rarpd_flags="" # Flags to rarpd. xtend_enable="NO" # Run the X-10 power controller daemon. xtend_flags="" # Flags to xtend (if enabled). ### Network Time Services options: ### timed_enable="NO" # Run the time daemon (or NO). timed_flags="" # Flags to timed (if enabled). ntpdate_enable="NO" # Run the ntpdate to sync time (or NO). ntpdate_program="ntpdate" # path to ntpdate, if you want a different one. ntpdate_flags="" # Flags to ntpdate (if enabled). xntpd_enable="NO" # Run xntpd Network Time Protocol (or NO). xntpd_program="xntpd" # path to xntpd, if you want a different one. xntpd_flags="-p /var/run/xntpd.pid" # Flags to xntpd (if enabled). # Network Information Services (NIS) options: ### nis_client_enable="NO" # We're an NIS client (or NO). nis_client_flags="" # Flags to ypbind (if enabled). nis_ypset_enable="NO" # Run ypset at boot time (or NO). nis_ypset_flags="" # Flags to ypset (if enabled). nis_server_enable="NO" # We're an NIS server (or NO). nis_server_flags="" # Flags to ypserv (if enabled). nis_ypxfrd_enable="NO" # Run rpc.ypxfrd at boot time (or NO). nis_ypxfrd_flags="" # Flags to rpc.ypxfrd (if enabled). nis_yppasswdd_enable="NO" # Run rpc.yppasswdd at boot time (or NO). nis_yppasswdd_flags="" # Flags to rpc.yppasswdd (if enabled). ### Network routing options: ### defaultrouter="NO" # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="NO" # Set to YES if this host will be a gateway. router_enable="NO" # Set to YES to enable a routing daemon. router="routed" # Name of routing daemon to use if enabled. router_flags="-q" # Flags for routing daemon. mrouted_enable="NO" # Do multicast routing (see /etc/mrouted.conf). mrouted_flags="" # Flags for multicast routing daemon. ipxgateway_enable="NO" # Set to YES to enable IPX routing. ipxrouted_enable="NO" # Set to YES to run the IPX routing daemon. ipxrouted_flags="" # Flags for IPX routing daemon. arpproxy_all="" # replaces obsolete kernel option ARP_PROXYALL. forward_sourceroute="NO" # do source routing (only if gateway_enable is set to "YES") accept_sourceroute="NO" # accept source routed packets to us ### ATM interface options: ### atm_enable="NO" # Configure ATM interfaces (or NO). #atm_netif_hea0="atm 1" # Network interfaces for physical interface. #atm_sigmgr_hea0="uni31" # Signalling manager for physical interface. #atm_prefix_hea0="ILMI" # NSAP prefix (UNI interfaces only) (or ILMI). #atm_macaddr_hea0="NO" # Override physical MAC address (or NO). #atm_arpserver_atm0="0x47.0005.80.999999.9999.9999.9999.999999999999.00" # ATMARP server address (or local). #atm_scsparp_atm0="NO" # Run SCSP/ATMARP on network interface (or NO). atm_pvcs="" # Set to PVC list (or leave empty). atm_arps="" # Set to permanent ARP list (or leave empty). ### ISDN interface options: ### isdn_enable="NO" # Enable the ISDN subsystem (or NO). isdn_fsdev="/dev/ttyv4" # Output device for fullscreen mode (or NO for daemon mode). isdn_flags="-dn -d0x1f9" # Flags for isdnd isdn_trace="NO" # Enable the ISDN trace subsystem (or NO). isdn_traceflags="-f /var/tmp/isdntrace0" # Flags for isdntrace ### Miscellaneous network options: ### icmp_bmcastecho="NO" # respond to broadcast ping packets ############################################################## ### System console options ################################# ############################################################## keymap="NO" # keymap in /usr/share/syscons/keymaps/* (or NO). keyrate="NO" # keyboard rate to: slow, normal, fast (or NO). keybell="NO" # bell to duration.pitch or normal or visual (or NO). keychange="NO" # function keys default values (or NO). cursor="NO" # cursor type {normal|blink|destructive} (or NO). scrnmap="NO" # screen map in /usr/share/syscons/scrnmaps/* (or NO). font8x16="NO" # font 8x16 from /usr/share/syscons/fonts/* (or NO). font8x14="NO" # font 8x14 from /usr/share/syscons/fonts/* (or NO). font8x8="NO" # font 8x8 from /usr/share/syscons/fonts/* (or NO). blanktime="300" # blank time (in seconds) or "NO" to turn it off. saver="NO" # screen saver: Uses /modules/${saver}_saver.ko moused_enable="YES" # Run the mouse daemon. moused_type="auto" # See man page for rc.conf(5) for available settings. moused_port="/dev/psm0" # Set to your mouse port. moused_flags="-3" # Any additional flags to moused. allscreens_flags="" # Set this vidcontrol mode for all virtual screens ############################################################## ### Miscellaneous administrative options ################### ############################################################## cron_enable="YES" # Run the periodic job daemon. lpd_enable="NO" # Run the line printer daemon. lpd_flags="" # Flags to lpd (if enabled). usbd_enable="NO" # Run the usbd daemon. usbd_flags="" # Flags to usbd (if enabled). sendmail_enable="YES" # Run the sendmail daemon (or NO). sendmail_flags="-bd -q30m" # -bd is pretty mandatory. dumpdev="NO" # Device name to crashdump to (if enabled). check_quotas="NO" # Check quotas (or NO). accounting_enable="NO" # Turn on process accounting (or NO). ibcs2_enable="NO" # Ibcs2 (SCO) emulation loaded at startup (or NO). linux_enable="NO" # Linux emulation loaded at startup (or NO). svr4_enable="NO" # SysVR4 emulation loaded at startup (or NO). rand_irqs="NO" # Stir the entropy pool (like "5 11" or NO). clear_tmp_enable="NO" # Clear /tmp at startup. ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" # shared library search paths ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout" # a.out shared library search paths kern_securelevel_enable="NO" # kernel security level (see init(8)), kern_securelevel="-1" # range: -1..3 ; `-1' is the most insecure update_motd="YES" # update version info in /etc/motd (or NO) vinum_drives="" # put in names of disks containing vinum drives ############################################################## ### Allow local configuration override at the very end here ## ############################################################## # # for i in ${rc_conf_files}; do if [ -f $i ]; then . $i fi done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 6:52:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from fxp.dhs.org (cx19313-a.nwptn1.va.home.com [24.2.49.151]) by hub.freebsd.org (Postfix) with ESMTP id 9AE8914D16; Sun, 25 Apr 1999 06:52:15 -0700 (PDT) (envelope-from jedgar@fxp.dhs.org) Received: from earth.fxp.dhs.org (jedgar@earth.fxp.dhs.org [192.168.1.21]) by fxp.dhs.org (8.9.3/8.9.3) with ESMTP id JAA18875; Sun, 25 Apr 1999 09:52:21 -0400 (EDT) (envelope-from jedgar@fxp.dhs.org) Date: Sun, 25 Apr 1999 09:52:08 -0400 (EDT) From: "Chris D. Faulhaber" To: Douglas Carmichael Cc: hosokawa@jp.freebsd.org, freebsd-mobile@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: PAO3 can't recognize a USR/Megahertz PCMCIA modem on an NEC Versa LX In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Out of curiosity, why is sio3 disabled in your kernel config.. > device sio0 at isa? port "IO_COM1" tty irq 4 > device sio3 at isa? disable port "IO_COM4" tty irq 9 ..when it is the serial port you want to assign to the card? -------------------------------------------------------------- | All the true gurus I've met never | Chris D. Faulhaber | | claimed they were one, and always | | | pointed to someone better. | | -------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 8:25:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id F1406152D6; Sun, 25 Apr 1999 08:25:32 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (730 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 25 Apr 1999 08:25:32 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sun, 25 Apr 1999 08:25:32 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Douglas Carmichael Cc: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Re: PAO3 can't recognize a USR/Megahertz PCMCIA modem on an NEC Versa LX References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > but when I tried a "cu -l /dev/cuaa3", I couldn't get an OK response > from the modem and the response when receiving a character is very slow > in cu. > ... > device sio3 at isa? disable port "IO_COM4" tty irq 9 ^^^^ ^^^^^^^ randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 9:52:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 11DC715546 for ; Sun, 25 Apr 1999 09:52:12 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (11436 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 25 Apr 1999 09:52:12 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sun, 25 Apr 1999 09:52:12 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: vaio 505tx 3.1-pao hangs after suspend Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sony vaio 505tx 3.1-release + pao3 if i type 'zzz' it responds with a single beep and the screen goes blank as expected. i then hit a key to unsuspend. the screen lights and redisplays etc. but no beep, no response to keyboard, ... dead machine except that the screen has relit. i then enabled all the suspend inclined goodies in the pao kernel config (see appended kernel config and dmesg), and got the same result. one time the result was kernel trap 1 with interrupts disabled Fatal trap 1: privileged intruction fault while in kernel mode instruction pointer = 0x48:0x503f stack pointer = 0x10:0xf0216b8c frame pointer = 0x10:0xf0216b9c code segment = base 0xf00f0000, limXXX( proceddor eflags = resume, IOPL = 0 current trap number = 1 panic: privileged instruction fault but usually it just freezes after relighting the screen. note that this is all without any pccards inserted. same result with, but i wanted to simplify things. zzz and the equivalent fn keys worked fine before i went to pao. randy # # Sample Laptop Configuration # Tatsumi Hosokawa # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.143.2.5 1999/03/29 17:59:38 ken Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident ROAM-PAO maxusers 64 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem #options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # If your laptop have not had Windoze95-Ready BIOS, please update it. # Such old BIOS'es sometimes have critical bugs at 32-bit protected # mode APM BIOS interface (which have not used by Windoze 3.1). # PC-card suspend/resume support (experimental) options APM_PCCARD_RESUME options PCIC_RESUME_RESET # Keep power for serial cards when the system suspends # (If your machine hangs up when you try to suspend the system with # FAX/Modem PCMCIA card, uncomment this option). #options SIO_SUSP_KEEP_PWR # Detach SCSI devices when the SCSI card is removed #options SCSI_DETACH # Detach ATAPI devices when the ATA card is removed #options ATAPI_DETACH # Japanese version of WaveLAN PCMCIA uses 2.4GHz band instead of 915MHz # band that US version uses. If you want to use Japanese version of # WaveLAN, uncomment this line, or edit the corresponding config entry # of /etc/pccard.conf. #options "WAVELAN_PCMCIA_24" # Suspend the system when the battery status is "Low" #options "APM_BATT_LOW_SUSPEND" # If you want to use NTP on laptop machines, uncomment the following # option. Current APM implementation affects NTP client. options "APM_NO_CLOCK_ADJUST" # Some X-servers cannot survive suspend/resume on laptop. # This option kicks her when the system is resumed from suspended mode. options SYSCONS_VTY_RESUME config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 # Dont remove these two lines! pseudo-device card 1 # You must use "flags 0x1" when you don't hear any negotiation noise(?) # if you use modem card, or pccardd doesn't read cis tuple, tell you # 'No card in database for"(null)"("(null)")' in case of Cirrus Logic's # pcic is your PC. #device pcic0 at isa? port 0x3e0 flags 0x1 irq 11 device pcic0 at isa? port 0x3e0 irq 11 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 #controller isp0 #controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? #controller scbus0 #device da0 #device sa0 #device pass0 #device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty options MAXCONS=4 # number of virtual consoles # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? # Advanced Power Management options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 #device sio2 at isa? disable port "IO_COM3" tty irq 5 #device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? net irq 7 controller ppbus0 device nlpt0 at ppbus? #device plip0 at ppbus? #device ppi0 at ppbus? #controller vpo0 at ppbus? # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ax0 #device de0 #device fxp0 #device mx0 #device pn0 #device rl0 #device tl0 #device tx0 #device vr0 #device vx0 #device wb0 #device xl0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 net irq ? device wlp0 at isa? port 0x300 net irq 11 pseudo-device loop pseudo-device ether #pseudo-device sl 1 #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Sun Apr 25 09:03:37 PDT 1999 root@roam.psg.com:/usr/src/sys/compile/ROAM-PAO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (quarter-micron) (298.42-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x582 Stepping=2 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 127889408 (124892K bytes) Preloaded elf kernel "kernel" at 0xf0284000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x02 on pci0.7.3 vga0: rev 0x01 int a irq 9 on pci0.8.0 pcic0: rev 0x00 int a irq 255 on pci0.10.0 RL5C4XX PCI Config Reg: [CSC isa irq] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ep0 not found at 0x300 wlp0 not found at 0x300 pcic0 at 0x3e0-0x3e1 irq 11 on isa PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s2a Card inserted, slot 0 ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 11:29:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 6E84D14EFF; Sun, 25 Apr 1999 11:29:23 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.webwizard.net.mx (8.9.3/8.9.3) with ESMTP id NAA49164; Sun, 25 Apr 1999 13:29:16 -0500 (CDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37235EF6.A74D6974@MexComUSA.net> Date: Sun, 25 Apr 1999 11:29:11 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Cc: freebsd-mobile@FreeBSD.ORG Subject: Network problem with Laptop/Current. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I try to configure my D-Link de-660 pcmcia card with a kernel from sources from the last 5 days or so, I get the following: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 5 Card inserted, slot 2 Card inserted, slot 3 ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ac150 stack pointer = 0x10:0xc60f0d58 frame pointer = 0x10:0xc60f0d60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 424 (ifconfig) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... 8 4 done Automatic reboot in 15 seconds - press a key on the console to abort With a kernel from April 20 everything works except my pcmcia Viking Modem which hasn't worked since last weekend. Is anyone else else having this problem? Could I be doing something wrong? Thanks, ed (This is a generic AMS K6-300 .) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 11:36:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 25A3514EFF; Sun, 25 Apr 1999 11:36:09 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA46007; Sun, 25 Apr 1999 20:35:49 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904251835.UAA46007@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <37235EF6.A74D6974@MexComUSA.net> from Edwin Culp at "Apr 25, 1999 11:29:11 am" To: eculp@MexComUSA.net (Edwin Culp) Date: Sun, 25 Apr 1999 20:35:49 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Edwin Culp wrote: > When I try to configure my D-Link de-660 pcmcia card with a kernel from > sources from the last 5 days or so, I get the following: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > pcic: controller irq 5 > Card inserted, slot 2 > Card inserted, slot 3 > ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Try the patch I posted a couble of days ago, that does it for me... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 12: 5:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id E35721555B; Sun, 25 Apr 1999 12:05:52 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id CAA00287; Sun, 25 Apr 1999 02:24:50 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Sun, 25 Apr 1999 02:24:50 -0500 (CDT) From: Douglas Carmichael To: hosokawa@jp.freebsd.org Cc: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: I tried changing the modem card to sio1 and trying different free interrupts, but it didn't work. (polled I/O did) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tried: 1) Enabling sio3 in the kernel config (didn't work) 2) Changing the modem card to sio1 and using different interrupts (didn't work) 3) Changing the modem card to use polled I/O (worked) However, if I remember right, polled I/O takes a *serious* performance hit over interrupt-driven I/O. Is there anything equivalent to "cat /proc/interrupts" in Linux that will tell you what interrupts are being used for what purposes? How can I successfully find a non-conflicting interrupt? Your assistance will be appreciated. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 19: 7:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 4494614C35; Sun, 25 Apr 1999 19:07:46 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA16297; Mon, 26 Apr 1999 02:05:28 GMT Message-Id: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> To: Edwin Culp Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-reply-to: Your message of "Sun, 25 Apr 1999 11:29:11 MST." <37235EF6.A74D6974@MexComUSA.net> Date: Mon, 26 Apr 1999 11:05:27 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) It is probably TI CardBus controller, -current code not support it correctly. You should be use PAO. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 19:17:13 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 3E2D114C59; Sun, 25 Apr 1999 19:17:06 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id JAA00841; Sun, 25 Apr 1999 09:36:01 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Sun, 25 Apr 1999 09:36:00 -0500 (CDT) From: Douglas Carmichael To: hosokawa@jp.freebsd.org Cc: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Even when I use an unused interrupt (IRQ 9), my serial modem card still doesn't work. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tried changing it to IRQ 9 which is unused, but I still can't access the card with interrupt-driven I/O. However, polled I/O does work. Here's my dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Sun Apr 25 13:27:09 CDT 1999 root@myname.my.domain:/usr/src/sys/compile/DCARMICH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (233.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff> real memory = 100663296 (98304K bytes) avail memory = 95399936 (93164K bytes) Preloaded elf kernel "kernel" at 0xf0249000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 vga0: rev 0xdc int a irq 10 on pci0.2.0 pcic0: rev 0x02 int a irq 255 on pci0.3.0 RL5C4XX PCI Config Reg: pcic1: rev 0x02 int b irq 255 on pci0.3.1 RL5C4XX PCI Config Reg: chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x02 on pci0.7.3 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 pcic0 at 0x3e0-0x3e1 irq 11 flags 0x1 on isa PC-Card ctlr(0) Ricoh RL5C478 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 changing root device to wd0s1a acd0: read_toc failed acd0: read_toc failed (a first try at the modem card) Card inserted, slot 0 sio1: type 16550A sio1: unload,gone Return IRQ=9 Card removed, slot 0 ************************************************ Card inserted, slot 0 (my 3Com Ethernet card which is detected) ep0: utp/bnc[*UTP*] address 00:00:86:1a:4b:80 ep0: unload Return IRQ=9 Card removed, slot 0 ************************************************* (a second try at the modem card) Card inserted, slot 0 sio1: type 16550A sio1: unload,gone Return IRQ=9 Card removed, slot 0 And here's the entry in pccard.conf for it: card "U.S. Robotics" "XJ/CC1560" config auto "sio1" any reset 10000 insert logger -s U.S. Robotics XJ/CC1560 Modem inserted remove logger -s U.S. Robotics XJ/CC1560 Modem removed What could be the problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 20: 9: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 0211614F37 for ; Sun, 25 Apr 1999 20:09:07 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id UAA01508; Sun, 25 Apr 1999 20:08:43 -0700 (PDT) Date: Sun, 25 Apr 1999 20:08:42 -0700 (PDT) From: Annelise Anderson To: Jun Kuriyama Cc: FreeBSD Mobile Subject: Re: First draft of pccardc.8 In-Reply-To: <372128CA.8B00E7E9@sky.rim.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 24 Apr 1999, Jun Kuriyama wrote: > Jun Kuriyama wrote: > > Can someone review this? > It will be nice to have a pccardc man page. I would like to know more about each of the options--a little more on what the purpose of each is, and under what circumstances it would be used. I wrote a "howto" on the process of getting pccards working, in which using the output of pccardc dumpcis to construct a pccard entry or definition for pccard.conf was explained. It really isn't explained in this draft of the man page, but perhaps it should be. The ppp man page is now not only documentation about the software, but a "howto" on getting it to work. Maybe this man page or a more general one on pccards ought to cover the "how to" aspects of this as well as the technical aspects. Now I am curious about pccardc enabler and when it might be necessary to use it. I'm not sure exactly how it interacts with pccard.conf, or whether if a card were removed and reinserted and pccard.conf got reread, whether that would overwrite anything put in with pccardc enabler. There seems to be no place in enabler to enter an ether offset for a network card; is that right? I was quite surprised to discover that apparently I can actually write to a card's memory using some pccardc commands. When would I want to do that? Would this change be permanent? Is it possible I could get some cards to work that way that won't work otherwise? Very interesting. Thanks-- Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 20:10:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id E2CF114C2D for ; Sun, 25 Apr 1999 20:10:56 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (726 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 25 Apr 1999 20:10:56 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sun, 25 Apr 1999 20:10:56 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Annelise Anderson Cc: Jun Kuriyama , FreeBSD Mobile Subject: Re: First draft of pccardc.8 References: <372128CA.8B00E7E9@sky.rim.or.jp> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I was quite surprised to discover that apparently I can actually > write to a card's memory using some pccardc commands. When would I > want to do that? well, if i can get the darn wlp0 to work at all, i hope to hack it to set nwid. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 23:43:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E81FA14CF1; Sun, 25 Apr 1999 23:43:51 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA47125; Mon, 26 Apr 1999 08:43:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904260643.IAA47125@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> from NAKAGAWA Yoshihisa at "Apr 26, 1999 11: 5:27 am" To: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa) Date: Mon, 26 Apr 1999 08:43:33 +0200 (CEST) Cc: eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems NAKAGAWA Yoshihisa wrote: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > It is probably TI CardBus controller, -current code not support it > correctly. You should be use PAO. It works fine with both 3.1 and 4.0-current, the reason it fails now is because the pcic/pccard stuff has not been moved to new-bus yet. The patches (well 3 oneliners) fixes this for the time being, until somebody has the time to convert the driver to new-bus. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Apr 25 23:58:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id C07EF14CF1 for ; Sun, 25 Apr 1999 23:58:50 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with ESMTP id IAA02003 for ; Mon, 26 Apr 1999 08:58:49 +0200 (CEST) Date: Mon, 26 Apr 1999 08:58:49 +0200 (CEST) From: Martin Blapp To: freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260643.IAA47125@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a C-Card VLSI 82C146 from Texas Instruments (TI PCI-250) and haven't been able to get pccards it running unter Stable/Current. (Current before and after new newbus-stuff came in, with or without Soerens patch, without pcic even couldn't get an irq) With PAO on 3.1 RELEASE, it's workling like a charm ! Martin PS: If anybody is interested i'll send him dmesg and pccardc etc ... On Mon, 26 Apr 1999, Soren Schmidt wrote: > It seems NAKAGAWA Yoshihisa wrote: > > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > > > It is probably TI CardBus controller, -current code not support it > > correctly. You should be use PAO. > > It works fine with both 3.1 and 4.0-current, the reason it fails now > is because the pcic/pccard stuff has not been moved to new-bus yet. > The patches (well 3 oneliners) fixes this for the time being, until > somebody has the time to convert the driver to new-bus. > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 0:31:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B6C581505A; Mon, 26 Apr 1999 00:31:48 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA82391; Mon, 26 Apr 1999 01:31:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA08814; Mon, 26 Apr 1999 01:31:25 -0600 (MDT) Message-Id: <199904260731.BAA08814@harmony.village.org> To: Edwin Culp Subject: Re: Network problem with Laptop/Current. Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 25 Apr 1999 11:29:11 PDT." <37235EF6.A74D6974@MexComUSA.net> References: <37235EF6.A74D6974@MexComUSA.net> Date: Mon, 26 Apr 1999 01:31:25 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <37235EF6.A74D6974@MexComUSA.net> Edwin Culp writes: : With a kernel from April 20 everything works except my pcmcia Viking : Modem which hasn't worked since last weekend. Is anyone else else : having this problem? Could I be doing something wrong? I'm painfully aware of this problem. I see variations on this theme many times. I'm about 2/3 through reworking pcic/pccard to work with the newer, much nicer newbus functions for allocating resources and such. This should be hitting the tree in the early part of this week. Until then, use the April 20th kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 0:37:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B29C5150B2; Mon, 26 Apr 1999 00:37:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA82408; Mon, 26 Apr 1999 01:36:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA08858; Mon, 26 Apr 1999 01:37:01 -0600 (MDT) Message-Id: <199904260737.BAA08858@harmony.village.org> To: Soren Schmidt Subject: Re: Network problem with Laptop/Current. Cc: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Apr 1999 08:43:33 +0200." <199904260643.IAA47125@freebsd.dk> References: <199904260643.IAA47125@freebsd.dk> Date: Mon, 26 Apr 1999 01:37:01 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: : It works fine with both 3.1 and 4.0-current, the reason it fails now : is because the pcic/pccard stuff has not been moved to new-bus yet. : The patches (well 3 oneliners) fixes this for the time being, until : somebody has the time to convert the driver to new-bus. The three oneliners kinda sorta fix it for the time being. Not all laptops are fixed by it (I know my vaio has me using the zp driver because of random panics when I unplug the card). However, if they work for you, more power to you. Rest assured that I'm working on the pcic/pccard stuff right now and should have stage one of newbusification done early this week. Phase one is where minimal cahnges are done to get rid of unstable interrupt hacking that it is doing which used to be right, but now is bogus. Phase two will be much more radical, hopefully obviating the need for pccardd in most cases. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 1:19: 0 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7471514A2F; Mon, 26 Apr 1999 01:18:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA47281; Mon, 26 Apr 1999 10:18:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904260818.KAA47281@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260737.BAA08858@harmony.village.org> from Warner Losh at "Apr 26, 1999 1:37: 1 am" To: imp@harmony.village.org (Warner Losh) Date: Mon, 26 Apr 1999 10:18:33 +0200 (CEST) Cc: y-nakaga@nwsl.mesh.ad.jp, eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Cool!, let me know if there is something I can test for you!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 9: 7: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 6B2D21520A; Mon, 26 Apr 1999 09:07:05 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA27540; Mon, 26 Apr 1999 10:05:09 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA29804; Mon, 26 Apr 1999 10:05:04 -0600 Date: Mon, 26 Apr 1999 10:05:04 -0600 Message-Id: <199904261605.KAA29804@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Soren Schmidt , y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260737.BAA08858@harmony.village.org> References: <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Go Warner Go! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 10:14: 0 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hub.lovett.com (hub.lovett.com [38.155.241.2]) by hub.freebsd.org (Postfix) with ESMTP id A21DD15162 for ; Mon, 26 Apr 1999 10:13:48 -0700 (PDT) (envelope-from ade@lovett.com) Received: from ade by hub.lovett.com with local (Exim 2.12 #1) id 10bowx-0000hG-00; Mon, 26 Apr 1999 12:13:43 -0500 Date: Mon, 26 Apr 1999 12:13:43 -0500 From: Ade Lovett To: Nate Williams Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. Message-ID: <19990426121343.B375@remarq.com> References: <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> <199904261605.KAA29804@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904261605.KAA29804@mt.sri.com>; from Nate Williams on Mon, Apr 26, 1999 at 10:05:04AM -0600 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [cc list trimmed somewhat] On Mon, Apr 26, 1999 at 10:05:04AM -0600, Nate Williams wrote: > > Rest assured that I'm working on the pcic/pccard stuff right now > > and should have stage one of newbusification done early this week. > > Phase one is where minimal cahnges are done to get rid of unstable > > interrupt hacking that it is doing which used to be right, but now is > > bogus. Phase two will be much more radical, hopefully obviating the > > need for pccardd in most cases. > > Go Warner Go! Does phase 2 include the initial beginnings of support for multifunction pccards? At the very least, some infrastructure to allow devices to request a second IO window would be very useful -- at the moment, the xe Xircom driver needs some relatively disgusting hacks to claim other 16 byte IO window, hampered by the fact that pcic_io() always seems to return success for a window mapping, even if the range happens to be being used by another (eg: ISA) device. -aDe -- Ade Lovett, RemarQ Communities, Inc., San Jose, CA. mailto:ade@remarq.com http://www.remarq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 11: 3:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7F46215162 for ; Mon, 26 Apr 1999 11:03:29 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA83786 for ; Mon, 26 Apr 1999 12:03:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA11180 for ; Mon, 26 Apr 1999 12:03:15 -0600 (MDT) Message-Id: <199904261803.MAA11180@harmony.village.org> To: freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-reply-to: Your message of "Mon, 26 Apr 1999 12:13:43 CDT." <19990426121343.B375@remarq.com> References: <19990426121343.B375@remarq.com> <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> <199904261605.KAA29804@mt.sri.com> Date: Mon, 26 Apr 1999 12:03:15 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19990426121343.B375@remarq.com> Ade Lovett writes: : Does phase 2 include the initial beginnings of support for multifunction : pccards? At the very least, some infrastructure to allow devices to : request a second IO window would be very useful -- at the moment, the : xe Xircom driver needs some relatively disgusting hacks to claim other : 16 byte IO window, hampered by the fact that pcic_io() always seems to : return success for a window mapping, even if the range happens to be : being used by another (eg: ISA) device. Yes. The plan is to make them just like normal devices, rather than bastard step children that are somewhat restricted in what they can do. I'm not completely sure the best approach to the multiple function, mind you, but I do know that the newbus stuff makes things like that a whole lot easier. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 13:49:44 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 1FDA91539C; Mon, 26 Apr 1999 13:49:37 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id NAA48042; Mon, 26 Apr 1999 13:49:22 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3724D154.D09BFEE8@MexComUSA.net> Date: Mon, 26 Apr 1999 13:49:24 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NAKAGAWA Yoshihisa wrote: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > It is probably TI CardBus controller, -current code not support it > correctly. You should be use PAO. > I cannot use paq with current and it has been working fine for sometime. The newbus seems to have killed it. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 13:50:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 1C2E815397; Mon, 26 Apr 1999 13:50:29 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id NAA48037; Mon, 26 Apr 1999 13:46:13 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3724D097.E781FB25@MexComUSA.net> Date: Mon, 26 Apr 1999 13:46:15 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Soren Schmidt , NAKAGAWA Yoshihisa , freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. > > Warner I'll be glad to test with a generic k6-2 running current, if it will help. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 17: 8: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from int-gw.staff.apnic.net (guardian.apnic.net [203.37.255.100]) by hub.freebsd.org (Postfix) with ESMTP id 1DB2F155E2 for ; Mon, 26 Apr 1999 17:07:55 -0700 (PDT) (envelope-from bc-freebsd@vicious.dropbear.id.au) Received: (from mail@localhost) by int-gw.staff.apnic.net (8.9.1a/8.9.1) id AAA06239 for ; Tue, 27 Apr 1999 00:07:54 GMT Received: from julubu.staff.apnic.net(192.168.1.37) by rex.apnic.net via smap (V2.1) id xma006237; Tue, 27 Apr 99 10:07:28 +1000 Received: (from bc@localhost) by julubu.staff.apnic.net (8.8.7/SCO5) id KAA15034; Tue, 27 Apr 1999 10:07:28 +1000 (EST) X-Authentication-Warning: julubu.staff.apnic.net: bc set sender to bc-freebsd@vicious.dropbear.id.au using -f Date: Tue, 27 Apr 1999 10:07:28 +1000 (EST) From: Bruce Campbell Reply-To: Bruce Campbell To: freebsd-mobile@freebsd.org Subject: Re: pccardd and ep0 (3c589D) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Apr 1999, Randy Bush wrote: randy> > Quick overview: randy> > randy> > 3.1-RELEASE kernel with ep0 on a laptop results in 'No buffer randy> > space available' when used with pccardd. 3c589D. Unloads ep0 randy> > right after getting mac address. randy> > ping: sendto: No buffer space available randy> randy> i am occasionally seeing the "No buffer space available" with zp0 on a sony randy> vaio. have yet to localize, but seems to do with killing rdumps or other randy> rmt processes. After trying -current(19990421) and finding that 3-1RELEASE config(8) does not grok the nexus. -stable(19990424) does work on the laptop, but the reliability of the connection is.. suspect, with about 1 out of 3 suspend/resumes of the laptop (pccardd is setting up the card each time) resulting in eventual 'host is down' messages. Its getting better though. ;) Thanks also to Sean O'Connell. --==-- Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Apr 26 18:50:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (sj-dsl-9-161-065.dspeed.net [209.249.161.65]) by hub.freebsd.org (Postfix) with ESMTP id 96E5215041; Mon, 26 Apr 1999 18:50:02 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id SAA49440; Mon, 26 Apr 1999 18:49:54 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372517C7.B7527A68@MexComUSA.net> Date: Mon, 26 Apr 1999 18:49:59 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <37235EF6.A74D6974@MexComUSA.net> <199904260731.BAA08814@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > In message <37235EF6.A74D6974@MexComUSA.net> Edwin Culp writes: > : With a kernel from April 20 everything works except my pcmcia Viking > : Modem which hasn't worked since last weekend. Is anyone else else > : having this problem? Could I be doing something wrong? > > I'm painfully aware of this problem. I see variations on this theme > many times. I'm about 2/3 through reworking pcic/pccard to work with > the newer, much nicer newbus functions for allocating resources and > such. This should be hitting the tree in the early part of this > week. Until then, use the April 20th kernel. > > Warner Thank you, that is what I'm doing:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 27 16: 4:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id EC93B1528F for ; Tue, 27 Apr 1999 16:04:36 -0700 (PDT) (envelope-from mik.thwaite@dial.pipex.com) Received: (qmail 22054 invoked from network); 27 Apr 1999 17:52:13 -0000 Received: from usern637.uk.uudial.com (HELO mik) (193.149.85.162) by smtp.dial.pipex.com with SMTP; 27 Apr 1999 17:52:13 -0000 Message-ID: <001c01be90d6$7b03cbc0$a25595c1@mik> From: "Mik Thwaite" To: Subject: How do I subscribe? Date: Tue, 27 Apr 1999 18:49:21 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BE90DE.A98D45E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BE90DE.A98D45E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm a newbie laptop user of FreeBSD and need as much information as = possible to configure my system. I've been told about this group and would like to access the knowledge = base it holds! Cheers Mik Thwaite, UK ------=_NextPart_000_0019_01BE90DE.A98D45E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm a newbie laptop user of FreeBSD = and need as=20 much information as possible to configure my system.
 
I've been told about this group and = would like=20 to access the knowledge base it holds!
 
Cheers Mik Thwaite,=20 UK
------=_NextPart_000_0019_01BE90DE.A98D45E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 27 16:36:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from pcayk.ukc.ac.uk (pcayk.ukc.ac.uk [129.12.41.131]) by hub.freebsd.org (Postfix) with ESMTP id 0874F156E9; Tue, 27 Apr 1999 16:36:22 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from excite.com (xtsw12c.ukc.ac.uk [129.12.41.85]) by pcayk.ukc.ac.uk (8.9.2/8.9.2) with ESMTP id AAA09033; Wed, 28 Apr 1999 00:36:30 +0100 (BST) (envelope-from dlombardo@excite.com) Message-ID: <37264B06.6FB4F675@excite.com> Date: Wed, 28 Apr 1999 00:40:54 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-multimedia@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: notebook ZV port support? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My notebook (AMS Tech Rodéo 3072 ECX) has a thing called "ZV port", which apparently is somehow internally connected to the C&T 65555 video chip, and supports things like MPEG decoders, live video input, video capture, etc. According to http://www.pc-card.com/papers/zv.htm, ZV (Zoomed Video) is a dedicated bus, or a connection between a PC-card and host system that allows the card to write video data directly into the VGA frame buffer. Now all this sounds real good, and complete documentation on the 65555 chip is available from C&T's web site: http://www.chips.com/design/graphics/mobilegraphics/datashts/ However, I have been so far unable to find a CCD camera that can be plugged into the ZV port on my notebook, and the responses I got from AMS Tech were completely useless - the bottom line was "we have no idea what you're talking about, get a USB camera like everyone else". Moreover, the 65555 datasheet is very clear - I think if I had a camera connected to the port, I could write a device driver for it - that is, provided such a thing is possible in the first place. Bearing the aforesaid in mind, I have several questions: 1) Can the ZV port on my notebook really be used for video capture, or is it one of those things that was designed to be used in many different ways in the future, but as of yet nothing? 2) If this is indeed possible, is there such a thing as "ZV camera" - or does it have to be used in conjunction with a PC card? 3) If a PC Card is needed, how do all these things (PC Card, ZV port, camera) get connected? (Or is there supposed to be some internal connection between the PCMCIA/Cardbus PCI bridge and the ZV port in order to identify the special "ZV" type of PC Cards?) I've heard that some Toshiba notebooks also have ZV ports - anyone out there have any ZV experience? Thanks, Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Apr 27 16:54: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from xnet-a-226.resnet.purdue.edu (xnet-a-226.resnet.purdue.edu [128.210.216.226]) by hub.freebsd.org (Postfix) with ESMTP id 0185A154BB; Tue, 27 Apr 1999 16:53:41 -0700 (PDT) (envelope-from matt@xnet-a-226.resnet.purdue.edu) Received: from localhost (matt@localhost) by xnet-a-226.resnet.purdue.edu (8.9.2/8.9.2) with ESMTP id SAA03638; Tue, 27 Apr 1999 18:57:45 GMT (envelope-from matt@xnet-a-226.resnet.purdue.edu) Date: Tue, 27 Apr 1999 18:57:45 +0000 (GMT) From: matt To: Dean Lombardo Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: notebook ZV port support? In-Reply-To: <37264B06.6FB4F675@excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a Toshiba 510CDT (p133, 32 megs ram, etc...) that has a ZV port. I'm not sure how they work either but I do know that there are a fwe pcmcia cards available that support the ZV port. I believe there are mpeg hardware decoding cards available, as well as video capture cards, though I have yet to find a ZV card that has a tv tuner in it, which is what I'd really like to find. If anyone knows of one, I'd like to know where to get one. Thanks, =09=09=09Matt On Wed, 28 Apr 1999, Dean Lombardo wrote: > My notebook (AMS Tech Rod=E9o 3072 ECX) has a thing called "ZV port", > which apparently is somehow internally connected to the C&T 65555 video > chip, and supports things like MPEG decoders, live video input, video > capture, etc. According to http://www.pc-card.com/papers/zv.htm, ZV > (Zoomed Video) is a dedicated bus, or a connection between a PC-card and > host system that allows the card to write video data directly into the > VGA frame buffer. >=20 > Now all this sounds real good, and complete documentation on the 65555 > chip is available from C&T's web site: > =09http://www.chips.com/design/graphics/mobilegraphics/datashts/ >=20 > However, I have been so far unable to find a CCD camera that can be > plugged into the ZV port on my notebook, and the responses I got from > AMS Tech were completely useless - the bottom line was "we have no idea > what you're talking about, get a USB camera like everyone else". >=20 > Moreover, the 65555 datasheet is very clear - I think if I had a camera > connected to the port, I could write a device driver for it - that is, > provided such a thing is possible in the first place. >=20 > Bearing the aforesaid in mind, I have several questions: >=20 > 1) Can the ZV port on my notebook really be used for video capture, or > is it one of those things that was designed to be used in many different > ways in the future, but as of yet nothing? >=20 > 2) If this is indeed possible, is there such a thing as "ZV camera" - or > does it have to be used in conjunction with a PC card? >=20 > 3) If a PC Card is needed, how do all these things (PC Card, ZV port, > camera) get connected? (Or is there supposed to be some internal > connection between the PCMCIA/Cardbus PCI bridge and the ZV port in > order to identify the special "ZV" type of PC Cards?) >=20 > I've heard that some Toshiba notebooks also have ZV ports - anyone out > there have any ZV experience? >=20 > Thanks, >=20 > Dean >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 7: 9:10 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from procyon.meridian-enviro.com (thunder.meridian-enviro.com [207.109.234.227]) by hub.freebsd.org (Postfix) with ESMTP id EDFD115861; Thu, 29 Apr 1999 07:09:06 -0700 (PDT) (envelope-from rand@meridian-enviro.com) Received: from deneb.meridian-enviro.com (deneb.meridian-enviro.com [10.10.10.32]) by procyon.meridian-enviro.com (8.9.2/8.9.2) with ESMTP id JAA08916; Thu, 29 Apr 1999 09:09:04 -0500 (CDT) Received: (from rand@localhost) by deneb.meridian-enviro.com (8.9.2/8.9.2) id JAA68984; Thu, 29 Apr 1999 09:09:04 -0500 (CDT) From: "Douglas K. Rand" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14120.26624.555740.731012@deneb.meridian-enviro.com> Date: Thu, 29 Apr 1999 09:09:04 -0500 (CDT) To: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Cc: Subject: Xircom CM56 modem X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid X-Face: $L%T~#'9fAQ])o]A][d7EH`V;"_;2K;TEPQB=v]rDf_2s%; Thu, 29 Apr 1999 08:12:50 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3Skel.COM [192.168.0.8]) by aaka.3skel.com (8.8.8/8.8.8) with ESMTP id LAA27234 for ; Thu, 29 Apr 1999 11:14:10 -0400 (EDT) (envelope-from danj@3skel.com) Received: (from danj@localhost) by fnur.3skel.com (8.9.2/8.8.2) id LAA76826 for freebsd-mobile@FreeBSD.ORG; Thu, 29 Apr 1999 11:13:17 -0400 (EDT) Date: Thu, 29 Apr 1999 11:13:17 -0400 (EDT) From: Dan Janowski Message-Id: <199904291513.LAA76826@fnur.3skel.com> To: freebsd-mobile@FreeBSD.ORG Subject: Dell Inspiron 3500 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a new machine, a Dell Inspiron 3500. PAO under 3.1-REL works, almost perfectly. ----------------- FYI ---------------------------------- For those considering this machine Only the left bay can take the CDROM or Floppy. As soon as I realized this I was worried, but then I found this odd cable in the box: it allows one to hook up the floppy to the parallel port so that you can have both the CD and floppy connected. It is a hardware level thing, so I could boot off the floppy and use it under FreeBSD! Both bays can take batteries. I have the DVD-ROM which works as a CDROM without a problem under FreeBSD. I added the pnp and pcm drivers and the audio works as well. The NeoMagic video controller works PERFECTLY under Xfree86 3.3.3.1, 1024x768, 24bit color. 256MB of RAM is seen without a problem. Don't bother buying the internal modem: it is a winmodem. It creates problems for PCCards, because it screws up IRQ 3 so that you have to add 'ignirq 3' to the /etc/pccard.conf file. The problem was that when I put my 3c589c ethernet card in, it gets put on IRQ 3 because sio1 fails the kernel boot scan. But the WinModem is there so when the IRQ gets pulled, it gets screwed up. I see the packets go out, but when they come back it takes 2-3 seconds for them to come up. Damn nice, that PAO. Nice notebook. Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 8:16:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id DBB0014EB8 for ; Thu, 29 Apr 1999 08:16:17 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (393 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 29 Apr 1999 08:16:17 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 29 Apr 1999 08:16:17 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: clock loss when sleeping Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sony vaio 505tx 3.1-release+pao when returning from zzz, the clock does not jump forward to current time. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 8:31:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from avalon.whirlygig.co.uk (avalon.whirlygig.co.uk [195.152.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 1C7BE14EB8 for ; Thu, 29 Apr 1999 08:30:35 -0700 (PDT) (envelope-from prt@prt.org) Received: from prt (helo=localhost) by avalon.whirlygig.co.uk with local-smtp (Exim 2.10 #2) id 10cslh-0003pC-00; Thu, 29 Apr 1999 16:30:29 +0100 Date: Thu, 29 Apr 1999 16:30:29 +0100 (BST) From: Paul Thornton X-Sender: prt@avalon.whirlygig.co.uk To: Randy Bush Cc: FreeBSD Laptoppers Subject: Re: clock loss when sleeping In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Randy Bush wrote: > sony vaio 505tx > 3.1-release+pao > > when returning from zzz, the clock does not jump forward to current time. FYI: This works fine for me on a sony vaio F190, 3.1-release +PAO. -- Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 8:31:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id BFB8C14EB8 for ; Thu, 29 Apr 1999 08:31:54 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (703 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 29 Apr 1999 08:31:54 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 29 Apr 1999 08:31:54 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Paul Thornton Cc: FreeBSD Laptoppers Subject: Re: clock loss when sleeping References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> sony vaio 505tx >> 3.1-release+pao >> when returning from zzz, the clock does not jump forward to current time. > FYI: This works fine for me on a sony vaio F190, 3.1-release +PAO. i neglected to say that i am running ntp and have options APM_NO_CLOCK_ADJUST randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 8:55:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (sj-dsl-9-161-065.dspeed.net [209.249.161.65]) by hub.freebsd.org (Postfix) with ESMTP id 8ACE314E84 for ; Thu, 29 Apr 1999 08:55:12 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id IAA97558; Thu, 29 Apr 1999 08:55:03 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372880DE.E9CDABAB@MexComUSA.net> Date: Thu, 29 Apr 1999 08:55:10 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG Cc: Soren Schmidt Subject: Re: Newbus Woes References: <199904250032.SAA01995@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > In message Jerry Alexandratos writes: > : So, are pccards basically useless until pccard folds into the newbus > : scheme? > > Yes and no. Soren has some patches that he posted to this list that > help things. However, SIO uses the newbus stuff, and there is no > newbus stuff working right now for pccard, so it won't work. zp works > for me, and I've had ep working for me, but I get panics on card > eject. > > I'm working on correcting the situation. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message This morning I had a problem bringing my laptop up and finally applied Soren's patches manually, recompiled the kernel, yesterday noon sources, and my ne2000 (ed0) clone no longer panics, it seems to work as well as ever. I don't need my old kernel from the 22nd that now had ps errors, THANKS SOREN. I should have done this a week ago when you posted the patch and not procrastinate:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9: 5:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9633314E5F for ; Thu, 29 Apr 1999 09:05:31 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA06061; Thu, 29 Apr 1999 18:05:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904291605.SAA06061@freebsd.dk> Subject: Re: Newbus Woes In-Reply-To: <372880DE.E9CDABAB@MexComUSA.net> from Edwin Culp at "Apr 29, 1999 8:55:10 am" To: eculp@MexComUSA.net (Edwin Culp) Date: Thu, 29 Apr 1999 18:05:09 +0200 (CEST) Cc: freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Edwin Culp wrote: > Warner Losh wrote: > > > Yes and no. Soren has some patches that he posted to this list that > > help things. However, SIO uses the newbus stuff, and there is no > > newbus stuff working right now for pccard, so it won't work. zp works > > for me, and I've had ep working for me, but I get panics on card > > eject. > > > > I'm working on correcting the situation. > > > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-mobile" in the body of the message > > This morning I had a problem bringing my laptop up and finally applied Soren's > patches manually, recompiled the kernel, yesterday noon sources, and my > ne2000 (ed0) clone no longer panics, it seems to work as well as ever. > > I don't need my old kernel from the 22nd that now had ps errors, THANKS SOREN. Your'e welcome, it is a quick hack though, only done to get my Latitude usable again, but it works... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9: 6:51 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from avalon.whirlygig.co.uk (avalon.whirlygig.co.uk [195.152.5.19]) by hub.freebsd.org (Postfix) with ESMTP id C8DAE14FF6 for ; Thu, 29 Apr 1999 09:06:42 -0700 (PDT) (envelope-from prt@prt.org) Received: from prt (helo=localhost) by avalon.whirlygig.co.uk with local-smtp (Exim 2.10 #2) id 10ctKi-0003qm-00; Thu, 29 Apr 1999 17:06:40 +0100 Date: Thu, 29 Apr 1999 17:06:39 +0100 (BST) From: Paul Thornton X-Sender: prt@avalon.whirlygig.co.uk To: Randy Bush Cc: FreeBSD Laptoppers Subject: Re: clock loss when sleeping In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Randy Bush wrote: > i neglected to say that i am running ntp and have > > options APM_NO_CLOCK_ADJUST Randy, I am also running NTP, but did not have APM_NO_CLOCK_ADJUST set. I just compiled with this option set, and noted two things: (a) When I ran xntpdc or ntpq, it claimed to have no associations, even though xntpd was running. (b) zzz caused the clock to lose time whilst it was sleeping. I have not had any problems running ntp up until now (and in fact, its only because I didn't RTFM that I never bothered to set that option in the first place!) -- Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:10:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 4DD3814FF6 for ; Thu, 29 Apr 1999 09:10:20 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (963 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 29 Apr 1999 09:10:19 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 29 Apr 1999 09:10:19 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Paul Thornton Cc: FreeBSD Laptoppers Subject: Re: clock loss when sleeping References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am also running NTP, but did not have APM_NO_CLOCK_ADJUST set. > > I just compiled with this option set, and noted two things: > (a) When I ran xntpdc or ntpq, it claimed to have no associations, even > though xntpd was running. > (b) zzz caused the clock to lose time whilst it was sleeping. > > I have not had any problems running ntp up until now (and in fact, its only > because I didn't RTFM that I never bothered to set that option in the first > place!) boing! i should know better than to rtfm. :-) thank you. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:25:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id A84DE14D3A for ; Thu, 29 Apr 1999 09:25:11 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id RAA62836; Thu, 29 Apr 1999 17:25:07 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA03907; Thu, 29 Apr 1999 17:24:50 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904291624.RAA03907@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: eculp@MexComUSA.net (Edwin Culp), freebsd-mobile@FreeBSD.ORG Subject: Re: Newbus Woes In-reply-to: Your message of "Thu, 29 Apr 1999 18:05:09 +0200." <199904291605.SAA06061@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 29 Apr 1999 17:24:50 +0100 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I don't need my old kernel from the 22nd that now had ps errors, THAN= KS SOREN. > = > = > Your'e welcome, it is a quick hack though, only done to get my Latitude= > usable again, but it works... It's probably worth committing 'till Warner gets his changes in. > -S=F8ren -- = Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:26:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 71E2B14CF3 for ; Thu, 29 Apr 1999 09:26:31 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 28238 invoked from network); 29 Apr 1999 16:26:30 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 29 Apr 1999 16:26:30 -0000 Date: Thu, 29 Apr 1999 11:26:30 -0500 (CDT) From: John Sconiers To: Dan Janowski Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Dell Inspiron 3500 In-Reply-To: <199904291513.LAA76826@fnur.3skel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does your touch pad work. I have a Latitude and it works pretty well however I can't get the touch pad to work. Any thoughts JOHN > I have a new machine, a Dell Inspiron 3500. PAO under 3.1-REL > works, almost perfectly. > > ----------------- FYI ---------------------------------- > For those considering this machine > > Only the left bay can take the CDROM or Floppy. > As soon as I realized this I was worried, but > then I found this odd cable in the box: it allows one to > hook up the floppy to the parallel port so that you > can have both the CD and floppy connected. It is a > hardware level thing, so I could boot off the floppy > and use it under FreeBSD! > > Both bays can take batteries. I have the DVD-ROM which > works as a CDROM without a problem under FreeBSD. > I added the pnp and pcm drivers and the audio works > as well. > > The NeoMagic video controller works PERFECTLY under Xfree86 > 3.3.3.1, 1024x768, 24bit color. > > 256MB of RAM is seen without a problem. > > Don't bother buying the internal modem: it is a winmodem. > It creates problems for PCCards, because it screws up > IRQ 3 so that you have to add 'ignirq 3' to the > /etc/pccard.conf file. > > The problem was that when I put my 3c589c ethernet card > in, it gets put on IRQ 3 because sio1 fails the kernel > boot scan. But the WinModem is there so when the IRQ > gets pulled, it gets screwed up. I see the packets go > out, but when they come back it takes 2-3 seconds for > them to come up. > > Damn nice, that PAO. Nice notebook. > > Dan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:35:12 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp3.fas.harvard.edu (smtp3.fas.harvard.edu [140.247.30.83]) by hub.freebsd.org (Postfix) with ESMTP id B46E614E5A for ; Thu, 29 Apr 1999 09:35:10 -0700 (PDT) (envelope-from ahwang@fas.harvard.edu) Received: from ice3.fas.harvard.edu (IDENT:ahwang@ice3.fas.harvard.edu [140.247.30.103]) by smtp3.fas.harvard.edu with ESMTP id MAA26450; Thu, 29 Apr 1999 12:35:09 -0400 (EDT) Received: by ice3.fas.harvard.edu with ESMTP id MAA29236; Thu, 29 Apr 1999 12:35:09 -0400 (EDT) Date: Thu, 29 Apr 1999 12:35:08 -0400 (EDT) From: Adon Reply-To: Adon To: freebsd-mobile@FreeBSD.ORG Subject: Hayes Optima 336 pccard modem problems w/ 3.0R Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have a dell inspiron 3500 running 3.0-Release. i recently got a Hayes Optima 336 pccard modem. pccardd finds the modem and attaches it to sio3. when opening /dev/cuaa3, say in ppp, open() goes into never-never land, i.e. it hangs the process. i don't want to clutter inboxes so i will post config files if necessary. i just want to know if this is an unsolvable problem and if i should go ahead and buy another modem that is known to work with 3.0R. thanks, adon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:44:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from po.cnet-sb.ne.jp (po.cnet-sb.ne.jp [210.172.112.132]) by hub.freebsd.org (Postfix) with ESMTP id E1A1D14CB1 for ; Thu, 29 Apr 1999 09:44:38 -0700 (PDT) (envelope-from yuhara@po.cnet-sb.ne.jp) Received: from atsu (sb38.cnet-sb.ne.jp [210.172.112.187]) by po.cnet-sb.ne.jp (8.9.0/3.7W) with SMTP id BAA25009 for ; Fri, 30 Apr 1999 01:44:27 +0900 (JST) Date: Fri, 30 Apr 1999 01:49:08 +0900 From: shinichi yuhara To: freebsd-mobile@freebsd.org Reply-To: b9712556@mn.waseda.ac.jp Message-Id: <37288D8464.F776YUHARA@po.cnet-sb.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.25.03 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 9:53:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6E87C14F93 for ; Thu, 29 Apr 1999 09:53:39 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA06203; Thu, 29 Apr 1999 18:53:29 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904291653.SAA06203@freebsd.dk> Subject: Re: Dell Inspiron 3500 In-Reply-To: from John Sconiers at "Apr 29, 1999 11:26:30 am" To: jrs@enteract.com (John Sconiers) Date: Thu, 29 Apr 1999 18:53:28 +0200 (CEST) Cc: danj@3skel.com, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems John Sconiers wrote: > > Does your touch pad work. I have a Latitude and it works pretty well > however I can't get the touch pad to work. Any thoughts I have a Latitude, the touchpad works just dandy, its seen as a psm (ps/2) mouse. Its been running current, for the 6 month I've had it, NO PAO, just plain and simple -current, works without a hitch.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 10: 7:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from eugate.sgi.com (eugate.sgi.com [193.73.159.10]) by hub.freebsd.org (Postfix) with ESMTP id 87BF615227 for ; Thu, 29 Apr 1999 10:07:17 -0700 (PDT) (envelope-from gwk@sgi.com) Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by eugate.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id TAA03473; Thu, 29 Apr 1999 19:04:06 +0200 (MDT) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA06638; Thu, 29 Apr 1999 19:03:56 +0200 Received: from zyw89 by cuckoo.munich.sgi.com via SMTP (980427.SGI.8.8.8/911001.SGI) id TAA25889; Thu, 29 Apr 1999 19:03:47 +0200 (MDT) From: "Georg-W. Koltermann" To: "Soren Schmidt" , "John Sconiers" Cc: , Subject: RE: Dell Inspiron 3500 Date: Thu, 29 Apr 1999 19:03:13 +0200 Message-ID: <000d01be9262$2a98a650$12c5fd90@zyw89> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <199904291653.SAA06203@freebsd.dk> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: owner-freebsd-mobile@freebsd.org > [mailto:owner-freebsd-mobile@freebsd.org]On Behalf Of Soren Schmidt > Sent: Thursday, April 29, 1999 6:53 PM > To: John Sconiers > Cc: danj@3skel.com; freebsd-mobile@freebsd.org > Subject: Re: Dell Inspiron 3500 >=20 >=20 > It seems John Sconiers wrote: > >=20 > > Does your touch pad work. I have a Latitude and it works pretty = well > > however I can't get the touch pad to work. Any thoughts >=20 > I have a Latitude, the touchpad works just dandy, its seen as > a psm (ps/2) mouse. >=20 > Its been running current, for the 6 month I've had it, NO PAO, just > plain and simple -current, works without a hitch.. >=20 > -S=F8ren >=20 ... and the touchpad works just as nicely on my Latitude running 3.1-R. Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 11:31:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 8A2C8153D0 for ; Thu, 29 Apr 1999 11:31:48 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 28879 invoked from network); 29 Apr 1999 18:31:48 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 29 Apr 1999 18:31:48 -0000 Date: Thu, 29 Apr 1999 13:31:47 -0500 (CDT) From: John Sconiers To: Soren Schmidt Cc: danj@3skel.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Dell Inspiron 3500 In-Reply-To: <199904291653.SAA06203@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It seems John Sconiers wrote: > > Does your touch pad work. I have a Latitude and it works pretty well > > however I can't get the touch pad to work. Any thoughts > I have a Latitude, the touchpad works just dandy, its seen as > a psm (ps/2) mouse. > Its been running current, for the 6 month I've had it, NO PAO, just > plain and simple -current, works without a hitch.. Have you used the docking station with the SCSI port?? JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 12:36:11 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id F2876150F9 for ; Thu, 29 Apr 1999 12:35:58 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA06562; Thu, 29 Apr 1999 21:35:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904291935.VAA06562@freebsd.dk> Subject: Re: Dell Inspiron 3500 In-Reply-To: from John Sconiers at "Apr 29, 1999 1:31:47 pm" To: jrs@enteract.com (John Sconiers) Date: Thu, 29 Apr 1999 21:35:45 +0200 (CEST) Cc: danj@3skel.com, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems John Sconiers wrote: > > It seems John Sconiers wrote: > > > Does your touch pad work. I have a Latitude and it works pretty well > > > however I can't get the touch pad to work. Any thoughts > > I have a Latitude, the touchpad works just dandy, its seen as > > a psm (ps/2) mouse. > > Its been running current, for the 6 month I've had it, NO PAO, just > > plain and simple -current, works without a hitch.. > > Have you used the docking station with the SCSI port?? Nope, not yet, I'd like to get one, but the pricetag is a bit on the rough side, so there is lots of other things that I'd buy instead, and I dont really need it for my use of the Latitude... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 13: 0: 8 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from qatar.net.qa (qatar.net.qa [194.133.33.11]) by hub.freebsd.org (Postfix) with ESMTP id 818B815231 for ; Thu, 29 Apr 1999 12:59:56 -0700 (PDT) (envelope-from sodah@qatar.net.qa) Received: from qatar.net.qa (ddbc.qatar.net.qa [194.133.35.38]) by qatar.net.qa (8.8.8/Internet-Qatar) with ESMTP id WAA07427 for ; Thu, 29 Apr 1999 22:58:12 +0300 (GMT) Message-ID: <3728B9D5.DB021C84@qatar.net.qa> Date: Thu, 29 Apr 1999 22:58:13 +0300 From: Fadi Sodah X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: mobile@freebsd.org Subject: 3com-NIC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi i built MYKERNEL to support my Network Card. i am using FreeBSD v.30 on my laptop Fujitsu (Lifebook 530T). the ful description of the network card is : - 3Comn Fast EtherLink 16Bit PC card (CardBus) called the 3C574-TX PC when i run the command 'dmesg | grep zp' , i get zp: pcmcia slot 0: 3Com3C574-TX Fats EtherLink PC Card A001 zp: slot 1: no card in slot zp0 not found at 0x300 what shall i do? or am i not going to get anywhere with that PC Card? thx in advance. -Pons P.S. i am not in the list To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 17:34:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from turtle.ee.ncku.edu.tw (turtle.ee.ncku.edu.tw [140.116.72.72]) by hub.freebsd.org (Postfix) with ESMTP id 534EF14E4F for ; Thu, 29 Apr 1999 17:29:26 -0700 (PDT) (envelope-from tung@turtle.ee.ncku.edu.tw) Received: (from tung@localhost) by turtle.ee.ncku.edu.tw (8.9.2/8.9.2) id IAA96103 for freebsd-mobile@FreeBSD.ORG; Fri, 30 Apr 1999 08:29:06 +0800 (CST) (envelope-from tung) Date: Fri, 30 Apr 1999 08:29:06 +0800 From: Chung-Kie Tung To: freebsd-mobile@FreeBSD.ORG Subject: the modem works but won't respsons immediately... Message-ID: <19990430082906.A96025@turtle.ee.ncku.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello... I have a pcmcia modem which works greatly with the old FreeBSD 2.2.5+PAO, but it has some strange behaver in the FreeBSD 3.1+PAO. The problem is that any command send to the modem works, but the response won't appear immidiately until I press the [enter] key. For Example: When I press 'at&f', I won't see the echo 'at&f' unless the [enter] is pressed, and the modem response 'OK' appears after I press the [enter] again. But if I input 'atdt2757575' and press [enter], though the echo 'atdt2757575' doesn't appear completely, the modem start to dial immediately. I try to use this modem to dialup to some ISP, the respons from the ISP won't appear unless I press more and more [enter]s. From my guess, the effect of the [enter] key is to put more data into the modem output buffer or something like that, and the output won't show up unless the number of chars in buffer has reached a boundary. This modem works ok when using win95, I also test my notebook with another external modem, it works okay too. So it seems that my FreeBSD and the pcmcia modem have no problem. My notebook PCIC is PD6729/6730 and It only works when flag 0x1 is used. The pcic is now using port 0xfcfc,IRQ 9 (IRQ 11 also has been tried) Below is my pccard.conf and the pccardc dumpcis output pccard.conf ---------------------------------------------------------------------- # Generally available IO ports #io 0x240-0x3ff io 0x240-0x320 0x3a0-0x3ff # Unavailable IRQs #ignirq 9 # refrain from using SoundBlaster's IRQ, by default. ignirq 5 # it may be helful for most of notebook PCs #ignirq 15 # Available memory slots memory 0xd4000 96k # NE2000 compatible PCMCIA card "Ethernet" "Adapter" config default "ed0" any insert logger -s NE2000 inserted insert /etc/pccard_ether $device remove logger -s NE2000 removed remove /etc/pccard_ether_remove $device card "Intelligent" "PCMCIA FAX/MODEM" # config 0x22 "sio2" 11 config auto "sio2" any insert logger -s 33.6K modem inserted remove logger -s 33.6K modem removed And the pccardc dumpcis output ---------------------------------------------------------------------- Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x15 (Version 1 info), length = 54 000: 04 01 49 6e 74 65 6c 6c 69 67 65 6e 74 00 50 43 010: 4d 43 49 41 20 20 46 41 58 2f 4d 4f 44 45 4d 00 020: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 030: 20 20 20 20 00 ff Version = 4.1, Manuf = [Intelligent], card vers = [PCMCIA FAX/MODEM] Addit. info = [ ] Tuple #3, code = 0x1a (Configuration map), length = 5 000: 01 23 00 01 03 Reg len = 2, config register addr = 0x100, last config = 0x23 Registers: XX------ Tuple #4, code = 0x1b (Configuration entry), length = 16 000: f0 41 99 49 55 46 0e aa 60 f8 03 07 30 ff ff 28 Config index = 0x30(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 4 x 100mA Power down supply current: 1.2 x 100mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #5, code = 0x1b (Configuration entry), length = 7 000: 21 08 aa 60 f8 02 07 Config index = 0x21 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #6, code = 0x1b (Configuration entry), length = 7 000: 22 08 aa 60 e8 03 07 Config index = 0x22 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #7, code = 0x1b (Configuration entry), length = 7 000: 23 08 aa 60 e8 02 07 Config index = 0x23 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #8, code = 0x0 (Null tuple), length = 21 000: ff ff ff ff ff fe be fa ba ff f8 ff 51 62 28 0f 010: 00 fa 34 00 34 Tuple #9, code = 0x20 (Manufacturer ID), length = 4 000: 02 01 06 00 PCMCIA ID = 0x102, OEM ID = 0x6 Tuple #10, code = 0x21 (Functional ID), length = 2 000: 02 01 Serial port/modem - POST initialize Tuple #11, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 5c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even Data bit - 7bit,8bit, Stop bit - 1bit,2bit Tuple #12, code = 0x22 (Functional EXT), length = 9 000: 01 1f 1f ff 03 00 ff 03 00 Modem interface capabilities: Tuple #13, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 02 b5 Data modem services available: Tuple #14, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 0f 00 02 00 b5 Fax1/modem services available: Tuple #15, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 0f 00 02 00 b5 Fax2/modem services available: Tuple #16, code = 0x0 (Null tuple), length = 7 000: 02 01 06 00 07 00 ff Tuple #17, code = 0x0 (Null tuple), length = 13 000: 30 30 30 30 38 36 30 30 34 34 33 31 ff Tuple #18, code = 0x14 (No link), length = 0 Tuple #19, code = 0xff (Terminator), length = 0 2 slots found Does anyone has the same problem with your problem? tung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Apr 29 17:40:44 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from fxp.dhs.org (cx19313-a.nwptn1.va.home.com [24.2.49.151]) by hub.freebsd.org (Postfix) with ESMTP id 3388214E4F for ; Thu, 29 Apr 1999 17:40:41 -0700 (PDT) (envelope-from jedgar@fxp.dhs.org) Received: from earth.fxp.dhs.org (jedgar@earth.fxp.dhs.org [192.168.1.21]) by fxp.dhs.org (8.9.3/8.9.3) with ESMTP id UAA05484; Thu, 29 Apr 1999 20:38:48 -0400 (EDT) (envelope-from jedgar@fxp.dhs.org) Date: Thu, 29 Apr 1999 20:38:48 -0400 (EDT) From: "Chris D. Faulhaber" To: Chung-Kie Tung Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: the modem works but won't respsons immediately... In-Reply-To: <19990430082906.A96025@turtle.ee.ncku.edu.tw> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Apr 1999, Chung-Kie Tung wrote: > Hello... > > I have a pcmcia modem which works greatly with the old FreeBSD 2.2.5+PAO, > but it has some strange behaver in the FreeBSD 3.1+PAO. > > The problem is that any command send to the modem works, but the response > won't appear immidiately until I press the [enter] key. > I had something like that with my pccard modem at first. Try adding "reset 1000": card "LUCENT-VENUS" "PCMCIA 56K DataFax" config 0x27 "sio2" 3 reset 1000 insert echo Lucent-Venus Modem inserted insert echo Lucent-Venus Moden removed -------------------------------------------------------------- | All the true gurus I've met never | Chris D. Faulhaber | | claimed they were one, and always | | | pointed to someone better. | | -------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 30 3:59:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 9139014C99 for ; Fri, 30 Apr 1999 03:59:17 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id SAA00664 for ; Fri, 30 Apr 1999 18:18:38 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Fri, 30 Apr 1999 18:18:37 -0500 (CDT) From: Douglas Carmichael To: freebsd-mobile@freebsd.org Subject: Anyone have a *working* pccard.conf entry for a modem card with interrupt-driven I/O? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Subject says it all. Any entries that work would be helpful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 30 9: 0:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 1D3CE1522E for ; Fri, 30 Apr 1999 09:00:12 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA12594; Fri, 30 Apr 1999 10:00:12 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA20387; Fri, 30 Apr 1999 10:00:11 -0600 Date: Fri, 30 Apr 1999 10:00:11 -0600 Message-Id: <199904301600.KAA20387@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Douglas Carmichael Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Anyone have a *working* pccard.conf entry for a modem card with interrupt-driven I/O? In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For which version of FreeBSD? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 30 9:23: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 9C11E14C56 for ; Fri, 30 Apr 1999 09:22:52 -0700 (PDT) (envelope-from mik.thwaite@dial.pipex.com) Received: (qmail 5142 invoked from network); 30 Apr 1999 16:22:44 -0000 Received: from userk999.uk.uudial.com (HELO mik) (193.149.73.67) by smtp.dial.pipex.com.128.43.158.in-addr.arpa with SMTP; 30 Apr 1999 16:22:44 -0000 Message-ID: <001c01be9325$7c2ab800$434995c1@mik> From: "Mik Thwaite" To: Subject: subscribe Date: Fri, 30 Apr 1999 17:20:27 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01BE932D.BD9F55E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0017_01BE932D.BD9F55E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0017_01BE932D.BD9F55E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0017_01BE932D.BD9F55E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 30 10:52:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 4EDD015123 for ; Fri, 30 Apr 1999 10:52:30 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id BAA00309; Sat, 1 May 1999 01:11:48 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Sat, 1 May 1999 01:11:46 -0500 (CDT) From: Douglas Carmichael To: Nate Williams Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Anyone have a *working* pccard.conf entry for a modem card with interrupt-driven I/O? In-Reply-To: <199904301600.KAA20387@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD 3.1 with PAO3-19990329-beta. On Fri, 30 Apr 1999, Nate Williams wrote: > For which version of FreeBSD? > > > Nate > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Apr 30 12:23:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 5FB3B14C4A for ; Fri, 30 Apr 1999 12:23:33 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA14456; Fri, 30 Apr 1999 13:23:32 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA21843; Fri, 30 Apr 1999 13:23:31 -0600 Date: Fri, 30 Apr 1999 13:23:31 -0600 Message-Id: <199904301923.NAA21843@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Douglas Carmichael Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: Anyone have a *working* pccard.conf entry for a modem card with interrupt-driven I/O? In-Reply-To: References: <199904301600.KAA20387@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > For which version of FreeBSD? > > FreeBSD 3.1 with PAO3-19990329-beta. I have it working fine with a number of cards in 2.2.* w/out PAO. I'm not running 3.*, but it should work fine with stock FreeBSD 3.* assuming the configuration stuff is setup correctly, since the code is almost exactly the same there. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 1 5:52:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from blodwen.watching.org (blodwen.demon.co.uk [158.152.26.67]) by hub.freebsd.org (Postfix) with SMTP id 73AEF14BD3 for ; Sat, 1 May 1999 05:52:37 -0700 (PDT) (envelope-from jrg@blodwen.demon.co.uk) Received: from renard.watching.org [193.37.42.76] by blodwen.watching.org with smtp (Exim 1.62 #4) id 10dZKy-0005ZT-00; Sat, 1 May 1999 13:57:44 +0100 Received: from jrg by renard.watching.org with local (Exim 1.62 #1) id 10dZUF-0001sZ-00; Sat, 1 May 1999 14:07:19 +0100 From: jrg@blodwen.demon.co.uk (James R Grinter) X-Subliminal: H is for Hypertext X-URL: http://www.blodwen.demon.co.uk/~jrg/ Organization: People's Front Against WWW To: freebsd-mobile@FreeBSD.ORG Subject: Re: 1) hibernation & 2) Re: IBM TP 760: X messed up on resume References: <19990417102422.B4796@zeus.rug.ac.be> <19990417111224.B19953@yoko.hsc.fr> <19990417162152.A8150@zeus.rug.ac.be> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 01 May 1999 14:07:17 +0100 In-Reply-To: Frank Louwers's message of Sat, 17 Apr 1999 16:21:52 +0200 Message-ID: Lines: 11 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Louwers writes: > I created a hibernation file (after the disks were partitioned, and after the > freebsd install), and it works in Win95, but in FBSD the machine just gives 3 > ugly beeps, so I think it can't find the hibernation file ... happens to me sometimes with my TP600. I've found that if I eject the PCMCIA ethernet card then it'll suspend. (a resume to XFree works fine, though!) James. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 1 12:28:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 0D59F15115 for ; Sat, 1 May 1999 12:28:17 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 21171 invoked from network); 1 May 1999 19:28:16 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 1 May 1999 19:28:16 -0000 Date: Sat, 1 May 1999 14:28:16 -0500 (CDT) From: John Sconiers To: freebsd-mobile@freebsd.org Subject: PAO DFE-650 and Latitude Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HI, I'm attempting to run freebsd on a dell Lattitude cpi with a D-Link DFE 650 TX PCMCIA 10/100 Network Card. So far I haven't had much luck. Last month I ran freebsd -release with PAO. I only used a Modem and not ethernet. Now I'm attempting to use a supported ethernet card and its not working. Can someone help me. I tried just installing from a 4.0-current CD-rom however that didn't work because it didn't pickup the ehternet card. I figured PAO would pick it up but it didn't when I booted off of the floppies. 1. Is this card supported? Is there another card I could use that would give me 10/100 and get to work? 2. For those of you that have Latitudes when I boot up and go to the visual configuration I show a conflict with the the PCMCIA slots. There are four 2 for slot0 and 2 for slot 1. Which ones should I enable and which ones should I remove?? 3. I mostly want to use the laptop as a stand alone and not docked. But has anyone gotton a docking station to work. 4. I have three other cards a Dell (3com) 3ccFE575BT-d that came with it a 3com Megahertz 3cxfe575BT and a 3com megahertz 3ccfem556. Do either of these cards work?? 5. How hard would it be for me to write a driver for one of them? 6. I see that Melco and Ontec are supported without any hitches. However I can't find a supplier. I'm guessing this is a card from out of this (USA) country. Can someone point me in the direction of a dealer or website that would ship the card to me. Any body willing to purchase the card for me if I supply the funds? Thanks in Advance JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 1 21: 7:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 3D1F714C8B for ; Sat, 1 May 1999 21:07:12 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id MAA06633; Sun, 2 May 1999 12:55:32 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: jrs@enteract.com Cc: freebsd-mobile@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: PAO DFE-650 and Latitude From: Tomoaki NISHIYAMA In-Reply-To: References: X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990502125532Q.tomoaki@moss.nibb.ac.jp> Date: Sun, 02 May 1999 12:55:32 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 30 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: John Sconiers Subject: PAO DFE-650 and Latitude Date: Sat, 1 May 1999 14:28:16 -0500 (CDT) Message-ID: jrs> 1. Is this card supported? Is there another card I could use that would jrs> give me 10/100 and get to work? The latest SUPPORTED.CARDS in pao228 states it as supported, and there is an entry in pccard.conf.sample. # D-Link DFE-650 Ethernet Card card "D-Link" "DFE-650" config default "ed0" any 0x10 insert logger -s D-link DFE-650 inserted insert /etc/pccard_ether $device remove logger -s D-link DFE-650 removed remove /etc/pccard_ether_remove $device I am using PLANEX FNW-3600-T without any trouble as 10 Base on FreeBSD-2.2.7 or 2.2.8 release with PAO, and I heard that it worked as 100 base if connected to a 100 base HUB, which I don't have. So, I guess if it does not work, something wrong is around your PCCARD interface, not the card itself. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun May 2 9:32:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id 0D08F15107 for ; Sun, 2 May 1999 09:32:44 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp516.kt.rim.or.jp [202.247.140.166]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id BAA00402 for ; Mon, 3 May 1999 01:32:43 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id BAA02812 for ; Mon, 3 May 1999 01:31:57 +0900 (JST) Message-ID: <372C7DCF.5BAB912C@sky.rim.or.jp> Date: Mon, 03 May 1999 01:31:11 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD Mobile Subject: Second draft of pccardc.8 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I've received a few patches for pccardc.8. I've merged that and checked-in into PAO repository. And I committed it into FreeBSD main repository. If someone interested in it has any comments, feel free to review and comment on it. Thanks! -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun May 2 13: 7: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 0AE2D14C34 for ; Sun, 2 May 1999 13:07:07 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 9829 invoked from network); 2 May 1999 20:07:06 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 2 May 1999 20:07:06 -0000 Date: Sun, 2 May 1999 15:07:06 -0500 (CDT) From: John Sconiers To: Tomoaki NISHIYAMA Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO DFE-650 and Latitude In-Reply-To: <19990502125532Q.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > jrs> 1. Is this card supported? Is there another card I could use that would > jrs> give me 10/100 and get to work? > The latest SUPPORTED.CARDS in pao228 states it as supported, and > there is an entry in pccard.conf.sample. I know.....but it has a *13 after it. I'm trying to install off of the internet using the D-Link and the PAO boot floppies. Should I be trying to install using the cdrom then add the package later and try to cinfigure it to work?? If anybody has a Dell Latitude what are your settings for your PCMCIA Slots set up for?? JOHN > # D-Link DFE-650 Ethernet Card > card "D-Link" "DFE-650" > config default "ed0" any 0x10 > insert logger -s D-link DFE-650 inserted > insert /etc/pccard_ether $device > remove logger -s D-link DFE-650 removed > remove /etc/pccard_ether_remove $device > > I am using PLANEX FNW-3600-T without any trouble as 10 Base on > FreeBSD-2.2.7 or 2.2.8 release with PAO, and I heard that > it worked as 100 base if connected to a 100 base HUB, > which I don't have. > > So, I guess if it does not work, something wrong is around > your PCCARD interface, not the card itself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun May 2 21:32:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B533215B92 for ; Sun, 2 May 1999 21:32:12 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA04756; Sun, 2 May 1999 22:31:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA40829; Sun, 2 May 1999 22:32:35 -0600 (MDT) Message-Id: <199905030432.WAA40829@harmony.village.org> To: Brian Somers Subject: Re: Newbus Woes Cc: Soren Schmidt , eculp@MexComUSA.net (Edwin Culp), freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 29 Apr 1999 17:24:50 BST." <199904291624.RAA03907@keep.lan.Awfulhak.org> References: <199904291624.RAA03907@keep.lan.Awfulhak.org> Date: Sun, 02 May 1999 22:32:35 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199904291624.RAA03907@keep.lan.Awfulhak.org> Brian Somers writes: : It's probably worth committing 'till Warner gets his changes in. The changes are coming Monday or Tuesday. I just got back from 5 days in the Jemez mountains..... And I just need to do one more thing to get the newbusified pccard code working. Well, it works now for new drivers, but the legacy ones need help... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 6:28:30 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7C60214F6A for ; Mon, 3 May 1999 06:27:52 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (502 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Mon, 3 May 1999 06:27:52 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Mon, 3 May 1999 06:27:52 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: PAO+ep0 slooooow Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sony vaio 500tx 3.1-release+pao 3c589c using zp0 (sans pao) this host would rdump (to a dlt on a neighboring host) in well under an hour using ep0 under pao it takes over 14 hours. any hints at where i should be looking? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 8:32:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dominator.eecs.harvard.edu (dominator.eecs.harvard.edu [140.247.60.28]) by hub.freebsd.org (Postfix) with SMTP id 187BC14D5E for ; Mon, 3 May 1999 08:32:22 -0700 (PDT) (envelope-from karp@eecs.harvard.edu) Received: (from karp@localhost) by dominator.eecs.harvard.edu (8.6.12/8.6.12) id LAA09005 for freebsd-mobile@freebsd.org; Mon, 3 May 1999 11:32:20 -0400 Date: Mon, 3 May 1999 11:32:20 -0400 From: Brad Karp Message-Id: <199905031532.LAA09005@dominator.eecs.harvard.edu> To: freebsd-mobile@freebsd.org Subject: my IEEE 802.11 WaveLAN driver for FreeBSD !! Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just ported the Linux WaveLAN 802.11 driver to FreeBSD 3.1-RELEASE. It works beautifully; ca. 1.4 Mbps application-to-application over TCP, which is about what the NT driver gets. I'm polishing it: - adding h/w multicast filter support - adding an analog for wlconfig, to read and set card-specific parameters (and read low-level tx and rx stats) To whom do I speak when it's time to have this committed? -Brad, karp@eecs.harvard.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 8:58:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 86F6B15043 for ; Mon, 3 May 1999 08:58:17 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1482 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Mon, 3 May 1999 08:30:01 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Mon, 3 May 1999 08:30:01 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Sean O'Connell" Cc: FreeBSD Laptoppers Subject: Re: PAO+ep0 slooooow References: <19990503101305.L23827@stat.Duke.EDU> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> using zp0 (sans pao) this host would rdump (to a dlt on a neighboring host) >> in well under an hour >> using ep0 under pao it takes over 14 hours. >> any hints at where i should be looking? > I'd worry about IRQ's. What IRQ is your pccard controller running > on? What does windoze think it should be running on? What about > ep0? > I had a similar problem with ep0 and an HP Omnibook. The pcic_irq > was being set to 3 (even though the hardware wanted to be on 10) and > ep0 just wouldn't work on 10 (due to the pcic listening there). It > was not until I had pcic on 10 and ep0 on 11 that life was happy. pcic0: rev 0x00 int a irq 255 on pci0.10.0 ... pcic0 at 0x3e0-0x3e1 irq 11 on isa PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 ... cmd ntpd pid 112 tried to use non-present sched_get_priority_min cmd ntpd pid 112 tried to use non-present sched_setscheduler ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 and ep0 is forced to int 10 by pccard.conf randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 9: 9: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id DC4CC15043 for ; Mon, 3 May 1999 09:09:01 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA16366; Mon, 3 May 1999 10:08:54 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA03370; Mon, 3 May 1999 10:08:54 -0600 Date: Mon, 3 May 1999 10:08:54 -0600 Message-Id: <199905031608.KAA03370@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Randy Bush Cc: "Sean O'Connell" , FreeBSD Laptoppers Subject: Re: PAO+ep0 slooooow In-Reply-To: References: <19990503101305.L23827@stat.Duke.EDU> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ Weird, I haven't gotten Sean's response to the list yet, but anyway ... ] > >> using zp0 (sans pao) this host would rdump (to a dlt on a neighboring host) > >> in well under an hour > >> using ep0 under pao it takes over 14 hours. > >> any hints at where i should be looking? > > I'd worry about IRQ's. What IRQ is your pccard controller running > > on? What does windoze think it should be running on? What about > > ep0? What windoze uses is irrelevant, because the PCIC and cards can use any available IRQ in the system. > > I had a similar problem with ep0 and an HP Omnibook. The pcic_irq > > was being set to 3 (even though the hardware wanted to be on 10) Just because windows used IRQ 10 means nothing. We can use IRQ 3 w/out any problems. > > and > > ep0 just wouldn't work on 10 (due to the pcic listening there). It > > was not until I had pcic on 10 and ep0 on 11 that life was happy. It shouldn't have made any difference. Is it possible that the second serial port was setup on IRQ 3? > > pcic0: rev 0x00 int a irq 255 on pci0.10.0 > ... > pcic0 at 0x3e0-0x3e1 irq 11 on isa > PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) > pcic0: slot 0 controller I/O address 0x3e0 > ... > cmd ntpd pid 112 tried to use non-present sched_get_priority_min > cmd ntpd pid 112 tried to use non-present sched_setscheduler > ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 > > and ep0 is forced to int 10 by pccard.conf So, is it working? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 9:11:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id B112815320 for ; Mon, 3 May 1999 09:11:44 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1184 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Mon, 3 May 1999 09:11:44 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Mon, 3 May 1999 09:11:44 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: "Sean O'Connell" , FreeBSD Laptoppers Subject: Re: PAO+ep0 slooooow References: <19990503101305.L23827@stat.Duke.EDU> <199905031608.KAA03370@mt.sri.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> pcic0: rev 0x00 int a irq 255 on pci0.10.0 >> ... >> pcic0 at 0x3e0-0x3e1 irq 11 on isa >> PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) >> pcic0: slot 0 controller I/O address 0x3e0 >> ... >> cmd ntpd pid 112 tried to use non-present sched_get_priority_min >> cmd ntpd pid 112 tried to use non-present sched_setscheduler >> ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 >> >> and ep0 is forced to int 10 by pccard.conf > > So, is it working? see original message. it works. problem is that it takes 15 hours to do an rdump when as zp0 pre-pao it took 45 minutes. i.e. this is a performance issue. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 9:13:58 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 99E7E15043 for ; Mon, 3 May 1999 09:13:53 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id MAA31992; Mon, 3 May 1999 12:13:52 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id MAA25036; Mon, 3 May 1999 12:13:52 -0400 (EDT) Message-ID: <19990503121351.P23827@stat.Duke.EDU> Date: Mon, 3 May 1999 12:13:51 -0400 From: "Sean O'Connell" To: Nate Williams Cc: FreeBSD mobile Subject: Re: PAO+ep0 slooooow Reply-To: "Sean O'Connell" References: <19990503101305.L23827@stat.Duke.EDU> <199905031608.KAA03370@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <199905031608.KAA03370@mt.sri.com>; from Nate Williams on Mon, May 03, 1999 at 10:08:54AM -0600 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999 May 03, Nate Williams (aka nate@mt.sri.com) wrote: > What windoze uses is irrelevant, because the PCIC and cards can use any > available IRQ in the system. I have not found this to be the case! If the hardware is still "interrupting" on 10 you are screwed. It's sort of like a *&^%ing winmodem. Let me restate, not true for pcic ... probably true for ep0. > > > I had a similar problem with ep0 and an HP Omnibook. The pcic_irq > > > was being set to 3 (even though the hardware wanted to be on 10) > > Just because windows used IRQ 10 means nothing. We can use IRQ 3 w/out > any problems. On ep0? Never tried ... I like things to "just work". > > > and > > > ep0 just wouldn't work on 10 (due to the pcic listening there). It > > > was not until I had pcic on 10 and ep0 on 11 that life was happy. > > It shouldn't have made any difference. Is it possible that the second > serial port was setup on IRQ 3? Ooooh or worse yet, an IR port! > Nate s -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 9:34:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D80C14C4F for ; Mon, 3 May 1999 09:34:44 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id MAA11042 for ; Mon, 3 May 1999 12:34:43 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id MAA25043 for freebsd-mobile@FreeBSD.ORG; Mon, 3 May 1999 12:34:43 -0400 (EDT) Message-ID: <19990503123443.R23827@stat.Duke.EDU> Date: Mon, 3 May 1999 12:34:43 -0400 From: "Sean O'Connell" To: FreeBSD mobile Subject: Poorly worded response by me Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All- I'd like to note that my reponse to Nate about the IRQ's was probably totally unclear. I have found that it helps to have the pcic_irq be the same one as that which windoze uses; otherwise, you can end up in a mess because the hardware (BIOS?) will use both the irq you assign it and the one it lives on in windoze. I experienced this with an HP Omnibook 900 that used IRQ10 with the pcic controller. I could use irq 3 for the controller and 10 for ep0. It would recognize the card fine and set up a connection, but as soon as your tried any real data transfer (nfs/scp/etc) it would hang and lock up. It was not until ep0 was on the same irq that windoze assigned it (11) both in the kernel and in pccard.conf was the networking happy. I also saw this problem with the modems too. Sorry about the confusing statements.... I typed before I thought. S -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 9:46: 8 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id CC9D314C4F for ; Mon, 3 May 1999 09:46:04 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id KAA09376 for ; Mon, 3 May 1999 10:46:00 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Mon, 3 May 1999 10:46:00 -0600 (MDT) From: Brian Handy To: freebsd-mobile@freebsd.org Subject: TP560 hardware woes Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, I had to send in my TP560 for service again -- this is the second time since I got it (2 years ago?) that I've blown the motherboard. It's out of warrantee, so they want $800 to fix it. This is awful close to the price of a new TP560E or so, I saw one on www.Pricewatch.com for around $1100. Any recommendations out there on this? Places I should check out for deals? I'd like to stay with the TP560's so I can use the pile of spare disk drives I have and be vaguely compatible with the other TP560's we already have here. Thanks, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 10: 7:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id AB684155F5 for ; Mon, 3 May 1999 10:07:43 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA16912; Mon, 3 May 1999 11:07:42 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA03776; Mon, 3 May 1999 11:07:41 -0600 Date: Mon, 3 May 1999 11:07:41 -0600 Message-Id: <199905031707.LAA03776@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Sean O'Connell" Cc: Nate Williams , FreeBSD mobile Subject: Re: PAO+ep0 slooooow In-Reply-To: <19990503121351.P23827@stat.Duke.EDU> References: <19990503101305.L23827@stat.Duke.EDU> <199905031608.KAA03370@mt.sri.com> <19990503121351.P23827@stat.Duke.EDU> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > What windoze uses is irrelevant, because the PCIC and cards can use any > > available IRQ in the system. > > I have not found this to be the case! If the hardware is still > "interrupting" on 10 you are screwed. It's sort of like a *&^%ing > winmodem. Let me restate, not true for pcic ... probably true for > ep0. Umm, you *configure* the PCIC controller to interrupt wherever you want it to. It's not hard-coded like an ISA card, but completely programmable. Just because Windoze chose to program it to IRQ 11 doesn't mean it must be an IRQ 11. > > > > I had a similar problem with ep0 and an HP Omnibook. The pcic_irq > > > > was being set to 3 (even though the hardware wanted to be on 10) > > > > Just because windows used IRQ 10 means nothing. We can use IRQ 3 w/out > > any problems. > > On ep0? Never tried ... I like things to "just work". Sure. It should 'just work' assuming there isn't any hardware hard-wired to a particular IRQ that FreeBSD doesn't know about. > > > > ep0 just wouldn't work on 10 (due to the pcic listening there). It > > > > was not until I had pcic on 10 and ep0 on 11 that life was happy. > > > > It shouldn't have made any difference. Is it possible that the second > > serial port was setup on IRQ 3? > > Ooooh or worse yet, an IR port! Same difference. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 10:10:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 8989814C32 for ; Mon, 3 May 1999 10:10:24 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA16955; Mon, 3 May 1999 11:10:22 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA03833; Mon, 3 May 1999 11:10:21 -0600 Date: Mon, 3 May 1999 11:10:21 -0600 Message-Id: <199905031710.LAA03833@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Randy Bush Cc: Nate Williams , "Sean O'Connell" , FreeBSD Laptoppers Subject: Re: PAO+ep0 slooooow In-Reply-To: References: <19990503101305.L23827@stat.Duke.EDU> <199905031608.KAA03370@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> pcic0: rev 0x00 int a irq 255 on pci0.10.0 > >> ... > >> pcic0 at 0x3e0-0x3e1 irq 11 on isa > >> PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) > >> pcic0: slot 0 controller I/O address 0x3e0 > >> ... > >> cmd ntpd pid 112 tried to use non-present sched_get_priority_min > >> cmd ntpd pid 112 tried to use non-present sched_setscheduler > >> ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 > >> > >> and ep0 is forced to int 10 by pccard.conf > > > > So, is it working? > > see original message. it works. problem is that it takes 15 hours to do an > rdump when as zp0 pre-pao it took 45 minutes. i.e. this is a performance > issue. Sounds like the interrupt is actually not being set, so you're actually using the watchdog timer to transfer data, which creates a fake interrupt 1/sec. Try hard-codeing the interrupt to something else in /etc/pccard.conf to see if that helps. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 13:41:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id AE2CD14E68 for ; Mon, 3 May 1999 13:41:03 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id DAA00390; Mon, 3 May 1999 03:41:29 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Mon, 3 May 1999 03:41:27 -0500 (CDT) From: Douglas Carmichael To: freebsd-mobile@freebsd.org Cc: hosokawa@jp.freebsd.org Subject: PAO3 is the cause of my modem problems (it works with PAO-971211+2.2.5R and Slackware Linux v3.6) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After trying different interrupts with PAO3 (even ones that are unused), I finally tried PAO-971211 with 2.2.5-RELEASE and Slackware Linux with pcmcia-cs-3.0.9. The modem card worked under both environments. (out of the box with PAO-971211 and on IRQ 3 with pcmcia-cs-3.0.9). That leads me to believe that there is some sort of bug in PAO3 interfering with use of PCMCIA modems. Have any of you had any luck with PAO3? When will there be a final release of PAO3? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 22: 3: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3C80315122 for ; Mon, 3 May 1999 22:02:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA08350 for ; Mon, 3 May 1999 23:02:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA54903 for ; Mon, 3 May 1999 23:03:34 -0600 (MDT) Message-Id: <199905040503.XAA54903@harmony.village.org> To: mobile@freebsd.org Subject: Progress on new bus conversion of pccard Date: Mon, 03 May 1999 23:03:34 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm making progress on the new busification of pccard. pcic0: at port 0x3e0-0x3e3 irq 9 on isa0 pcic0: interrupting at irq 9 pccard0: on pcic0 Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s2a ... devclass_alloc_unit: ep0 already exists, using next available unit number ep1 on pccard0 ep1: utp/bnc[*UTP*] address 00:60:97:95:9f:3d Data modified on freelist: word 2 of object 0xc059e260 size 20 previous type devbuf (0x80 != 0xdeadc0de) ep1: interrupting at irq 10 I was able to set the IRQ in my config file, but not from userconfig (otherwise it defaulted to irq 5, which was wrong for this PCI device). So things are looking promsing. However, the freelist message tells me that this code isn't quite ready for prime time, or even simple testing outside of people that can fix crashes :-). The pcic is on isa0 rather than pci0, but that is a simple probe issue, I hope. Also, the ep1 should really be ep0, but for some reason that device is reserved by the new config stuff. I don't know why. Now, to see where I'm mangling memory... With luck, I should have patches available for testing in the next 24 hours. However, given the scope of the changes I made to this code to get things working, it may be a while longer before they are committed to -current. It all depends on how well things work for people and how quickly they test it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 3 22:37:19 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AAB4914F22 for ; Mon, 3 May 1999 22:37:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA08443 for ; Mon, 3 May 1999 23:36:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA55127 for ; Mon, 3 May 1999 23:37:51 -0600 (MDT) Message-Id: <199905040537.XAA55127@harmony.village.org> To: mobile@freebsd.org Subject: slow ep response... Date: Mon, 03 May 1999 23:37:51 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was just able to recreate the slow ep response on my machine here (granted, it is running my experiental pccard stuff, which is prone to crashing), but I was seeing the following on an unloaded ethernet connection: % ping 10.5 PING 10.5 (10.0.0.5): 56 data bytes 64 bytes from 10.0.0.5: icmp_seq=0 ttl=255 time=931.404 ms 64 bytes from 10.0.0.5: icmp_seq=1 ttl=255 time=1924.132 ms 64 bytes from 10.0.0.5: icmp_seq=2 ttl=255 time=914.182 ms 64 bytes from 10.0.0.5: icmp_seq=3 ttl=255 time=1904.401 ms 64 bytes from 10.0.0.5: icmp_seq=4 ttl=255 time=894.465 ms 64 bytes from 10.0.0.5: icmp_seq=5 ttl=255 time=1884.667 ms 64 bytes from 10.0.0.5: icmp_seq=6 ttl=255 time=874.722 ms This would certainly account for the problems you've been seeing. I suspect it has something to do with interrupts, but I'm not sure what. I just wanted to let people know that I've seen this here... It seems like it is interrupt related... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 1:14:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from turtle.ee.ncku.edu.tw (turtle.ee.ncku.edu.tw [140.116.72.72]) by hub.freebsd.org (Postfix) with ESMTP id 6F56314C33 for ; Tue, 4 May 1999 01:13:27 -0700 (PDT) (envelope-from tung@turtle.ee.ncku.edu.tw) Received: (from tung@localhost) by turtle.ee.ncku.edu.tw (8.9.2/8.9.2) id QAA83291 for freebsd-mobile@FreeBSD.ORG; Tue, 4 May 1999 16:12:35 +0800 (CST) (envelope-from tung) Date: Tue, 4 May 1999 16:12:35 +0800 From: Chung-Kie Tung To: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO3 is the cause of my modem problems (it works with PAO-971211+2.2.5Rand Slackware Linux v3.6) Message-ID: <19990504161235.A83263@turtle.ee.ncku.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi... I got exactly the same problem as you, my modem also worked with 2.2.5R+PAO before. But it can not work when I upgrade to 3.1R+PAO3. What is the PCIC of your notebook? tung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 1:33:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 1BD7314A2E for ; Tue, 4 May 1999 01:33:45 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (ppp2.imasy.or.jp [202.227.24.12]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.00) with ESMTP id RAA11421; Tue, 4 May 1999 17:33:35 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199905040833.RAA11421@tasogare.imasy.or.jp> To: freebsd-mobile@freebsd.org Cc: dcarmich@xnet.com, hosokawa@jp.freebsd.org, tung@turtle.ee.ncku.edu.tw, jedgar@fxp.dhs.org Subject: Re: PAO3 is the cause of my modem problems (it works with PAO-971211+2.2.5R and Slackware Linux v3.6) In-Reply-To: Your message of "Mon, 3 May 1999 03:41:27 -0500 (CDT)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 04 May 1999 17:32:39 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 83 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. My name is Iwasaki. I noticed this problem on PAO3 few days before, and trying to fix it now. It seems that the bugs in sioinit() and sioprobe() of sys/i386/isa/sio.c (PAO3). sioinit(): In /etc/pccard.conf of PAO3, flags 0x40000 is specified by digital communication cards entry. For normal modems this flags is not given. However sioinit() always overrides this flags to COM_C_NOPROBE (0x40000). (If COM_C_NOPROBE bit is enabled, initialization procedue will be skipped in sioprobe().) sioprobe(): Code for device with COM_C_NOPROBE flags is duplicated. I suspect that first one must be deleted because the initialization procedue starts after this block. The following patch works well for me. So far so good. But I'm not sure this is correct solution because I don't have any digital communication cards which specified 0x40000 flags in /etc/pccard.conf, and don't understand clearly why COM_C_NOPROBE bit can be set in sioinit(). Can anyone test this patch or review it? --- /usr/PAO3/src/sys/i386/isa/sio.c- Mon May 3 15:20:37 1999 +++ /usr/PAO3/src/sys/i386/isa/sio.c Mon May 3 22:41:38 1999 @@ -489,8 +489,16 @@ if (com_addr(unit)) return(EBUSY); +#if 0 + /* + * XXX This line overrides device flags specified + * in /etc/pccard.conf on COM_C_NOPROBE (0x40000). + * iwasaki@jp.FreeBSD.org + */ + /* It's already probed as serial by Upper */ devi->isahd.id_flags |= COM_C_NOPROBE; +#endif /* * Probe the device. If a value is returned, the @@ -652,37 +660,6 @@ bzero(failures, sizeof failures); iobase = dev->id_iobase; - - /* - * It's a definitly Serial PCMCIA(16550A), but still be required - * for IIR_TXRDY implementation ( Palido 321s, DC-1S... ) - */ - if ( COM_NOPROBE(dev) ) { - /* Reading IIR register twice */ - for ( fn = 0; fn < 2; fn ++ ) { - DELAY(10000); - failures[6] = inb(iobase + com_iir); - } - /* Check IIR_TXRDY clear ? */ - result = IO_COMSIZE; - if ( failures[6] & IIR_TXRDY ) { - /* Nop, Double check with clearing IER */ - outb(iobase + com_ier, 0); - if ( inb(iobase + com_iir) & IIR_NOPEND ) { - /* Ok. we're familia this gang */ - dev->id_flags |= COM_C_IIR_TXRDYBUG; /* Set IIR_TXRDYBUG */ - } else { - /* Unknow, Just omit this chip.. XXX*/ - result = 0; - } - } else { - /* OK. this is well-known guys */ - dev->id_flags &= ~COM_C_IIR_TXRDYBUG; /*Clear IIR_TXRDYBUG*/ - } - outb(iobase + com_cfcr, CFCR_8BITS); - enable_intr(); - return( result ); - } /* * We don't want to get actual interrupts, just masked ones. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 1:48:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CE0B3154DF for ; Tue, 4 May 1999 01:48:28 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA21854; Tue, 4 May 1999 10:48:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905040848.KAA21854@freebsd.dk> Subject: Re: slow ep response... In-Reply-To: <199905040537.XAA55127@harmony.village.org> from Warner Losh at "May 3, 1999 11:37:51 pm" To: imp@harmony.village.org (Warner Losh) Date: Tue, 4 May 1999 10:48:23 +0200 (CEST) Cc: mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > > I was just able to recreate the slow ep response on my machine here > (granted, it is running my experiental pccard stuff, which is prone to > crashing), but I was seeing the following on an unloaded ethernet > connection: > > % ping 10.5 > PING 10.5 (10.0.0.5): 56 data bytes > 64 bytes from 10.0.0.5: icmp_seq=0 ttl=255 time=931.404 ms > 64 bytes from 10.0.0.5: icmp_seq=1 ttl=255 time=1924.132 ms > 64 bytes from 10.0.0.5: icmp_seq=2 ttl=255 time=914.182 ms > 64 bytes from 10.0.0.5: icmp_seq=3 ttl=255 time=1904.401 ms > 64 bytes from 10.0.0.5: icmp_seq=4 ttl=255 time=894.465 ms > 64 bytes from 10.0.0.5: icmp_seq=5 ttl=255 time=1884.667 ms > 64 bytes from 10.0.0.5: icmp_seq=6 ttl=255 time=874.722 ms > > This would certainly account for the problems you've been seeing. > > I suspect it has something to do with interrupts, but I'm not sure > what. I just wanted to let people know that I've seen this here... > It seems like it is interrupt related... You are not getting the interrupt, you are running on the timeout watchdog... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 1:50:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A09DA15709 for ; Tue, 4 May 1999 01:50:45 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA21873; Tue, 4 May 1999 10:50:19 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905040850.KAA21873@freebsd.dk> Subject: Re: my IEEE 802.11 WaveLAN driver for FreeBSD !! In-Reply-To: <199905031532.LAA09005@dominator.eecs.harvard.edu> from Brad Karp at "May 3, 1999 11:32:20 am" To: karp@eecs.harvard.edu (Brad Karp) Date: Tue, 4 May 1999 10:50:19 +0200 (CEST) Cc: freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Brad Karp wrote: > I've just ported the Linux WaveLAN 802.11 driver to FreeBSD 3.1-RELEASE. > > It works beautifully; ca. 1.4 Mbps application-to-application over TCP, > which is about what the NT driver gets. > > I'm polishing it: > > - adding h/w multicast filter support > - adding an analog for wlconfig, to read and set card-specific > parameters (and read low-level tx and rx stats) > > To whom do I speak when it's time to have this committed? Hmm is it GPL infected ??, then it will be difficult to get it into the kernel... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 4: 6:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from turtle.ee.ncku.edu.tw (turtle.ee.ncku.edu.tw [140.116.72.72]) by hub.freebsd.org (Postfix) with ESMTP id 70F7F14A2E for ; Tue, 4 May 1999 04:06:43 -0700 (PDT) (envelope-from tung@turtle.ee.ncku.edu.tw) Received: (from tung@localhost) by turtle.ee.ncku.edu.tw (8.9.2/8.9.2) id TAA99326; Tue, 4 May 1999 19:06:34 +0800 (CST) (envelope-from tung) Date: Tue, 4 May 1999 19:06:34 +0800 From: Chung-Kie Tung To: Mitsuru IWASAKI Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO3 is the cause of my modem problems (it works with PAO-971211+2.2.5R and Slackware Linux v3.6) Message-ID: <19990504190634.A99213@turtle.ee.ncku.edu.tw> References: <199905040833.RAA11421@tasogare.imasy.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199905040833.RAA11421@tasogare.imasy.or.jp>; from Mitsuru IWASAKI on Tue, May 04, 1999 at 05:32:39PM +0900 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 04, 1999 at 05:32:39PM +0900, Mitsuru IWASAKI wrote: > The following patch works well for me. So far so good. > But I'm not sure this is correct solution because I don't have > any digital communication cards which specified 0x40000 flags in > /etc/pccard.conf, and don't understand clearly why COM_C_NOPROBE > bit can be set in sioinit(). > > Can anyone test this patch or review it? > Hello... Your patch has fixed my problem of modem with PAO3. Thank you very very much :) tung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 5: 0: 6 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from aaka.3skel.com (3skel-inch-rtr.3skel.com [207.240.212.3]) by hub.freebsd.org (Postfix) with ESMTP id C47E514C01 for ; Tue, 4 May 1999 05:00:01 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3Skel.COM [192.168.0.8]) by aaka.3skel.com (8.8.8/8.8.8) with ESMTP id IAA05678; Tue, 4 May 1999 08:00:00 -0400 (EDT) (envelope-from danj@3skel.com) Received: from localhost (danj@localhost) by fnur.3skel.com (8.9.2/8.8.2) with ESMTP id HAA20598; Tue, 4 May 1999 07:59:55 -0400 (EDT) Date: Tue, 4 May 1999 07:59:55 -0400 (EDT) From: Dan Janowski To: Nate Williams Cc: Randy Bush , "Sean O'Connell" , FreeBSD Laptoppers Subject: Re: PAO+ep0 slooooow In-Reply-To: <199905031710.LAA03833@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If this horse is not dead yet, I have a simple contribution. I just set up a 3c589c on a Dell Inspiron 3500. Ethernet traffic was BAD, would go out fine, but coming back it was obviously missing an interrupt. One thing is for SURE, FreeBSD is currently unable to detect, some or all, win-modems AND the interrupts they steal. Since most winmodems are parked on IRQ-3 and insertion will try to use the first available IRQ... well, forget about it. I knew for sure by this, when you eject the card, the system reports what IRQ it was on. When I noticed that mine was saying IRQ-3, I smelled a rat. I was able to quickly confirm by turning off the winmodem in the BIOS, and like magic it worked. The long term solution was to do this: ignirq 3 in the pccard.conf since I don't want to have to remember to turn the winmodem on or off if I use windows. Dan On Mon, 3 May 1999, Nate Williams wrote: > > >> pcic0: rev 0x00 int a irq 255 on pci0.10.0 > > >> ... > > >> pcic0 at 0x3e0-0x3e1 irq 11 on isa > > >> PC-Card ctlr(0) Ricoh RL5C475/476 [CardBus bridge mode] (5 mem & 2 I/O windows) > > >> pcic0: slot 0 controller I/O address 0x3e0 > > >> ... > > >> cmd ntpd pid 112 tried to use non-present sched_get_priority_min > > >> cmd ntpd pid 112 tried to use non-present sched_setscheduler > > >> ep0: utp/bnc[*UTP*] address 00:a0:24:ac:89:33 > > >> > > >> and ep0 is forced to int 10 by pccard.conf > > > > > > So, is it working? > > > > see original message. it works. problem is that it takes 15 hours to do an > > rdump when as zp0 pre-pao it took 45 minutes. i.e. this is a performance > > issue. > > Sounds like the interrupt is actually not being set, so you're actually > using the watchdog timer to transfer data, which creates a fake > interrupt 1/sec. > > Try hard-codeing the interrupt to something else in /etc/pccard.conf to > see if that helps. > > > > Nate > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > -- Dan Janowski danj@3skel.com Triskelion Systems, Inc. Bronx, NY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 5: 4:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from aaka.3skel.com (3skel-inch-rtr.3skel.com [207.240.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 8BED31548B for ; Tue, 4 May 1999 05:04:51 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3Skel.COM [192.168.0.8]) by aaka.3skel.com (8.8.8/8.8.8) with ESMTP id IAA05697; Tue, 4 May 1999 08:04:50 -0400 (EDT) (envelope-from danj@3skel.com) Received: from localhost (danj@localhost) by fnur.3skel.com (8.9.2/8.8.2) with ESMTP id IAA20651; Tue, 4 May 1999 08:04:47 -0400 (EDT) Date: Tue, 4 May 1999 08:04:47 -0400 (EDT) From: Dan Janowski To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: slow ep response... In-Reply-To: <199905040537.XAA55127@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org PAO3, 3c589c on an unloaded ethernet: % /sbin/ifconfig ep0 ep0: flags=8843 mtu 1500 inet 192.168.0.21 netmask 0xffffff00 broadcast 192.168.0.255 inet 192.168.0.101 netmask 0xffffffff broadcast 192.168.0.101 ether 00:a0:24:5f:ce:46 % /sbin/ping 192.168.0.8 PING 192.168.0.8 (192.168.0.8): 56 data bytes 64 bytes from 192.168.0.8: icmp_seq=0 ttl=255 time=0.528 ms 64 bytes from 192.168.0.8: icmp_seq=1 ttl=255 time=0.518 ms 64 bytes from 192.168.0.8: icmp_seq=2 ttl=255 time=0.485 ms 64 bytes from 192.168.0.8: icmp_seq=3 ttl=255 time=0.472 ms 64 bytes from 192.168.0.8: icmp_seq=4 ttl=255 time=0.504 ms 64 bytes from 192.168.0.8: icmp_seq=5 ttl=255 time=0.473 ms 64 bytes from 192.168.0.8: icmp_seq=6 ttl=255 time=0.470 ms Dan On Mon, 3 May 1999, Warner Losh wrote: > > I was just able to recreate the slow ep response on my machine here > (granted, it is running my experiental pccard stuff, which is prone to > crashing), but I was seeing the following on an unloaded ethernet > connection: > > % ping 10.5 > PING 10.5 (10.0.0.5): 56 data bytes > 64 bytes from 10.0.0.5: icmp_seq=0 ttl=255 time=931.404 ms > 64 bytes from 10.0.0.5: icmp_seq=1 ttl=255 time=1924.132 ms > 64 bytes from 10.0.0.5: icmp_seq=2 ttl=255 time=914.182 ms > 64 bytes from 10.0.0.5: icmp_seq=3 ttl=255 time=1904.401 ms > 64 bytes from 10.0.0.5: icmp_seq=4 ttl=255 time=894.465 ms > 64 bytes from 10.0.0.5: icmp_seq=5 ttl=255 time=1884.667 ms > 64 bytes from 10.0.0.5: icmp_seq=6 ttl=255 time=874.722 ms > > This would certainly account for the problems you've been seeing. > > I suspect it has something to do with interrupts, but I'm not sure > what. I just wanted to let people know that I've seen this here... > It seems like it is interrupt related... > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > -- Dan Janowski danj@3skel.com Triskelion Systems, Inc. Bronx, NY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 6:20: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 959E015341 for ; Tue, 4 May 1999 06:19:54 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id WAA03874; Tue, 4 May 1999 22:19:53 +0900 (JST) Date: Tue, 4 May 1999 22:19:53 +0900 (JST) Message-Id: <199905041319.WAA03874@afs.ntc.mita.keio.ac.jp> To: mobile@freebsd.org Cc: hosokawa@itc.keio.ac.jp Subject: Suspend and time warp problem of -current apm driver From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I'm playing -current with Toshiba Libretto SS1000. This machine sleeps correctly with plain 3.1-RELEASE w/o PAO, but it can't sleep with -current (when I type zzz from console). I can suspend it with power button, but it brings about time-warp. I've looked into apm driver in CVS repository, but I can't find any major changes between HEAD and RELENG_3_1_0_RELEASE except newbus import. But I can't believe that newbus import causes such problem. Anyone experienced such trouble? -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 6:38:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 475AA15117 for ; Tue, 4 May 1999 06:38:48 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id WAA04020; Tue, 4 May 1999 22:38:41 +0900 (JST) Date: Tue, 4 May 1999 22:38:41 +0900 (JST) Message-Id: <199905041338.WAA04020@afs.ntc.mita.keio.ac.jp> To: dcarmich@xnet.com Cc: freebsd-mobile@FreeBSD.ORG, hosokawa@itc.keio.ac.jp Subject: Re: Anyone have a *working* pccard.conf entry for a modem card withinterrupt-driven I/O? In-Reply-To: Your message of "Sat, 1 May 1999 08:18:37 JST". From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article dcarmich@xnet.com writes: >> Subject says it all. >> >> Any entries that work would be helpful. I believe that most of pccard.conf.sample entries with static IRQ definition can work with dynamic IRQ definition ("?" in -current, and "any" in PAO). Please test following patch (confirm that "irq" definition is correct. I'm using "irq 10 11" on Libretto). --- pccard.conf.sample.orig Tue May 4 22:24:15 1999 +++ pccard.conf.sample Tue May 4 22:36:03 1999 @@ -19,7 +19,7 @@ #IBM PCMCIA Ethernet I/II card "IBM Corp." "Ethernet" - config 0x1 "ed0" 11 + config 0x1 "ed0" ? ether 0xff0 insert echo IBM PCMCIA Ethernet inserted insert /etc/pccard_ether ed0 @@ -28,7 +28,7 @@ # Melco LPC-T (PIO mode) card "PCMCIA" "UE2212" - config 0x1 "ed0" 11 0x10 + config 0x1 "ed0" ? 0x10 ether 0xff0 insert echo UE2212 inserted insert /etc/pccard_ether ed0 @@ -38,7 +38,7 @@ # Accton EN2212 # Very slow! (PIO mode) card "ACCTON" "EN2212" - config 0x1 "ed0" 11 0x10 + config 0x1 "ed0" ? 0x10 ether 0xff0 insert echo Accton EN2212 inserted insert /etc/pccard_ether ed0 @@ -47,7 +47,7 @@ #Accton 2216 card "ACCTON" "EN2216-PCMCIA-ETHERNET" - config 0x20 "ed0" 10 + config 0x20 "ed0" ? insert echo Accton 2216 inserted insert /etc/pccard_ether ed0 remove echo Accton 2216 removed @@ -72,7 +72,7 @@ # LinkSys ethernet card card "E-CARD" "E-CARD" - config 0x20 "ed0" 10 + config 0x20 "ed0" ? insert echo "LinkSys card inserted" insert /etc/pccard_ether ed0 remove echo "LinkSys card removed" @@ -80,7 +80,7 @@ # Linksys Combo PCMCIA EthernetCard (model EC2T on box) card "Linksys" "Combo PCMCIA EthernetCard (EC" - config 0x1 "ed0" 10 + config 0x1 "ed0" ? insert echo Linksys Ethernet inserted insert /etc/pccard_ether ed0 remove echo Linksys Ethernet removed @@ -97,7 +97,7 @@ # Fujitsu MBH10302 card "PCMCIA MBH10302" "01" - config 0x14 "fe0" 10 + config 0x14 "fe0" ? insert echo Fujitsu MBH10302 inserted insert /etc/pccard_ether fe0 remove echo Fujitsu MBH10302 removed @@ -105,7 +105,7 @@ # NextCom J Link NC5310 card "NextComK.K." "NC5310 Ver1.0 " - config 0x14 "fe0" 10 + config 0x14 "fe0" ? insert echo NextCom J Link NC5310 inserted insert /etc/pccard_ether fe0 remove echo NextCom J Link NC5310 removed @@ -113,7 +113,7 @@ # HITACHI HT-4840-11 card "HITACHI" "HT-4840-11" - config 0x1a "fe0" 15 + config 0x1a "fe0" ? insert echo HT-4840-11 inserted insert /etc/pccard_ether fe0 remove echo HT-4840-11 removed @@ -121,7 +121,7 @@ # Danpex (Alloy, etc.) EN-6200P2 card "DANPEX" "EN-6200P2" - config 0x22 "ed0" 9 + config 0x22 "ed0" ? insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete @@ -133,7 +133,7 @@ # Compex Net-A adapter card "Ethernet" "Adapter" - config 0x1 "ed0" 11 + config 0x1 "ed0" ? ether 0xff0 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete @@ -161,91 +161,91 @@ # AIWA PV-JF288 card "AIWA CO.,LTD." "PV-JF288 " - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo AIWA PV-JF288 inserted remove echo AIWA PV-JF288 removed # Apex Data 28.8 PC Card "MOBILE PLUS Cellular" modem. card "AD PC_CARD" "RC288ACL" - config 0x22 "sio2" 10 + config 0x22 "sio2" ? insert echo Apex Data Mobile Plus 28.8 Modem inserted remove echo Apex Data Mobile Plus 28.8 Modem removed # Megahertz XJ1144 card "MEGAHERTZ" "XJ1144" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Megahertz XJ1144 inserted remove echo Megahertz XJ1144 removed # Megahertz XJ2144 (US) card "MEGAHERTZ" "XJ2144" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Megahertz XJ2144 inserted remove echo Megahertz XJ2144 removed # Megahertz XJ2144 (JP) card "MEGAHERTZ" "XJ2144-81" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Megahertz XJ2144 inserted remove echo Megahertz XJ2144 removed # Megahertz XJ2288 card "MEGAHERTZ" "XJ2288" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Megahertz XJ2288 inserted remove echo Megahertz XJ2288 removed # Megahertz XJ4336 card "Megahertz" "XJ4336-CC4336" - config 0x21 "sio1" 10 + config 0x21 "sio1" ? insert echo Megahertz XJ4336 inserted remove echo Megahertz XJ4336 removed # Megahertz XJ1336 card "U.S. Robotics" "XJ/CC1336" - config 0x21 "sio2" 10 + config 0x21 "sio2" ? insert echo U.S. Robotics XJ/CC1336 inserted remove echo U.S. Robotics XJ/CC1336 removed # Omron ME2814 FAX/DATA MODEM card "OMRON" "ME2814 FAX/DATA MOD" - config 0x23 "sio2" 3 + config 0x23 "sio2" ? insert echo OMRON ME2814 Modem inserted remove echo OMRON ME2814 Modem removed # TDK 14.4 FAX/Data Modem card "TDK" "DF1414 DATA/FAX MOD" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo TDK DF1414 inserted remove echo TDK DF1414 removed # TDK 14.4 FAX/Data Modem card "TDK" "DF1414EX DATA/FAX M" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo TDK DF1414 inserted remove echo TDK DF1414 removed # Panasonic Modem Card TO-706C card "Panasonic" "TO-706C" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Panasonic TO-706C inserted remove echo Panasonic TO-706C removed # Panasonic Modem Card TO-706C card "Panasonic" "TO-CAF288" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Panasonic TO-CAF288 inserted remove echo Panasonic TO-CAF288 removed # NewMedia 14.4K FAX/Data Modem card "CIRRUS LOGIC" "FAX MODEM" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo Newmedia 14.4 Modem inserted remove echo Newmedia 14.4 Modem removed # Omron MD24XCA FAX/Data Modem #card "OMRON Corp." "MD24XCA" -# config 0x23 "sio2" 16 +# config 0x23 "sio2" ? # reset 10000 # insert echo OMRON MD24XCA Modem inserted # remove echo OMRON MD24XCA Modem removed @@ -253,33 +253,33 @@ # Hayes OPTIMA 288 FAX/Data Modem # currently does not work on my machine card "Hayes" "OPTIMA 288 + FAX fo" - config 0x24 "sio2" 5 + config 0x24 "sio2" ? reset 10000 insert echo Optima 288 inserted remove echo Optima 288 removed # This one does work though card "HAYES" "OPT288" - config 0x23 "sio3" 9 + config 0x23 "sio3" ? insert echo Hayes Optima 28.8k inserted remove echo Hayes Optima 28.8k removed # PREMAX FM288 FAX/Data Modem card "PREMAX" "FM288 " - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo PREMAX FM288 Modem inserted remove echo PREMAX FM288 Modem removed # Novalink NovaModem 144 card "NovaLink Tech." "NovaModem 144 " - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo NovaModem 144 Modem inserted remove echo NovaModem 144 Modem removed # US Robotics Sportster PCMCIA V.34 # US Robotics COURIER PCMCIA V.34 card "USRobotics" "PCMCIA 28800 Data/F" - config 0x3 "sio2" 3 + config 0x3 "sio2" ? insert echo USRobotics PCMCIA Modem inserted remove echo USRobotics PCMCIA Modem removed @@ -292,31 +292,31 @@ # Xircom CreditCard Ethernet+Modem (Modem only !!!) card "Xircom" "CreditCard Ethernet" - config 0x23 "sio2" 3 + config 0x23 "sio2" ? insert echo Xircom CreditCard Modem inserted remove echo Xircom CreditCard Modem removed # Xircom CreditCard Ethernet 10/100 + modem (modem only) card "Xircom" "CreditCard Ethernet 10/100 + " - config 0x1f "sio3" 10 + config 0x1f "sio3" ? insert echo Xircom CreditCard Modem inserted remove echo Xircom CreditCard Modem removed # Xircom GlobalACCESS modem card "Xircom" "CreditCard Modem 56 - GlobalA" - config 0x1f "sio2" 11 + config 0x1f "sio2" ? insert echo Xircom CreditCard Modem 56 - GlobalACCESS inserted remove echo Xircom CreditCard Modem 56 - GlobalACCESS removed # GATEWAY 2000 FAX/Data Modem (14.4K) card "GATEWAY2000" "CC3144" - config 0x22 "sio3" 7 + config 0x22 "sio3" ? insert echo GATEWAY2000 FAX/Data Modem inserted remove echo GATEWAY2000 FAX/Data Modem removed # IBM Push/Pop Modem (14.4K) card "IBM" "Push/Pop Modem(14.4" - config 0x22 "sio2" 5 + config 0x22 "sio2" ? insert echo IBM Push/Pop Modem inserted remove echo IBM Push/Pop Modem removed @@ -330,119 +330,119 @@ # NTT ThunderCard Modem card "NTT-IT CO., LTD" "ThunderCard AVF288, V.34" - config 0x22 "sio2" 10 + config 0x22 "sio2" ? insert echo NTT ThunderCard inserted remove echo NTT ThunderCard removed # U.S. Robotics XJ1560J card "U.S. Robotics" "XJ/CC1560J" - config 0x22 "sio2" 10 + config 0x22 "sio2" ? insert echo U.S. Robotics XJ1560J inserted remove echo U.S. Robotics XJ1560J removed # 3com/USR/Megahertz 3CCM556 card "3Com" "3CXM/3CCM556" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo 3Com PCMCIA 56K Modem inserted remove echo 3Com PCMCIA 56K Modem removed # 3Com/NoteWorthy 56K modem (bundled with Toshiba notebooks) card "Toshiba America" "3CXM056-BNW" - config 0x20 "sio1" 3 + config 0x20 "sio1" ? insert echo NoteWorthy 56K PCMCIA Modem inserted remove echo NoteWorthy 56K PCMCIA Modem removed # BUG Linkboy D64K (ISDN) card "BUG Inc." "Linkboy D64K" - config 0x23 "sio2" 3 + config 0x23 "sio2" ? insert echo BUG Linkboy D64K inserted remove echo BUG Linkboy D64K removed # NTT DoCoMo DATA/FAX Adapter card "NTT DoCoMo" "PCMCIA DATA/FAX ADA" - config 0x22 "sio3" 10 0x82 + config 0x22 "sio3" ? 0x82 insert echo NTT DoCoMo DATA/FAX Adapter inserted remove echo NTT DoCoMo DATA/FAX Adapter removed # Random modem bundled with Dell systems card "Psion Dacom" "Gold Card Global 56K+Fax" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo "Psion Dacom modem card inserted" remove echo "Psion Dacom modem card removed" # Actiontec Datalink with v.90 upgrade card "PCMCIA " "56K V.90 Fax Modem (LK) " - config 0x1f "sio2" 10 + config 0x1f "sio2" ? insert echo "Actiontec Datalink modem card inserted" remove echo "Actiontec Datalink modem card removed" # Panasonic FM-RADIO card #card "Panasonic" "CF-JVR101" -# config 0x22 "sio3" 16 +# config 0x22 "sio3" ? # insert echo Panasonic FM radio card inserted # remove echo Panasonic FM radio card removed # SunDisk Flash ATA # (OEM: Epson Flash Packer) #card "SunDisk" "SDP5" -# config 0x3 "wdc1" 7 +# config 0x3 "wdc1" ? # insert echo Sundisk Flash ATA inserted # remove echo Sundisk Flash ATA removed #card "SunDisk" "SDP" -# config 0x3 "wdc1" 7 +# config 0x3 "wdc1" ? # insert echo SunDisk Flash ATA Inserted # remove echo SunDisk Flash ATA Removed # Midori Elec Fast Flash #card "Midori Elec." "FAST FLASH" -# config 0x3 "wdc1" 9 +# config 0x3 "wdc1" ? # insert echo Midori Elec Fast FLASH inserted # remove echo Midori Elec Fast FLASH removed # Maxtor 131MB Type III HDD #card "Maxtor" "MXL131" -# config 0x03 "wdc1" 10 +# config 0x03 "wdc1" ? # insert echo Maxtor 131MB HDD inserted # remove echo Maxtor 131MB HDD removed # Adaptec SlimSCSI (also included with Sony CD-ROM players) card "Adaptec, Inc." "APA-1460 SCSI Host Adapter" - config 0x9 "aic0" 10 + config 0x9 "aic0" ? insert echo Adaptec Slim SCSI inserted remove echo Adaptec Slim SCSI removed # NewMedia Bustoaster SCSI card "New Media" "SCSI" - config 0x22 "aic0" 10 + config 0x22 "aic0" ? insert echo New Media Bus Toaster inserted remove echo New Media Bus Toaster removed # REX5535AC, REX5535X SCSI #card "PCMCIA SCSI MBH1040" "01" -# config 0x3a "spc0" 11 +# config 0x3a "spc0" ? # insert echo REX-5535 SCSI card inserted # remove echo REX-5535 SCSI card removed # Libretto Floppy disk card "Y-E DATA" "External FDD" - config 0x4 "fdc0" 10 + config 0x4 "fdc0" ? # Viking V.90/K56Flex modem card "Viking" "V.90 K56flex" - config 0x23 "sio3" 9 + config 0x23 "sio3" ? insert echo Viking 56K Modem inserted remove echo Viking 56K Modem removed # Zoom 56K modem card "Zoom Telephonics, Inc." "PCMCIA 56K LT DataFax" - config 0x1f "sio2" 10 + config 0x1f "sio2" ? insert echo Zoom modem inserted remove echo Zoom modem removed # 3Com Megahertz 3CCE589E* 10 Mbps LAN PC Card card "3Com" "Megahertz 589E" - config 0x1 "ep0" 10 + config 0x1 "ep0" ? insert echo 3Com Megahertz Ethernet card inserted insert /etc/pccard_ether ep0 remove echo 3Com Megahertz Ethernet card removed @@ -450,13 +450,13 @@ # 3Com/USR/MegaHertz 3CCM156 card "3COM" "3CCM156" - config 0x23 "sio2" 10 + config 0x23 "sio2" ? insert echo 3Com PCMCIA 56K modem inserted remove echo 3Com PCMCIA 56K modem removed #AR-P500 ethernet card card "IC-CARD" "IC-CARD" - config 0x20 "ed0" 15 + config 0x20 "ed0" ? insert echo AR-P500 Ethernet card inserted insert /etc/pccard_ether ed0 remove echo AR-P500 Ethernet card removed @@ -464,17 +464,17 @@ #Eiger 33.6 modem card "AT&T" "V34+ Fax Modem" - config 0x23 "sio1" 10 + config 0x23 "sio1" ? insert echo Eiger 33.6K modem inserted remove echo Eiger 33.6K modem removed # Motorola Montana card "Motorola" "MONTANA 33.6 FAX/MODEM" - config 0x21 "sio1" 10 + config 0x21 "sio1" ? # AmbiCom 10BaseT card card "AmbiCom Inc" "AMB8002T" - config 0x20 "ed0" 11 + config 0x20 "ed0" ? insert echo AmbiCom 8002T inserted insert /etc/pccard_ether ed0 remove echo AmbiCom 8002T removed -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 12: 1: 9 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.netacc.net (mail.netacc.net [206.28.142.35]) by hub.freebsd.org (Postfix) with SMTP id 6444E152CB for ; Tue, 4 May 1999 12:01:03 -0700 (PDT) (envelope-from kenney@netacc.net) Received: (qmail 508 invoked from network); 4 May 1999 15:01:02 -0400 Received: from dns2.netacc.net (kenney@206.28.142.3) by mail.netacc.net with SMTP; 4 May 1999 15:01:02 -0400 Received: from localhost (kenney@localhost) by dns2.netacc.net (8.8.8/8.8.8) with ESMTP id OAA08739; Tue, 4 May 1999 14:59:07 GMT (envelope-from kenney@netacc.net) X-Authentication-Warning: dns2.netacc.net: kenney owned process doing -bs Date: Tue, 4 May 1999 14:59:07 +0000 (GMT) From: Jeffrey Kenney Reply-To: kenney@netacc.net To: Mitsuru IWASAKI Cc: freebsd-mobile@freebsd.org Subject: Re: PAO3 is the cause of my modem problems (it works with PAO-971211+2.2.5R and Slackware Linux v3.6) In-Reply-To: <199905040833.RAA11421@tasogare.imasy.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks so much,that fixed the problem on the first try. On Tue, 4 May 1999, Mitsuru IWASAKI wrote: > Hello. My name is Iwasaki. > I noticed this problem on PAO3 few days before, and trying to fix it now. > It seems that the bugs in sioinit() and sioprobe() of > sys/i386/isa/sio.c (PAO3). > > sioinit(): In /etc/pccard.conf of PAO3, flags 0x40000 is specified by > digital communication cards entry. For normal modems this > flags is not given. However sioinit() always overrides > this flags to COM_C_NOPROBE (0x40000). (If COM_C_NOPROBE > bit is enabled, initialization procedue will be skipped > in sioprobe().) > > sioprobe(): Code for device with COM_C_NOPROBE flags is duplicated. > I suspect that first one must be deleted because the > initialization procedue starts after this block. > > The following patch works well for me. So far so good. > But I'm not sure this is correct solution because I don't have > any digital communication cards which specified 0x40000 flags in > /etc/pccard.conf, and don't understand clearly why COM_C_NOPROBE > bit can be set in sioinit(). > > Can anyone test this patch or review it? > > --- /usr/PAO3/src/sys/i386/isa/sio.c- Mon May 3 15:20:37 1999 > +++ /usr/PAO3/src/sys/i386/isa/sio.c Mon May 3 22:41:38 1999 > @@ -489,8 +489,16 @@ > if (com_addr(unit)) > return(EBUSY); > > +#if 0 > + /* > + * XXX This line overrides device flags specified > + * in /etc/pccard.conf on COM_C_NOPROBE (0x40000). > + * iwasaki@jp.FreeBSD.org > + */ > + > /* It's already probed as serial by Upper */ > devi->isahd.id_flags |= COM_C_NOPROBE; > +#endif > > /* > * Probe the device. If a value is returned, the > @@ -652,37 +660,6 @@ > > bzero(failures, sizeof failures); > iobase = dev->id_iobase; > - > - /* > - * It's a definitly Serial PCMCIA(16550A), but still be required > - * for IIR_TXRDY implementation ( Palido 321s, DC-1S... ) > - */ > - if ( COM_NOPROBE(dev) ) { > - /* Reading IIR register twice */ > - for ( fn = 0; fn < 2; fn ++ ) { > - DELAY(10000); > - failures[6] = inb(iobase + com_iir); > - } > - /* Check IIR_TXRDY clear ? */ > - result = IO_COMSIZE; > - if ( failures[6] & IIR_TXRDY ) { > - /* Nop, Double check with clearing IER */ > - outb(iobase + com_ier, 0); > - if ( inb(iobase + com_iir) & IIR_NOPEND ) { > - /* Ok. we're familia this gang */ > - dev->id_flags |= COM_C_IIR_TXRDYBUG; /* Set IIR_TXRDYBUG */ > - } else { > - /* Unknow, Just omit this chip.. XXX*/ > - result = 0; > - } > - } else { > - /* OK. this is well-known guys */ > - dev->id_flags &= ~COM_C_IIR_TXRDYBUG; /*Clear IIR_TXRDYBUG*/ > - } > - outb(iobase + com_cfcr, CFCR_8BITS); > - enable_intr(); > - return( result ); > - } > > /* > * We don't want to get actual interrupts, just masked ones. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 12:42:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 090BA15D31 for ; Tue, 4 May 1999 12:42:47 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA53832; Tue, 4 May 1999 20:42:14 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 4 May 1999 20:42:14 +0100 (BST) From: Doug Rabson To: HOSOKAWA Tatsumi Cc: mobile@freebsd.org Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: <199905041319.WAA03874@afs.ntc.mita.keio.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 May 1999, HOSOKAWA Tatsumi wrote: > Hi. > > I'm playing -current with Toshiba Libretto SS1000. This machine > sleeps correctly with plain 3.1-RELEASE w/o PAO, but it can't sleep > with -current (when I type zzz from console). I can suspend it with > power button, but it brings about time-warp. > > I've looked into apm driver in CVS repository, but I can't find any > major changes between HEAD and RELENG_3_1_0_RELEASE except newbus > import. But I can't believe that newbus import causes such problem. > Anyone experienced such trouble? There was a problem with suspend which new-bus introduced but a workaround was committed soon after. I have a proper fix which will be committed fairly soon. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 18: 1:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id BEC891507B for ; Tue, 4 May 1999 18:01:46 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id KAA10023; Wed, 5 May 1999 10:01:38 +0900 (JST) Date: Wed, 5 May 1999 10:01:38 +0900 (JST) Message-Id: <199905050101.KAA10023@afs.ntc.mita.keio.ac.jp> To: dfr@nlsystems.com Cc: mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: Your message of "Wed, 5 May 1999 04:42:14 JST". From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article dfr@nlsystems.com writes: >> On Tue, 4 May 1999, HOSOKAWA Tatsumi wrote: >> >> > Hi. >> > >> > I'm playing -current with Toshiba Libretto SS1000. This machine >> > sleeps correctly with plain 3.1-RELEASE w/o PAO, but it can't sleep >> > with -current (when I type zzz from console). I can suspend it with >> > power button, but it brings about time-warp. >> > >> > I've looked into apm driver in CVS repository, but I can't find any >> > major changes between HEAD and RELENG_3_1_0_RELEASE except newbus >> > import. But I can't believe that newbus import causes such problem. >> > Anyone experienced such trouble? >> >> There was a problem with suspend which new-bus introduced but a workaround >> was committed soon after. I have a proper fix which will be committed >> fairly soon. Thank you. But I make world'ed today's -current again, this problem does not take place. Hmm.... -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 19:18:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id C8F6315732 for ; Tue, 4 May 1999 19:18:19 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id VAA01294; Tue, 4 May 1999 21:18:37 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Tue, 4 May 1999 21:18:37 -0500 (CDT) From: Douglas Carmichael To: freebsd-mobile@freebsd.org Cc: iwasaki@jp.freebsd.org, hosokawa@jp.freebsd.org Subject: With the patch, I can see/use the modem, but it wedges after a while with PPP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The patch that was posted on freebsd-mobile (against PAO3-beta-19990329) lets my laptop see the modem and use it. However, after a few minutes of modem activity, the PPP connection hangs, requiring me to either quit PPP or close PPP to reestablish it. After quitting/closing PPP, I do not need to reboot to see the modem again (I can do a term from the PPP session with success). Here's a sample of some of the ping times (this is with light Netscape+ NNTP activity): PING typhoon.xnet.com (198.147.221.70): 56 data bytes 64 bytes from 198.147.221.70: icmp_seq=0 ttl=253 time=169.550 ms 64 bytes from 198.147.221.70: icmp_seq=1 ttl=253 time=160.097 ms 64 bytes from 198.147.221.70: icmp_seq=2 ttl=253 time=150.263 ms 64 bytes from 198.147.221.70: icmp_seq=3 ttl=253 time=140.113 ms 64 bytes from 198.147.221.70: icmp_seq=4 ttl=253 time=140.116 ms 64 bytes from 198.147.221.70: icmp_seq=5 ttl=253 time=140.109 ms 64 bytes from 198.147.221.70: icmp_seq=6 ttl=253 time=130.137 ms 64 bytes from 198.147.221.70: icmp_seq=7 ttl=253 time=140.120 ms 64 bytes from 198.147.221.70: icmp_seq=8 ttl=253 time=260.181 ms 64 bytes from 198.147.221.70: icmp_seq=9 ttl=253 time=480.738 ms 64 bytes from 198.147.221.70: icmp_seq=10 ttl=253 time=234.024 ms 64 bytes from 198.147.221.70: icmp_seq=14 ttl=253 time=789.728 ms 64 bytes from 198.147.221.70: icmp_seq=15 ttl=253 time=620.209 ms 64 bytes from 198.147.221.70: icmp_seq=16 ttl=253 time=1400.156 ms 64 bytes from 198.147.221.70: icmp_seq=17 ttl=253 time=6260.257 ms 64 bytes from 198.147.221.70: icmp_seq=18 ttl=253 time=5280.222 ms 64 bytes from 198.147.221.70: icmp_seq=19 ttl=253 time=5900.146 ms 64 bytes from 198.147.221.70: icmp_seq=20 ttl=253 time=4900.181 ms 64 bytes from 198.147.221.70: icmp_seq=21 ttl=253 time=3920.428 ms 64 bytes from 198.147.221.70: icmp_seq=22 ttl=253 time=2950.206 ms 64 bytes from 198.147.221.70: icmp_seq=23 ttl=253 time=1940.375 ms 64 bytes from 198.147.221.70: icmp_seq=24 ttl=253 time=1102.698 ms When icmp_seq gets to about 194, it wedges. However, when I configure pccard.conf to use pio instead of IRQ 3, the wedging doesn't occur. But, it is significantly slower. BTW, Here's the output of dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Tue May 4 06:55:20 CDT 1999 root@myname.my.domain:/usr/src/sys/compile/DCARMICH-TEST Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (233.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff> real memory = 100663296 (98304K bytes) avail memory = 95424512 (93188K bytes) Preloaded elf kernel "kernel" at 0xf0243000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 vga0: rev 0xdc int a irq 10 on pci0.2.0 pcic0: rev 0x02 int a irq 255 on pci0.3.0 RL5C4XX PCI Config Reg: pcic1: rev 0x02 int b irq 255 on pci0.3.1 RL5C4XX PCI Config Reg: chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x02 on pci0.7.3 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 pcic0 at 0x3e0-0x3e1 irq 11 on isa PC-Card ctlr(0) Ricoh RL5C478 [CardBus bridge mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 changing root device to wd0s1a Card inserted, slot 0 sio3: type 16550A pid 239 (Xaccel): trap 12 with interrupts disabled acd0: read_toc failed acd0: read_toc failed sio3: unload,gone Return IRQ=3 Card removed, slot 0 ******* Tried different interrupts (didn't work, couldn't be an IRQ conflict) ****** Card inserted, slot 0 sio3: configured irq 10 not in bitmap of probed irqs 0 sio3: type 16550A sio3: unload,gone Return IRQ=10 Card removed, slot 0 Card inserted, slot 0 crd: slot_ctrl IRQ mask mismatched.Card removed, slot 0 Card inserted, slot 0 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3: type 16550A sio3: unload,gone Return IRQ=9 Card removed, slot 0 ******************************* Tried pio here (didn't wedge) ********* Card inserted, slot 0 sio3: type 16550A sio3: unload,gone Card removed, slot 0 ************************************************************************ ** Back to IRQ 3 (which *DOES* work) ** Card inserted, slot 0 Slot 0, unfielded interrupt (0) sio3: type 16550A sio3: unload,gone Return IRQ=3 Card removed, slot 0 Card inserted, slot 0 Slot 0, unfielded interrupt (0) sio3: type 16550A *********************************************************** Here's my kernel configuration: # # Sample Laptop Configuration # for lenlen.ntc.keio.ac.jp (Toshiba Libretto 50CT) # Tatsumi Hosokawa # machine "i386" cpu "I686_CPU" ident DCARMICH-TEST maxusers 48 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console # If your laptop have not had Windoze95-Ready BIOS, please update it. # Such old BIOS'es sometimes have critical bugs at 32-bit protected # mode APM BIOS interface (which have not used by Windoze 3.1). # PC-card suspend/resume support (experimental) #options APM_PCCARD_RESUME options PCIC_RESUME_RESET # Keep power for serial cards when the system suspends # (If your machine hangs up when you try to suspend the system with # FAX/Modem PCMCIA card, uncomment this option). #options SIO_SUSP_KEEP_PWR # Detach SCSI devices when the SCSI card is removed #options SCSI_DETACH # Detach ATAPI devices when the ATA card is removed options ATAPI_DETACH # Japanese version of WaveLAN PCMCIA uses 2.4GHz band instead of 915MHz # band that US version uses. If you want to use Japanese version of # WaveLAN, uncomment this line, or edit the corresponding config entry # of /etc/pccard.conf. #options "WAVELAN_PCMCIA_24" # Suspend the system when the battery status is "Low" #options "APM_BATT_LOW_SUSPEND" # If you want to use NTP on laptop machines, uncomment the following # option. Current APM implementation affects NTP client. #options "APM_NO_CLOCK_ADJUST" # Some X-servers cannot survive suspend/resume on laptop. # This option kicks her when the system is resumed from suspended mode. #options SYSCONS_VTY_RESUME config kernel root on wd0 controller isa0 controller pci0 # Dont remove these two lines! pseudo-device card 1 # You must use "flags 0x1" when you don't hear any negotiation noise(?) # if you use modem card, or pccardd doesn't read cis tuple, tell you # 'No card in database for"(null)"("(null)")' in case of Cirrus Logic's # pcic is your PC. #device pcic0 at isa? port 0x3e0 flags 0x1 irq 11 device pcic0 at isa? port 0x3e0 irq 11 #device pcic0 at isa? port 0x3e4 irq 11 #device pcic1 at isa? port 0x3e2 # for HiNote Ultra II #device pcic1 at isa? port 0x3e4 # for Chandra II controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM device wfd0 #IDE floppy (LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? disable port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 device sio4 at isa? disable port "IO_COM3" tty irq 5 #device mse0 at isa? port 0x23c tty irq 5 # Parallel port device ppc0 at isa? port? net irq 7 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ax0 #device de0 #device fxp0 #device mx0 #device pn0 #device rl0 #device tl0 #device tx0 #device vr0 #device vx0 #device wb0 #device xl0 pseudo-device loop # DHCP uses BPF (Berkeley Packet Filter) pseudo-device bpfilter 4 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 5 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG # USB support #controller uhci0 #controller ohci0 #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device uhub0 #device ucom0 #device umodem0 #device hid0 #device ugen0 # #options USB_DEBUG #options USBVERBOSE Judging from the fact that pio does work, it seems to me like it is a problem with the interrupt handling code. What could the problem be? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 19:23:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 027DC15763 for ; Tue, 4 May 1999 19:23:28 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id VAA01322; Tue, 4 May 1999 21:23:46 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Tue, 4 May 1999 21:23:46 -0500 (CDT) From: Douglas Carmichael To: freebsd-mobile@freebsd.org Cc: hosokawa@jp.freebsd.org, iwasaki@jp.freebsd.org Subject: Here's the pccard.conf entry I used for my modem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org # PC-card sample configuration file # Tatsumi Hosokawa # # Removing all IRQ conflicts from this file can't be done because of some # IRQ-selfish PC-cards. So if you want to use some of these cards in # your machine, you will be forced to modify their IRQ parameters from # the following list. # # $Id: pccard.conf.sample,v 1.1.1.1.2.10.2.6.2.21.2.18 1999/03/17 14:29:45 toshi Exp $ # Generally available IO ports io 0x240-0x3ff # Generally available IRQs (DEPRECATED, USE OF THE OPTION IS DISCOURAGED) #irq 10 11 # Unavailable IRQs #ignirq 9 # refrain from using SoundBlaster's IRQ, by default. ignirq 5 # it may be helful for most of notebook PCs #ignirq 15 # Available memory slots memory 0xd4000 96k # ------------------------------------------------------------------- # # "Wildcard" entries # # ------------------------------------------------------------------- # GENERIC PCMCIA modem function serial config auto "sio3" any # config 0x23 "sio3" any # alternative definitions # config 0x21 "sio3" any # ......... # config 0x22 "sio3" any # config 0x23 "sio3" pio # config 0x21 "sio3" pio # config 0x22 "sio3" pio # config 0x23 "sio3" 5 # config 0x21 "sio3" 5 # config 0x22 "sio3" 5 # reset 100 # default reset 1000 # safety reset time # reset 10000 # for unstable cards insert logger -s PCMCIA Modem inserted remove logger -s PCMCIA Modem removed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 4 21:25:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 2812C14C07 for ; Tue, 4 May 1999 21:25:28 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id VAA50490; Tue, 4 May 1999 21:25:11 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372FC831.79451797@MexComUSA.net> Date: Tue, 04 May 1999 21:25:21 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: HOSOKAWA Tatsumi Cc: dfr@nlsystems.com, mobile@FreeBSD.ORG Subject: Re: Suspend and time warp problem of -current apm driver References: <199905050101.KAA10023@afs.ntc.mita.keio.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HOSOKAWA Tatsumi wrote: > In article > dfr@nlsystems.com writes: > > >> On Tue, 4 May 1999, HOSOKAWA Tatsumi wrote: > >> > >> > Hi. > >> > > >> > I'm playing -current with Toshiba Libretto SS1000. This machine > >> > sleeps correctly with plain 3.1-RELEASE w/o PAO, but it can't sleep > >> > with -current (when I type zzz from console). I can suspend it with > >> > power button, but it brings about time-warp. > >> > > >> > I've looked into apm driver in CVS repository, but I can't find any > >> > major changes between HEAD and RELENG_3_1_0_RELEASE except newbus > >> > import. But I can't believe that newbus import causes such problem. > >> > Anyone experienced such trouble? > >> > >> There was a problem with suspend which new-bus introduced but a workaround > >> was committed soon after. I have a proper fix which will be committed > >> fairly soon. > > Thank you. > But I make world'ed today's -current again, > this problem does not take place. > Hmm.... Do you have a pcmcia modem and network card? Do they work with current and newbus? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 0: 5:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id B1C6114C24 for ; Wed, 5 May 1999 00:05:53 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (ppp0.imasy.or.jp [202.227.24.10]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare) with ESMTP id QAA21803; Wed, 5 May 1999 16:05:35 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199905050705.QAA21803@tasogare.imasy.or.jp> To: dcarmich@xnet.com Cc: freebsd-mobile@freebsd.org, iwasaki@jp.freebsd.org, hosokawa@jp.freebsd.org Subject: Re: With the patch, I can see/use the modem, but it wedges after a while with PPP In-Reply-To: Your message of "Tue, 4 May 1999 21:18:37 -0500 (CDT)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 05 May 1999 16:04:34 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 21 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > The patch that was posted on freebsd-mobile > (against PAO3-beta-19990329) lets my laptop see the modem and > use it. However, after a few minutes of modem activity, the PPP connection > hangs, requiring me to either quit PPP or close PPP to reestablish it. Hmmm, it sounds like a IRQ conflict problem... Could you check your hardware setting (BIOS Setup) whether COM2 is disabled? If COM2 is enabled and uses IRQ 3, allocating IRQ 3 for your modem card may cause such a problem. My suggestions: - To disable COM2 by BIOS Setup menu to avoid IRQ 3 conflict. - To make other free IRQ and allocate it for your modem card. something like: To disable Parallel port port by BIOS Setup menu and disable ppc0 related device entry in your kernel config file if you do need to use it. Then allocate IRQ 7 for your modem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 1: 5:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 56ED11559E for ; Wed, 5 May 1999 01:05:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA13139; Wed, 5 May 1999 02:05:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA08865; Wed, 5 May 1999 02:05:13 -0600 (MDT) Message-Id: <199905050805.CAA08865@harmony.village.org> To: new-bus-arch@bostonradio.org Cc: mobile@freebsd.org Subject: Pccard rewrite, patch #1 Date: Wed, 05 May 1999 02:05:11 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've uploaded my current set of patches to the pccard stuff to http://www.freebsd.org/~imp/pccard-990505.diff.gz These patches are still green. They seem stable on my laptop, but I still sometimes see odd messages indicating problems when I have INVARIANTS enabled. Do not use these patches if you need a stable machines. They may even trash your data. They are for testing purposes only, and only be skilled testers that really know how to test and debug kernel problems, as there will be plenty of them in these patches. DO NOT USE THESE PATCHES IN A PRODUCTION ENVIRONMENT. DO NOT USE THESE PATCHES IF YOU WANT A STABLE LAPTOP. THEY ARE GREEN, EXPERIMENTAL AND MAY CAUSE DATA LOSS, ULCERS, BODY ODER, DATA CORRUPTION OR HAIR LOSS. These contain the new bus conversion of the old pccard code. I've rewritten much of the code here, since most of it used interfaces that were depricated with the conversion to newbus. I've also cleaned up the resource allocation mechanisms so that they use the rman/new bus stuff rather than the various kludges that had been used. I'm still getting some of the parameters from pccardd. pccardd is still required in this version, and will be for what I've been calling the "new-old" pccard code. I've moved the pccard files from pccard/ to dev/pccard. pcic.c will likely be moved to isa/pcic.c in the future, and pcic_p.c will go away to be replaced by pci/cbb.c. I've also changed the kernel config file. See patches to GENERIC for details. Problems that I'm aware of are that care removal might not work right, reinsertion runs up against the name already in use problem. Also, you may want to hard wire the irq your pccard is using in your kernel config file. I've started adding support to the ata for ata-flash, but that might not work in this version (4MB ata flash card for this work courtesy of Nate Williams). I've not touched sio or fdc yet. They are also being made available for anybody who wishes to review and comment on these changes. Given the lack of docs on newbus, I've tried to follow the examples of pci, isa, et al for writing a bus, but I'm not sure that I understand all the nuances that are needed for newbus. Comments to me or the list. I'll likely be releasing snapshots like this for interested parties every few days depending on how much time I find to spend on pushing forward. Bug fixes also welcome :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 1:19: 5 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DD5D915894 for ; Wed, 5 May 1999 01:19:02 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA25208; Wed, 5 May 1999 10:18:50 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905050818.KAA25208@freebsd.dk> Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905050805.CAA08865@harmony.village.org> from Warner Losh at "May 5, 1999 2: 5:11 am" To: imp@harmony.village.org (Warner Losh) Date: Wed, 5 May 1999 10:18:50 +0200 (CEST) Cc: new-bus-arch@bostonradio.org, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > > I've uploaded my current set of patches to the pccard stuff to > http://www.freebsd.org/~imp/pccard-990505.diff.gz > > These patches are still green. They seem stable on my laptop, but I > still sometimes see odd messages indicating problems when I have > INVARIANTS enabled. Do not use these patches if you need a stable > machines. They may even trash your data. They are for testing > purposes only, and only be skilled testers that really know how to > test and debug kernel problems, as there will be plenty of them in > these patches. At least they break Promise support, but that is probably not interesting for laptop owners. Warner, I have some other changes to ata-all.c etc, I'll try to integrate your changes into that... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 1:25:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6859C158BF for ; Wed, 5 May 1999 01:25:17 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA00499; Wed, 5 May 1999 09:24:57 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 5 May 1999 09:24:57 +0100 (BST) From: Doug Rabson To: HOSOKAWA Tatsumi Cc: mobile@freebsd.org Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: <199905050101.KAA10023@afs.ntc.mita.keio.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 May 1999, HOSOKAWA Tatsumi wrote: > In article > dfr@nlsystems.com writes: > > >> On Tue, 4 May 1999, HOSOKAWA Tatsumi wrote: > >> > >> > Hi. > >> > > >> > I'm playing -current with Toshiba Libretto SS1000. This machine > >> > sleeps correctly with plain 3.1-RELEASE w/o PAO, but it can't sleep > >> > with -current (when I type zzz from console). I can suspend it with > >> > power button, but it brings about time-warp. > >> > > >> > I've looked into apm driver in CVS repository, but I can't find any > >> > major changes between HEAD and RELENG_3_1_0_RELEASE except newbus > >> > import. But I can't believe that newbus import causes such problem. > >> > Anyone experienced such trouble? > >> > >> There was a problem with suspend which new-bus introduced but a workaround > >> was committed soon after. I have a proper fix which will be committed > >> fairly soon. > > Thank you. > But I make world'ed today's -current again, > this problem does not take place. > Hmm.... Do you mean that suspend works now? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 2:24: 3 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 664D714C06 for ; Wed, 5 May 1999 02:24:00 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id SAA13925; Wed, 5 May 1999 18:23:55 +0900 (JST) Date: Wed, 5 May 1999 18:23:55 +0900 (JST) Message-Id: <199905050923.SAA13925@afs.ntc.mita.keio.ac.jp> To: dfr@nlsystems.com Cc: mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: Your message of "Wed, 5 May 1999 17:24:57 JST". From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article dfr@nlsystems.com writes: >> Do you mean that suspend works now? Yes, it works perfectly. But I don't know why. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 2:30:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4B76F14D85 for ; Wed, 5 May 1999 02:30:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA00684; Wed, 5 May 1999 10:29:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 5 May 1999 10:29:29 +0100 (BST) From: Doug Rabson To: HOSOKAWA Tatsumi Cc: mobile@freebsd.org Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: <199905050923.SAA13925@afs.ntc.mita.keio.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 May 1999, HOSOKAWA Tatsumi wrote: > In article > dfr@nlsystems.com writes: > > >> Do you mean that suspend works now? > > Yes, it works perfectly. But I don't know why. The original bug was that DEVICE_SUSPEND(root_bus) was returning ENXIO (since many drivers don't support the method) and the workaround was to ignore ENXIO errors. You are sure the non-working kernel wasn't from before this fix was made? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 2:40:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id EAF9415098 for ; Wed, 5 May 1999 02:40:14 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id SAA14164; Wed, 5 May 1999 18:40:06 +0900 (JST) Date: Wed, 5 May 1999 18:40:06 +0900 (JST) Message-Id: <199905050940.SAA14164@afs.ntc.mita.keio.ac.jp> To: dfr@nlsystems.com Cc: mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Suspend and time warp problem of -current apm driver In-Reply-To: Your message of "Wed, 5 May 1999 18:29:29 JST". From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article dfr@nlsystems.com writes: >> The original bug was that DEVICE_SUSPEND(root_bus) was returning ENXIO >> (since many drivers don't support the method) and the workaround was to >> ignore ENXIO errors. >> >> You are sure the non-working kernel wasn't from before this fix was made? Maybe. Working kernel displays "DEVICE_SUSPEND..." message after it wakes up, and non-working kernel does not. Thank you very much. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 5: 3:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mordor.xti.org (mordor.xti.org [193.212.232.254]) by hub.freebsd.org (Postfix) with SMTP id EB0C714CCD for ; Wed, 5 May 1999 05:03:50 -0700 (PDT) (envelope-from delta@xti.org) Received: (qmail 46399 invoked from network); 5 May 1999 12:03:49 -0000 Received: from mordor.xti.org (193.212.232.254) by login.xti.org with SMTP; 5 May 1999 12:03:49 -0000 Date: Wed, 5 May 1999 14:03:49 +0200 (CEST) From: Terje Elde To: freebsd-mobile@freebsd.org Subject: Which laptop?? (Compaq Armada 6500?) Message-ID: KEY-ID: 0x5B439BB3 Stuff: Why are you reading all the headers?? Do you think I hide lots of stuff up here?? Question: Do you know where *your* towel is? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I need a laptop I can use with FreeBSD. I kinda like a Compaq Armada 6500, with internal 10/100 network card, 56k modem and so on, but I'd like some comments from you all, both on this laptop, and in general about selecting a laptop for FreeBSD use. Also, I'd be happy to hear about any other laptops recommended. Thanks... Friendly greetings, Terje Elde "One world, one web, one program" - Microsoft Promo ad. "Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 5:46:17 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id A565A14CCD for ; Wed, 5 May 1999 05:46:08 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp516.kt.rim.or.jp [202.247.140.166]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id VAA08140 for ; Wed, 5 May 1999 21:46:06 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id VAA01985 for ; Wed, 5 May 1999 21:46:04 +0900 (JST) Message-ID: <37303D5B.39BFA86E@sky.rim.or.jp> Date: Wed, 05 May 1999 21:45:15 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD Mobile Subject: Memory Stick Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org $B!!(BSONY VAIO PCG-Z505D $B$KFbB"$N(B Memory Stick $B%9%m%C%H$O$3$s$J46$8$K8+$($^(B $B$9!#(B16MB $B$N%a%G%#%"$r;X$79~$s$@>uBV!#(B > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd1): > wd1: 15MB (31680 sectors), 495 cyls, 4 heads, 16 S/T, 512 B/S $B!!$3$l$r(B # mount -t msdos /dev/wd1s1 /mnt $B$H$+$9$k$H%^%&%s%H$G$-$^$9!#%a%G%#%">e$K%i%$%H%W%m%F%/%HMQ$N%9%$%C%A$,$"(B $B$k$s$G$9$,!"$3$l$r=q9~$_6X;_$K$7$F$b0UL#L5$$$_$?$$!#$^$s$^=q$-9~$a$k!#(B $B!!0l2s%i%$%H%W%m%F%/%H$K$7$F=q$-9~$b$&$H$7$?$i(B I/O failure ($B:F8=$G$-$J$$(B $B$N$G$&$m3P$((B)$B$@$+$,=P$F!"$=$l$r(B umount $B$7$h$&$H$7$?$i(B OS $B$4$H8G$^$C$F$7(B $B$^$C$?;v$,$"$j$^$7$?!#(B $B!!$b$R$H$D!"(BMemory Stick $B$N(B PC Card Adaptor $B$G$"$k(B SONY $B$N(B MSAC-PC1 $B$H$$(B $B$&$d$D!#$3$l$N(B dumpcis $B$O(B > leda: {101} pccardc dumpcis > Configuration data for card in slot 0 > Tuple #1, code = 0x1 (Common memory descriptor), length = 4 > 000: df 4a 01 ff > Common memory device information: > Device number 1, type Function specific, WPS = ON > Speed = 4.0 x 100 ns, Memory block size = reserved, 32 units > Device number 2, type No device, WPS = OFF > Speed = No speed, Memory block size = 512b, 1 units > Tuple #2, code = 0x1c (Other conditions for common memory), length = 4 > 000: 02 d9 01 ff > (3V card) > Tuple #3, code = 0x18 (JEDEC descr for common memory), length = 2 > 000: df 01 > Tuple #4, code = 0x20 (Manufacturer ID), length = 4 > 000: f1 00 00 00 > PCMCIA ID = 0xf1, OEM ID = 0x0 > Tuple #5, code = 0x15 (Version 1 info), length = 30 > 000: 04 01 53 4f 4e 59 00 4d 45 4d 4f 52 59 53 54 49 > 010: 43 4b 28 20 31 36 4d 29 00 31 2e 30 00 ff > Version = 4.1, Manuf = [SONY], card vers = [MEMORYSTICK( 16M)] > Addit. info = [1.0] > Tuple #6, code = 0x21 > Tuple #6, code = 0x21 (Functional ID), length = 2 > 000: 04 01 > Fixed disk card - POST initialize > Tuple #7, code = 0x22 (Functional EXT), length = 2 > 000: 01 01 > Disk interface: IDE > Tuple #8, code = 0x22 (Functional EXT), length = 3 > 000: 02 0c 0f > Disk features: Silicon, Unique, Single > Sleep, Standby, Idle, Low power, > Tuple #9, code = 0x1a (Configuration map), length = 5 > 000: 01 03 00 02 0f > Reg len = 2, config register addr = 0x200, last config = 0x3 > Registers: XXXX---- > Tuple #10, code = 0x1b (Configuration entry), length = 8 > 000: c0 c0 a1 01 55 08 00 20 > Config index = 0x0(default) > Interface byte = 0xc0 (memory) +RDY/-BSY active, wait signal supported > Vcc pwr: > Nominal operating supply voltage: 5 x 1V > Memory space length = 0x8 > Max twin cards = 0 > Misc attr: (Power down supported) > Tuple #11, code = 0x1b (Configuration entry), length = 6 > 000: 00 01 21 b5 1e 0e > Config index = 0x0 > Vcc pwr: > Nominal operating supply voltage: 3 x 1V, ext = 0x1e > Max current average 0x1e > Max current averagee over 10 ms: 1.2 x 100mA > Tuple #12, code = 0x1b (Configuration entry), length = 10 > 000: c1 41 99 01 55 64 f0 ff ff 20 > Config index = 0x1(default) > Interface byte = 0x41 (I/O) +RDY/-BSY active > Vcc pwr: > Nominal operating supply voltage: 5 x 1V > Card decodes 4 address lines, full 8/16 Bit I/O > IRQ modes: Level, Pulse, Shared > IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 > Max twin cards = 0 > Misc attr: (Power down supported) > Tuple #13, code = 0x1b (Configuration entry), length = 6 > 000: 01 01 21 b5 1e 4d > Config index = 0x1 > Vcc pwr: > Nominal operating supply voltage: 3 x 1V, ext = 0x1e > Max current average over 10 ms: 4.5 x 10mA > Tuple #14, code = 0x1b (Configuration entry), length = 15 > 000: c2 41 99 01 55 ea 61 f0 01 07 f6 03 01 ee 20 > Config index = 0x2(default) > Interface byte = 0x41 (I/O) +RDY/-BSY active > Vcc pwr: > Nominal operating supply voltage: 5 x 1V > Card decodes 10 address lines, full 8/16 Bit I/O > I/O address # 1: block start = 0x1f0 block length = 0 = 0x1f0 bl > ock length = 0x8 > I/O address # 2: block start = 0x3f6 block length = 0x2 > IRQ modes: Level, Pulse, Shared > IRQ level = 14 > Max twin cards = 0 > Misc attr: (Power down supported) > Tuple #15, code = 0x1b (Configuration entry), length = 6 > 000: 02 01 21 b5 1e 4d > Config index = 0x2 > Vcc pwr: > Nominal operating supply voltage: 3 x 1V, ext = 0x1e > Max current average over 10 ms: 4.5 x 10mA > Tuple #16, code = 0x1b (Configuration entry), length = 15 > 000: c3 41 99 01 55 ea 61 70 01 07 76 03 01 ee 20 > Config index = 0x3(default) > Interface byte = 0x41 (I/O) +RDY/-BSY active > Vcc pwr: > Nominal operating supply voltage: 5 x 1V > Card decodes 10 address lines, full 8/16 Bit I/O > I/O address # 1: block start = 0x170 block length = 0x8 > I/O address # 2: block start = 0x376 block length = 0x2 > IRQ modes: Level, Pulse, Shared > IRQ level = 14 > Max twin cards = 0 > Misc attr: (Power down supported) > Tuple #17, code = 0x1b (Configuration entry), length = 6 > 000: 03 01 21 b5 1e 4d > Config index = b5 1e 4d > Config index = 0x3 > Vcc pwr: > Nominal operating supply voltage: 3 x 1V, ext = 0x1e > Max current average over 10 ms: 4.5 x 10mA > Tuple #18, code = 0x14 (No link), length = 0 > Tuple #19, code = 0xff (Terminator), length = 0 > 1 slots found $B$H$$$&46$8!#(B/etc/pccard.conf $B$K(B > io 0x240-0x2e0 0x300-0x360 > memoryy 0xd4000 96k > > card "SONY" "MEMORYSTICK\( 16M\)" > config 0x3 "wdc1" 7 > insert echo SONY Memory Stick inserted > remove echo SONY Memory Stick removed $B$H$7$F$_$?$N$G$9$,!"(BResource allocation failure $B$N(B Reason I/O block allocation failed $B$C$F1>$o$l$F$&$^$/$$$-$^$;$s$G$7$?!#$=$l0JA0$K(B Flash ATA $B$H$+;H$C$?;vL5$$$N$G8+Ev30$l$N$3$H$r$7$F$$$k$h$&$J5$$,$9$k$1$I!#(B $B!!(Bwdc1 $B$N(B wd1 $B$,(B Memory Stick $B$N%9%m%C%H$G$9$G$K;H$o$l$A$c$C$F$k$N$,$$$+(B $B$s$N$+$J!#(B -- $B$/$j$d$^(B // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 7: 5:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id 05547152B0 for ; Wed, 5 May 1999 07:05:28 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp536.kt.rim.or.jp [202.247.140.186]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id XAA21651 for ; Wed, 5 May 1999 23:05:27 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id XAA05333 for ; Wed, 5 May 1999 23:05:25 +0900 (JST) Message-ID: <37304FF5.FAB6C337@sky.rim.or.jp> Date: Wed, 05 May 1999 23:04:37 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD Mobile Subject: Re: Memory Stick References: <37303D5B.39BFA86E@sky.rim.or.jp> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry, I misposted report for memory stick. That mail was represented in Japanese language. In short, content of this report is: o for SONY VAIO PCG-Z505D with PAO 3.1 o which has a Memory Stick slot above PCCARD slot o its slot is recognized as wd1 on wdc1 o Memory Stick media is recognized as remobable IDE drive (like as Flash ATA PCCARD?) o mountable as msdos filesystem Jun Kuriyama wrote: > > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (wd1): > > wd1: 15MB (31680 sectors), 495 cyls, 4 heads, 16 S/T, 512 B/S > ... > > # mount -t msdos /dev/wd1s1 /mnt ... -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 7: 7:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from www.in-design.com (www.in-design.com [206.210.93.16]) by hub.freebsd.org (Postfix) with ESMTP id 9031715844 for ; Wed, 5 May 1999 07:07:16 -0700 (PDT) (envelope-from archive@in-design.com) Received: from [136.142.22.203] (ehdup-s2-13.rmt.net.pitt.edu [136.142.22.203]) by www.in-design.com (8.9.2/8.9.2) with ESMTP id KAA11135 for ; Wed, 5 May 1999 10:07:15 -0400 (EDT) X-Sender: archive@mail.in-design.com Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 5 May 1999 09:41:35 -0400 To: freebsd-mobile@FreeBSD.ORG From: Intuitive Design Archives Subject: Best Laptop for FreeBSD Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all; I am thinking of buying a new laptop, and will install FreeBSD on it. I was wondering which laptops work well with FreeBSD and has almost all support. Thanks for your help Tamer Ziady Intuitive Design Archive archive@in-design.com http://www.in-design.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 8:21:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 31E5D15332 for ; Wed, 5 May 1999 08:21:10 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA09786; Wed, 5 May 1999 09:21:09 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA16609; Wed, 5 May 1999 09:21:09 -0600 Date: Wed, 5 May 1999 09:21:09 -0600 Message-Id: <199905051521.JAA16609@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Intuitive Design Archives Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Best Laptop for FreeBSD In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am thinking of buying a new laptop, and will install FreeBSD on > it. I was wondering which laptops work well with FreeBSD and has almost > all support. I've had *really* good luck with IBM's. My new 366Mhz ThinkPad 600E works great, although I haven't (yet) tried to get sound working, I don't expect to have any problems. It required one minor change to the kernel to recognize my PCCARD/CardBus controller, but that will be part of FreeBSD 3.2 soon to be released. I recommend IBM's whole-heartedly. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 8:30:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 8721B1592D for ; Wed, 5 May 1999 08:30:11 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id AAA16840; Thu, 6 May 1999 00:29:26 +0900 (JST) Date: Thu, 6 May 1999 00:29:26 +0900 (JST) Message-Id: <199905051529.AAA16840@afs.ntc.mita.keio.ac.jp> To: imp@harmony.village.org Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Pccard rewrite, patch #1 In-Reply-To: Your message of "Wed, 5 May 1999 17:05:11 JST". <199905050805.CAA08865@harmony.village.org> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199905050805.CAA08865@harmony.village.org> imp@harmony.village.org writes: >> I've uploaded my current set of patches to the pccard stuff to >> http://www.freebsd.org/~imp/pccard-990505.diff.gz >> >> These patches are still green. They seem stable on my laptop, but I >> still sometimes see odd messages indicating problems when I have >> INVARIANTS enabled. Do not use these patches if you need a stable >> machines. They may even trash your data. They are for testing >> purposes only, and only be skilled testers that really know how to >> test and debug kernel problems, as there will be plenty of them in >> these patches. I tested it now, but I can't compile GENERIC at first. I did s/#include "card.h"/#include "pccard.h"/, and s/NCARD/NPCCARD/, GENERIC was compiled without errors. Did I something wrong? I boot the new kernel on my Toshiba Libretto SS1000. But no PC-card slots were probed (today's current finds PC-card slots, but insertion and removal does not cause interrupt). Dmesg says that.... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed May 5 23:29:55 JST 1999 root@myname.my.domain:/usr/src/sys/compile/HOSOKAWA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (quarter-micron) (166.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x581 Stepping=1 Features=0x8001bf real memory = 33685504 (32896K bytes) avail memory = 29356032 (28668K bytes) Preloaded elf kernel "kernel" at 0xc0377000. Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 eisa0: on motherboard isa0: on motherboard fdc0: interrupting at irq 6 fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! bt_isa_probe: Probe failed for card at 0x330 bt_isa_probe: Probe failed for card at 0x334 bt_isa_probe: Probe failed for card at 0x230 bt_isa_probe: Probe failed for card at 0x234 bt_isa_probe: Probe failed for card at 0x130 bt_isa_probe: Probe failed for card at 0x134 haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1: configured irq 3 not in bitmap of probed irqs 0 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 ie0: unknown board_id: f000 Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s2a -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 8:42:41 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (Postfix) with ESMTP id 2BDC81599E for ; Wed, 5 May 1999 08:42:35 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.3/8.9.3) with ESMTP id IAA05519; Wed, 5 May 1999 08:42:30 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Date: Wed, 5 May 1999 08:42:29 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Intuitive Design Archives Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Best Laptop for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 May 1999, Intuitive Design Archives wrote: > Hello all; > > I am thinking of buying a new laptop, and will install FreeBSD on > it. I was wondering which laptops work well with FreeBSD and has almost > all support. I have a Toshiba Libretto 110CT. While it was pricy, I found it was the best choice for me because it's so small and light that I can just slip it into my backpack and take it anywhere. With 2.2.8-PAO (I've not tried any other versions), everything works fine (hibernation mode, XFree86, sound, the integrated pointing device, etc.), with the exception of the IrDA port, which FreeBSD does not currently support. I use a LinkSys PCMCIA ethernet card with it, and a cheap generic PCMCIA v.34 modem, both of which PAO supports without complaint. PAO also supports the Libretto's PCMCIA floppy drive, and I believe -CURRENT and PAO3 do as well (Not sure about straight -STABLE). My only complaint is that FreeBSD stickers don't adhere well to the cover. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 8:59:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from tardis.perspectives.net (unknown [63.66.225.69]) by hub.freebsd.org (Postfix) with ESMTP id 5752F14F4C for ; Wed, 5 May 1999 08:59:22 -0700 (PDT) (envelope-from jerry.alexandratos@perspectives.net) Received: from localhost ([127.0.0.1] helo=tardis.perspectives.net) by tardis.perspectives.net with esmtp (Exim 2.12 #1) id 10f43h-0000gY-00; Wed, 5 May 1999 11:58:05 -0400 To: Nate Williams Cc: Intuitive Design Archives , freebsd-mobile@FreeBSD.ORG Subject: Re: Best Laptop for FreeBSD In-Reply-To: Message from Nate Williams of "Wed, 05 May 1999 09:21:09 MDT." <199905051521.JAA16609@mt.sri.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2630.925919885.1@tardis.perspectives.net> Date: Wed, 05 May 1999 11:58:05 -0400 From: Jerry Alexandratos Message-Id: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams says: : > I am thinking of buying a new laptop, and will install FreeBSD on : > it. I was wondering which laptops work well with FreeBSD and has almost : > all support. : : I've had *really* good luck with IBM's. My new 366Mhz ThinkPad 600E : works great, although I haven't (yet) tried to get sound working, I : don't expect to have any problems. I agree with Nate. This is a solid machine. Only caveat is that you need to install with >=64M of mem and then build a kernel where MAXMEM= whatever the machine reports when it first boots. Nate, try this (works for me): device pcm0 at isa? port 0x52c irq 5 drq 1 flags 0x13 --Jerry name: Jerry Alexandratos || Open-Source software isn't a phone: 302.521.1018 || matter of life or death... email: jalexand@perspectives.net || ...It's much more important || than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 10:41:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 57D1314DFF for ; Wed, 5 May 1999 10:41:44 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA26451; Wed, 5 May 1999 19:41:02 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905051741.TAA26451@freebsd.dk> Subject: Re: Best Laptop for FreeBSD In-Reply-To: from Intuitive Design Archives at "May 5, 1999 9:41:35 am" To: archive@in-design.com (Intuitive Design Archives) Date: Wed, 5 May 1999 19:41:01 +0200 (CEST) Cc: freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Intuitive Design Archives wrote: > Hello all; > > I am thinking of buying a new laptop, and will install FreeBSD on > it. I was wondering which laptops work well with FreeBSD and has almost > all support. I love my Dell Latitude CPi, its one of the most rugged laptops you can get for resonable money, its relatively small but still has a 13.3" LCD, its not too heavy (2.7Kg), and has about 4 hours of batterylife (on one battery that is, it does two make worlds in a row with plenty of time to spare on a full battery), and quick recharge (for 0 to full in ~50mins). -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 12:19:13 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7B51E14ECA for ; Wed, 5 May 1999 12:19:08 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA01750; Wed, 5 May 1999 20:19:01 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 5 May 1999 20:19:01 +0100 (BST) From: Doug Rabson To: Intuitive Design Archives Cc: freebsd-mobile@freebsd.org Subject: Re: Best Laptop for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 May 1999, Intuitive Design Archives wrote: > Hello all; > > I am thinking of buying a new laptop, and will install FreeBSD on > it. I was wondering which laptops work well with FreeBSD and has almost > all support. > > Thanks for your help > Tamer Ziady > > Intuitive Design Archive > archive@in-design.com > http://www.in-design.com I have a Toshiba Tecra 8000DVD which is working just fine. No IrDA support yet and cardbus is a forthcoming attraction but everything else works great (about 100mins for a make world). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 14: 0:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 0F3EE15823 for ; Wed, 5 May 1999 13:59:54 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA47343; Wed, 5 May 1999 22:59:51 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA14640; Wed, 5 May 1999 22:59:49 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905052059.WAA14640@greenpeace.grondar.za> To: Terje Elde Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Which laptop?? (Compaq Armada 6500?) In-Reply-To: Your message of " Wed, 05 May 1999 14:03:49 +0200." References: Date: Wed, 05 May 1999 22:59:49 +0200 From: Mark Murray Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terje Elde wrote: > I need a laptop I can use with FreeBSD. I kinda like a Compaq Armada 6500, > with internal 10/100 network card, 56k modem and so on, but I'd like some > comments from you all, both on this laptop, and in general about selecting > a laptop for FreeBSD use. Also, I'd be happy to hear about any other > laptops recommended. Asking for laptop advice is like asking for automobile advice! Some folk want a sportscar, some need a station wagon, others need a truck , and there are folk who _really_ want a hand built Morgan in custom colours. What are your requirements? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 15: 1:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dominator.eecs.harvard.edu (dominator.eecs.harvard.edu [140.247.60.28]) by hub.freebsd.org (Postfix) with SMTP id 7F45815338 for ; Wed, 5 May 1999 15:01:08 -0700 (PDT) (envelope-from karp@eecs.harvard.edu) Received: (from karp@localhost) by dominator.eecs.harvard.edu (8.6.12/8.6.12) id SAA26051; Wed, 5 May 1999 18:01:03 -0400 Date: Wed, 5 May 1999 18:01:03 -0400 From: Brad Karp Message-Id: <199905052201.SAA26051@dominator.eecs.harvard.edu> To: freebsd-mobile@freebsd.org Subject: code now available: my Lucent 802.11 WaveLAN driver for 3.1R! Cc: karp@dominator.eecs.harvard.edu Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm pleased to announce the availability of the first 802.11 WaveLAN driver for FreeBSD. This is my port (with cleanup and extensions) of Andreas Neuhaus' Linux driver, which was in turn based on Nico Valster of Lucent's code. Thanks, Andreas and Nico! Note that the code I started with is GPL'ed. So it can't be part of a FreeBSD binary-distributed kernel. But I sincerely hope that the code can be contributed to FreeBSD as a source-only distribution, if demand warrants. FreeBSD team members: how do I proceed to have it committed? You can get my code at: http://www.eecs.harvard.edu/~karp/iwl.tar.gz *WARNING* This is the very first release of this code. Use it at your own risk! And if you find bugs, please report them to me. I enclose the head of the README from my distribution for your information: --- FreeBSD WaveLAN IEEE 802.11 PCMCIA Driver *TEST* release 0.1 5 May, 1999 --- Author: Brad Karp, Harvard University EECS karp@eecs.harvard.edu Ported from: Linux driver by Andreas Neuhaus: http://www.fasta.fh-dortmund.de/users/andy/wvlan/ which was in turn based on a Lucent driver by Nico Valster of Lucent. WARNING: This driver is a very early, experimental release. It undoubtedly contains many bugs, and may cause crashes or data loss on your system. It is provided AS-IS, with no warranty. Please read the licensing and copyright in the source files for more details. IF YOU AREN'T FAMILIAR WITH WAVELAN IEEE, OR BUILDING AND CONFIGURING PCCARD KERNELS FOR FREEBSD, STOP HERE! THE AUTHOR CANNOT PROVIDE SUPPORT IN THESE BASIC AREAS! --- This kit contains my WaveLAN 802.11 PCMCIA driver for FreeBSD 3.1-RELEASE. The driver has *only* been tested using 3.1-RELEASE, and a Lucent-branded WaveLAN card. The Linux driver that was the basis for this code, and its Lucent-authored substrate, are GPL'ed. Hence, this code is encumbered by the GPL. Thus, it is likely never to be part of a FreeBSD *binary* kernel distribution (e.g., GENERIC). Hopefully, the driver can still be part of FreeBSD's source distribution, since I expect many users will benefit from it. This driver supports: - dynamic card insertion and removal - promiscuous mode - multicast address filtering in hardware - reading detailed low-level statistics from the WaveLAN card - power management (sleep/wakeup cycling by the WaveLAN card) - operation with a base station - operation in ad-hoc mode - configuration of the WaveLAN IEEE "Network Name" (SSID) [ detail elided from announcement email ] Enjoy!! -Brad, karp@eecs.harvard.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 15:53:22 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0603915154 for ; Wed, 5 May 1999 15:53:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA03612; Wed, 5 May 1999 23:52:47 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 5 May 1999 23:52:47 +0100 (BST) From: Doug Rabson To: Brad Karp Cc: freebsd-mobile@freebsd.org, karp@dominator.eecs.harvard.edu Subject: Re: code now available: my Lucent 802.11 WaveLAN driver for 3.1R! In-Reply-To: <199905052201.SAA26051@dominator.eecs.harvard.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 May 1999, Brad Karp wrote: > I'm pleased to announce the availability of the first 802.11 WaveLAN driver for > FreeBSD. Does this have any connection with the WaveLAN driver which Bill Paul just committed to FreeBSD-current? If not, you should coordinate your efforts with Bill. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 16:54:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id B1999158F8; Wed, 5 May 1999 16:54:51 -0700 (PDT) Subject: Re: code now available: my Lucent 802.11 WaveLAN driver for 3.1R! In-Reply-To: from Doug Rabson at "May 5, 1999 11:52:47 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 5 May 1999 16:54:51 -0700 (PDT) Cc: karp@eecs.harvard.edu, freebsd-mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 788 Message-Id: <19990505235451.B1999158F8@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Wed, 5 May 1999, Brad Karp wrote: > > > I'm pleased to announce the availability of the first 802.11 WaveLAN driver for > > FreeBSD. > > Does this have any connection with the WaveLAN driver which Bill Paul just > committed to FreeBSD-current? If not, you should coordinate your efforts > with Bill. Yes this is the same device, however my driver doesn't use any of the HCF Light code and is therefore uncontaminated by the GPL. It's also much prettier to look at, if I do say so myself. :) Don't be too upset though: at least I know there's somebody out there who can test my driver and tell me if it works right. I have only been able to test ad-hoc mode since I don't have an access point. If you could test BSS mode with your equipment, I'd really appreciate it. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 17:10:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dominator.eecs.harvard.edu (dominator.eecs.harvard.edu [140.247.60.28]) by hub.freebsd.org (Postfix) with SMTP id 320A114E85 for ; Wed, 5 May 1999 17:10:31 -0700 (PDT) (envelope-from karp@eecs.harvard.edu) Received: (from karp@localhost) by dominator.eecs.harvard.edu (8.6.12/8.6.12) id UAA25721; Wed, 5 May 1999 20:10:23 -0400 Date: Wed, 5 May 1999 20:10:23 -0400 From: Brad Karp Message-Id: <199905060010.UAA25721@dominator.eecs.harvard.edu> To: freebsd-mobile@freebsd.org Subject: duplicate 802.11 drivers Cc: dfr@nlsystems.com, wpaul@ctr.columbia.edu Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was unaware of Bill Paul's work; I don't subscribe to -current, only -mobile. No time to read both. I'm utterly despondent that I spent time doing this port when a non-GPL'ed driver was already almost complete. My own fault, I guess. As Bill points out, he didn't use the GPL Linux driver as a starting point; he only used it as a spec document for the programming interface of the WaveLAN 802.11 card. He started writing from scratch, so his driver is not GPL-encumbered. Bill also said of his driver vs. my own: > It's also much prettier to look at, if I do say so myself. :) I only want to point out that I believe Bill's comment refers mainly to the ugliness of the HCF-Light code, which I did not write--I took it from the Linux driver, which it in turn took from Lucent. I didn't have time to write a driver from scratch. Starting from the HCF-Light let me complete the port in under 4 days. But yes, that HCF-Light code is monstrous. Code by my hand is not. :-) -Brad, karp@eecs.harvard.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 17:28:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id B8AA814E22 for ; Wed, 5 May 1999 17:28:25 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from startide.ctr.columbia.edu (wpaul@startide.ctr.columbia.edu [128.59.64.52]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id UAA02674; Wed, 5 May 1999 20:28:15 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by startide.ctr.columbia.edu (8.9.1/8.6.4.788743) id UAA13862; Wed, 5 May 1999 20:28:14 -0400 (EDT) Message-Id: <199905060028.UAA13862@startide.ctr.columbia.edu> Subject: Re: duplicate 802.11 drivers To: karp@eecs.harvard.edu (Brad Karp) Date: Wed, 5 May 1999 20:28:13 -0400 (EDT) Cc: freebsd-mobile@freebsd.org, dfr@nlsystems.com In-Reply-To: <199905060010.UAA25721@dominator.eecs.harvard.edu> from "Brad Karp" at May 5, 99 08:10:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of all the gin joints in all the towns in all the world, Brad Karp had to walk into mine and say: > I was unaware of Bill Paul's work; I don't subscribe to -current, only > -mobile. No time to read both. I'm utterly despondent that I spent time > doing this port when a non-GPL'ed driver was already almost complete. My own > fault, I guess. Well, I probably should have said something too, but I'm also swamped with Real Work (tm) and other drivers (I also have another PCI 10/100 driver in the works, and both the PCI sample cards and the WaveLANs arrived on the same day; and then there's fixing bugs in existing drivers). > As Bill points out, he didn't use the GPL Linux driver as a starting point; > he only used it as a spec document for the programming interface of the > WaveLAN 802.11 card. He started writing from scratch, so his driver is not > GPL-encumbered. > > Bill also said of his driver vs. my own: > > > It's also much prettier to look at, if I do say so myself. :) > > I only want to point out that I believe Bill's comment refers mainly to the > ugliness of the HCF-Light code, which I did not write--I took it from the Linux > driver, which it in turn took from Lucent. Oh, yes: definitely. I certainly didn't mean to imply anything about your own code (I haven't even looked at it yet: I'm just on my way out of the office and will check it out when I get home). I apologize for the misunderstanding: it's the HCF code I was talking about. Given the appearance of the HCF Light, I shudder to think what the Hermes firmware source code looks like. > I didn't have time to write a driver from scratch. Starting from the HCF-Light > let me complete the port in under 4 days. But yes, that HCF-Light code is > monstrous. Code by my hand is not. :-) Indeed. :) Oh, incidentally, there's another Linux WaveLAN driver written by a commercial outfit called TriplePoint, Inc. on behalf of Lucent which uses the full HCF library, however it's supplied as object code only, and only for the x86 platform. Then again, FreeBSD's pccard support currently doesn't work anywhere except on the x86 either. Maybe that will change with the newbus stuff. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 20:48:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 3B23314C33 for ; Wed, 5 May 1999 20:47:51 -0700 (PDT) (envelope-from randy@psg.com) Received: by roam.psg.com id m10fF8D-00000HC; Wed, 5 May 1999 20:47:29 -0700 (PDT) (Smail3.2.0.101#2) Message-Id: Date: Wed, 5 May 1999 20:47:29 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Laptoppers Subject: vaio modem sound Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sony vaio 505tx -release+pao so how do i get the modem sound to work so i can hear the sucker dial? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 22:16:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6551A158FD for ; Wed, 5 May 1999 22:16:29 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA16224; Wed, 5 May 1999 23:15:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA15142; Wed, 5 May 1999 23:15:55 -0600 (MDT) Message-Id: <199905060515.XAA15142@harmony.village.org> To: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) Subject: Re: Pccard rewrite, patch #1 Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org In-reply-to: Your message of "Thu, 06 May 1999 00:29:26 +0900." <199905051529.AAA16840@afs.ntc.mita.keio.ac.jp> References: <199905051529.AAA16840@afs.ntc.mita.keio.ac.jp> Date: Wed, 05 May 1999 23:15:55 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905051529.AAA16840@afs.ntc.mita.keio.ac.jp> HOSOKAWA Tatsumi writes: : I tested it now, but I can't compile GENERIC at first. : I did s/#include "card.h"/#include "pccard.h"/, : and s/NCARD/NPCCARD/, GENERIC was compiled without errors. : Did I something wrong? No. I did. I had a card.h left over in my compile area, so I didn't catch this problem. I have corrected it. : I boot the new kernel on my Toshiba Libretto SS1000. : But no PC-card slots were probed (today's current finds PC-card slots, : but insertion and removal does not cause interrupt). Hmmm. IIRC, that machine has a pci cardbus bridge. I must have fubar'd the legacy probe/enable support. I'm working on writing a card bus bridge driver so that all card bus bridges will work (at least all of the YENTA ones. The newconfig folks have a driver which I'm porting over. This should make the pci cardbus machines more reliable. I'm doing this because my cardbu machine is being flakey in generation of interrupts... Sometimes it does and sometimes it doesn't. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 22:35:50 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9971A1512C for ; Wed, 5 May 1999 22:35:20 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA16277; Wed, 5 May 1999 23:34:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA15329; Wed, 5 May 1999 23:34:44 -0600 (MDT) Message-Id: <199905060534.XAA15329@harmony.village.org> To: wpaul@ctr.columbia.edu (Bill Paul) Subject: Re: duplicate 802.11 drivers Cc: karp@eecs.harvard.edu (Brad Karp), freebsd-mobile@FreeBSD.ORG, dfr@nlsystems.com In-reply-to: Your message of "Wed, 05 May 1999 20:28:13 EDT." <199905060028.UAA13862@startide.ctr.columbia.edu> References: <199905060028.UAA13862@startide.ctr.columbia.edu> Date: Wed, 05 May 1999 23:34:43 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905060028.UAA13862@startide.ctr.columbia.edu> Bill Paul writes: : Then again, FreeBSD's pccard support currently : doesn't work anywhere except on the x86 either. Maybe that will change : with the newbus stuff. That is certainly a goal. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 5 23:51:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id 30BBF14CED for ; Wed, 5 May 1999 23:51:54 -0700 (PDT) (envelope-from rsm@acm.org) Received: from modem-38.neodymium.dialup.pol.co.uk ([62.136.29.166] helo=valis.goatsucker.org) by mail5.svr.pol.co.uk with esmtp (Exim 2.12 #1) id 10fI0f-0007Q4-00 for freebsd-mobile@FreeBSD.ORG; Thu, 6 May 1999 07:51:53 +0100 Received: (from scott@localhost) by valis.goatsucker.org (8.8.8/8.8.7) id TAA00651; Wed, 5 May 1999 19:26:54 +0100 (BST) (envelope-from scott) Message-ID: <19990505192653.10327@goatsucker.org> Date: Wed, 5 May 1999 19:26:53 +0100 From: Scott Mitchell To: Intuitive Design Archives Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Best Laptop for FreeBSD References: <199905051521.JAA16609@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199905051521.JAA16609@mt.sri.com>; from Nate Williams on Wed, May 05, 1999 at 09:21:09AM -0600 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 05, 1999 at 09:21:09AM -0600, Nate Williams wrote: > > I am thinking of buying a new laptop, and will install FreeBSD on > > it. I was wondering which laptops work well with FreeBSD and has almost > > all support. > > I've had *really* good luck with IBM's. My new 366Mhz ThinkPad 600E > works great, although I haven't (yet) tried to get sound working, I > don't expect to have any problems. > > It required one minor change to the kernel to recognize my > PCCARD/CardBus controller, but that will be part of FreeBSD 3.2 soon to > be released. > > I recommend IBM's whole-heartedly. I'll second that. ThinkPad's aren't the cheapest laptops around by a (very) long shot, but they're extremely well built and seem to get along just fine with FreeBSD. Bear in mind that most laptops use funky graphics chipsets that may be only minimally supported by XFree86, if at all. Make sure you know *exactly* what's in the box before you take it home :) Scott -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just | 0x54B171B9 | like a dried up piece of roast goat" QMW College, London, UK | 0xAA775B8B | -- J. S. Bach. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 2:40:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from inga.augusta.de (inga.augusta.de [193.175.23.65]) by hub.freebsd.org (Postfix) with ESMTP id 2A2201599D for ; Thu, 6 May 1999 02:40:24 -0700 (PDT) (envelope-from case@inga.augusta.de) Received: (from case@localhost) by inga.augusta.de (8.8.8/8.8.7) id LAA21015 for freebsd-mobile@FreeBSD.ORG; Thu, 6 May 1999 11:40:19 +0200 (MET DST) Message-ID: <19990506114019.A19281@augusta.de> Date: Thu, 6 May 1999 11:40:19 +0200 From: Wolfgang Kess To: freebsd-mobile@FreeBSD.ORG Subject: Best Laptop for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I use a AT&T 486-33 Notebook as a PGP Certification Authority System. FreeBSD 2.2.8, 20 MB RAM, 60 MB HD, PGP data stored on a 170 MB Viper PCCard HD. It works very good :-) Bye, Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 7:47:41 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 2BD9415045 for ; Thu, 6 May 1999 07:47:38 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 27581 invoked from network); 6 May 1999 14:47:24 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 6 May 1999 14:47:24 -0000 Date: Thu, 6 May 1999 09:47:10 -0500 (CDT) From: John Sconiers To: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: latest PAO boot.flp, Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've read there was some changes in PAO over the last couple of days. Where can I download the latest PAO boot.flp from that will include those changes. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 8:21:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 8328014D4E for ; Thu, 6 May 1999 08:21:03 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id AAA00214; Fri, 7 May 1999 00:20:40 +0900 (JST) Date: Fri, 7 May 1999 00:20:40 +0900 (JST) Message-Id: <199905061520.AAA00214@afs.ntc.mita.keio.ac.jp> To: imp@harmony.village.org Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Pccard rewrite, patch #1 In-Reply-To: Your message of "Thu, 6 May 1999 14:15:55 JST". <199905060515.XAA15142@harmony.village.org> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199905060515.XAA15142@harmony.village.org> imp@harmony.village.org writes: >> Hmmm. IIRC, that machine has a pci cardbus bridge. Yes. It has ToPIC97 PCI/CardBus bridge. >> I must have >> fubar'd the legacy probe/enable support. I'm working on writing a >> card bus bridge driver so that all card bus bridges will work (at >> least all of the YENTA ones. The newconfig folks have a driver which >> I'm porting over. This should make the pci cardbus machines more >> reliable. I'm doing this because my cardbu machine is being flakey in >> generation of interrupts... Sometimes it does and sometimes it >> doesn't. Does it mean IRQ routing? or card removal interrupt? Today's -current pccard code does not generate (or does not catch) interrupt caused by card removal on my Libretto SS1000. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 8:22:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 606F114D4E; Thu, 6 May 1999 08:22:28 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id AAA00232; Fri, 7 May 1999 00:21:59 +0900 (JST) Date: Fri, 7 May 1999 00:21:59 +0900 (JST) Message-Id: <199905061521.AAA00232@afs.ntc.mita.keio.ac.jp> To: jrs@enteract.com Cc: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: latest PAO boot.flp, In-Reply-To: Your message of "Thu, 6 May 1999 23:47:10 JST". From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article jrs@enteract.com writes: >> I've read there was some changes in PAO over the last couple of days. >> Where can I download the latest PAO boot.flp from that will include those >> changes. Not yet. Sorry. I'm working on porting PAO boot.flp feature to -current. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 9: 9:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 7C26315282 for ; Thu, 6 May 1999 09:09:33 -0700 (PDT) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.8.6/8.7.3) id MAA03869 for mobile@freebsd.org; Thu, 6 May 1999 12:10:36 -0400 (EDT) Date: Thu, 6 May 1999 12:10:36 -0400 (EDT) From: Kent Hauser Message-Id: <199905061610.MAA03869@rtp.tfd.com> To: mobile@freebsd.org Subject: Bootmgr problem Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I've got a new ThinkPad 600E (which is great with FreeBSD 3.1) *except* that it appears that the bootmgr somehow queries the bios and disables my com port. I put a serial datascope on the thing & once I've enabled the serial port via the config mgr in W98, the port stays on thru the POST & is disabled as soon as the F1=DOS/F2=FreeBSD prompt appears. Is there anyway to make the bootmgr just prompt the keyboard/screen & leave the serial ports alone? (I looked in /sys/boot & promptly got lost...) Thanks all. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 9:54:30 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id CFFC815001 for ; Thu, 6 May 1999 09:54:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA04287; Thu, 6 May 1999 09:53:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905061653.JAA04287@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kent Hauser Cc: mobile@freebsd.org Subject: Re: Bootmgr problem In-reply-to: Your message of "Thu, 06 May 1999 12:10:36 EDT." <199905061610.MAA03869@rtp.tfd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 09:53:11 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I've got a new ThinkPad 600E (which is great with FreeBSD 3.1) *except* > that it appears that the bootmgr somehow queries the bios and disables > my com port. I put a serial datascope on the thing & once I've enabled > the serial port via the config mgr in W98, the port stays on thru the POST > & is disabled as soon as the F1=DOS/F2=FreeBSD prompt appears. > > Is there anyway to make the bootmgr just prompt the keyboard/screen & > leave the serial ports alone? It doesn't touch them; your BIOS is doing it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 10:23:25 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1C4EF14D4F for ; Thu, 6 May 1999 10:23:20 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA17920; Thu, 6 May 1999 11:22:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA17998; Thu, 6 May 1999 11:22:52 -0600 (MDT) Message-Id: <199905061722.LAA17998@harmony.village.org> To: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) Subject: Re: Pccard rewrite, patch #1 Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org In-reply-to: Your message of "Fri, 07 May 1999 00:20:40 +0900." <199905061520.AAA00214@afs.ntc.mita.keio.ac.jp> References: <199905061520.AAA00214@afs.ntc.mita.keio.ac.jp> Date: Thu, 06 May 1999 11:22:52 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905061520.AAA00214@afs.ntc.mita.keio.ac.jp> HOSOKAWA Tatsumi writes: : Yes. It has ToPIC97 PCI/CardBus bridge. That's good to know. : >> I must have : >> fubar'd the legacy probe/enable support. I'm working on writing a : >> card bus bridge driver so that all card bus bridges will work (at : >> least all of the YENTA ones. The newconfig folks have a driver which : >> I'm porting over. This should make the pci cardbus machines more : >> reliable. I'm doing this because my cardbu machine is being flakey in : >> generation of interrupts... Sometimes it does and sometimes it : >> doesn't. : : Does it mean IRQ routing? or card removal interrupt? : : Today's -current pccard code does not generate (or does not catch) : interrupt caused by card removal on my Libretto SS1000. It should mean both IRQ routing for the card, as well as the irq for socket events. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 10:26:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C50A4150DF for ; Thu, 6 May 1999 10:26:43 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA23390; Thu, 6 May 1999 13:26:40 -0400 (EDT) (envelope-from wollman) Date: Thu, 6 May 1999 13:26:40 -0400 (EDT) From: Garrett Wollman Message-Id: <199905061726.NAA23390@khavrinen.lcs.mit.edu> To: Warner Losh Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905061722.LAA17998@harmony.village.org> References: <199905061520.AAA00214@afs.ntc.mita.keio.ac.jp> <199905061722.LAA17998@harmony.village.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > It should mean both IRQ routing for the card, as well as the irq for > socket events. But you'll need to use the PCI BIOS to figure out what IRQ the CardBus INTA and INTB are wired to, at least on many laptops similar to mine (a Micron TranSport XKE). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 10:29:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id BC022150DF; Thu, 6 May 1999 10:29:16 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id KAA03435; Thu, 6 May 1999 10:29:15 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3731D16A.27667779@MexComUSA.net> Date: Thu, 06 May 1999 10:29:14 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul Cc: Doug Rabson , karp@eecs.harvard.edu, freebsd-mobile@FreeBSD.ORG Subject: Re: code now available: my Lucent 802.11 WaveLAN driver for 3.1R! References: <19990505235451.B1999158F8@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Paul wrote: > > On Wed, 5 May 1999, Brad Karp wrote: > > > > > I'm pleased to announce the availability of the first 802.11 WaveLAN driver for > > > FreeBSD. > > > > Does this have any connection with the WaveLAN driver which Bill Paul just > > committed to FreeBSD-current? If not, you should coordinate your efforts > > with Bill. > > Yes this is the same device, however my driver doesn't use any of the > HCF Light code and is therefore uncontaminated by the GPL. It's also much > prettier to look at, if I do say so myself. :) > > Don't be too upset though: at least I know there's somebody out there who > can test my driver and tell me if it works right. I have only been able to > test ad-hoc mode since I don't have an access point. If you could test > BSS mode with your equipment, I'd really appreciate it. > > -Bill > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message I'm installing a Lucent access-point, now. Would this driver work on current or would the newbus changes be a problem? Where can the code be found or has it been commited? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 13:39:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 25A751534B for ; Thu, 6 May 1999 13:39:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA36791; Thu, 6 May 1999 21:37:16 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 6 May 1999 21:37:16 +0100 (BST) From: Doug Rabson To: Garrett Wollman Cc: Warner Losh , new-bus-arch@bostonradio.org, mobile@freebsd.org Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905061726.NAA23390@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 May 1999, Garrett Wollman wrote: > < said: > > > It should mean both IRQ routing for the card, as well as the irq for > > socket events. > > But you'll need to use the PCI BIOS to figure out what IRQ the CardBus > INTA and INTB are wired to, at least on many laptops similar to mine > (a Micron TranSport XKE). This should be doable - the newconfig folks have code to talk to the PCI BIOS. In the long term, ACPI will also provide this kind of access without having to call any bios functions. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 13:59:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dominator.eecs.harvard.edu (dominator.eecs.harvard.edu [140.247.60.28]) by hub.freebsd.org (Postfix) with SMTP id 6398D15BE8 for ; Thu, 6 May 1999 13:59:26 -0700 (PDT) (envelope-from karp@eecs.harvard.edu) Received: (from karp@localhost) by dominator.eecs.harvard.edu (8.6.12/8.6.12) id QAA32433; Thu, 6 May 1999 16:59:25 -0400 Date: Thu, 6 May 1999 16:59:25 -0400 From: Brad Karp Message-Id: <199905062059.QAA32433@dominator.eecs.harvard.edu> To: freebsd-mobile@freebsd.org Subject: if_wi Lucent WaveLAN driver: patches and power management Cc: wpaul@ctr.columbia.edu Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For anyone who's interested: Bill Paul's WaveLAN 802.11 PC-Card driver, if_wi, was committed before I announced my own driver for this hardware. His driver is not a port of the Linux driver, and so is not GPL'ed, and is less gross, not having started from the nasty Lucent/Linux codebase. I found a couple byte-order bugs in the if_wi driver, that caused coredumps in the user-level configuration program wicontrol, and also resulted in configuration information being improperly written to the card. I submitted patches for these, and Bill's committed them to -current. After those patches, I've verified that this driver works great with WavePoint II base stations. (Bill had asked me to verify this, since I have a base station and he does not.) I'm still in denial over having produced my driver for naught, so in the effort to contribute some shred, here's an enhancement to Bill's driver you might all want: power management support! In short: the WaveLAN PC-Card supports a protocol of alternating sleep/wake, in the interest of saving power, at the expense of some increased receive latency. To use this, you *must* use the card with a base station (the protocol requires the base station's cooperation, and doesn't work in ad-hoc mode), and you need WavePoint firmware 2.03 or newer, and WaveLAN PC-Card firmware 2.00 or newer. (Lower revs, and the WaveLAN card will silently ignore your request to do power management.) Below are patches to add support for power management to Bill's driver. It defaults to off; change it to on with "wicontrol -i wi0 -P 1". You can also change the sleep interval. Longer means more power saving, but worse worst-case receive latency. Shorter, vice-versa. The sleep interval can be changed with "wicontrol -i wi0 -S " (where i is an integer number of milliseconds; 100 ms is the default). Enjoy, -Brad, karp@eecs.harvard.edu --- wi.orig/usr/sbin/wicontrol/wicontrol.c Wed May 5 11:13:18 1999 +++ wi/usr/sbin/wicontrol/wicontrol.c Thu May 6 16:42:40 1999 @@ -308,6 +308,8 @@ { WI_RID_RTS_THRESH, WI_WORDS, "RTS/CTS handshake threshold:\t\t"}, { WI_RID_CREATE_IBSS, WI_BOOL, "Create IBSS:\t\t\t\t" }, { WI_RID_SYSTEM_SCALE, WI_WORDS, "Access point density:\t\t\t" }, + { WI_RID_PM_ENABLED, WI_WORDS, "Power Mgmt (1=on, 0=off):\t\t" }, + { WI_RID_MAX_SLEEP, WI_WORDS, "Max sleep time:\t\t\t\t" }, { 0, NULL } }; @@ -426,6 +428,8 @@ fprintf(stderr, "\t%s -i iface -m mac address\n", p); fprintf(stderr, "\t%s -i iface -d max data length\n", p); fprintf(stderr, "\t%s -i iface -r RTS threshold\n", p); + fprintf(stderr, "\t%s -i iface -P power mgmt\n", p); + fprintf(stderr, "\t%s -i iface -S max sleep duration\n", p); exit(1); } @@ -438,7 +442,7 @@ char *iface = NULL; char *p = argv[0]; - while((ch = getopt(argc, argv, "hoc:d:i:p:r:q:t:n:s:m:")) != -1) { + while((ch = getopt(argc, argv, "hoc:d:i:p:r:q:t:n:s:m:P:S:")) != -1) { switch(ch) { case 'o': wi_dumpstats(iface); @@ -481,6 +485,14 @@ break; case 'q': wi_setstr(iface, WI_RID_OWN_SSID, optarg); + exit(0); + break; + case 'S': + wi_setword(iface, WI_RID_MAX_SLEEP, atoi(optarg)); + exit(0); + break; + case 'P': + wi_setword(iface, WI_RID_PM_ENABLED, atoi(optarg)); exit(0); break; case 'h': --- wi.orig/sys/i386/isa/if_wi.c Wed May 5 11:12:16 1999 +++ /sys/i386/isa/if_wi.c Thu May 6 16:47:07 1999 @@ -323,12 +323,14 @@ sizeof(WI_DEFAULT_IBSS) - 1); sc->wi_portnum = WI_DEFAULT_PORT; sc->wi_ptype = WI_PORTTYPE_ADHOC; sc->wi_ap_density = WI_DEFAULT_AP_DENSITY; sc->wi_rts_thresh = WI_DEFAULT_RTS_THRESH; sc->wi_tx_rate = WI_DEFAULT_TX_RATE; sc->wi_max_data_len = WI_DEFAULT_DATALEN; sc->wi_create_ibss = WI_DEFAULT_CREATE_IBSS; + sc->wi_pm_enabled = WI_DEFAULT_PM_ENABLED; + sc->wi_max_sleep = WI_DEFAULT_MAX_SLEEP; bzero((char *)&sc->wi_stats, sizeof(sc->wi_stats)); @@ -953,6 +955,12 @@ bzero(sc->wi_ibss_name, sizeof(sc->wi_ibss_name)); bcopy((char *)&wreq->wi_val[1], sc->wi_ibss_name, 30); break; + case WI_RID_PM_ENABLED: + sc->wi_pm_enabled = wreq->wi_val[0]; + break; + case WI_RID_MAX_SLEEP: + sc->wi_max_sleep = wreq->wi_val[0]; + break; default: break; } @@ -1087,6 +1095,12 @@ /* Access point density */ WI_SETVAL(WI_RID_SYSTEM_SCALE, sc->wi_ap_density); + + /* Power Management Enabled */ + WI_SETVAL(WI_RID_PM_ENABLED, sc->wi_pm_enabled); + + /* Power Management Max Sleep */ + WI_SETVAL(WI_RID_MAX_SLEEP, sc->wi_max_sleep); /* Specify the IBSS name */ WI_SETSTR(WI_RID_OWN_SSID, sc->wi_ibss_name); --- wi.orig/sys/i386/isa/if_wireg.h Wed May 5 11:12:21 1999 +++ /sys/i386/isa/if_wireg.h Thu May 6 16:46:34 1999 @@ -73,6 +73,8 @@ u_int16_t wi_ap_density; u_int16_t wi_tx_rate; u_int16_t wi_create_ibss; + u_int16_t wi_pm_enabled; + u_int16_t wi_max_sleep; char wi_node_name[32]; char wi_net_name[32]; char wi_ibss_name[32]; @@ -111,6 +113,10 @@ #define WI_DEFAULT_IBSS "FreeBSD IBSS" +#define WI_DEFAULT_PM_ENABLED 0 + +#define WI_DEFAULT_MAX_SLEEP 100 + /* * register space access macros */ @@ -461,7 +467,17 @@ /* * Frame data size. */ #define WI_RID_MAX_DATALEN 0xFC07 + +/* + * ESS power management enable + */ +#define WI_RID_PM_ENABLED 0xFC09 + +/* + * ESS max PM sleep interval + */ +#define WI_RID_MAX_SLEEP 0xFC0C /* * Set our station name. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 18:18: 2 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C4505152E4 for ; Thu, 6 May 1999 18:17:12 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA19198; Thu, 6 May 1999 19:16:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA20728; Thu, 6 May 1999 19:16:51 -0600 (MDT) Message-Id: <199905070116.TAA20728@harmony.village.org> To: Doug Rabson Subject: Re: Pccard rewrite, patch #1 Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org In-reply-to: Your message of "Thu, 06 May 1999 21:37:16 BST." References: Date: Thu, 06 May 1999 19:16:51 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Doug Rabson writes: : This should be doable - the newconfig folks have code to talk to the PCI : BIOS. In the long term, ACPI will also provide this kind of access without : having to call any bios functions. ACPI looks very promising. Looks like it attempts to move the management of many things into a p-code like machine. The machine appears to be relatively simple. I'm not aware of any good (or bad for that matter) AML implementations that are freely available. If you read the spec carefully, you'll note that they leave the door open for ACPI impelementations on non-x86 architectures. The newconfig code has support for cardbus bridges. I've not looked closely at what they offer, however. I know that on my laptop it makes a difference between having PnP OS set to Y and N. With it set to 'Y,' almost nothing is configured (which is correct, per the pnp spec) and it is hard to get things working. When it is set to 'N,' then it appears to assign all the chips on the PCI bus to the int-a irq 9. But then again, PCI interrupt routing has always been a confusing thing to me... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 20:34:35 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id 7CE8414D0F for ; Thu, 6 May 1999 20:34:29 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: (wpaul@localhost) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) id XAA20933; Thu, 6 May 1999 23:34:28 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Message-Id: <199905070334.XAA20933@sirius.ctr.columbia.edu> Subject: Re: if_wi Lucent WaveLAN driver: patches and power management To: karp@eecs.harvard.edu (Brad Karp) Date: Thu, 6 May 1999 23:34:27 -0400 (EDT) Cc: freebsd-mobile@freebsd.org In-Reply-To: <199905062059.QAA32433@dominator.eecs.harvard.edu> from "Brad Karp" at May 6, 99 04:59:25 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of all the gin joints in all the towns in all the world, Brad Karp had to walk into mine and say: [...] > I'm still in denial over having produced my driver for naught, so in the > effort to contribute some shred, here's an enhancement to Bill's driver you > might all want: power management support! > > In short: the WaveLAN PC-Card supports a protocol of alternating sleep/wake, > in the interest of saving power, at the expense of some increased receive > latency. To use this, you *must* use the card with a base station (the > protocol requires the base station's cooperation, and doesn't work in ad-hoc > mode), and you need WavePoint firmware 2.03 or newer, and WaveLAN PC-Card > firmware 2.00 or newer. (Lower revs, and the WaveLAN card will silently ignore > your request to do power management.) FYI, I have applied Brad's power management patches to -current. I also added the ability to set the radio frequency with wicontrol (-f option) and I updated the wicontrol man page. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 21:21:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rocky.citr.com (unknown [206.168.217.146]) by hub.freebsd.org (Postfix) with ESMTP id A86F915041; Thu, 6 May 1999 21:21:21 -0700 (PDT) (envelope-from eblood@citr.com) Received: from pearl.citr.com ([192.168.1.1]) by rocky.citr.com (8.8.5/8.8.5) with ESMTP id WAA28166; Thu, 6 May 1999 22:01:03 -0600 (MDT) Received: (from eblood@localhost) by pearl.citr.com (8.8.5/8.8.5) id WAA05695; Thu, 6 May 1999 22:21:14 -0600 (MDT) From: Eric Blood MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14130.27194.311593.355249@pearl.citr.com> Date: Thu, 6 May 1999 22:21:14 -0600 (MDT) To: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Drive noise X-Mailer: VM 6.67 under 21.0 "20 minutes to Nikko" XEmacs Lucid (beta67) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just installed FreeBSD 3.1 on a laptop and it sounds like the heads of the drive are getting parked a lot. I've tried tracking down how to increase the update time, but for some reason, sysctl doesn't think there's a kern.update. How do I go about setting it? Is there anything else I can do to delay writing to the drive? Tuning a filesystem parameter, or some sort memory cache parameter? Thanks for your help. -- Eric Blood To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22: 1:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id A48D814CA3 for ; Thu, 6 May 1999 22:01:39 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA28623; Thu, 6 May 1999 23:01:28 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA27197; Thu, 6 May 1999 23:01:28 -0600 Date: Thu, 6 May 1999 23:01:28 -0600 Message-Id: <199905070501.XAA27197@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Doug Rabson , new-bus-arch@bostonradio.org, mobile@FreeBSD.ORG Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905070116.TAA20728@harmony.village.org> References: <199905070116.TAA20728@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The newconfig code has support for cardbus bridges. I've not looked > closely at what they offer, however. So does FreeBSD-current and -stable, or am I missing something. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22: 2:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 52F8C14CA3 for ; Thu, 6 May 1999 22:02:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA19832; Thu, 6 May 1999 23:02:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21575; Thu, 6 May 1999 23:02:38 -0600 (MDT) Message-Id: <199905070502.XAA21575@harmony.village.org> To: Nate Williams Subject: Re: Pccard rewrite, patch #1 Cc: Doug Rabson , new-bus-arch@bostonradio.org, mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 May 1999 23:01:28 MDT." <199905070501.XAA27197@mt.sri.com> References: <199905070501.XAA27197@mt.sri.com> <199905070116.TAA20728@harmony.village.org> Date: Thu, 06 May 1999 23:02:38 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905070501.XAA27197@mt.sri.com> Nate Williams writes: : So does FreeBSD-current and -stable, or am I missing something. FreeBSD-current/stable supports cardbus bridges in "legacy" mode only. The newconfig stuff supports them using the PCI interface (as well as supporting cardbus cards in cardbus systems). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22: 4:59 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 9DD9A14CA3 for ; Thu, 6 May 1999 22:04:57 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA28670; Thu, 6 May 1999 23:04:53 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA27243; Thu, 6 May 1999 23:04:53 -0600 Date: Thu, 6 May 1999 23:04:53 -0600 Message-Id: <199905070504.XAA27243@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Nate Williams , Doug Rabson , new-bus-arch@bostonradio.org, mobile@FreeBSD.ORG Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905070502.XAA21575@harmony.village.org> References: <199905070501.XAA27197@mt.sri.com> <199905070116.TAA20728@harmony.village.org> <199905070502.XAA21575@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ CardBus bridge support ] > : So does FreeBSD-current and -stable, or am I missing something. > > FreeBSD-current/stable supports cardbus bridges in "legacy" mode > only. The newconfig stuff supports them using the PCI interface (as > well as supporting cardbus cards in cardbus systems). Ahh, OK. In my setup, I only need 'legacy' support, since I don't own any CardBus cards. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22:10:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (Postfix) with ESMTP id B778214D2A; Thu, 6 May 1999 22:10:19 -0700 (PDT) (envelope-from A_Johns@TurnAround.com.au) Received: from TurnAround.com.au (dhcp64.turnaround.com.au [192.168.1.64]) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with ESMTP id PAA14416; Fri, 7 May 1999 15:20:54 +1000 (EST) (envelope-from A_Johns@TurnAround.com.au) Message-ID: <373275C5.D2C17F01@TurnAround.com.au> Date: Fri, 07 May 1999 15:10:29 +1000 From: Andrew Johns Organization: TurnAround Solutions P/L X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Eric Blood Cc: freebsd-mobile@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Drive noise References: <14130.27194.311593.355249@pearl.citr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eric Blood wrote: > > I've just installed FreeBSD 3.1 on a laptop and it sounds like the > heads of the drive are getting parked a lot. I've tried tracking down > how to increase the update time, but for some reason, sysctl doesn't > think there's a kern.update. How do I go about setting it? > > Is there anything else I can do to delay writing to the drive? Tuning > a filesystem parameter, or some sort memory cache parameter? > You might want to look at softupdates (write caching) available in 3.0 and above (if I remember correctly). -- Regards | _/\_/\ Andrew Johns BSc (Comp Sci) | / \ TurnAround Solutions Pty Ltd | \_...__/ http://www.turnaround.com.au/ | \/ "The box said 'Requires Windows 98, NT, Linux or better' so I installed FreeBSD." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22:11:56 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 049CB14D2A for ; Thu, 6 May 1999 22:11:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA19867; Thu, 6 May 1999 23:11:07 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21655; Thu, 6 May 1999 23:11:36 -0600 (MDT) Message-Id: <199905070511.XAA21655@harmony.village.org> To: Nate Williams Subject: Re: Pccard rewrite, patch #1 Cc: Doug Rabson , new-bus-arch@bostonradio.org, mobile@freebsd.org In-reply-to: Your message of "Thu, 06 May 1999 23:04:53 MDT." <199905070504.XAA27243@mt.sri.com> References: <199905070504.XAA27243@mt.sri.com> <199905070501.XAA27197@mt.sri.com> <199905070116.TAA20728@harmony.village.org> <199905070502.XAA21575@harmony.village.org> Date: Thu, 06 May 1999 23:11:35 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905070504.XAA27243@mt.sri.com> Nate Williams writes: : Ahh, OK. In my setup, I only need 'legacy' support, since I don't own : any CardBus cards. Evidentally, I can get more reliable interrupts with the cbb in pci mode than I can in "legacy" mode. At least that's what preliminary indications seem to point to. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 6 22:13: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C6C6B15C23 for ; Thu, 6 May 1999 22:12:59 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA28772; Thu, 6 May 1999 23:12:55 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA27335; Thu, 6 May 1999 23:12:54 -0600 Date: Thu, 6 May 1999 23:12:54 -0600 Message-Id: <199905070512.XAA27335@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Nate Williams , Doug Rabson , new-bus-arch@bostonradio.org, mobile@freebsd.org Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905070511.XAA21655@harmony.village.org> References: <199905070504.XAA27243@mt.sri.com> <199905070501.XAA27197@mt.sri.com> <199905070116.TAA20728@harmony.village.org> <199905070502.XAA21575@harmony.village.org> <199905070511.XAA21655@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : Ahh, OK. In my setup, I only need 'legacy' support, since I don't own > : any CardBus cards. > > Evidentally, I can get more reliable interrupts with the cbb in pci > mode than I can in "legacy" mode. At least that's what preliminary > indications seem to point to. Really? It's certainly not the case with my old ThinkPad, or my new one. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 0:14:18 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0846C153D2 for ; Fri, 7 May 1999 00:14:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA20215; Fri, 7 May 1999 01:13:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA01276; Fri, 7 May 1999 01:13:18 -0600 (MDT) Message-Id: <199905070713.BAA01276@harmony.village.org> To: Nate Williams Subject: Re: Pccard rewrite, patch #1 Cc: Doug Rabson , new-bus-arch@bostonradio.org, mobile@freebsd.org In-reply-to: Your message of "Thu, 06 May 1999 23:12:54 MDT." <199905070512.XAA27335@mt.sri.com> References: <199905070512.XAA27335@mt.sri.com> <199905070504.XAA27243@mt.sri.com> <199905070501.XAA27197@mt.sri.com> <199905070116.TAA20728@harmony.village.org> <199905070502.XAA21575@harmony.village.org> <199905070511.XAA21655@harmony.village.org> Date: Fri, 07 May 1999 01:13:18 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905070512.XAA27335@mt.sri.com> Nate Williams writes: : Really? It's certainly not the case with my old ThinkPad, or my new : one. Yes. I don't understand it completely right now, but that seems to be the case. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 0:45:28 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from area51.fremont.ca.us (d60-076.leach.ucdavis.edu [169.237.60.76]) by hub.freebsd.org (Postfix) with ESMTP id C1B4714F53 for ; Fri, 7 May 1999 00:45:26 -0700 (PDT) (envelope-from mharo@area51.fremont.ca.us) Received: (from mharo@localhost) by area51.fremont.ca.us (8.9.2/8.9.2) id AAA21721 for freebsd-mobile@freebsd.org; Fri, 7 May 1999 00:45:26 -0700 (PDT) (envelope-from mharo) Date: Fri, 7 May 1999 00:45:26 -0700 From: Michael Haro To: freebsd-mobile@freebsd.org Subject: Which pccard network card? Message-ID: <19990507004526.A21702@area51.fremont.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm planning on buying a laptop soon and I was wondering which pccard (type 2) network card I should buy. I'm probably just going to stick with 10mbit due to cost, but if 100mbit isn't much more expensive then I'll probably do that. What cards does FreeBSD support well? Think I should install PAO on my laptop when I get it? As a side note, do any of you know of any reasons why I shouldn't buy a Sony Vaio 505tx? Thanks, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 1: 7:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D901B15E96 for ; Fri, 7 May 1999 01:07:25 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA09642; Fri, 7 May 1999 09:07:39 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 09:07:25 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905070116.TAA20728@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 May 1999, Warner Losh wrote: > In message Doug Rabson writes: > : This should be doable - the newconfig folks have code to talk to the PCI > : BIOS. In the long term, ACPI will also provide this kind of access without > : having to call any bios functions. > > ACPI looks very promising. Looks like it attempts to move the > management of many things into a p-code like machine. The machine > appears to be relatively simple. I'm not aware of any good (or bad > for that matter) AML implementations that are freely available. > > If you read the spec carefully, you'll note that they leave the door > open for ACPI impelementations on non-x86 architectures. I saw that too. It really does look quite useful. I have a test program which parses and decompiles all the AML in my laptop. I don't think that an implementation of the interpreter will be too hard. Slightly harder is implementing the ACPI event model and integrating ACPI hooks into the rest of the drivers but its all doable. > > The newconfig code has support for cardbus bridges. I've not looked > closely at what they offer, however. > > I know that on my laptop it makes a difference between having PnP OS > set to Y and N. With it set to 'Y,' almost nothing is configured (which > is correct, per the pnp spec) and it is hard to get things working. > When it is set to 'N,' then it appears to assign all the chips on the > PCI bus to the int-a irq 9. But then again, PCI interrupt routing has > always been a confusing thing to me... Me too. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 1:27:25 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D20E015B25; Fri, 7 May 1999 01:27:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA09964; Fri, 7 May 1999 09:27:41 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 09:27:41 +0100 (BST) From: Doug Rabson To: Edwin Culp Cc: Bill Paul , karp@eecs.harvard.edu, freebsd-mobile@FreeBSD.ORG Subject: Re: code now available: my Lucent 802.11 WaveLAN driver for 3.1R! In-Reply-To: <3731D16A.27667779@MexComUSA.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 May 1999, Edwin Culp wrote: > I'm installing a Lucent access-point, now. Would this driver work on current or would > the newbus changes be a problem? Where can the code be found or has it been commited? Bill fixed the only recent breakage with pccard so it should work fine. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 1:36:37 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id AE38E15CC6 for ; Fri, 7 May 1999 01:36:22 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id RAA10810; Fri, 7 May 1999 17:36:01 +0900 (JST) Date: Fri, 7 May 1999 17:36:01 +0900 (JST) Message-Id: <199905070836.RAA10810@afs.ntc.mita.keio.ac.jp> To: mharo@area51.fremont.ca.us Cc: freebsd-mobile@freebsd.org, hosokawa@itc.keio.ac.jp Subject: Re: Which pccard network card? In-Reply-To: Your message of "Fri, 7 May 1999 16:45:26 JST". <19990507004526.A21702@area51.fremont.ca.us> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990507004526.A21702@area51.fremont.ca.us> mharo@area51.fremont.ca.us writes: >> Hi, I'm planning on buying a laptop soon and I was wondering >> which pccard (type 2) network card I should buy. I'm probably >> just going to stick with 10mbit due to cost, but if 100mbit >> isn't much more expensive then I'll probably do that. What >> cards does FreeBSD support well? Think I should install PAO >> on my laptop when I get it? Currently, 100Mbps cards supported by PAO are slower than fast 10Mbps card. I don't recommend them if you have had switching hub already. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 1:46:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from logatome.micronet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 6C0FB1532D for ; Fri, 7 May 1999 01:46:47 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from kisoft-services.com (Nantes10.francenet.net [193.149.110.74]) by logatome.micronet.fr (8.8.8/8.8.8) with ESMTP id KAA22913 for ; Fri, 7 May 1999 10:45:33 +0200 (CEST) Message-ID: <3732A881.A3C96F6D@kisoft-services.com> Date: Fri, 07 May 1999 10:46:57 +0200 From: Eric MASSON Organization: Kisoft Services X-Mailer: Mozilla 4.5 [fr] (WinNT; I) X-Accept-Language: fr MIME-Version: 1.0 To: Mailing list FreeBSD Mobile Subject: Driver for 3Com Megahertz 3CCFEM556BI multifunction NIC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I own a Thinkpad 390 and a 3Com Megahertz 3CCFEM556BI NIC (Lan 10/100 + V90 Modem). I'm looking for a driver to make this PCCARD work under 3.1-STABLE. Regards. Eric MASSON (Developper, France) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 6:27:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id CFC6614E23 for ; Fri, 7 May 1999 06:27:37 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 17037 invoked from network); 7 May 1999 13:27:36 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 7 May 1999 13:27:36 -0000 Date: Fri, 7 May 1999 08:27:36 -0500 (CDT) From: John Sconiers To: HOSOKAWA Tatsumi Cc: mharo@area51.fremont.ca.us, freebsd-mobile@FreeBSD.ORG Subject: Re: Which pccard network card? In-Reply-To: <199905070836.RAA10810@afs.ntc.mita.keio.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Currently, 100Mbps cards supported by PAO are slower than fast 10Mbps > card. I don't recommend them if you have had switching hub already. > Then what 10mb cards are supported?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 6:41:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from crash.lovett.com (crash.lovett.com [38.155.241.4]) by hub.freebsd.org (Postfix) with ESMTP id DB81F14DC6 for ; Fri, 7 May 1999 06:41:24 -0700 (PDT) (envelope-from ade@lovett.com) Received: from ade by crash.lovett.com with local (Exim 2.12 #1) id 10fkr2-00056G-00; Fri, 7 May 1999 08:39:52 -0500 Date: Fri, 7 May 1999 08:39:52 -0500 From: Ade Lovett To: HOSOKAWA Tatsumi Cc: freebsd-mobile@freebsd.org Subject: Re: Which pccard network card? Message-ID: <19990507083952.C19453@remarq.com> References: <19990507004526.A21702@area51.fremont.ca.us> <199905070836.RAA10810@afs.ntc.mita.keio.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905070836.RAA10810@afs.ntc.mita.keio.ac.jp>; from HOSOKAWA Tatsumi on Fri, May 07, 1999 at 05:36:01PM +0900 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 07, 1999 at 05:36:01PM +0900, HOSOKAWA Tatsumi wrote: > > Currently, 100Mbps cards supported by PAO are slower than fast 10Mbps > card. I don't recommend them if you have had switching hub already. Interesting. What transfer rates are you seeing with 100Mbit cards.. general consensus of opinion is around 1.1-1.3MB/sec using the non-PAO if_xe Xircom drivers. Still not amazing, but certainly faster than any 10baseT pc-card I've tried. -aDe -- Ade Lovett, RemarQ Communities, Inc., San Jose, CA. mailto:ade@remarq.com http://www.remarq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 7: 7:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (Postfix) with ESMTP id 35969152F6 for ; Fri, 7 May 1999 07:07:30 -0700 (PDT) (envelope-from root@wagsky.com) Received: from localhost (root@localhost) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id HAA00963; Fri, 7 May 1999 07:07:25 -0700 (PDT) (envelope-from root@wagsky.com) Date: Fri, 7 May 1999 07:07:25 -0700 (PDT) From: Jeff Kletsky To: Michael Haro Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Which pccard network card? In-Reply-To: <19990507004526.A21702@area51.fremont.ca.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 May 1999, Michael Haro wrote: > Hi, I'm planning on buying a laptop soon and I was wondering > which pccard (type 2) network card I should buy. I'm probably > just going to stick with 10mbit due to cost, but if 100mbit > isn't much more expensive then I'll probably do that. What > cards does FreeBSD support well? I've had good luck with the LinkSys 100Base/T card -- about $75. Cheap and functional (so I don't need dual-speed hubs here). Speed? Who knows, but I'm not planning to use my notebook as a server ;-) You will need the patches by Asami to get if_ed.c to recognize the card. > Think I should install PAO on my laptop when I get it? Now we're getting into "religion" -- I'll just say that 3.1-STABLE works just fine for my needs... Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 10:55:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from kent.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id BB11514EF8 for ; Fri, 7 May 1999 10:55:32 -0700 (PDT) (envelope-from kent@kent.tfd.com) Received: (from kent@localhost) by kent.tfd.com (8.9.2/8.9.2) id NAA00248 for mobile@freebsd.org; Fri, 7 May 1999 13:58:48 -0400 (EDT) (envelope-from kent) Date: Fri, 7 May 1999 13:58:48 -0400 (EDT) From: Kent Hauser Message-Id: <199905071758.NAA00248@kent.tfd.com> To: mobile@freebsd.org Subject: pccard.conf entry help needed Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, In my continuing quest to get a serial port working for my new ThinkPad, I obtained one of the "socket communications" serial port PCMCIA cards. It's supposed to look like a standard serial port -- and so I assumed the modem card support would be sufficient. It might be, but at the very least, I am unable to get my "pccard.conf" entry correct. Attached is the kernel "sio" device declarations, a small excerpt of the /var/log/messages file, my attempt at a pccard.conf entry, and the dumpcis output. And I do have other pccard stuff running on the machine. This email is coming to you via my 5C589 & the ep0 driver. Any help sorting this out would be greatly appreciated. Thanks. Kent =========== >>> kernel config excerpt: device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? port "IO_COM3" tty irq 5 device sio3 at isa? port "IO_COM4" tty irq 9 =========== >>> /var/log/messages messages: May 7 13:48:56 kent /kernel: psm0: model Generic PS/2 mouse, device ID 0 May 7 13:48:56 kent /kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 May 7 13:48:56 kent /kernel: sio0 not found at 0x3f8 May 7 13:48:56 kent /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 May 7 13:48:56 kent /kernel: sio1 not found at 0x2f8 May 7 13:48:56 kent /kernel: sio2: configured irq 5 not in bitmap of probed irqs 0 May 7 13:48:56 kent /kernel: sio2 not found at 0x3e8 May 7 13:48:56 kent /kernel: sio3: configured irq 9 not in bitmap of probed irqs 0 May 7 13:48:56 kent /kernel: sio3 May 7 13:48:56 kent /kernel: not found at 0x2e8 ... May 7 13:48:56 kent /kernel: Initializing PC-card drivers: ed May 7 13:48:56 kent /kernel: changing root device to wd0s2a May 7 13:48:56 kent /kernel: PC-Card Intel 82365 (5 mem & 2 I/O windows) May 7 13:48:56 kent /kernel: pcic: controller irq 3 May 7 13:48:56 kent /kernel: Card inserted, slot 0 May 7 13:48:56 kent /kernel: Card inserted, slot 1 May 7 13:48:59 kent pccardd[58]: Resource allocation failure for Socket Communications Inc May 7 13:49:09 kent /kernel: ep0: utp/bnc[*UTP*] address 00:a0:24:65:76:28 May 7 13:49:09 kent routed[89]: ignore RTM_ADD without gateway May 7 13:49:09 kent routed[89]: write(rt_sock) RTM_ADD 10.9.0.0/16 --> 10.9.200.50: File exists May 7 13:49:09 kent pccardd[58]: pccardd started =========== >>> pccard.conf excerpt: # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 3 5 10 11 13 15 # Available memory slots memory 0xd4000 96k # Serial IO adapter card "Socket Communications Inc" "Serial Port Adapter Revision " config 0x5 "sio2" 5 insert echo Serial I/O inserted remove echo Serial I/O removed ================ >>> pccardc dumpcis: output Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: d4 3a Common memory device information: Device number 1, type Function specific, WPS = OFF Speed = 100nS, Memory block size = 8Kb, 8 units Tuple #2, code = 0x10 (Checksum), length = 5 000: 07 00 e8 00 6f Checksum from offset 7, length 232, value is 0x6f Tuple #3, code = 0x17 (Attribute memory descriptor), length = 2 000: d4 3a Attribute memory device information: Device number 1, type Function specific, WPS = OFF Speed = 100nS, Memory block size = 8Kb, 8 units Tuple #4, code = 0x14 (No link), length = 0 Tuple #5, code = 0x20 (Manufacturer ID), length = 4 000: 04 01 01 00 PCMCIA ID = 0x104, OEM ID = 0x1 Tuple #6, code = 0x21 (Functional ID), length = 2 000: 02 01 Serial port/modem - POST initialize Tuple #7, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 7f Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #8, code = 0x15 (Version 1 info), length = 59 000: 04 01 53 6f 63 6b 65 74 20 43 6f 6d 6d 75 6e 69 010: 63 61 74 69 6f 6e 73 20 49 6e 63 00 53 65 72 69 020: 61 6c 20 50 6f 72 74 20 41 64 61 70 74 65 72 20 030: 52 65 76 69 73 69 6f 6e 20 42 00 Version = 4.1, Manuf = [Socket Communications Inc],card vers = [Serial Port Adapter Revision B] Addit. info = [],[] Tuple #9, code = 0x1a (Configuration map), length = 5 000: 01 00 00 80 0f Reg len = 2, config register addr = 0x8000, last config = 0x0 Registers: XXXX---- Tuple #10, code = 0x1b (Configuration entry), length = 19 000: c1 41 99 49 55 2d 54 23 30 ff ff 20 c1 05 43 4f 010: 4d 58 00 Config index = 0x1(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Card decodes 3 address lines, 8 Bit I/O only IRQ modes: Level IRQ level = 3 Max twin cards = 0 Misc attr: (Read-only) (Power down supported) Tuple #11, code = 0x1b (Configuration entry), length = 23 000: c3 41 99 49 55 2d 54 b0 60 f8 03 07 30 10 00 20 010: c1 05 43 4f 4d 31 00 Config index = 0x3(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Card decodes 16 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level IRQs: 4 5 12 Max twin cards = 0 Misc attr: (Power down supported) Tuple #12, code = 0x1b (Configuration entry), length = 23 000: c5 41 99 49 55 2d 54 b0 60 f8 02 07 30 08 00 20 010: c1 05 43 4f 4d 32 00 Config index = 0x5(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Card decodes 16 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 IRQ modes: Level IRQs: 4 5 11 Max twin cards = 0 Misc attr: (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 23 000: c7 41 99 49 55 2d 54 b0 60 e8 03 07 30 10 00 20 010: c1 05 43 4f 4d 33 00 Config index = 0x7(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Card decodes 16 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 IRQ modes: Level IRQs: 4 5 12 Max twin cards = 0 Misc attr: (Power down supported) Tuple #14, code = 0x1b (Configuration entry), length = 23 000: c9 41 99 49 55 2d 54 b0 60 e8 02 07 30 08 00 20 010: c1 05 43 4f 4d 34 00 Config index = 0x9(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Card decodes 16 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 IRQ modes: Level IRQs: 4 5 11 Max twin cards = 0 Misc attr: (Power down supported) Tuple #15, code = 0x1b (Configuration entry), length = 18 000: c0 40 e1 49 55 2d 54 48 01 80 00 20 c1 04 4d 45 010: 4d 00 Config index = 0x0(default) Interface byte = 0x40 (memory) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2.5 x 10mA Power down supply current: 5 x 1mA Memory descriptor 1 blk length = 0x100 card addr = 0x8000 Max twin cards = 0 Misc attr: (Power down supported) Tuple #16, code = 0xff (Terminator), length = 0 2 slots found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 12:42:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ThinkPad.katz.de (dieringe.dialup.fu-berlin.de [160.45.221.216]) by hub.freebsd.org (Postfix) with ESMTP id 895CE14CFB for ; Fri, 7 May 1999 12:42:36 -0700 (PDT) (envelope-from martin@dieringe.dialup.fu-berlin.de) Received: from localhost (localhost.katz.de [127.0.0.1]) by ThinkPad.katz.de (8.8.8/8.8.8) with ESMTP id VAA04124; Fri, 7 May 1999 21:09:38 +0200 (CEST) (envelope-from martin@dieringe.dialup.fu-berlin.de) Date: Fri, 7 May 1999 21:09:37 +0200 (CEST) From: Martin Dieringer X-Sender: martin@ThinkPad.katz.de Reply-To: Martin Dieringer To: Kent Hauser Cc: mobile@FreeBSD.ORG Subject: Re: pccard.conf entry help needed In-Reply-To: <199905071758.NAA00248@kent.tfd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have no problems with the Thinkpad 600(not E)'s serial port. my config is device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? disable port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr and I get sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A When I insert my modem card, I get sio2 Card inserted, slot 0 sio2: type 16550A pccard.conf: # Megahertz XJ1336 card "U.S. Robotics" "XJ/CC1336" config 0x23 "sio2" 10 insert echo U.S. Robotics XJ/CC1336 inserted remove echo U.S. Robotics XJ/CC1336 removed (this in on 2.2.8, but I remember that this worked the same way with 3.1-STABLE) just add "vector siointr" to your kernel-config! martin On Fri, 7 May 1999, Kent Hauser wrote: > In my continuing quest to get a serial port working for my new > ThinkPad, I obtained one of the "socket communications" serial port > PCMCIA cards. It's supposed to look like a standard serial port -- > and so I assumed the modem card support would be sufficient. It might > be, but at the very least, I am unable to get my "pccard.conf" entry > correct. > > =========== > >>> kernel config excerpt: > > device sio0 at isa? port "IO_COM1" tty irq 4 > device sio1 at isa? port "IO_COM2" tty irq 3 > device sio2 at isa? port "IO_COM3" tty irq 5 > device sio3 at isa? port "IO_COM4" tty irq 9 > =========== > >>> /var/log/messages messages: > > May 7 13:48:56 kent /kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 > May 7 13:48:56 kent /kernel: sio0 not found at 0x3f8 > May 7 13:48:56 kent /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 > May 7 13:48:56 kent /kernel: sio1 not found at 0x2f8 > May 7 13:48:56 kent /kernel: sio2: configured irq 5 not in bitmap of probed irqs 0 > May 7 13:48:56 kent /kernel: sio2 not found at 0x3e8 > May 7 13:48:56 kent /kernel: sio3: configured irq 9 not in bitmap of probed irqs 0 > May 7 13:48:56 kent /kernel: sio3 > May 7 13:48:56 kent /kernel: not found at 0x2e8 > May 7 13:48:59 kent pccardd[58]: Resource allocation failure for Socket Communications Inc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 18:19:15 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dcarmich.xnet.com (dcarmich.xnet.com [205.243.153.129]) by hub.freebsd.org (Postfix) with ESMTP id 9E86114CE0 for ; Fri, 7 May 1999 18:19:10 -0700 (PDT) (envelope-from dcarmich@dcarmich.xnet.com) Received: from localhost (dcarmich@localhost) by dcarmich.xnet.com (8.9.2/8.9.2) with ESMTP id UAA01598 for ; Fri, 7 May 1999 20:19:15 -0500 (CDT) (envelope-from dcarmich@dcarmich.xnet.com) Date: Fri, 7 May 1999 20:19:12 -0500 (CDT) From: Douglas Carmichael To: freebsd-mobile@freebsd.org Subject: Do you guys run your ThinkPads with FreeBSD only or FreeBSD/Windoze? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm considering getting a ThinkPad 600E to run FreeBSD 3.x and I'd like to get your opinions on it. 1) Do any of you run yours in "dangerously dedicated" mode with FreeBSD or do you have to keep Windoze around to configure the ThinkPad? 2) How will does it work with PAO3? (any glitches??) 3) Does XFree86 work on it or do you have to purchase AccelX? Any and all comments would be appreciated. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 21:25:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 966DD1566D for ; Fri, 7 May 1999 21:25:35 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA04189; Fri, 7 May 1999 22:25:35 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA02958; Fri, 7 May 1999 22:25:34 -0600 Date: Fri, 7 May 1999 22:25:34 -0600 Message-Id: <199905080425.WAA02958@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Douglas Carmichael Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Do you guys run your ThinkPads with FreeBSD only or FreeBSD/Windoze? In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm considering getting a ThinkPad 600E to run FreeBSD 3.x and I'd like to > get your opinions on it. > > 1) Do any of you run yours in "dangerously dedicated" mode with FreeBSD or > do you have to keep Windoze around to configure the ThinkPad? I'm running both, but I'm also running 2.2.8 on my box instead of 3.X. > 2) How will does it work with PAO3? (any glitches??) No idea. It runs great in 2.2.8 if you merge in the very simple changes for CardBus bridge probing from 3.*. > 3) Does XFree86 work on it or do you have to purchase AccelX? XFree86 works great. The CD works, the PCMCIA stuff (no CardBus support in any FreeBSD release yet), APM seems to work (although I haven't tried it much). However, I haven't gotten sound to work yet. It panics when I use a line someone else sent me, and I haven't been motivated to figure out what the problem is. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 7 21:57: 1 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rgate2.ricochet.net (rgate2.ricochet.net [204.179.143.3]) by hub.freebsd.org (Postfix) with ESMTP id EF64914C0C for ; Fri, 7 May 1999 21:56:59 -0700 (PDT) (envelope-from shibumi@ricochet.net) Received: from miranda.marchordie.org (mg-20425426-37.ricochet.net [204.254.26.37]) by rgate2.ricochet.net (8.9.3/8.9.3) with ESMTP id XAA08419 for ; Fri, 7 May 1999 23:56:55 -0500 (CDT) Received: from localhost by miranda.marchordie.org (8.9.2) id VAA01853; Fri, 7 May 1999 21:57:05 -0700 (PDT) Message-Id: <199905080457.VAA01853@miranda.marchordie.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-mobile@FreeBSD.ORG Subject: Re: Do you guys run your ThinkPads with FreeBSD only or FreeBSD/Windoze? In-reply-to: Your message of "Fri, 07 May 1999 20:19:12 CDT." Reply-To: shibumi@marchordie.org X-Disclaimer: Unless otherwise noted below, this is not a policy statement X-Url: http://www.shockwave.org/~shibumi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 21:57:05 -0700 From: "Kenton A. Hoover" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 1) You have to keep a DOS partition if you want hibernation to work (the hibernation file has to be a DOS file) 2) I haven't been able to get the PAO3 APM drivers to work on a TP600 yet. 3) You can get XFree to work, but you should spend the money on AccelX, as its much faster. On Fri, 07 May 1999 20:19:12 CDT, Sendmail channeled Douglas Carmichael saying: > I'm considering getting a ThinkPad 600E to run FreeBSD 3.x and I'd like to > get your opinions on it. > > 1) Do any of you run yours in "dangerously dedicated" mode with FreeBSD or > do you have to keep Windoze around to configure the ThinkPad? > > 2) How will does it work with PAO3? (any glitches??) > > 3) Does XFree86 work on it or do you have to purchase AccelX? > > Any and all comments would be appreciated. | Kenton A. Hoover | shibumi@marchordie.org | | Private Citizen | | | San Francisco, California | | |===================== http://www.shockwave.org/~shibumi ====================| | The dictatorship means -- learn this once and for all -- unrestrained | | power based on force, not on law. -- V. I. Lenin | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 8 4:26:55 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ThinkPad.katz.de (dieringe.dialup.fu-berlin.de [160.45.221.216]) by hub.freebsd.org (Postfix) with ESMTP id BC50C15489 for ; Sat, 8 May 1999 04:26:48 -0700 (PDT) (envelope-from martin@dieringe.dialup.fu-berlin.de) Received: from localhost (localhost.katz.de [127.0.0.1]) by ThinkPad.katz.de (8.8.8/8.8.8) with ESMTP id NAA00691 for ; Sat, 8 May 1999 13:09:16 +0200 (CEST) (envelope-from martin@dieringe.dialup.fu-berlin.de) Date: Sat, 8 May 1999 13:09:16 +0200 (CEST) From: Martin Dieringer X-Sender: martin@ThinkPad.katz.de Reply-To: Martin Dieringer To: freebsd-mobile@FreeBSD.ORG Subject: Re: Do you guys run your ThinkPads with FreeBSD only or FreeBSD/Windoze? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 May 1999, Douglas Carmichael wrote: > I'm considering getting a ThinkPad 600E to run FreeBSD 3.x and I'd like to > get your opinions on it. > > 1) Do any of you run yours in "dangerously dedicated" mode with FreeBSD or > do you have to keep Windoze around to configure the ThinkPad? I have a 600 and use windoze to configure and to have the hibernation file (but you could do this with DOS only) > 2) How will does it work with PAO3? (any glitches??) I don't use PAO for 3.1-STABLE. I can't suspend with pccards inserted and 'zzz' doesn't work (suspend only by hotkey). but that will with PAO. Hibernation works. The trackpoint works, all three buttons, but without pushing on the point itself to click (which is unusable anyway). Sound works, too (pcm driver). You have to take out your expansion memory and install with <=64MB, then set up a kernel with a MAXMEM line. > 3) Does XFree86 work on it or do you have to purchase AccelX? XFree works fine since 3.3.3.1 XFree86 Version 3.3.3.1 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 4 1999 (--) SVGA: PCI: NeoMagic NM2160 rev 1, Memory @ 0xe0000000, 0x20000000 (--) SVGA: chipset: NM2160 (--) SVGA: videoram: 2048k (**) SVGA: Using 16 bpp, Depth 16, Color weight: 565 (**) SVGA: Mode "1024x768": mode clock = 85.000 (--) SVGA: Virtual resolution set to 1024x768 (--) SVGA: NeoMagic MagicGraph 128XD (NM2160) chip (--) SVGA: NM2160: Panel is a 1024x768 color TFT display Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message