0001 ==================
0002 SA1100 serial port
0003 ==================
0004
0005 The SA1100 serial port had its major/minor numbers officially assigned::
0006
0007 > Date: Sun, 24 Sep 2000 21:40:27 -0700
0008 > From: H. Peter Anvin <hpa@transmeta.com>
0009 > To: Nicolas Pitre <nico@CAM.ORG>
0010 > Cc: Device List Maintainer <device@lanana.org>
0011 > Subject: Re: device
0012 >
0013 > Okay. Note that device numbers 204 and 205 are used for "low density
0014 > serial devices", so you will have a range of minors on those majors (the
0015 > tty device layer handles this just fine, so you don't have to worry about
0016 > doing anything special.)
0017 >
0018 > So your assignments are:
0019 >
0020 > 204 char Low-density serial ports
0021 > 5 = /dev/ttySA0 SA1100 builtin serial port 0
0022 > 6 = /dev/ttySA1 SA1100 builtin serial port 1
0023 > 7 = /dev/ttySA2 SA1100 builtin serial port 2
0024 >
0025 > 205 char Low-density serial ports (alternate device)
0026 > 5 = /dev/cusa0 Callout device for ttySA0
0027 > 6 = /dev/cusa1 Callout device for ttySA1
0028 > 7 = /dev/cusa2 Callout device for ttySA2
0029 >
0030
0031 You must create those inodes in /dev on the root filesystem used
0032 by your SA1100-based device::
0033
0034 mknod ttySA0 c 204 5
0035 mknod ttySA1 c 204 6
0036 mknod ttySA2 c 204 7
0037 mknod cusa0 c 205 5
0038 mknod cusa1 c 205 6
0039 mknod cusa2 c 205 7
0040
0041 In addition to the creation of the appropriate device nodes above, you
0042 must ensure your user space applications make use of the correct device
0043 name. The classic example is the content of the /etc/inittab file where
0044 you might have a getty process started on ttyS0.
0045
0046 In this case:
0047
0048 - replace occurrences of ttyS0 with ttySA0, ttyS1 with ttySA1, etc.
0049
0050 - don't forget to add 'ttySA0', 'console', or the appropriate tty name
0051 in /etc/securetty for root to be allowed to login as well.
