From: Nix <nix@esperi.org.uk>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>,
a.zummo@towertech.it
Subject: Re: pktcdvd -> sysfs warning with 2.6.27
Date: Mon, 13 Oct 2008 22:28:13 +0100 [thread overview]
Message-ID: <87prm4mbgy.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20081012181700.GA21072@kroah.com> (Greg KH's message of "Sun, 12 Oct 2008 11:17:00 -0700")
On 12 Oct 2008, Greg KH uttered the following:
> Perhaps some other kernel code is registering with that same major/minor
> number, making it already present in sysfs. Where does that sysfs file
> link to before you load your driver?
Exactly so. This is probably *not* a regression after all: the only
change I made to my 2.6.27 config (weeks before actually rebooting, so I
forgot) was to build in the CMOS RTC driver, in a hopeless attempt to
make hrtimers work on this old hardware (I knew it was hopeless but
tried anyway). (Unsurprisingly it didn't work:
<http://www.ussg.iu.edu/hypermail/linux/kernel/0810.1/1033.html> worked,
thank *you* Jeff, I have glitch-free pulseaudio and microsecond sleeps
and several of my programs are happier!)
And, looky here, a smoking gun:
hades:~# ls -l /sys/dev/char/254:0 /dev/rtc*
lrwxrwxrwx 1 root root 0 2008-10-13 22:16 /sys/dev/char/254:0 -> ../../devices/platform/rtc_cmos/rtc/rtc0
hades:~# ls -l
lrwxrwxrwx 1 root root 4 2008-10-13 21:57 /dev/rtc -> rtc0
crw-r--r-- 1 root root 254, 0 2008-10-13 21:57 /dev/rtc0
hades:~# pktsetup cdrw /dev/cdrw
hades:~# ls -l /dev/pktcdvd/
total 0
brw-r----- 1 root root 254, 0 2008-10-13 22:23 cdrw
crw-r--r-- 1 root root 10, 63 2008-10-13 21:57 control
brw-rw---- 1 root cdrom 254, 0 2008-10-13 22:23 pktcdvd0
Am I right in assuming that this sort of isn't going to work? :)
Major 254 is listed as LOCAL/EXPERIMENTAL USE in devices.txt. I don't
consider either pktcdvd or the rtc drivers as LOCAL/EXPERIMENTAL: the
former in particular has been in the kernel for years.
They could do with proper device numbers. No matter what this is going
to break some non-udev setups :(
next prev parent reply other threads:[~2008-10-13 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 12:26 Nix
2008-10-12 18:17 ` Greg KH
2008-10-12 20:25 ` Nix
2008-10-12 22:18 ` Greg KH
2008-10-12 22:36 ` Nix
2008-10-13 10:27 ` Philip Martin
2008-10-13 21:28 ` Nix [this message]
2008-10-13 21:47 ` Greg KH
2008-10-13 22:01 ` Alessandro Zummo
2008-10-13 22:03 ` Nix
2008-10-14 5:27 ` Peter Osterlund
2008-10-14 8:38 ` Kay Sievers
2008-10-14 9:20 ` Kay Sievers
2008-10-14 19:53 ` Peter Osterlund
2008-10-14 22:32 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prm4mbgy.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=a.zummo@towertech.it \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®