devfs
[Top] [All Lists]

Re: ttyS1, S2, etc...

To: devfs@xxxxxxxxxxxxxxxxx
Subject: Re: ttyS1, S2, etc...
From: tytso@xxxxxxx
Date: Sun, 19 Mar 2000 21:38:38 -0500
Cc: jurgen@xxxxxxxx, rgooch@xxxxxxxxxxxxx, devfs@xxxxxxxxxxx
In-reply-to: <ABWOsquCCS@khim.sch57.msk.ru> (devfs@khim.sch57.msk.ru)
Phone: (781) 391-3464
References: <200003170543.AAA02886@trampoline.thunk.org> <200003161751.JAA24104@nova.botz.org> <ABWOsquCCS@khim.sch57.msk.ru>
Sender: owner-devfs@xxxxxxxxxxx
   From: "Khimenko Victor" <devfs@xxxxxxxxxxxxxxxxx>
   Date: Sat, 18 Mar 2000 14:18:56 +0300 (MSK)

   All this setserial stuff is just a hack. Why you can not just use
   normal way: command-line kernel parameters and/or module parameters
   like other devices (like IDE or SCSI) are doing ? What's so special
   with serial ports anyway ?  It's onething to change settings of
   device via ioctl (number of stop-bits, speed of port, etc) and it's
   other task to specify IRQ or IO port number.  For latter most other
   drivers are using module command-lines, not magic ioctls.

Some people have as many as 32-64 dumb serial ports, and so configuring
them on the command-line can get very ugly.  Personally, if you can't
reliably autodetect devices (which is the real problem; the ISA bus is a
hack), I consider being able to configure and reconfigure devices from a
booted system to be much cleaner than boot-time only configuration via a
command-line, which to me seems to be infinitely more kludgy.  

                                                - Ted

<Prev in Thread] Current Thread [Next in Thread>