From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Muhammad Waseem <vasim98@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Fwd: UART #1 access on Sequoia board
Date: Mon, 23 May 2011 16:42:08 -0400 [thread overview]
Message-ID: <20110523204208.GA28540@zod.rchland.ibm.com> (raw)
In-Reply-To: <BANLkTikvmy-bkckgxyQttoKQqkuNUd2+5g@mail.gmail.com>
On Tue, May 24, 2011 at 12:22:14AM +0500, Muhammad Waseem wrote:
Please don't top post.
>I am using kernel version 2.6.23 which came with the Sequoia support CD. So
>that means UART # 1 BSP would probably not there? But device file
>/dev/ttyS1 is present in rootfs when listed using 'ls'. Do you think
>updating the kernel might solve the problem?
Not necessarily. You can create device nodes on the rootfs without
anything being bound to them. One of the easiest ways to see if
something discovered the serial port is to look in the boot output. You
should see something like:
serial8250.0: ttyS0 at MMIO 0x1ef600300 (irq = 17) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x1ef600400 (irq = 18) is a 16550A
serial8250.0: ttyS2 at MMIO 0x1ef600500 (irq = 19) is a 16550A
serial8250.0: ttyS3 at MMIO 0x1ef600600 (irq = 20) is a 16550A
or:
1ef600300.serial: ttyS0 at MMIO 0x1ef600300 (irq = 17) is a 16550
1ef600400.serial: ttyS1 at MMIO 0x1ef600400 (irq = 18) is a 16550
1ef600500.serial: ttyS2 at MMIO 0x1ef600500 (irq = 19) is a 16550
1ef600600.serial: ttyS3 at MMIO 0x1ef600600 (irq = 20) is a 16550
>BTW where can I see the board's DTS file?
arch/powerpc/boot/dts/sequoia.dts
josh
prev parent reply other threads:[~2011-05-23 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 6:34 UART #1 access on Sequoia board Muhammad Waseem
2011-05-23 12:40 ` Josh Boyer
[not found] ` <BANLkTin5TyfdfNDfXokDdtdpDmnoRQ6aAA@mail.gmail.com>
2011-05-23 19:22 ` Fwd: " Muhammad Waseem
2011-05-23 20:42 ` Josh Boyer [this message]
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=20110523204208.GA28540@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vasim98@gmail.com \
/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).