qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Michael Rolnik" <mrolnik@gmail.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Cc: Sarah Harris <S.E.Harris@kent.ac.uk>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Subject: Re: [PATCH v4 00/18] hw/avr: Introduce few Arduino boards
Date: Wed, 22 Jan 2020 10:46:40 -1000	[thread overview]
Message-ID: <dfffa872-86fb-9cac-5738-93e88d5accc8@twiddle.net> (raw)
In-Reply-To: <CAAdtpL5FdzYga1sA+nsN4+JP2QMO5NMRDtdcJ0v1prHgjxZ+QQ@mail.gmail.com>

On 1/21/20 11:23 AM, Philippe Mathieu-Daudé wrote:
>> 4. There is difference between -bios and -kernel (arduino boars crash when -bios is used, but this seems because I run avr6 on avr5 CPU). I would be happy if you explained what is the difference between these two arguments.
> 
> qemu man page is not very helpful...
> 
>        -bios file
>            Set the filename for the BIOS.
> 
>        -kernel bzImage
>            Use bzImage as kernel image. The kernel can be either a
> Linux kernel or in multiboot format.
> 
> Paolo, Peter, do you have a simple explanation?

It depends on your target board.  They *can* do very different things.

E.g. for "pc" (x86) machine, -bios sets the seabios image to use, and -kernel
loads a kernel image that seabios will invoke.

E.g. for "dp264" (alpha) machine, -bios sets the palcode image to use and
-kernel loads a kernel image.  Note that in this case, the alpha kernel relies
on palcode services, so both must be present for the system to work.

E.g. for "virt" (arm) machine, -bios loads a raw image at which the reset
vector will be pointed, whereas -kernel loads a linux kernel image and follows
the arm-linux kernel boot protocol.  In other words the images are treated very
differently.

I don't know what, if anything, an avr kernel would require from boot services.
 I suspect the two options *could* be treated identically.


r~


  reply	other threads:[~2020-01-22 20:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 22:00 [PATCH v4 00/18] hw/avr: Introduce few Arduino boards Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 01/18] MAINTAINERS: Move machine test to the machine section (not ARCH one) Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 02/18] MAINTAINERS: Move the AVR machines in new section (not within ARM) Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 03/18] tests/acceptance: Do not set the machine type manually Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 04/18] tests/acceptance: Keep multilines comment consistent with other tests Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 05/18] hw/char/avr: Reduce USART I/O size Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 06/18] hw/timer/avr_timer16: Rename memory region debugging name Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 07/18] hw/misc/avr_mask: Remove unused include Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 08/18] hw/avr/Makefile: Use CONFIG_AVR_SAMPLE variable Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 09/18] hw/char: Rename avr_usart -> atmel_usart Philippe Mathieu-Daudé
2020-01-20 22:00 ` [PATCH v4 10/18] hw/timer: Rename avr_timer16 -> atmel_timer16 Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 11/18] hw/misc: Rename avr_mask -> atmel_power Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 12/18] hw/avr: Introduce ATMEL_ATMEGA_MCU config Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 13/18] hw/avr: Add some ATmega microcontrollers Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 14/18] hw/avr: Add some Arduino boards Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 15/18] tests/boot-serial-test: Test some Arduino boards (AVR based) Philippe Mathieu-Daudé
2020-01-21  6:11   ` Thomas Huth
2020-01-20 22:01 ` [PATCH v4 16/18] tests/acceptance: Test the Arduino MEGA2560 board Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 17/18] hw/avr: Remove the unrealistic AVR 'sample' board Philippe Mathieu-Daudé
2020-01-20 22:01 ` [PATCH v4 18/18] .travis.yml: Run the AVR acceptance tests Philippe Mathieu-Daudé
2020-01-20 23:30 ` [PATCH v4 00/18] hw/avr: Introduce few Arduino boards Philippe Mathieu-Daudé
2020-01-21 19:25 ` Michael Rolnik
2020-01-21 21:23   ` Philippe Mathieu-Daudé
2020-01-22 20:46     ` Richard Henderson [this message]
2020-01-22 21:56       ` Philippe Mathieu-Daudé

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=dfffa872-86fb-9cac-5738-93e88d5accc8@twiddle.net \
    --to=rth@twiddle.net \
    --cc=S.E.Harris@kent.ac.uk \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=mrolnik@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).