52 lines · plain
1==================2SA1100 serial port3==================4 5The SA1100 serial port had its major/minor numbers officially assigned::6 7 > Date: Sun, 24 Sep 2000 21:40:27 -07008 > From: H. Peter Anvin <hpa@transmeta.com>9 > To: Nicolas Pitre <nico@CAM.ORG>10 > Cc: Device List Maintainer <device@lanana.org>11 > Subject: Re: device12 >13 > Okay. Note that device numbers 204 and 205 are used for "low density14 > serial devices", so you will have a range of minors on those majors (the15 > tty device layer handles this just fine, so you don't have to worry about16 > doing anything special.)17 >18 > So your assignments are:19 >20 > 204 char Low-density serial ports21 > 5 = /dev/ttySA0 SA1100 builtin serial port 022 > 6 = /dev/ttySA1 SA1100 builtin serial port 123 > 7 = /dev/ttySA2 SA1100 builtin serial port 224 >25 > 205 char Low-density serial ports (alternate device)26 > 5 = /dev/cusa0 Callout device for ttySA027 > 6 = /dev/cusa1 Callout device for ttySA128 > 7 = /dev/cusa2 Callout device for ttySA229 >30 31You must create those inodes in /dev on the root filesystem used32by your SA1100-based device::33 34 mknod ttySA0 c 204 535 mknod ttySA1 c 204 636 mknod ttySA2 c 204 737 mknod cusa0 c 205 538 mknod cusa1 c 205 639 mknod cusa2 c 205 740 41In addition to the creation of the appropriate device nodes above, you42must ensure your user space applications make use of the correct device43name. The classic example is the content of the /etc/inittab file where44you might have a getty process started on ttyS0.45 46In this case:47 48- replace occurrences of ttyS0 with ttySA0, ttyS1 with ttySA1, etc.49 50- don't forget to add 'ttySA0', 'console', or the appropriate tty name51 in /etc/securetty for root to be allowed to login as well.52