From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: andrew.cooper3@citrix.com, aravind.gopalakrishnan@amd.com,
xen-devel@lists.xenproject.org, jbeulich@suse.com
Subject: [PATCH v3] Enable serial output for Oxford Semiconductor PCIe cards and fix bugs.
Date: Mon, 10 Mar 2014 15:35:25 -0400 [thread overview]
Message-ID: <1394480131-8083-1-git-send-email-konrad.wilk@oracle.com> (raw)
Since v1 [http://mid.gmane.org/1394040334-16278-1-git-send-email-konrad.wilk@oracle.com]:
- Update it per Jan and Andrew comments
- Tackle on two bug-fixes.
v2: [http://mid.gmane.org/1394218904-21535-1-git-send-email-konrad.wilk@oracle.com]:
- Squash two patches in,
- Add appropiate tags,
- Rework bug-fixes per Jan's recommendations.
Hey,
This is the third posting of the changes to the ns16550 driver
to also support other chipsets - like the Oxford 16C950 one - popular on
the inexpensive Rosewill RC-300E.
There are also two bug-fixes that I discovered while testing my code.
One of them was found through code inspection while the other was
when I was testing my code. Aravind graciously had tested the patches -
so I affixed Tested-by on the patches that did not have much (or any)
code churn since v2 posting.
Of interest is:
[PATCH 3/6] serial: Support OXPCIe952 aka Oxford Semiconductor Ltd
that enables the functionality on the PCIe card I have - while the rest
of the patches flesh out the code to support more of PCI and PCIe type cards.
xen/arch/x86/oprofile/op_model_athlon.c | 4 +-
xen/arch/x86/x86_64/mmconf-fam10h.c | 1 +
xen/arch/x86/x86_64/mmconfig-shared.c | 1 +
xen/arch/x86/x86_64/mmconfig.h | 4 -
xen/drivers/char/ns16550.c | 255 ++++++++++++++++++++++++++++---
xen/include/xen/pci_ids.h | 9 +
6 files changed, 249 insertions(+), 25 deletions(-)
Konrad Rzeszutek Wilk (6):
serial: Skip over PCIe device which have no quirks (fix AMT regression).
serial: Fix COM1 assumption if pci_uart_config did not find the AMT card.
serial: Support OXPCIe952 aka Oxford Semiconductor Ltd Device c138 (1415:c138)
serial: Seperate the PCI device ids and parameters (v1)
pci: Use #defines for PCI vendors.
serial: Expand the PCI serial quirks for OXPCIe200 and OXPCIe952 1 Native UART
next reply other threads:[~2014-03-10 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 19:35 Konrad Rzeszutek Wilk [this message]
2014-03-10 19:35 ` [PATCH 1/6] serial: Skip over PCIe device which have no quirks (fix AMT regression) Konrad Rzeszutek Wilk
2014-03-10 19:35 ` [PATCH 2/6] serial: Fix COM1 assumption if pci_uart_config did not find the AMT card Konrad Rzeszutek Wilk
2014-03-10 19:35 ` [PATCH 3/6] serial: Support OXPCIe952 aka Oxford Semiconductor Ltd Device c138 (1415:c138) Konrad Rzeszutek Wilk
2014-03-10 19:35 ` [PATCH 4/6] serial: Seperate the PCI device ids and parameters (v1) Konrad Rzeszutek Wilk
2014-03-10 19:35 ` [PATCH 5/6] pci: Use #defines for PCI vendors Konrad Rzeszutek Wilk
2014-03-11 8:35 ` Jan Beulich
2014-03-11 15:15 ` Konrad Rzeszutek Wilk
2014-03-11 16:00 ` Jan Beulich
2014-03-10 19:35 ` [PATCH 6/6] serial: Expand the PCI serial quirks for OXPCIe200 and OXPCIe952 1 Native UART Konrad Rzeszutek Wilk
2014-03-11 8:30 ` [PATCH v3] Enable serial output for Oxford Semiconductor PCIe cards and fix bugs Jan Beulich
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=1394480131-8083-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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).