From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Non-HP PCI cards & x86 BOOT-ROMS
Date: Fri, 16 Jan 2004 11:12:19 -0500 [thread overview]
Message-ID: <20040116161219.GT5550@systemhalted> (raw)
In-Reply-To: <20040116115940.GN14285@lug-owl.de>
On Fri, Jan 16, 2004 at 12:59:40PM +0100, Jan-Benedict Glaw wrote:
> On Fri, 2004-01-16 12:55:17 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de>
> wrote in message <20040116115517.GM14285@lug-owl.de>:
> > On Fri, 2004-01-16 12:04:22 +0100, Ivar Orskaug <Ivar.Olav.Harstad.Orskaug@idi.ntnu.no>
> > wrote in message <Pine.GSO.4.58.0401161155280.15789@vier.idi.ntnu.no>:
>
> > Maybe it would be a nice idea to hack bochs to initialize those cards,
> > but that's a lot of work, though...
>
> Thinking again about that, it maybe isn't all *that* hard. Bochs already
> does know about the concept of shared DRAM and ROM BIOSes etc. Maybe
> it's really just enough to hack it's memory class (yup, it's written in
> C++) to not back the memory by RAM or on-disk storage, but to redirect
> all accesses to physical RAM.
>
> The same is to be done with I/O ports too, of course... For complex card
> (SCSI RAID host adaptors), you may need to service interrupts, too:-(
How can you use Bochs? It runs a virtualized machine. The purpose of
running card firmware is to effect the *current* machine with some
configuration process.
c.
next prev parent reply other threads:[~2004-01-16 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 11:04 [parisc-linux] Non-HP PCI cards & x86 BOOT-ROMS Ivar Orskaug
2004-01-16 11:16 ` Michael Wood
2004-01-16 11:55 ` Jan-Benedict Glaw
2004-01-16 11:59 ` Jan-Benedict Glaw
2004-01-16 16:12 ` Carlos O'Donell [this message]
2004-01-16 16:27 ` Jan-Benedict Glaw
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=20040116161219.GT5550@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=jbglaw@lug-owl.de \
--cc=parisc-linux@lists.parisc-linux.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