linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev - Hot/Cold Plugging and Sparc
Date: Fri, 20 Jan 2006 00:55:36 +0000	[thread overview]
Message-ID: <20060120005535.GA2206@wonderland.linux.it> (raw)
In-Reply-To: <43D03320.6050301@jg555.com>

On Jan 20, Jim Gifford <maillist@jg555.com> wrote:

> On the x86, the rtc module gets located ok and loads, while on the sparc 
> it doesn't seem to ever find it, not sure if it's a script problem, udev 
> problem, or it's a module issue. I do know when I modprobe rtc, it shows 
It's a module issue. At least on Debian x86 systems, rtc.ko is loaded
because I manually added an alias for pnp:dPNP0b00 and IIRC sparc
systems do not have a PNP subsystem which could be used for this (maybe
sbus? Do we need some kind of OF-based coldplugging?).

But anyway, what is the point of building the rtc driver modular? Every
normal system needs it.

-- 
ciao,
Marco


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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

  reply	other threads:[~2006-01-20  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:47 Udev - Hot/Cold Plugging and Sparc Jim Gifford
2006-01-20  0:55 ` Marco d'Itri [this message]
2006-01-20  3:46 ` Andrey Borzenkov

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=20060120005535.GA2206@wonderland.linux.it \
    --to=md@linux.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).