All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: device model and character devices
Date: Wed, 5 Apr 2006 11:31:54 -0700	[thread overview]
Message-ID: <20060405183154.GB2466@kroah.com> (raw)
In-Reply-To: <44337759.4040507@yandex.ru>

On Wed, Apr 05, 2006 at 11:52:57AM +0400, Artem B. Bityutskiy wrote:
> Greg KH wrote:
> >Because "struct device" generally is not related to a major:minor pair
> >at all.  That is what a struct class_device is for.  Lots of struct
> >device users have nothing to do with a char device, and some have
> >multiple char devices associated with a single struct device.
> Well, OK, but AFAIK, your long-term plan is to merge class_device and 
> device, so in the long-term perspective it does not matter. And those 
> who do not need a character device support may have a possibility to 
> disable it.

Yes, that's my goal in the long term, and I have a patch availble that
starts to do that:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/device-class.patch

but we have a lot of work to get there.

And even then, a struct device will be separate from a char device.  For
one example, the cdev structure is used by the kernel to look up the
device properly, which has nothing to do with struct device (or struct
class_device) at all at this time.

thanks,

greg k-h

      reply	other threads:[~2006-04-05 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  8:12 device model and character devices Artem B. Bityutskiy
2006-04-04 16:48 ` Greg KH
2006-04-05  7:52   ` Artem B. Bityutskiy
2006-04-05 18:31     ` Greg KH [this message]

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=20060405183154.GB2466@kroah.com \
    --to=greg@kroah.com \
    --cc=dedekind@yandex.ru \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.