Date: Fri, 25 Jul 1997 14:59:35 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: hosokawa@jp.FreeBSD.org, current@FreeBSD.ORG Subject: Re: Well, I finally bought a test laptop and decided to jump in... Message-ID: <199707250529.OAA20122@genesis.atrad.adelaide.edu.au> In-Reply-To: <13127.869764432@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 24, 97 10:13:52 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard stands accused of saying: > > Now I'm up with 2.2.2 and the pccard support has, of course, > disappeared so I'm patching in the PAO-970616 stuff and I'm noticing I would have suggested _not_ taking this step initially. The LINKSYS card is, IIRC, an NE2000 clone which works just fine with the stock code. > enabled kernel of my own. Then comes the hassling with the contents > of /etc/*pccard* and getting them updated, but after a few false > starts and the insertion of a 10 second sleep into the file which > starts pccardd so that it can have my ethernet device configured > _before_ the other ifconfig stuff is run, it's working. Yay. Why is this an issue? There are hooks specifically in place for doing interface configuration on the fly as cards arrive and depart. Aren't they well-enough advertised? > Conclusions: This is harder than it needs to be and it really should > be better integrated with the system - I understand that some of this > stuff is "experimental", but where better to test and develop it than > in FreeBSD's CVS repository? Because, no insult to the Nomads intended, Nate didn't (and I agree with him) feel that bringing in a great deal of cruft was a good trade for the resultant functionality. I'm inclined to think that real PnP support is going to have somewhat of a drastic effect on the shape of PCCARD support and implementation too. > To all these ends, I'm willing to help test, integrate and import this > stuff into -current but I need to know if the 2.2.2 stuff is a good > starting place. Some things appear to no longer be quite in sync > there, such as the shutdown mods which don't appear to use the fancier > callout list that was introduced in 3.0, and I'm also fairly sure that > a little editing will have to take place with the /etc files to bring > them up to date. I'm also not sure about the current state of > integration with the APM code - the patches there would not apply at > all, leading me to believe that the APM bits in the 2.2.2 PAO kit are > already in -current. There were some fixes to the APM code done a little while back (by Garret?) which may be interfering here. You're spot-on the money wrt. the need to clean things up though. > Shall we get this stuff into 3.0? It's light-years better than what > we have now, and had it not been for the PAO kit I would not have had > an easy time of installing this machine at all. By not integrating > the PAO stuff in all this time, we've denied laptop users the ability > to install the 3.0 SNAPs and that's an unfortunate situation which > should be fixed. Ideally, I think no. Pragmatically, I suspect that you're right, and that until the code is right there in front of people, annoying them, nothing is going to happen. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707250529.OAA20122>