From: andrew may <acmay@acmay.homeip.net>
To: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
Cc: "Richard Gooch" <rgooch@ras.ucalgary.ca>,
"Christian Bornträger" <linux-kernel@borntraeger.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.17pre2: devfs: devfs_mk_dir(printers): could not append to dir: dffe45c0 "", err: -17
Date: Sat, 1 Dec 2001 18:09:40 -0800 [thread overview]
Message-ID: <20011201180940.B21185@ecam.san.rr.com> (raw)
In-Reply-To: <E16A6LR-00042s-00@mrvdom02.schlund.de> <200112011808.fB1I8lq31535@vindaloo.ras.ucalgary.ca> <20011202013724.9085AFB80D@tabris.net>
In-Reply-To: <20011202013724.9085AFB80D@tabris.net>
On Sat, Dec 01, 2001 at 08:37:24PM -0500, Adam Schrotenboer wrote:
> On Saturday 01 December 2001 13:08, Richard Gooch wrote:
> > linux-kernel@borntraeger.net writes:
> <snip>
> > The new devfs core is less forgiving about these kinds of
> > bugs/misuses.
> >
> > > devfs: devfs_register(nvidiactl): could not append to parent, err: -17
> > > devfs: devfs_register(nvidia0): could not append to parent, err: -17
> > >
> > > with 2.4.16 and before the message was:
> > >
> > > devfs: devfs_register(): device already registered: "nvidia0"
> >
> > Who knows what nvidia does? Talk to them. Could be a bug in their
> > driver where they create duplicate entries (the old devfs code would
> > often let you get away with this). Or again, perhaps something in
> > user-space is creating these entries.
> >
> As of 1541 anyway (haven't tried anything newer, assuming newer exists), the
> make install of the nvidia driver also runs makedevices.sh (a vendor sp
> script that makes the devnodes. This may also have been put in the
> initscripts (mine isn't, but i tend to use the tar.gz fmt, not using the RPMs)
> Perhaps there is no check for devfs (likely will be fixed in the next
> release, as this is a new situation)
There is now a 2313 version of the driver. It has put in devfs calls, but it
seems they still call the makedefs script in the make install.
I don't know if the devfs code is correct but here it is.
from nv.c modules_init();
#ifdef CONFIG_DEVFS_FS
rc = devfs_register_chrdev(nv_major, "nvidia", &nv_fops);
#else
rc = register_chrdev(nv_major, "nvidia", &nv_fops);
#endif
if (rc < 0) {
NV_EMSG((nv_state_t *) 0, "init_module: register failed");
return rc;
}
osMemSet(nv_linux_devices, 0, sizeof(nv_linux_state_t) * NV_MAX_DEVICES);
num_devices = nvos_probe_devices();
#ifdef CONFIG_DEVFS_FS
osMemSet(nv_dev_handle, 0, sizeof(devfs_handle_t) * NV_MAX_DEVICES);
do {
char name[16];
int i;
nv_ctl_handle = devfs_register(NULL, "nvidiactl",
DEVFS_FL_DEFAULT, nv_major, 255,
S_IFCHR | S_IRUGO | S_IWUGO,
&nv_fops, NULL);
for (i = 0; i < num_devices; i++) {
snprintf(name, 16, "nvidia%d", i);
nv_dev_handle[i] = devfs_register(NULL, name,
DEVFS_FL_DEFAULT, nv_major, i,
S_IFCHR | S_IRUGO | S_IWUGO,
&nv_fops, NULL);
}
} while(0);
#endif
next prev parent reply other threads:[~2001-12-02 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 9:20 2.4.17pre2: devfs: devfs_mk_dir(printers): could not append to dir: dffe45c0 "", err: -17 Christian Bornträger
2001-12-01 18:08 ` Richard Gooch
2001-12-02 1:37 ` Adam Schrotenboer
2001-12-02 1:49 ` Richard Gooch
2001-12-02 2:09 ` andrew may [this message]
2001-12-02 18:47 ` Richard Gooch
2001-12-02 19:10 ` Christian Bornträger
2001-12-02 19:41 ` Richard Gooch
2001-12-02 19:57 ` Alan Cox
2001-12-02 20:01 ` Richard Gooch
2001-12-02 20:14 ` Alan Cox
2001-12-02 20:22 ` Richard Gooch
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=20011201180940.B21185@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=ajschrotenboer@lycosmail.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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