qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Michael Tokarev <mjt@tls.msk.ru>
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 18:44:14 +0100 (CET)	[thread overview]
Message-ID: <alpine.LMD.2.02.1403141834500.15847@jedlik.phy.bme.hu> (raw)
In-Reply-To: <53232C8C.3070403@msgid.tls.msk.ru>

On Fri, 14 Mar 2014, Michael Tokarev wrote:
> 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?

I'm not completely sure what the correct value should be for 
multi_serial_pci_init so I've left that alone. There's also 07 02 00 that 
means multiport serial controller that might apply for that case. For the 
simple case I've sent the patch for I had a client expecting this value so 
I think it is correct for that at least but I don't know about the 
multiport case.

Regards,
BALATON Zoltan

  reply	other threads:[~2014-03-14 17:44 UTC|newest]

Thread overview: 16+ 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 ` BALATON Zoltan
2014-03-14 16:21   ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-03-14 17:44     ` BALATON Zoltan [this message]
2014-03-14 17:57       ` BALATON Zoltan
2014-03-17 12:32         ` Gerd Hoffmann
2014-03-20  9:58           ` BALATON Zoltan
2014-03-21  8:43             ` Gerd Hoffmann
2014-03-21  9:10               ` BALATON Zoltan
2014-03-20 15:42   ` Michael Tokarev
2014-03-20 15:51     ` Paolo Bonzini
2014-03-20 16:01       ` BALATON Zoltan
2014-03-20 16:32         ` Paolo Bonzini
2014-03-20 16:58           ` BALATON Zoltan
2014-03-20 17:35             ` Paolo Bonzini
2014-03-21  8:19       ` 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=alpine.LMD.2.02.1403141834500.15847@jedlik.phy.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=mjt@tls.msk.ru \
    --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 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).