From: Marko Kohtala <marko.kohtala@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jason Dravet <dravet@hotmail.com>,
greg@kroah.com, device@lanana.org, linux-kernel@vger.kernel.org,
linux-parport@lists.infradead.org
Subject: Re: [RFC]: add sysfs support to parport_pc, v3
Date: Thu, 5 Jan 2006 18:17:51 +0200 [thread overview]
Message-ID: <9cfa10eb0601050817u56b007dbj@mail.gmail.com> (raw)
In-Reply-To: <20060104143157.357f9830.akpm@osdl.org>
2006/1/5, Andrew Morton <akpm@osdl.org>:
> "Jason Dravet" <dravet@hotmail.com> wrote:
> > >From: Greg KH <greg@kroah.com>
> > > > + * Added sysfs and udev - Jason Dravet <dravet@hotmail.com>
> > > > */
>
> 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
JSFD is a block device so tha majors are ok. I'm not just sure if the
PP_MAJOR from linux/ppdev.h should be moved to major.h.
The patch by Jason however is not ok. He had another problem and this
is not the fix. What he tries to do is already in lp and ppdev, where
I think they belong.
There is also something weird: why does RedHat create these nodes in
/dev when udev already does that.
next prev parent reply other threads:[~2006-01-05 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 15:39 [RFC]: add sysfs support to parport_pc, v3 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
2006-01-05 16:17 ` Marko Kohtala [this message]
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=9cfa10eb0601050817u56b007dbj@mail.gmail.com \
--to=marko.kohtala@gmail.com \
--cc=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