In message [EMAIL PROTECTED] Mike Smith writes:
: a larger issue. It is not the loader's job to detect the underlying
: hardware configuration.
:
: Actually, in a broad fashion, it _is_. This is why the loader
: understands PCI and PnP, for example.
How hard would it be to add usb
In message [EMAIL PROTECTED] Mike Smith writes:
: As far as the loader is concerned, though, neither of these are on the
: boot path, so we can typically wait until the kernel's up and we can use
: some "real real" drivers. 8)
Well, I have seen boards that support booting off pccard devices...
In message [EMAIL PROTECTED] Mike Smith writes:
: a larger issue. It is not the loader's job to detect the underlying
: hardware configuration.
:
: Actually, in a broad fashion, it _is_. This is why the loader
: understands PCI and PnP, for example.
How hard would it be to add usb and
In [EMAIL PROTECTED], Luoqi Chen wrote:
In [EMAIL PROTECTED], Luoqi Chen wrote:
It is not the loader's job to detect the underlying
hardware configuration.
I disagree. I would like to tell which machine I am booting on to
choose an appropriate kernel.
Eventually (it may take
In [EMAIL PROTECTED], Luoqi Chen wrote:
It is not the loader's job to detect the underlying
hardware configuration.
I disagree. I would like to tell which machine I am booting on to
choose an appropriate kernel.
Eventually (it may take a while) we should be able to boot any i386/AT
Given the way VMware works, I'd have nothing against making it a FICL
words, except...
...VMware is a port. For some reason, I dislike the idea of having
support targetted at exclusively one specific port. Though we have
features added specifically to deal with certain ports, they were all
a larger issue. It is not the loader's job to detect the underlying
hardware configuration.
Actually, in a broad fashion, it _is_. This is why the loader
understands PCI and PnP, for example.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn
a larger issue. It is not the loader's job to detect the underlying
hardware configuration.
Actually, in a broad fashion, it _is_. This is why the loader
understands PCI and PnP, for example.
Why do we want to do that? Are we going to offload device probe routines to
the
Mike Smith wrote:
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
I think, again, that adding an i386-specific word that detects the
presence of VMware is a perfectly sensible
Mike Smith wrote:
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
I think, again, that adding an i386-specific word that detects the
presence of VMware is a perfectly
"Daniel C. Sobral" wrote:
Mike Smith wrote:
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
I think, again, that adding an i386-specific word that detects the
presence of
Mike Smith wrote:
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
I think, again, that adding an i386-specific word that detects the
presence of VMware is a perfectly
Peter Wemm wrote:
2) Add the VMware detecting to FICL, as originally suggested.
Why make #2 vmware specific? Why not set $emulation to native,vmware,bochs,
etc. This is applicable to any platform that may have some sort of emulator.
Putting it in an environment variable has the
Mike Smith wrote:
...VMware is a port. For some reason, I dislike the idea of having
support targetted at exclusively one specific port. Though we have
features added specifically to deal with certain ports, they were all
more generic features.
It's not a port, it's a
At 10:47 AM -0700 6/11/00, Mike Smith wrote:
It's not a port, it's a platform. We probably want to add extra
words to detect other platform features, eg. i386, alpha, ia64,
etc. but that doesn't invalidate the basic idea.
For instance, I might be running the vmware program itself under
linux,
We have inb and outb. Can't vmware be written in Forth? If inl cannot be
replaced with inb, I'd rather add inl than vmware.
But we can't set registers to specific values before inb/outb, which also
means our inb/outb are quite useless in making BIOS calls.
IMHO, it would be better to add
As for setting registers ti specific values... huh? Why does this
matter? Can you explain exactly what your code does and how?
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
-lq
To
As for setting registers ti specific values... huh? Why does this
matter? Can you explain exactly what your code does and how?
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
I
Would anyone object if I add a ficl word to detect whether we're booting
from a vmware virtual machine?
Sounds good to me!
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a
Luoqi Chen wrote:
Would anyone object if I add a ficl word to detect whether we're booting
from a vmware virtual machine? I find it extremely useful when I'm running
FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
single kernel to boot both directly or inside the
On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
I'm not sure it is a good idea to name this variable VMWare as
that is implementation specific. It may be better to have a var
named 'emulation' set to 'none' or 'vmware' or 'bochs' or ...
Mmm.. or, giving forth the
extern void ficlOutb(FICL_VM *pVM);
extern void ficlInb(FICL_VM *pVM);
I'm an idiot.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net
Free yourself, free your machine, free the
Christopher Masto wrote:
On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
I'm not sure it is a good idea to name this variable VMWare as
that is implementation specific. It may be better to have a var
named 'emulation' set to 'none' or 'vmware' or 'bochs' or ...
Peter Wemm wrote:
Christopher Masto wrote:
On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
I'm not sure it is a good idea to name this variable VMWare as
that is implementation specific. It may be better to have a var
named 'emulation' set to 'none' or
Luoqi Chen wrote:
Would anyone object if I add a ficl word to detect whether we're booting
from a vmware virtual machine? I find it extremely useful when I'm running
FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
single kernel to boot both directly or inside the
25 matches
Mail list logo
