> Great! This is really great!! I didn't think we can have ACPICA
> kernel so earlier.
Well, let's see if it works right first. 8) I hear from Intel that they
plan to release a new code revision today, so I will be updating when
they do. I also hear that Andrew Grover (the chap at Intel that's been
answering my mails) has just joined acpi-jp (G'day!).
> > Comments and suggestions would definitely be appreciated.
> > http://people.freebsd.org/~msmith/acpica-bsd-20001002.tar.gz
> OK, I have a patch for AcpiOsSleep and AcpiOsSleepUsec which I was
> involed in recently.
Thanks, I've incorporated it.
> For Semaphore, mtx_* (ported from BSD/OS?) is used in your implementation.
> I just wonder if NetBSD people will use traditional lock...
I guess that depends on how they decide to thread their kernel. Right
now, the code can be built entirely unthreaded and that might be their
best option. At some point, they'll have to bite the bullet and
implement some synchronisation primitives of their own. If they have any
common sense, they'll use the BSD/OS model as we have (or some variant on
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message