From: "Nobuhiro Iwamatsu" <iwamatsu@nigauri.org>
To: oihana <munoz.o@ikusi.es>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Change console to another UART
Date: Wed, 18 Jun 2008 18:43:45 +0900 [thread overview]
Message-ID: <29ab51dc0806180243h46b4373ej1e29dcf425eef994@mail.gmail.com> (raw)
In-Reply-To: <1213773664.15059.26.camel@localhost.localdomain>
Hi,
2008/6/18 oihana <munoz.o@ikusi.es>:
> Hello,
>
> I am working with a STi7109 and mb411. The STi7109 has 4 UARTs and they
> are configured by default as follow....
> - UART0 is reserved for SC0
> - UART1 is reserved for SC1
> - UART2 is reserved for console
> - UART3 is reserved for KGDB
>
> What I need is to have the Console in the UART1 because I need the UART2
> free, and I have enough with one SC (SC0).
>
> I realized that if I change on my STWorkBench the Kernel Debug
> configuration, from ttyAS0 to ttyAS1, the console comes out from the
> other serial port, but it still uses the UART2.
>
> So I tried to change the configuration in the stasc.c
> (kernel/src/drivers/serial/stasc.c).
Hmm? I could not find it.
Is this a thing peculiar to ST?
You should send an email to support of ST if so.
Best regards,
Nobuhiro
next prev parent reply other threads:[~2008-06-18 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 0:36 [2.6 patch] sh/kernel/ cleanups Adrian Bunk
2008-06-17 22:33 ` [2.6 patch] sh: make pcibios_max_latency static Adrian Bunk
2008-06-17 22:31 ` [2.6 patch] sh: make EARLY_PCI_OP's static Adrian Bunk
2008-06-17 22:30 ` [2.6 patch] sh/boards/dreamcast/rtc.c: make 2 functions static Adrian Bunk
2008-06-17 22:30 ` [2.6 patch] move arch/sh/lib/io.o to obj-y Adrian Bunk
2008-06-17 22:30 ` [2.6 patch] sh dreamcast: export board_pci_channels Adrian Bunk
2008-06-17 22:30 ` [2.6 patch] sh: export get_cpu_subtype Adrian Bunk
2008-06-18 7:21 ` Change console to another UART oihana
2008-06-18 9:43 ` Nobuhiro Iwamatsu [this message]
2008-06-24 4:03 ` [2.6 patch] sh: export get_cpu_subtype Paul Mundt
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=29ab51dc0806180243h46b4373ej1e29dcf425eef994@mail.gmail.com \
--to=iwamatsu@nigauri.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=munoz.o@ikusi.es \
/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
all inboxes | Powered by JetHome®