Re: CCD and the new ATA/ATAPI subsystem?
Without getting into the ccd/vinum comparisons, is there a reason you want to use ad? and not wd? ? AFAIK, wd? works fine with Soren's new driver (well, it's working for me, at any rate). Soren's driver is alpha level, and danger with some chipset. For example, it cause file system crash with Opti Viper-M chipset. -- 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: cvs commit: src/sys/pci pcisupport.c
I replied to this in private, but, for the record, it was not a joke. Ok, I see your say. I feel inadequate metaphor and provocation form, so that message seemed vulgar joke. New-bus's goal is meaningful, but not only that one. Also newconfig is same. Difference between these is realization way. But I don't reply that message, I must become to cool. Probably other member of newconfig will reply. I keep quiet in a while. #I'm busy recently, and shocked by suddenly new-bus merge #happening (I think, its process is not fair). I was lost my head. #Also, one of stress cause is language barrier. English is hard #for me. It is my weak point. -- 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: cvs commit: src/sys/pci pcisupport.c
This is pointless. All you're doing is pointing your finger and screaming It's not right! It's not fair! without saying anything of actual value. OK OK, you are right. I have language barrier, so I can't explain well. I talk other newconfig member, one of member, Furuta-san will go to Usenix and presentation of newconfig paper. After Usenix, still misunderstanding is exist, argument again. I will become to explain if needed. -- 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: cvs commit: src/sys/pci pcisupport.c
Any chance of getting a preview of that paper? Is it, or will it be, available on the Web? I don't know, probably the paper not yet available on Web. Please ask to Furuta-san. -- 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: cvs commit: src/sys/pci pcisupport.c
You bought a computer with the super-ultra-new Microsoft (tm) Microsoft Bus (tm), for which you bought the latest and greatest device X. It is extremely vulgar joke. I doubt your character. -- 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: cvs commit: src/sys/pci pcisupport.c
On whose authority do you say that? Garrett is a core team member. I heard from Asami-san, Any voting not yet for new-bus. After that, new-bus patch merge is decided. new-bus merge is core decision, but drop static configration, ... these are not yet voted. Then explain to us why newbus is wrong and why the 4.4BSD scheme is right. Because, you are misunderstanding 4.4BSD scheme (and newconfig). -- 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: cvs commit: src/sys/pci pcisupport.c
For the sake of the thread, this got committed a day or two ago, and these hacks have been replaced with a low priority match. Why do you use another mechanism of 4.4BSD ? Don't loss time and loss inter-operability between other BSDs. -- 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: cvs commit: src/sys/pci pcisupport.c
Because 4.4BSD got it wrong. It has always been the belief of the FreeBSD Project's management that 4.4's totally-static configuration No! 4.4BSD mechanism is good. Newconfig already support dynamic configuration and *good* module support (not yet merge newconfig CVS). mechanism was unacceptable -- else we would have used it years ago. It is not formal core decision. Our policy in all areas has been that we'd rather do the Right Thing than follow the crowd. new-bus is wrong way. You are misunderstanding 4.4BSD mechanism. -- 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: cvs commit: src/sys/pci pcisupport.c
I was thinking of doing this, the same as alpm and intpm: case 0xdevid: #if NUHCI 0 return NULL; #else return VIA blah USB controller; #endif It depends on old-config, so poor mechanism. newconfig already implimented best match probe/attach. -- 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: Network problem with Laptop/Current.
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-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!
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!
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: aic (adaptec 152x) still not supported in -current?
I'd love to see the aic supported, mostly for my notebook. However, no one seems to have a confluance of time, information and talent to write the driver, or even port the other one in all its gory. If CAMed aic driver is available, SlimSCSI support is very easy. First of all, we need CAMed aic driver. -- 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: RELNOTES.TXT
As far as I know, I don't think the 2920 is supported since it's not a standard adaptec card (it was bought from another company) Old 2920, AHA-2920A is using Future Domain chip. Newer 2920, AHA-2920C? is using adaptec chip. But I don't test yet. And, 2910 is using adaptec chip, too. This card has not boot-ROM. -- 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: aic (adaptec 152x) still not supported in -current?
If you want SCSI support any time soon, I would suggest getting a supported card. An ISA Advansys card might be a good, cheap substitute for your 6360/6260 board. Adaptec SlimSCSI is major PC-Card SCSI-IF, it is based on aic6360. Now, aic not supported yet, so Note-PC user can't use any PC-Card SCSI-IF. In PAO, another PC-Card SCSI-IF supported, but these are 2.2-stable only, not yet CAMed. -- 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
