qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Richard Henderson <rth@twiddle.net>
Cc: pbonzini@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] alpha-softmmu fixes
Date: Sun, 14 Jul 2013 01:05:16 -0500	[thread overview]
Message-ID: <1373781916.20031.5@driftwood> (raw)
In-Reply-To: <51DD666F.2050400@twiddle.net> (from rth@twiddle.net on Wed Jul 10 08:49:35 2013)

On 07/10/2013 08:49:35 AM, Richard Henderson wrote:
> On 07/09/2013 10:43 AM, Rob Landley wrote:
> > Do you have a kernel .config that boots on this board? I'd really  
> like to try
> > this out myself...
> 
> I haven't worked on this in quite some time.  But I've located two  
> branches
> that look like they might be the code corresponding to my image.  Try
> 
>   git://github.com/rth7680/linux.git axp-qemu-{1,2}

Do I just do 'make defconfig'? Or do I need to involve  
arch/alpha/defconfig somehow?

> The -1 branch looks newer, but the -2 branch contains more code  
> specific to
> qemu.  Both are over 2 years old, so I'm not sure what I was going  
> for...

There are now -3 and -4 branches...

Wow, -4 is current with upstream I think? Cool, I'll try that. Still no  
obvious arch/alpha/config, but I'll just try "make defconfig" and hope  
for the best...

> The most important bits are trivial to Kconfig, enabling the pci  
> virtio
> devices, as they don't require a working IOMMU.

Many moons ago (2009?) I built an alpha toolchain, userspace, and  
kernel, but couldn't boot it under qemu because there was no  
qemu-system-alpha.

what I'd like to do is build a 3.10 kernel with:

1) Serial console on qemu's stdin/stdout.
2) Block device driver of some kind (ide, scsi, virtio...)
3) network card
4) at least 256 megs memory
5) battery backed up clock

> The IOMMU was a bit of a pipe dream 2 years ago, and only in the last  
> 3-4
> months has the code enabling that actually gotten merged.  Perhaps  
> I'll find
> some time to actually write the code to emulate that now...
> 
> As for configury, choose dp264 or generic.

"clipper" seems to be default, and that's dp264...

Rob

  reply	other threads:[~2013-07-14  6:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  1:01 [Qemu-devel] [PATCH 0/4] alpha-softmmu fixes Richard Henderson
2013-07-09  1:01 ` [Qemu-devel] [PATCH 1/4] hw/alpha: Don't use get_system_io Richard Henderson
2013-07-09  1:01 ` [Qemu-devel] [PATCH 2/4] hw/alpha: Don't machine check on missing pci i/o Richard Henderson
2013-07-09  1:01 ` [Qemu-devel] [PATCH 3/4] exec: Support 64-bit operations in address_space_rw Richard Henderson
2013-07-14  6:38   ` Paolo Bonzini
2013-07-09  1:01 ` [Qemu-devel] [PATCH 4/4] hw/alpha: Drop latch_tmp hack Richard Henderson
2013-07-09 17:43 ` [Qemu-devel] [PATCH 0/4] alpha-softmmu fixes Rob Landley
2013-07-10 13:49   ` Richard Henderson
2013-07-14  6:05     ` Rob Landley [this message]
2013-07-15  1:19       ` Richard Henderson

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=1373781916.20031.5@driftwood \
    --to=rob@landley.net \
    --cc=aliguori@us.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).