From: Tony Lindgren <tony@atomide.com>
To: 林小玫 <subsun.ece94g@nctu.edu.tw>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: A problem about the uart3 of OMAP osk5912
Date: Fri, 17 Feb 2006 13:08:25 -0800 [thread overview]
Message-ID: <20060217210824.GB771@atomide.com> (raw)
In-Reply-To: <20060217163457.9B78586CF0@mailreg.nctu.edu.tw>
* 林小玫 <subsun.ece94g@nctu.edu.tw> [060217 00:29]:
> Hi there,
>
> I have a problem about the uart3 of OMAP osk5912. The fact is that osk5912
> don't have a second substantial uart port. We tried to send a echo signal to
> /dev/ttyS02(which is a character device node with the major number 4 and
> minor number 65 we made), but there was no voltage change on the TX of
> uart3. Can you tell me how to control the second uart of osk5912 under OS?
> Further more, can you tell me how to use the USB serial converter? We were
> using the GMUS-03 with chipset prolific, although the required convert is
> Elecom's US-SGT.
If you solder a second UART to osk, you also have to init the additional
internal port. See board-osk.c for that. USB serial port should show up
as /dev/ttyUSB0.
Tony
prev parent reply other threads:[~2006-02-17 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 8:27 A problem about the uart3 of OMAP osk5912 林小玫
2006-02-17 21:08 ` Tony Lindgren [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=20060217210824.GB771@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=subsun.ece94g@nctu.edu.tw \
/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