qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: blueswir1@hotmail.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch: Sparc system support
Date: Sat, 02 Oct 2004 15:07:10 +0200	[thread overview]
Message-ID: <415EA7FE.8000100@bellard.org> (raw)
In-Reply-To: <BAY12-F34PpQmWL9vVm0004081e@hotmail.com>

Blue Swirl wrote:
> Most of your changes are ok, except for the DHCP one. It's idea is to 
> respond to BOOTP clients which use no extensions added by DHCP.
> 
> The magic address-banging loader is a quick & dirty hack anyway, I'm 
> thinking of a better way to initialise Proll and implement kernel loading.

OK. So you mean I must reverse your patch in bootp.c or implement a 
correct bootp server ?

> What are you planning for env->access_type? Sparc MMU needs to know 
> whether the memory access is for data or instructions, did the access 
> come from user or kernel code and is it read or write.

rw == 2 in cpu_handle_mmu_fault() will mean 'code access'. I made the 
patch in my repository for i386 and PowerPC, but I need to test it more 
before commiting.

Fabrice.

  reply	other threads:[~2004-10-02 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-02 11:07 [Qemu-devel] Patch: Sparc system support Blue Swirl
2004-10-02 13:07 ` Fabrice Bellard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-03  7:37 Blue Swirl
2004-09-26 16:01 Blue Swirl
2004-09-30 22:23 ` Fabrice Bellard
2004-10-01 14:10   ` Renzo Davoli
2004-10-01 16:00     ` Johannes Schindelin
2004-10-01 23:06       ` J. Mayer
2004-10-02  3:50         ` Johannes Schindelin

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=415EA7FE.8000100@bellard.org \
    --to=fabrice@bellard.org \
    --cc=blueswir1@hotmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).