Nothing like answering your own questions (no one else volunteered) :-)
Martin Costabel wrote:
> 1. My printer uses /dev/ttyS1, and when I used devfs for the first time
> with kernel 2.3.51, there was no such device. Instead of ttyS0-3 there
> was only a /dev/ttyS with major 4, minor 64. 3 days ago, I booted with a
> kernel 2.3.52, and suddenly the devices ttyS0 and ttyS1 (which
> correspond to the 2 serial ports I have) were back. Printing worked. Now
> yesterday I booted with 2.3.99-pre2, and I was back to square one: no
> ttyS1, only a ttyS. All 3 kernels used basically the same config options
> and the same kernel command line, and devfsd was started automatically
> in the same way. Where does this difference come from and how can I make
> sure that devfsd creates ttyS0 and ttyS1 as, according to README, it is
> supposed to do? Where does devfsd get its list of devices from? How does
> it decide which ones to create?
I got it working now. The problem was that I am using Macintosh serial
ports (compiled in with the MAC_SERIAL config option), and
drivers/macintosh/macserial.c was not yet devfs aware. I patched it with
some lines from drivers/char/serial.c, and I have now /dev/tts/ and
/dev/cua/ directories that were not there before. The 2.3.52 kernel
which worked also came from a different tree and apparently had a
patched version of the macserial.c file, too.
--
Martin
|