Messages in this thread | | | Date | Tue, 24 Aug 2010 14:10:16 -0700 | From | Greg KH <> | Subject | Re: [PATCH] detour TTY driver - now ttyprintk |
| |
On Tue, Aug 24, 2010 at 10:57:50PM +0200, Samo Pogacnik wrote: > On 25.06.2010 (Fri) at 12:03 +0100 Alan Cox wrote: > > With my devices.txt owner hat on I'll allocate the minor as you suggest > > (and double check this causes no problems), with my tty hat on can you > > send it to GregKH for merging into the tree. > > Hi, > > I hope that this TTY driver is ok for merging. It is very basic - > removed all flow control and rate limiting. Patch has been generated > against 2.6.34 kernel version. > > Ttyprintk is a pseudo TTY driver, which allows users to make printk messages, > via output to ttyprintk device. It is possible to store "console" messages > inline with kernel messages for better analyses of the boot process, for > example.
Why does this need to be a tty driver? Why not a misc device?
And what about the normal way of just writing to /dev/kmsg to do this? Why a whole new driver for this same functionality?
confused,
greg k-h
| |