All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/input/pckbd: The i8042 device should not be user_creatable
Date: Mon, 08 Apr 2019 08:01:13 +0200	[thread overview]
Message-ID: <87ef6djas6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <02729d68-9714-141b-b221-74ff31dca977@redhat.com> (Paolo Bonzini's message of "Fri, 5 Apr 2019 09:58:21 +0200")

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 04/04/19 22:49, Philippe Mathieu-Daudé wrote:
>> While I wonder if someone still use the r4k machine, I have more doubts
>> about users running with more the 2 -serial options...
>
> I sort of remember ISA extension cards that had jumpers or dip switches
> to choose between COM1/COM2/COM3/COM4...

They still exist, with I/O ports and IRQ lines selectable via jumpers &
DIP switches.  Traditionally:

    COM1: I/O port 0x3F8, IRQ 4
    COM2: I/O port 0x2F8, IRQ 3
    COM3: I/O port 0x3E8, IRQ 4
    COM4: I/O port 0x2E8, IRQ 3

WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/input/pckbd: The i8042 device should not be user_creatable
Date: Mon, 08 Apr 2019 08:01:13 +0200	[thread overview]
Message-ID: <87ef6djas6.fsf@dusky.pond.sub.org> (raw)
Message-ID: <20190408060113.mQNCEwpJlKgyLbUjf7stHfmkBbb2Z7UUPiCgkuUP5Ds@z> (raw)
In-Reply-To: <02729d68-9714-141b-b221-74ff31dca977@redhat.com> (Paolo Bonzini's message of "Fri, 5 Apr 2019 09:58:21 +0200")

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 04/04/19 22:49, Philippe Mathieu-Daudé wrote:
>> While I wonder if someone still use the r4k machine, I have more doubts
>> about users running with more the 2 -serial options...
>
> I sort of remember ISA extension cards that had jumpers or dip switches
> to choose between COM1/COM2/COM3/COM4...

They still exist, with I/O ports and IRQ lines selectable via jumpers &
DIP switches.  Traditionally:

    COM1: I/O port 0x3F8, IRQ 4
    COM2: I/O port 0x2F8, IRQ 3
    COM3: I/O port 0x3E8, IRQ 4
    COM4: I/O port 0x2E8, IRQ 3


  reply	other threads:[~2019-04-08  6:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  7:14 [Qemu-devel] [PATCH] hw/input/pckbd: The i8042 device should not be user_creatable Thomas Huth
2019-04-04 10:07 ` Paolo Bonzini
2019-04-04 13:29   ` Philippe Mathieu-Daudé
2019-04-04 14:19     ` Thomas Huth
2019-04-04 16:30       ` Markus Armbruster
2019-04-05 10:57         ` Thomas Huth
2019-04-05 10:57           ` Thomas Huth
2019-04-08  6:29           ` Markus Armbruster
2019-04-04 16:40       ` Philippe Mathieu-Daudé
2019-04-04 20:49         ` Philippe Mathieu-Daudé
2019-04-05  7:58           ` Paolo Bonzini
2019-04-08  6:01             ` Markus Armbruster [this message]
2019-04-08  6:01               ` Markus Armbruster

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=87ef6djas6.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.