From: Andrew Morton <akpm@osdl.org>
To: "Jason Dravet" <dravet@hotmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
linux-parport@lists.infradead.org, device@lanana.org
Subject: Re: [RFC]: add sysfs support to parport_pc, v3
Date: Wed, 4 Jan 2006 14:31:57 -0800 [thread overview]
Message-ID: <20060104143157.357f9830.akpm@osdl.org> (raw)
In-Reply-To: <BAY103-F400667AF1AF50590C4990CDF2F0@phx.gbl>
"Jason Dravet" <dravet@hotmail.com> wrote:
>
> >From: Greg KH <greg@kroah.com>
> > > +++ /usr/src/linux-2.6.14/drivers/parport/parport_pc.c 2006-01-01
> > > 11:29:05.000000000 -0600
> >
> >Line wrapped so it can't be applied :(
> >
> > > + * Added sysfs and udev - Jason Dravet <dravet@hotmail.com>
> > > */
> >
> >Doesn't belong here, this goes in the change log.
> My mistake.
>
> > > +#include <linux/sysfs.h>
> >
> >Your email client also ate the leading spaces :(
> My email client is hotmail. I have come to realize how much hotmail sucks
> for email. It eats the leading spaces, converts tabs to spaces, and line
> wraps. I will work on getting a new mail account.
>
> > > + class_device_create(parallel_class, NULL, MKDEV(6, countports),
> > > NULL, "lp%i", countports);
> > > + class_device_create(parallel_class, NULL, MKDEV(99, countports),
> > > NULL, "parport%i", countports);
> > > + countports++;
> >
> >What does the 6 and 99 come from? Aren't these #defined in a header file
> >somewhere?
> Good question. The answer is I have no idea. I booted Fedora Core and I
> did a ls -l /dev and wrote down the specs for lp0 and parport0. lp0 looked
> like crw-rw---- root lp 6, 0 date lp0 so that is what I used. After
> reading Linux Device Drivers I found out that 6 is the major number and 0 is
> the minor number. The goal was to make sure that the nodes generated by my
> patch were the same as the nodes generated before my patch so I used those
> numbers. Should I have used different major numbers?
>
6 is OK - it's LP_MAJOR.
However 99 is JSFD_MAJOR, used by drivers/sbus/char/jsflash.c. And yet my
/dev/parport0 is also 99:0 (RH 7.3 and RH FC1). I've no idea how that came
about??
bix:/home/akpm> grep parport /etc/makedev.d/*
/etc/makedev.d/generic:a generic parport
/etc/makedev.d/linux-2.4.x:c $PRINTER 99 0 1 8 parport%d
next prev parent reply other threads:[~2006-01-04 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 15:39 Jason Dravet
2006-01-02 19:50 ` [Linux-parport] " Marko Kohtala
2006-01-04 1:08 ` Greg KH
2006-01-04 3:24 ` Jason Dravet
2006-01-04 9:14 ` Jan Engelhardt
2006-01-04 22:31 ` Andrew Morton [this message]
2006-01-05 16:17 ` Marko Kohtala
2006-01-05 21:25 ` 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=20060104143157.357f9830.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=device@lanana.org \
--cc=dravet@hotmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
/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®