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@xxxxxxxxxxx> wrote:
* Felipe Balbi <me@xxxxxxxxxxxxxxx> [080521 12:37]:
On Wed, 21 May 2008 10:44:28 -0700, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
* mohammed shareef <mdshareef@xxxxxxxxx> [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@xxxxxxxxxxxxxx
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
