From: Steve Poulsen <spoulsen@css-design.us>
To: mohammed shareef <mdshareef@gmail.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
omap <linux-omap@vger.kernel.org>,
linux-omap-open-source@linux.omap.com
Subject: Re: enabling uart2 on omap5912 osk
Date: Thu, 22 May 2008 09:14:31 -0500 [thread overview]
Message-ID: <48357FC7.6080504@css-design.us> (raw)
In-Reply-To: <a1d91fa0805211516y2651ce64u1930681831871f64@mail.gmail.com>
If you do not have a "c" as the first character in the permissions, then
your device file is not a true device file, but just a file. You should
delete that file (ttyS1) and create the device file:
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
Steve
mohammed shareef wrote:
> hi,
>
> i have changed the line in omap_osk.c to:
>
> static struct omap_uart_config osk_uart_config __initdata = {
> .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2)),
> };
>
> And all the three UARTs are enabled now as i can see in the kernel boot-log:
>
> serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
> serial8250.0: ttyS1 at MMIO 0xfffb0800 (irq = 47) is a ST16654
> serial8250.0: ttyS2 at MMIO 0xfffb9800 (irq = 15) is a ST16654
>
> A node called ttyS0 is already there which is linked to uart0.
>
> when i type:
>
> ls -l /dev/ttyS0
> crw-rw-rw- 1 root root 4, 64 Aug 8 2004
> \0x1b[1;35m/dev/ttyS0\0x1b[0m
> # ls -l /dev/ttyS1
> -rw-r--r-- 1 root root 16 May 21 2008
> \0x1b[0;0m/dev/ttyS1\0x1b[0m
>
> i have a question on the above output. the major and minor number for
> ttyS0 are 4, 64 but fot ttyS1 i dont find a major number. what does
> this indicate?
>
> thanx for all the help.
>
> regards,
> Shareef
>
>
> On Thu, May 22, 2008 at 2:18 AM, Tony Lindgren <tony@atomide.com> wrote:
>
>> * Felipe Balbi <me@felipebalbi.com> [080521 12:37]:
>>
>>> On Wed, 21 May 2008 10:44:28 -0700, Tony Lindgren <tony@atomide.com> wrote:
>>>
>>>> * mohammed shareef <mdshareef@gmail.com> [080521 10:12]:
>>>>
>>>>> i see the following lines in the omap-osk.c file regarding the uarts:
>>>>>
>>>>> static struct omap_uart_config osk_uart_config __initdata = {
>>>>> .enabled_uarts = (1 << 0),
>>>>> };
>>>>>
>>>>>
>>>>> what does it mean? i want all my uarts (1,2,3) enabled. how do i have
>>>>> to modify the above line?
>>>>>
>>>> How about try .enabled_uarts = 3
>>>>
>>> this would enable only uarts 1 and 2, right?
>>> maybe it's enough :-p
>>>
>> Oh yeh, that's true :)
>>
>> Tony
>>
>>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>
next prev parent reply other threads:[~2008-05-22 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 6:42 enabling uart2 on omap5912 osk mohammed shareef
2008-05-21 15:40 ` Tony Lindgren
2008-05-21 17:12 ` mohammed shareef
2008-05-21 17:41 ` roman.tereshonkov
2008-05-21 17:44 ` Tony Lindgren
2008-05-21 19:37 ` Felipe Balbi
2008-05-21 20:48 ` Tony Lindgren
2008-05-21 22:16 ` mohammed shareef
2008-05-21 22:21 ` Felipe Balbi
2008-05-21 22:31 ` mohammed shareef
2008-05-21 22:33 ` Felipe Balbi
2008-05-22 14:14 ` Steve Poulsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 10:27 mohammed shareef
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=48357FC7.6080504@css-design.us \
--to=spoulsen@css-design.us \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@vger.kernel.org \
--cc=mdshareef@gmail.com \
--cc=me@felipebalbi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.