All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: mga_vid
Date: Tue, 23 Mar 2004 16:01:09 +0000	[thread overview]
Message-ID: <20040323160109.GC30122@kroah.com> (raw)
In-Reply-To: <20040322221440.GA16562@harfang.homelinux.org>

On Tue, Mar 23, 2004 at 02:00:18PM +0100, gilles@harfang.homelinux.org wrote:
> > > > but there is no '/dev/mga_vid'.
> > > > With udev, what would be required to set it up?
> > >
> > > The kernel driver needs to be modified to use sysfs.
> 
> Is it a lot of work?

Not really, only 3-10 lines of code need to be added to the driver.

> Is there a standard way to proceed [Like: you should find <this>
> and replace it with <that>] ?  Is it explained somewhere?

I've documented it a number of times in the linux-kernel archives.
Basically you need to add a class_simple structure, and add devices to
that structure when needed.  See the drivers/base/class_simple.c code
for information on the API, and any of the drivers that use that
interface for examples of how to use it (like drivers/char/misc.c or
drivers/char/mem.c).

Hope this helps,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-03-23 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 22:14 mga_vid gilles
2004-03-22 22:30 ` mga_vid Greg KH
2004-03-23  7:05 ` mga_vid Frédéric L. W. Meunier
2004-03-23 13:00 ` mga_vid gilles
2004-03-23 16:01 ` 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=20040323160109.GC30122@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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.