From: David Brownell <david-b@pacbell.net>
To: rick@efn.org
Cc: linux-omap@vger.kernel.org, nmonson@gmail.com
Subject: Re: What happened to the serial console on BeagleBoard with 2.6.28-rc2?
Date: Sun, 2 Nov 2008 09:03:42 -0700 [thread overview]
Message-ID: <200811020803.42834.david-b@pacbell.net> (raw)
In-Reply-To: <E1KwOu8-0005NM-LE@amazonia.comcast.net>
On Saturday 01 November 2008, Rick Bronson wrote:
> @@ -155,7 +155,7 @@ static struct map_desc omap34xx_io_desc[
> .virtual = L4_PER_34XX_VIRT,
> .pfn = __phys_to_pfn(L4_PER_34XX_PHYS),
> .length = L4_PER_34XX_SIZE,
> - .type = MT_DEVICE
> + .type = MT_MEMORY_SO /* debug only */
> },
> {
> .virtual = L4_EMU_34XX_VIRT,
Leaving only one map_desc[] entry left using MT_DEVICE not MT_MEMORY_SO...
I didn't try this, since I'm currently not hooking up that serial port,
but dmesg does show(*):
Serial: 8250/16550 driver3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16650V2
console [ttyS2] enabled
Is that what you saw too?
- Dave
(*) Only the third port ("ttyS2") is physically wired of course...
the second could be, but isn't.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-02 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 22:25 What happened to the serial console on BeagleBoard with 2.6.28-rc2? Rick Bronson
2008-11-02 16:03 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-04 21:08 Rick Bronson
2008-11-04 21:26 ` Tony Lindgren
2008-11-02 18:03 Rick Bronson
2008-11-02 19:26 ` David Brownell
2008-11-02 22:07 ` Tony Lindgren
2008-10-29 16:44 Rick Bronson
2008-10-28 4:03 Nathan Monson
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=200811020803.42834.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=nmonson@gmail.com \
--cc=rick@efn.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