[lkml]   [2000]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode
Richard Gooch wrote:
> > create_proc_read_entry ("driver/rtc", 0, 0, rtc_read_proc, NULL);
> >
> > in addition to the binary-data device /dev/rtc (which is in
> > /dev/misc/rtc of devfs). The /proc/driver/rtc is the human-readable
> > dump of RTC data and I thought it should find its proper place in
> > devfs instead of /proc for the same reasons why we moved microcode
> > from /proc/driver to /dev/cpu.
> Yep, it should just be in devfs.

Devfs _is not_ the place for generic, driver-specific text output to

The RTC data dump is in /proc and is not a /dev device for a reason...


Jeff Garzik |
Building 1024 | Viva la open source!
MandrakeSoft, Inc. |

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.177 / U:1.588 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site