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
ess 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
> 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
> 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
r, 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
n 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 "u
> 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.
--
NAK
> 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
> I was thinking of doing this, the same as alpm and intpm:
>
> case 0x:
> #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
> 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.o
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
> 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...
f 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
#x27;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-curr
aptec 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
15 matches
Mail list logo
