All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] serial-pci: Set prog interface field of pci config to 16550 compatible
Date: Fri, 14 Mar 2014 20:21:32 +0400	[thread overview]
Message-ID: <53232C8C.3070403@msgid.tls.msk.ru> (raw)
In-Reply-To: <alpine.LMD.2.02.1403101939400.485@jedlik.phy.bme.hu>

10.03.2014 22:40, BALATON Zoltan wrote:
> Ping!
> http://patchwork.ozlabs.org/patch/324674/
> 
> On Thu, 27 Feb 2014, BALATON Zoltan wrote:
>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>> ---
>> hw/char/serial-pci.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/char/serial-pci.c b/hw/char/serial-pci.c
>> index 991c99f..e662b77 100644
>> --- a/hw/char/serial-pci.c
>> +++ b/hw/char/serial-pci.c
>> @@ -60,6 +60,7 @@ static int serial_pci_init(PCIDevice *dev)
>>         return -1;
>>     }
>>
>> +    pci->dev.config[PCI_CLASS_PROG] = 0x02; /* 16550 compatible */
>>     pci->dev.config[PCI_INTERRUPT_PIN] = 0x01;
>>     s->irq = pci_allocate_irq(&pci->dev);

Hm. While this is an one-liner indeed, I'm not sure it's the right
value.  From my pci.ids:

C 07  Communication controller
        00  Serial controller
                00  8250
                01  16450
                02  16550
                03  16650
                04  16750
                05  16850
                06  16950

so it seems correct thing to do.

What about multi_serial_pci_init() -- should it too set prog-if
like this?

Thanks,

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] serial-pci: Set prog interface field of pci config to 16550 compatible
Date: Fri, 14 Mar 2014 20:21:32 +0400	[thread overview]
Message-ID: <53232C8C.3070403@msgid.tls.msk.ru> (raw)
In-Reply-To: <alpine.LMD.2.02.1403101939400.485@jedlik.phy.bme.hu>

10.03.2014 22:40, BALATON Zoltan wrote:
> Ping!
> http://patchwork.ozlabs.org/patch/324674/
> 
> On Thu, 27 Feb 2014, BALATON Zoltan wrote:
>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>> ---
>> hw/char/serial-pci.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/char/serial-pci.c b/hw/char/serial-pci.c
>> index 991c99f..e662b77 100644
>> --- a/hw/char/serial-pci.c
>> +++ b/hw/char/serial-pci.c
>> @@ -60,6 +60,7 @@ static int serial_pci_init(PCIDevice *dev)
>>         return -1;
>>     }
>>
>> +    pci->dev.config[PCI_CLASS_PROG] = 0x02; /* 16550 compatible */
>>     pci->dev.config[PCI_INTERRUPT_PIN] = 0x01;
>>     s->irq = pci_allocate_irq(&pci->dev);

Hm. While this is an one-liner indeed, I'm not sure it's the right
value.  From my pci.ids:

C 07  Communication controller
        00  Serial controller
                00  8250
                01  16450
                02  16550
                03  16650
                04  16750
                05  16850
                06  16950

so it seems correct thing to do.

What about multi_serial_pci_init() -- should it too set prog-if
like this?

Thanks,

/mjt

  reply	other threads:[~2014-03-14 16:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  1:05 [Qemu-devel] [PATCH] serial-pci: Set prog interface field of pci config to 16550 compatible BALATON Zoltan
2014-03-10 18:40 ` [Qemu-trivial] " BALATON Zoltan
2014-03-10 18:40   ` BALATON Zoltan
2014-03-14 16:21   ` Michael Tokarev [this message]
2014-03-14 16:21     ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-03-14 17:44     ` [Qemu-trivial] [Qemu-devel] " BALATON Zoltan
2014-03-14 17:44       ` [Qemu-devel] [Qemu-trivial] " BALATON Zoltan
2014-03-14 17:57       ` [Qemu-trivial] [Qemu-devel] " BALATON Zoltan
2014-03-14 17:57         ` [Qemu-devel] [Qemu-trivial] " BALATON Zoltan
2014-03-17 12:32         ` [Qemu-trivial] [Qemu-devel] " Gerd Hoffmann
2014-03-17 12:32           ` [Qemu-devel] [Qemu-trivial] " Gerd Hoffmann
2014-03-20  9:58           ` [Qemu-trivial] [Qemu-devel] " BALATON Zoltan
2014-03-20  9:58             ` [Qemu-devel] [Qemu-trivial] " BALATON Zoltan
2014-03-21  8:43             ` [Qemu-trivial] [Qemu-devel] " Gerd Hoffmann
2014-03-21  8:43               ` [Qemu-devel] [Qemu-trivial] " Gerd Hoffmann
2014-03-21  9:10               ` [Qemu-trivial] [Qemu-devel] " BALATON Zoltan
2014-03-21  9:10                 ` [Qemu-devel] [Qemu-trivial] " BALATON Zoltan
2014-03-20 15:42   ` [Qemu-trivial] [Qemu-devel] " Michael Tokarev
2014-03-20 15:42     ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-03-20 15:51     ` Paolo Bonzini
2014-03-20 15:51       ` [Qemu-devel] " Paolo Bonzini
2014-03-20 16:01       ` BALATON Zoltan
2014-03-20 16:01         ` [Qemu-devel] " BALATON Zoltan
2014-03-20 16:32         ` Paolo Bonzini
2014-03-20 16:32           ` [Qemu-devel] " Paolo Bonzini
2014-03-20 16:58           ` BALATON Zoltan
2014-03-20 16:58             ` [Qemu-devel] " BALATON Zoltan
2014-03-20 17:35             ` Paolo Bonzini
2014-03-20 17:35               ` [Qemu-devel] " Paolo Bonzini
2014-03-21  8:19       ` Michael Tokarev
2014-03-21  8:19         ` [Qemu-devel] " Michael Tokarev

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=53232C8C.3070403@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=balaton@eik.bme.hu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.