From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Moore,
Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: RE: _OSI (Re: Re: cvs commit: src/sys/contrib/dev/acpica acfreebsd.h)
Date: Thu, 11 Mar 2004 20:00:48 -0800 (PST) [thread overview]
Message-ID: <20040311200031.J67848@root.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401CBB748-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, 11 Mar 2004, Yu, Luming wrote:
> > On Wed, 11 Mar 2004, Len Brown wrote:
> > > On Wed, 2004-03-10 at 21:26, Nate Lawson wrote:
> > > > Bob, any word on _OSI implementation?
> > >
> > > Bob sent me an initial implementation for review today;-)
> > >
> > > I'm uncomfortable, however, at claiming to be compatible
> > with Windows,
> > > since I don't really have a definition of exactly what that means...
> > >
> > > -Len
> >
> > Doesn't matter to me. I plan on claiming to be everything from Win 2k
> > onward and sort out the rest on the mailing list. :)
> >
> > We already fixed some problems by claiming to be Win 2k for _OS.
> >
>
> Cool! what kind of problems? :)
PCI routing.
-Nate
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-12 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 7:27 _OSI (Re: Re: cvs commit: src/sys/contrib/dev/acpica acfreebsd.h) Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB748-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-03-12 4:00 ` Nate Lawson [this message]
[not found] ` <20040311200031.J67848-Y6VGUYTwhu0@public.gmane.org>
2004-03-12 6:39 ` Len Brown
[not found] ` <1079073556.3868.37.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-13 8:22 ` _OSI boot hang Len Brown
[not found] ` <1079166150.2168.94.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-13 9:37 ` Len Brown
2004-03-17 22:36 ` Nate Lawson
2004-03-17 22:45 ` _OSI (Re: Re: cvs commit: src/sys/contrib/dev/acpica acfreebsd.h) Nate Lawson
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 15:40 Moore, Robert
[not found] <20040303220117.R21587@root.org>
[not found] ` <20040309110721.B88330@mail.ncircle.com>
2004-03-11 2:26 ` cvs commit: src/sys/contrib/dev/acpica acfreebsd.h Nate Lawson
[not found] ` <20040310182253.P61709-Y6VGUYTwhu0@public.gmane.org>
2004-03-11 7:08 ` _OSI (Re: Re: cvs commit: src/sys/contrib/dev/acpica acfreebsd.h) Len Brown
[not found] ` <1078988912.2549.94.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-11 7:18 ` Nate Lawson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040311200031.J67848@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox