Re: HEADS UP!!!! Important instructions for -current users!
To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? Yes. Nick FreeBSD USB Project. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Peer review (was: HEADS UP!!!! Important instructions for -current users!)
On Tue, 20 Apr 1999, Greg Lehey wrote: On Monday, 19 April 1999 at 21:46:30 -0700, Jordan K. Hubbard wrote: integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. But as we have seen, posting on -hackers doesn't guarantee that anybody of any importance will see it. Possibly -current is better for ongoing development reports. I read both :-) -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Peer review (was: HEADS UP!!!! Important instructions for -current users!)
I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. But as we have seen, posting on -hackers doesn't guarantee that anybody of any importance will see it. Possibly -current is better for ongoing development reports. I read both :-) Which means that someone will crosspost it if necessary... Post and forget. Nick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Thank you for the update on progress of new config, Nishiyama-san. Are snapshots of the new config work available to members outside the development team? If so, can you post a URL pointing to them. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
From: Warner Losh i...@harmony.village.org Subject: Re: HEADS UP Important instructions for -current users! Date: Tue, 20 Apr 1999 09:27:56 -0600 Message-ID: 199904201527.jaa03...@harmony.village.org imp Thank you for the update on progress of new config, Nishiyama-san. imp Are snapshots of the new config work available to members outside the imp development team? If so, can you post a URL pointing to them. Yes, the source code is available to everyone in the world. General information is shown at http://www.jp.freebsd.org/newconfig/ Snapshots will appear at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/newconfig/snapshot/ You can also CVSup newconfig source from cvsup.jp.FreeBSD.ORG or its mirrors (cvsup[2-5].jp.FreeBSD.ORG). Example of CVSup file is: begin example # Defaults that apply to all the collections *default host=cvsup.jp.freebsd.org *default base=/some/where/you/want *default prefix=/some/where/you/want/prefix *default release=cvs *default delete use-rel-suffix jp-newconfig end example The test implementation code of dynamic configuration by UCHIYAMA Yasushi [newconfig-jp 1710] is at ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/ sys4c990410-newconfig990413-kld990419test2.patch.gz Note that this code is a test implementation and does not yet work completely. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
imp Let us not forget that much of the newconfig work can be used with imp newconfig shims in the newbus scheme. If you are to construct a newconfig shim in the new-bus scheme, it means that you'll have two interface to device drivers. Then, you should consider, whether it is better to make a newconfig shim in the new-bus scheme than to make a new-bus shim in the newconfig scheme. By the way, how can I subscribe new-bus mailing list? It does not seem to be controlled by majord...@freebsd.org. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
jkh I don't go to new-bus, this direction is disunion of BSDs. It is jkh bad decision. jkh jkh I'm sorry that you feel this way, but I can only re-state that better jkh communication could have prevented this in the first place and hope jkh that you've learned your own lessons from this exercise. If you jkh haven't, then a good opportunity for learning has simply been wasted. One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated jkh the difference with new-bus being jkh that we were working just that much more closely with Doug Rabson (and jkh the others helping him) and had already used the new-bus stuff for jkh FreeBSD/alpha. Nakagawa would not be so upset if you could convince him that new-bus were superior. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated I don't think they're so far apart that there's a clear superiority, and we certainly didn't get that impression from any of the discussions we saw between you guys and the new-bus folks. All I saw were some strong differences of opinion being expressed and a good chance that superiority would never be objectively determined by any of the parties involved. Nakagawa would not be so upset if you could convince him that new-bus were superior. Again, this appeared to be a matter of fierce argument more than anything else and I'd probably be just as inclined to try and get a Mercedes owner to agree that BMW made a superior car when, in fact, both vehicles provide a more than adequate ride and have a number of nice features. Given that neither system is exactly standing still, it also meant that relative superiority was a constantly changing factor and even though it might have been possible to say that newconfig was superior on one month, it would be by no means assured that this would remain a constant. What it ultimately came down to, as I said before, was choosing the group we had the best communication with and had some existing precedent, in new-bus's case that being FreeBSD/alpha. We learned a lot of painful lessons from the PAO project given the difficulties we've had with integrating that technology on an ongoing basis, and those are lessons we had no wish to learn again. Judging superiority is only partially a technical issue, and there are many other factors of equal importance when you start discussing projects of long-term significance to FreeBSD. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
As Warner Losh wrote ... In message 199904181923.naa25...@mt.sri.com Nate Williams writes: : This is wonderful, but has this ever happened in our mailing lists? I : guess I don't remember anyone *ever* ridiculing or harassing someone for : not being fluent in the language. I have seen people ask others to explain again since they didn't understand, but I cannot recall ever seeing anybody holding someone up to ridicule publically. I have deep respect for several people that have pushed through the language barrier. Maybe we should decide that this is a thing to keep in mind and let it rest for now? Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
--- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm pe...@netplex.com.au, d...@freebsd.org Cc: s...@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.95c7b1...@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 br...@keep.lan.awfulhak.org 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 br...@awfulhak.orgbr...@freebsd.org http://www.Awfulhak.org br...@openbsd.org Don't _EVER_ lose your sense of humour ! br...@uk.freebsd.org --- End of Blind-Carbon-Copy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
from my understanding, the biggest difference is that New-bus is being designed to eventually delegate 'config' to a very minor role where newconfig (as it's name suggests' maintains 'config' a s a major component.. It has been a long standing goal of FreeBSD to make the system as dynamic as possible. My personal goal is to see it more dynamically configurable than NT with all it's DLLs. julian On Mon, 19 Apr 1999, Tomoaki NISHIYAMA wrote: jkh I don't go to new-bus, this direction is disunion of BSDs. It is jkh bad decision. jkh jkh I'm sorry that you feel this way, but I can only re-state that better jkh communication could have prevented this in the first place and hope jkh that you've learned your own lessons from this exercise. If you jkh haven't, then a good opportunity for learning has simply been wasted. One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated jkh the difference with new-bus being jkh that we were working just that much more closely with Doug Rabson (and jkh the others helping him) and had already used the new-bus stuff for jkh FreeBSD/alpha. Nakagawa would not be so upset if you could convince him that new-bus were superior. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
From: Julian Elischer jul...@whistle.com Subject: Re: HEADS UP Important instructions for -current users! Date: Mon, 19 Apr 1999 19:59:03 -0700 (PDT) Message-ID: pine.bsf.3.95.990419195617.11256a-100...@current1.whistle.com julian from my understanding, the biggest difference is that New-bus julian is being designed to eventually delegate 'config' to a very minor role julian where newconfig (as it's name suggests' maintains 'config' a s a major julian component. You should not forget that newconfig is a different thing from the old config. It will remove the illness of the old config. julian It has been a long standing goal of FreeBSD to make the system julian as dynamic as possible. My personal goal is to see it more dynamically julian configurable than NT with all it's DLLs. By now, newconfig people decided to continue its development until its dynamic configuration stuff works under FreeBSD, despite the decision to merge newbus into the main CVS repository You can see the implementation of dynamic configuration under newconfig, which means that you have one more chance to integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. Currently proposed schedule is on April 21 import sys4c990410 syncing and test around April 28 import PRE_NEWBUS Achievement is now announced in newconfig mailing list (newcon...@jp.freebsd.org, controlled by majord...@jp.freebsd.org). Although most discussion are done in Japanese in newconfig-jp mailing list but any comment, suggestion, or question in English to newcon...@jp.freebsd.org will be appreciated. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Peer review (was: HEADS UP!!!! Important instructions for -current users!)
On Monday, 19 April 1999 at 21:46:30 -0700, Jordan K. Hubbard wrote: integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. But as we have seen, posting on -hackers doesn't guarantee that anybody of any importance will see it. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. It looks like the stat clock isn't started after this. I have tried a SMP and UNI kernel and both behave the same. Looking with vmstat -i and systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate also have profhz and stathz as 100. A kernel of about a week ago doesn't have this problem. John -- John Hay -- john@mikom.csir.co.za To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
John Hay wrote:
As of a few minutes ago, a minimal set of changes to bring the so-called
'new-bus' functionality to the i386 kernel in -current.
It looks like the stat clock isn't started after this. I have tried a SMP
and UNI kernel and both behave the same. Looking with vmstat -i and
systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate
also have profhz and stathz as 100. A kernel of about a week ago doesn't
have this problem.
Hmm...
[7:38pm]~-103# sysctl kern.clockrate
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 1024,
stathz = 128 }
And from systat:
zfod Interrupts
Proc:r p d s wCsw Trp Sys Int Sof Fltcow 230 total
2 2 23592 141 230 306 16016 wirepci irq11
15636 act 2 pci irq5
1.1%Sys 1.1%Intr 0.8%User 97.0%Nice 0.0%Idl24480 inact pci irq6
|||||||||| 3736 cache pci irq4
=-- 1400 freepci irq7
daefr 100 clk0 irq2
Namei Name-cacheDir-cache prcfr 128 rtc0 irq8
The labelling of the source column is known to be broken at the moment, there
are a number of key places where the fake isa unit number is getting passed
down to the lower level code. This will be fixed up shortly.
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Let us not forget that much of the newconfig work can be used with newconfig shims in the newbus scheme. Probably some simple drivers for newconfig works with newconfig shims, but bus code that depends on newconfig may not work. I don't go to new-bus, this direction is disunion of BSDs. It is bad decision. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
I don't go to new-bus, this direction is disunion of BSDs. It is bad decision. I'm sorry that you feel this way, but I can only re-state that better communication could have prevented this in the first place and hope that you've learned your own lessons from this exercise. If you haven't, then a good opportunity for learning has simply been wasted. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
John Hay wrote:
As of a few minutes ago, a minimal set of changes to bring the so-called
'new-bus' functionality to the i386 kernel in -current.
It looks like the stat clock isn't started after this. I have tried a SMP
and UNI kernel and both behave the same. Looking with vmstat -i and
systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate
also have profhz and stathz as 100. A kernel of about a week ago doesn't
have this problem.
Hmm...
[7:38pm]~-103# sysctl kern.clockrate
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 1024,
stathz = 128 }
Ok, I have found it. My kernel still had the apm line from its GENERIC
days, which didn't hurt me before:
device apm0at nexus? disable flags 0x31 # Advanced Power Management
It seems that the disable keyword is ignored, because the apm0 device
suddenly appeared in the probe messages and that set statclock_disable to 1.
I have removed apm from my kernel config file and all is well again.
John
--
John Hay -- john@mikom.csir.co.za
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
On Sun, 18 Apr 1999, John Hay wrote:
John Hay wrote:
As of a few minutes ago, a minimal set of changes to bring the so-called
'new-bus' functionality to the i386 kernel in -current.
It looks like the stat clock isn't started after this. I have tried a SMP
and UNI kernel and both behave the same. Looking with vmstat -i and
systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate
also have profhz and stathz as 100. A kernel of about a week ago doesn't
have this problem.
Hmm...
[7:38pm]~-103# sysctl kern.clockrate
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 1024,
stathz = 128 }
Ok, I have found it. My kernel still had the apm line from its GENERIC
days, which didn't hurt me before:
device apm0at nexus? disable flags 0x31 # Advanced Power
Management
It seems that the disable keyword is ignored, because the apm0 device
suddenly appeared in the probe messages and that set statclock_disable to 1.
I have removed apm from my kernel config file and all is well again.
This should be fixed. I changed the apm driver to honour the disabled
keyword.
--
Doug Rabson Mail: d...@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
I would ask people to STOP DOING THIS. Do not harass or ridicule someone for not being fluent in english! Now, it is sorely true that someone wil Let me just reinforce this statement. This is wonderful, but has this ever happened in our mailing lists? I guess I don't remember anyone *ever* ridiculing or harassing someone for not being fluent in the language. Nate To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
John Hay wrote: As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. It looks like the stat clock isn't started after this. I have tried a SMP and UNI kernel and both behave the same. Looking with vmstat -i and systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate also have profhz and stathz as 100. A kernel of about a week ago doesn't have this problem. There are also some funny results in systat -vmstat; lots of interrupt names are wrong; a pnp-probed sound card is listed as ??? irq5, and everything else except clk0 int0 and rtc0 irq8 are listed as pci irqNN (with NN replaced some believable number). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
: that someone wil : : Let me just reinforce this statement. : :This is wonderful, but has this ever happened in our mailing lists? I :guess I don't remember anyone *ever* ridiculing or harassing someone for :not being fluent in the language. : :Nate Oh sure, it happens quite often. I've seen people 'talk down' to other people lots of time in responding to their questions. I see it most often when the person who posted the question has trouble with the language. Sometimes you can just see how much time it took the guy to ooze-out a single sentence and it really makes me angry when all they get for their trouble is a flip answer from some bozo. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Mark Murray wrote: John Hay wrote: As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. It looks like the stat clock isn't started after this. I have tried a SMP and UNI kernel and both behave the same. Looking with vmstat -i and systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate also have profhz and stathz as 100. A kernel of about a week ago doesn't have this problem. There are also some funny results in systat -vmstat; lots of interrupt names are wrong; a pnp-probed sound card is listed as ??? irq5, and everything else except clk0 int0 and rtc0 irq8 are listed as pci irqNN (with NN replaced some believable number). Known bogon... In between putting out fires (here), I hope to take a further shot at cleaning up the interrupt layering shortly. I wasn't too worried about that, I didn't think the world would end if the labels fell off the irq table, so I left it out. :-] Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Peter Wemm wrote: Known bogon... In between putting out fires (here), I hope to take a further shot at cleaning up the interrupt layering shortly. ... as I saw 3 messages later. I wasn't too worried about that, I didn't think the world would end if the labels fell off the irq table, so I left it out. :-] No problem. No-one got hurt ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
In message 199904181923.naa25...@mt.sri.com Nate Williams writes: : This is wonderful, but has this ever happened in our mailing lists? I : guess I don't remember anyone *ever* ridiculing or harassing someone for : not being fluent in the language. I have seen people ask others to explain again since they didn't understand, but I cannot recall ever seeing anybody holding someone up to ridicule publically. I have deep respect for several people that have pushed through the language barrier. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
According to David E . O'Brien: Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the config file has both a da0 device (to get the generic SCSI disk code) and disk (to wire it down). I've never defined da* twice in oldconfig-style config. You're not supposed to do that I think. In LINT, there is only one definition. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
According to Peter Wemm: As a special warning: The APIC_IO interrupt management could be a little wonky on systems that require the special mptable fixups. If you have warnings about broken mptables, or additional interrupts being wired, hold back until it's been checked. Seems to work fine on my 2x PPro/200, Intel Providence MB, 64 MB, SMP. I've built but not yet tested the new fxp.ko module though. 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 #15: Sat Apr 17 12:33:10 CEST 1999 robe...@tara:/src/src/sys/compile/TARA_SMP Timecounter i8254 frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = GenuineIntel Id = 0x619 Stepping=9 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 67108864 (65536K bytes) avail memory = 62119936 (60664K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc0307000. Preloaded elf module nfs.ko at 0xc030709c. Preloaded elf module linux.ko at 0xc0307138. Preloaded elf module green_saver.ko at 0xc03071d8. Preloaded elf module procfs.ko at 0xc030727c. Pentium Pro MTRR support enabled, default memory type is uncacheable npx0: math processor on motherboard npx0: INT 16 interface pcib0: PCI host bus adapter on motherboard pci0: PCI bus on pcib0 chip0: Intel 82440FX (Natoma) PCI and memory controller at device 0.0 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet at device 6.0 on pci0 fxp0: interrupting at irq 18 fxp0: Ethernet address 00:a0:c9:49:5a:ef isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 uhci0: Intel 82371SB (PIIX3) USB Host Controller at device 7.2 on pci0 uhci0: interrupting at irq 10 usb0: Intel 82371SB (PIIX3) USB Host Controller on 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 ahc0: Adaptec aic7880 Ultra SCSI adapter at device 9.0 on pci0 ahc0: interrupting at irq 17 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: interrupting at irq 6 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive at fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 psm0: PS/2 Mouse on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: Generic ISA VGA on isa0 sc0: System console on isa0 sc0: VGA color 10 virtual consoles, flags=0x0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 6 lun 0 da0: QUANTUM VIKING II 4.5WLS 4110 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. Is this formal decision of core team ? I feel a huge despair, as a member of newconfig project -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
In message 199904170528.oaa05...@chandra.eatell.msr.prug.or.jp, NAKAGAWA Yoshihisa writes: As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. Is this formal decision of core team ? I feel a huge despair, as a member of newconfig project Yes, this was a decision by the core team. -- Poul-Henning Kamp FreeBSD coreteam member p...@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 majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Is this formal decision of core team ? I feel a huge despair, as a member of newconfig project This was a core team decision, but I really do hope we can still figure out some way of working together on a final hybrid of the best ideas from both projects since this honestly wasn't done with the intention of making the newconfig people unhappy, please believe me. This is simply one of those unfortunate situations where two groups of developers have worked in relative isolation from one another and come up with more or less the same thing, the difference with new-bus being that we were working just that much more closely with Doug Rabson (and the others helping him) and had already used the new-bus stuff for FreeBSD/alpha. The core team did not make this decision lightly and there was considerable debate over it until we finally made the decision to take the clearest choice we could see before us and simply synchronize the FreeBSD/alpha and FreeBSD/x86 code bases. I also have to say that this has pointed out, once again, that communication is really lacking between the various groups, especially in situations where a language barrier exists. Most of us didn't even know about the newconfig project until comparatively recently, and I didn't even really know about it until I saw you guys submit a paper for the FREENIX track at USENIX. Doug's new-bus stuff, on the other hand, was a well known factor for at least a year and, as I noted, had already made it to the Alpha platform, getting it to the x86 simply being a project which was delayed by many various factors. It would, in fact, probably have gone into FreeBSD 6 months ago if everyone involved had simply had a bit more free time. However this situation came about, the core team also ultimately had to make a decision one way or another and no matter *which* alternative we picked, somebody was going to be the loser so it wasn't even as if we had that many good alternatives. The discussions on merging the two efforts really didn't seem to be going anywhere and the more we watched the two groups talk the more it seemed like they simply weren't going to converge on their thinking on this. I don't really like the word loser very much, however, and would much rather that everyone focus instead on the best route forward from here since we've made the decision, for better or for worse, and need to figure out some way for everyone's best ideas to still win in some way. With that in mind, I would be more than happy to take you and all the other newconfig project people out to dinner at the upcoming USENIX conference, perhaps with Satoshi serving as translator, along with Doug Rabson and any other new-bus people who'd like to come. Rather than sinking into despair, we really need to start discussing how to fix the communications problems we've had in the past since that will be addressing the *cause* rather than the symptoms of our current problem. I also truly feel that much can still be salvaged in a number of different ways if we're willing to put the well-being of FreeBSD first and foremost in our minds, and I'm more than happy to do anything I can to make that happen. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
: : Is this formal decision of core team ? I feel a huge despair, as a : member of newconfig project : :This was a core team decision, but I really do hope we can still :figure out some way of working together on a final hybrid of the best :ideas from both projects since this honestly wasn't done with the :... : :I also have to say that this has pointed out, once again, that :communication is really lacking between the various groups, especially :in situations where a language barrier exists. Most of us didn't even :know about the newconfig project until comparatively recently, and I :... : :I don't really like the word loser very much, however, and would :much rather that everyone focus instead on the best route forward from :here since we've made the decision, for better or for worse, and need :... :- Jordan I think Jordan has nailed it on the head, as usual. I would like to address the communications aspect of the problem, because I think it is fairly easy for us to solve it. Simply put, people are not using the 'hackers' mailing list enough. If you notice, whenever I'm working on something that is fairly intrusive to the code base, I post updates to hackers at fairly regular intervals ( or to current if its a patchset for a bug ). I think it is especially important to do this even if there does not appear to be a huge amount of external interest. A week or a month down the line, someone might *become* interested in doing something similar to what you are doing and they aren't going to remember the one message you posted N months ago. As an example of the obviousness of the solution, I would point to CAM. the CAM guys posted updates 'almost' regularly enough. When the time came to shoehorn it into the source tree, there was grumbling but enough people knew it was coming that CAM had no real trouble getting in. I would say that if the CAM group had posted updates more regularly then they did, there would have been even less argument and confusion. If they hadn't posted anything at all, it might not have gotten in at all. Same thing goes here. -- Point #2 : The language barrier. Language is always a barrier, but it is made much worse when people to take a guy to task for his 'bad english'. I would ask people to STOP DOING THIS. Do not harass or ridicule someone for not being fluent in english! Now, it is sorely true that someone will often post to the list a message on the order of my machine crashed, please fix it! without one iota of additional information -- but please, people, be polite! If you don't want to try to help the person, do not answer at all. Else allow other people to lead him through the procedure. Many of these people are trying a hellofalot harder to communicate then us fluent english speakers ( we who tend to not know any language other then english, which is quite sad! ). -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
I would ask people to STOP DOING THIS. Do not harass or ridicule someone for not being fluent in english! Now, it is sorely true that someone wil Let me just reinforce this statement. It truly does no good at all and, speaking as a former non-speaker-of-the-native-language when I lived in Germany, I can say it's frustrating enough as it is just trying to make yourself understood in a language that's not your mother tongue, especially when you're reasonably intelligent in your own. :-) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Let us not forget that much of the newconfig work can be used with newconfig shims in the newbus scheme. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
HEADS UP!!!! Important instructions for -current users!
As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. This is a complete, from the ground up, change in the way the system boots and configures. For the most part, we've gone to a lot of trouble to make it work the way it used to, but there are some minor changes required to your kernel config file that make a BIG DIFFERENCE to what happens when you boot up. If you do not update the config file, you will not have a working keyboard! A brief summary of the changes you should make (see GENERIC!!): * apm and npx should attach to the nexus, not isa. * atkbd and psm should attach to the atkbdc, not isa. (critical!) I have bracketed the commit with PRE_NEWBUS and POST_NEWBUS tags. As a special warning: The APIC_IO interrupt management could be a little wonky on systems that require the special mptable fixups. If you have warnings about broken mptables, or additional interrupts being wired, hold back until it's been checked. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. This seems to have broken disk wiring for me. Is there some necessary change in syntax that I am not aware of? I have the following scsi related stuff in my config file.. controller ahc0 controller ncr0 controller ncr1 controller scbus0 at ahc0 controller scbus1 at ncr0 controller scbus2 at ncr1 device da0 device cd0 device pass0 diskda0 at scbus2 target 0 diskda1 at scbus2 target 1 diskda2 at scbus1 target 2 ..and when I try to build a kernel, it fails. Also, for some reason I seem to need both the ncr0 and ncr1 or config complains. These are the error messages I get: cc -c -O2 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ioconf.c ioconf.c:111: warning: `da0_count' redefined ioconf.c:100: warning: this is the location of the previous definition ioconf.c:107: redefinition of `da0_resources' ioconf.c:98: `da0_resources' previously defined here Any ideas what the problem may be? In any case, it is very nice to see new-bus being integrated. I have been awaiting loadable PCI drivers for some time. :) Great work.. Thanks, Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
Chris Csanady wrote: As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. This seems to have broken disk wiring for me. Is there some necessary change in syntax that I am not aware of? I have the following scsi related stuff in my config file.. controller ahc0 controller ncr0 controller ncr1 controller scbus0 at ahc0 controller scbus1 at ncr0 controller scbus2 at ncr1 device da0 device cd0 device pass0 diskda0 at scbus2 target 0 diskda1 at scbus2 target 1 diskda2 at scbus1 target 2 ..and when I try to build a kernel, it fails. Also, for some reason I seem to need both the ncr0 and ncr1 or config complains. These are the error messages I get: cc -c -O2 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extens ions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STA CK -include opt_global.h -elf ioconf.c ioconf.c:111: warning: `da0_count' redefined ioconf.c:100: warning: this is the location of the previous definition ioconf.c:107: redefinition of `da0_resources' ioconf.c:98: `da0_resources' previously defined here Any ideas what the problem may be? In any case, it is very nice to see new-bus being integrated. I have been awaiting loadable PCI drivers for some time. :) Err, perhaps it's because you've defined da0 twice? Great work.. Thanks, Chris Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
device da0 ..snip.. diskda0 at scbus2 target 0 Err, perhaps it's because you've defined da0 twice? Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the config file has both a da0 device (to get the generic SCSI disk code) and disk (to wire it down). -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Wiring down disks under newbus (was: HEADS UP!!!! Important instructions for -current users!)
On Friday, 16 April 1999 at 20:06:08 -0700, David O'Brien wrote: device da0 ..snip.. diskda0 at scbus2 target 0 Err, perhaps it's because you've defined da0 twice? Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the config file has both a da0 device (to get the generic SCSI disk code) and disk (to wire it down). It doesn't have to. I have only one reference in my config: device da0 at scbus1 target 0 unit 0 So what's the difference in semantics between a 'device' entry and a 'disk' entry? Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Wiring down disks under newbus (was: HEADS UP!!!! Important instructions for -current users!)
It doesn't have to. I have only one reference in my config: device da0 at scbus1 target 0 unit 0 I commented out my device da0 and changed all my disk's (16 of them across two controlers) to devices's and I was able to config and build a kernel. So the distinction between disk and device isn't what I thought it was. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
