From: Bjorn Helgaas <bhelgaas@google.com>
To: "Hornung, Michael" <mhornung@init-ka.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Kernel > 2.6.30: PCI issue causes Kernel freeze at booting
Date: Wed, 18 May 2011 07:56:04 -0600 [thread overview]
Message-ID: <BANLkTimX1KG-BZ98LH_NweOUOaUbQtZirg@mail.gmail.com> (raw)
In-Reply-To: <334319B2EBE0B144BAE1402B79D82DC5CE13B05A@srvpegasus>
On Wed, May 18, 2011 at 1:44 AM, Hornung, Michael <mhornung@init-ka.de> wrote:
>>> There is an UART (FPGA IP Core) in that system located at address 1900h using interrupt 3. In order to get Kernel messages at boot time,
>>> I changed file arch/x86/include/asm/serial.h as follows:
>>>
>>> - { 0, BASE_BAUD, 0x3F8, 4, STD_COM_FLAGS }, /* ttyS0 */ \
>>> + { 0, BASE_BAUD, 0x1900, 3, STD_COM_FLAGS }, /* ttyS0 */ \
>>>
>>> that is the only change I made to the kernel sources.
>
>> Is this UART connected via PCI? I don't think so, because I don't see
>> any I/O BARs that include 0x1900.
>
> The UART is connected via LPC bus.
Makes sense; that's a common way for attaching UARTs, and they are
normally described via ACPI. When you do that, I think it will show
up as ttyS4 (be sure you build with CONFIG_SERIAL_8250_PNP=y), so
you'll have to use "console=ttyS4" when you boot. ttyS0-ttyS3 are
taken by the hard-coded ports in serial.h, even though they may not
exist on your platform.
Bjorn
next prev parent reply other threads:[~2011-05-18 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 7:01 Kernel > 2.6.30: PCI issue causes Kernel freeze at booting Hornung, Michael
2011-05-17 14:48 ` Bjorn Helgaas
2011-05-18 7:44 ` AW: " Hornung, Michael
2011-05-18 13:56 ` Bjorn Helgaas [this message]
2011-05-23 16:29 ` Bjorn Helgaas
2011-05-25 12:28 ` AW: " Hornung, Michael
2011-05-25 15:55 ` Bjorn Helgaas
2011-05-27 6:48 ` AW: " Hornung, Michael
2011-06-01 16:36 ` Bjorn Helgaas
2011-06-09 8:48 ` AW: " Hornung, Michael
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=BANLkTimX1KG-BZ98LH_NweOUOaUbQtZirg@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mhornung@init-ka.de \
/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).