From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] serial: Skip over PCIe device which have no quirks (fix AMT regression).
Date: Thu, 6 Mar 2014 15:33:03 -0600 [thread overview]
Message-ID: <5318E98F.2000801@amd.com> (raw)
In-Reply-To: <201403060043.s260hr5S028392@aserz7021.oracle.com>
On 3/5/2014 6:43 PM, Konrad Rzeszutek Wilk wrote:
> On Mar 5, 2014 5:46 PM, Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com> wrote:
>> On 3/5/2014 3:09 PM, Konrad Rzeszutek Wilk wrote:
>>> This patch fixes it and allows us to use AMT again by zeroing
>>> out io_base to zero. If the scan did not work, the io_base is
>>> set back to a default value.
>> If you provide 'amt' on command line => 'skip_amt' = 0
>> Then we'd just return -1 without setting io_base to 0x3f8 due to this
>> condition-
>> if ( !skip_amt )
>> return -1;
>>
>> (or am I missing something?)
> That particular piece of code is executed after the loop. In the loop is where the AMT is found.
>>> + uart->io_base = 0;
>> Why not set ns16550.io_base = 0; in arch/x86/setup.c ?
> Because then you would break the default COM ports which are not find via PCI scanning.
>
> Say: com1=9600,8n1
>
> Which will use by default the 3f8 io base.
Ah. Okay, I see it now..
Thanks for the clarifications.
-Aravind.
next prev parent reply other threads:[~2014-03-06 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 0:43 [PATCH] serial: Skip over PCIe device which have no quirks (fix AMT regression) Konrad Rzeszutek Wilk
2014-03-06 21:33 ` Aravind Gopalakrishnan [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 19:45 Konrad Rzeszutek Wilk
2014-03-05 19:56 ` Konrad Rzeszutek Wilk
2014-03-05 21:09 ` Konrad Rzeszutek Wilk
2014-03-05 22:46 ` Aravind Gopalakrishnan
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=5318E98F.2000801@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--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).